All messages sent in the JBI bus should conform with the *abstract* WSDL description. This also means that all JBI exchanges should have a valid Operation name set and that the xml content should conform to the xml schema element referenced by this particular operation.
Note that SOAP protocol should not be sent inside the JBI bus, but rather handled by the BC. Makes sense ? On 11/5/06, BrendenBain <[EMAIL PROTECTED]> wrote:
Hello, I have a generic question about JBI. The specification says that each service should document the service it provides using a WSDL 2.0 document. However, the specification and documentation is a little scant on exactly what should be sent in the Normalized message. What exactly are we meant to be sending in the Normalized message? Are we meant to be honouring the binding from the WSDL document and embed our requests within SOAP documents? If not then what are we meant to send? I'm not asking what can be done more what should be done. Consider a simple application that takes a JMS message from a Queue and is meant to execute a command. We can use a JMS BC to read the message and another Exector BC to run the command. The Exector BC has a simple WSDL 2.0 interface with a single operation that takes the name of the command and executes it. What would be the message sent between the JMS BC and the Exector BC? Thanks, Brenden. -- View this message in context: http://www.nabble.com/WDSL-2.0-tf2579240s12049.html#a7190208 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
