You need to define the targetService attribute on the http endpoint (and not use the activationSpec) and ensure an endpoint with the same service name has been activated. If not specified, it defaults to the service attribute value.
On 12/6/06, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
L.S, After mailing to this list yesterday, I've ran into trouble once again... With some help from Guillaume, I got a WSDL-based HTTP endpoint up and running. When trying to use the web service, I got errors indicating that I was missing a destination for the XML message to be sent to. After looking through the documentation, I found out that <http:endpoint/> doesn't have a destinationService attribute, but <sm:activationSpec/> does. Luckily, on http://servicemix.goopen.org/site/servicemix-http.html, there is a section which shows how to wrap the <http:endpoint/> in an <sm:activationSpec/>. Only, when I redeploy my application, I get an exception stating that there are 'No endpoints found'. I'm completely puzzled... probably missing the point in ServiceMix completely. What I'm trying to do: I have a WSDL from an external partner, who will use this interface to send orders to our system. I want to receive the XML contents of the SOAP request and send it to a backoffice machine using FTP. Alternatively, if I could get the message contents in a Java class, I could use the backoffice system's API to write the XML file directly to disk. Either solution would do fine... Regards, Gert Vanthienen
-- Cheers, Guillaume Nodet
