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.-tf3787849s12049.html#a10752686
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to