I got this working. It turns out that the problem was some whitespace in the EPR that was causing the message to not route properly. I entered this bug as SM-1835.
It's also necessary to tack on some query params to the wsa:Address to signal to the HttpComponent that the message should be sent as soap. For example: <wsa:EndpointReference> <wsa:Address>http://example.com/services/MyService?http.soap=true&http.soapVersion=1.1</wsa:Address> </wsa:EndpointReference> On 3/30/09 2:56 PM, "Ford, Mark" <[email protected]> wrote: How do people handle invoking SOAP/HTTP services when the address of the service isn't known until runtime? If I know the address at deployment time then I can create a service unit for servicemix-http with the appropriate endpoints configured. However, I won't know the address at deployment time, just the interfaces. I've tried manipulating the wsa:EndpointReference for my BPEL process at runtime to specify the correct wsa:Address but the only way I can get this to work is if I invoke previously configured endpoints using the jbi:end-point-reference element to target the service endpoint.
