Hello All, 

First we wish our community a very happy new year and hope that it will grow
and be prosperous. 

Following our previous message "using Database binding in CASA editor", we
note that WSDL validations differ whether you define a SOAP binding in a
concrete WSDL in your project or an abstract WSDL in your project then add a
SOAP binding in the Composite Application WSDL. 

As I understood, the WS-I basic profile impose (Rule R2203/4) to use type
for message part in a RPC SOAP binding and element for document SOAP
binding. 

Open-ESB checks this rules when we create a concrete WSDL. 

Now as explain in our previous message at Pymma we are used to create
abstract WSDL first then we add concrete binding during the composite
definition step. Unfortunately, in that case, no validations are made.
Worse, we observe strange behaviour we suppose implementation dependant. 

We defined 4 very simple "Hello + name" abstract WSDL and added SOAP binding
in the composite application. The only differences between the 4 abstract
wsdl were the value of "element Or type". (I put in attachment the 4
projects in a rar file). 
http://www.nabble.com/file/p21333266/NB%2BProjects.rar NB+Projects.rar 

So we get the following results : 

Case 1 : Input part =Type          Output part = Type       result = OK 
Case 2 : Input part = Element     Output part = Type       result = KO
Case 3 : Input part = Type         Output part = Element   result = OK 
Case 4 : Input part = Element     Output part = Element   result = OK 

The first case can be view as a RPC SOAP
The fourth case can be view as a Document SOAP

We understand that the second case does not work, but we get no validation
and worse no error message event in the finest logging

We don't understand why the third message works even if this wsdl
configuration is not compatible with the WS-I rules. 

Is it an implementation decision ? If it is the case, the compatibility with
other implementation can make problems. 

Thanks for your reply 

Paul Perez 
www.pymma.com