Hi Andreas, I believe I have this issue sorted. This is due to multiplexing of endpoints and clients in TransportTestSuiteBuilder. The message is in fact correct. However, the approach still is questionable.
Regards, Senaka On Mon, Oct 27, 2008 at 1:17 AM, Andreas Veithen <[EMAIL PROTECTED]>wrote: > Senaka, > > There are test cases for SOAP 1.1, SOAP 1.2 and POX. As far as I can > see, the tests for POX produce exactly the kind of message (<root>test > string</root>) you expect. Which is the test case where you see an > incorrect message? > > Andreas > > On Thu, Oct 23, 2008 at 15:02, Senaka Fernando <[EMAIL PROTECTED]> > wrote: > > Hi all, > > > > It seems that according to the way in which the JMS message tests are > > structured, the actual JMS Messages exchanged contain the message content > > (payload) in the format: > > > > <soapenv:Envelope > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ > "><soapenv:Body><root>test > > string</root></soapenv:Body></soapenv:Envelope> > > > > instead of, > > > > <root>test string</root> > > > > Is there any special reason for this? > > > > Also, can you point me to the exact location that does this appending of > the > > SOAP envelope? > > > > Thanks, > > Senaka > > >
