L.S.,
OK, I guess the HTTP 404 is not from the actual SOAP request then, but rather from SoapUI trying to get to the WSDL for the HTTP/SOAP endpoint. The default behavior for the HTTP endpoint when you ask for a WSDL is to look at the target endpoint's WSDL if nothing has been explicitly configured on the http:endpoint itself. Now, if you connect the http:endpoint directly to the JSR-181 endpoint, looking up the abstract WSDL from the JSR-181 works fine and you get the WSDL back in SoapUI. When you put the Camel endpoint in between, the HTTP endpoint does the lookup on the Camel endpoint instead but that one does not expose a WSDL which results in the HTTP 404 (not found) status. Unfortunately, the Camel endpoint does now allow adding a WSDL to it nor can it somehow figure out what the target endpoint is to look up the WSDL, so the only solution that's left is to explicitly configure the WSDL on the http:endpoint itself. You can do that by adding the wsdlResource attribute (e.g. wsdlResource="classpath:mywsdl.wsdl" if you add the WSDL document to the SU itself) Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Wed, Oct 26, 2011 at 12:55 PM, Nico <[email protected]> wrote: > Hi Gert, thanks for your reply. > > The definition of the namespace look like this: > > xmlns:example="http://example.com";, > > so I think it's correct. > > The jsr181 endpoint works just fine if I connect it directly to the Http > Component. In fact, I can get the WSDL and make some calls using SOAPUI. > > What I think the problem really is, is on the Htpp Component <-> Camel > comunication. If I try this configuration on the Camel Context xml file > description: > > <camelContext id="camel" trace="true" > xmlns="http://activemq.apache.org/camel/schema/spring";> > <endpoint id="camelByPass" > uri="jbi:endpoint:http://example.com/camelReceiver/camelReceiverEndoint"; > /> > > <route> > <from ref="camelByPass" /> > <to uri="log:INPUT" /> > </route> > > </camelContext> > > nothing its printed on the "INPUT" log. > > What am i doing wrong? > >
