Owen,
In that case, you should add a service/endpoint attribute on your
JSR-181 endpoint tag. The reason why the example on the logicblaze
website isn't doing so, is because they are using a WSDL file that
specifies this information. Your HTTP consumer endpoint should refer to
the same name as well to get things working.
Regards,
Gert
Owen Thomas wrote:
Hi Gert
I created my JSR-181 SU class-first, so therefore, have not defined a
WSDL.
Owen.
-----Original Message-----
From: Gert Vanthienen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 3:27 PM
To: [email protected]
Subject: Re: Confusion over documentation referring to the "Creating the
HTTPConsumer Service Unit".
Owen,
If I'm not mistaking, the service name is specified in the service.wsdl
file that is referenced from the JSR-181 endpoint tag.
Regards,
Gert
Owen Thomas wrote:
Hello.
This documentation:
http://devzone.logicblaze.com/site/providing-and-consuming-web-services-
using-logicblaze-fuse.html apparently tells me how to create a JSR-181
SU and bind it to an HTTP BC in the JBI bus so that I can use it from
outside servicemix.
In constructing the "HTTP Consumer", it refers, in the following
code...
<beans xmlns:http="http://servicemix.apache.org/http/1.0";
xmlns:servicemix="http://www.servicemix.org";>
<http:endpoint service="servicemix:TextWeatherService"
endpoint="soap"
role="consumer"
locationURI="http://localhost:8192/example/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
</beans>
... to the service name (I assume this is the value
"servicemix:TextWeatherService") that "must refer to another service
that exists in the JBI container. In our case, this will match the
name
of the JSR181 service unit". However, in the xbean.xml file for the
JSR-181 SU, I can't see any such text".
What is wrong with my understanding?
Owen.
