I was using the soap address from the wsdl's service as the endpoint for
my invocation which lacks that trailing '/'. I noticed the hello world
example process also suffers from the same fate, using the service
address results in a http 302 response, is this a problem service mix is
causing?
Alex Boisvert wrote:
I couldn't spot the issue from a quick inspection of your service
assembly...
Do you know if the process is started? Do you get any errors or clues in
the logs?
alex
On Fri, Jan 23, 2009 at 7:52 AM, Bill McCusker <[email protected]>wrote:
Hi,
I have an ODE bpel process that works when I deploy it to tomcat for both
1.X and trunk builds. However this same process does not work in service for
both 1.X and trunk. The service assembly deploys without error but when I
send a SOAP message to the process all I get back is an http 302 status
header when I should get a response message back. I am using servicemix 3.3.
Any idea what might be wrong? Attached is the service assembly for the
process.
Bill McCusker
