Hi there. Thanks for the advice, but I only now just discovered that all I had to do was rebuild my HTTP BC as well as the JSR-181 SE which I had changed, and the SA to get it to return the response.
I was rebuilding the SE and SA only. I had mistakenly thought that the BC, because I had changed nothing in it, didn't need rebuilding. Owen. -----Original Message----- From: ib22841 [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 7:12 AM To: [email protected] Subject: RE: Deploying JSR-181 SU with predefined schemas. Hi, I've seen the same behavior in a case I missed the last / in endpoint url in soapUI. In such a case I get a HTTP 302 error - try to switch in 'http headers' tab of soapUI' response window to see this. So make sure the url is exactly the same as described in wsdl. Look at http://www.nabble.com/Error-in-http-transaction-t3790045s12049.html Owen Thomas wrote: > > Hi again Bruce. > > After making the changes you state below, I can now see one line appear > on the server console output: > > DEBUG - JettyContextManager - Dispatching job: > [EMAIL PROTECTED],io=0,w=true,b=0|0] > > Might you know what it means? Anything pertinent? > > Owen. > > -- View this message in context: http://www.nabble.com/Deploying-JSR-181-SU-with-predefined-schemas.-tf37 87849s12049.html#a10752686 Sent from the ServiceMix - User mailing list archive at Nabble.com.
