You can check the SM-1721 in which I have provided a patch on the HTTP component to be able to proxy WSDL of the underlying component.
Else, you need to define the WSDL (which is not very efficient). Regards JB -- Jean-Baptiste Onofré [email protected] BuildProcess/AutoDeploy Project Leader http://buildprocess.sourceforge.net On Mon 22/12/08 15:20, KenBarnesJr [email protected] wrote: > > I have a http-consumer that looks like > > <beans xmlns:http="http://servicemix.apache.org/http/1.0"; xmlns:jsr="urn:barnes:jsr"> > > > <http:endpoint service="jsr:TestService" > endpoint="myProvider" > role="consumer" > targetEndpoint="jsr:TestServiceJBIPort" > locationURI="http://0.0.0.0:8192/TestService/"; defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; soap="true" > /> > </beans> > > and a jsr-181 bean > > <beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"; xmlns:jsr="urn:barnes:jsr"> > > <jsr181:endpoint endpoint="testEndPoint" > pojoClass="barnes.jsr.TestService"/> > > </beans> > > with an annotated web service > > @WebService(name = "TestService", targetNamespace = "urn:barnes:jsr") > public class TestService { > > @WebMethod > public String sayHello(String name) { > return "Hello "+name; > } > } > > In my jconsole i get endpoints that are > {urn_barnes_jsr}TestServicemyProvider > {urn_barnes_jsr}TestServicetestEndPoint > > but when i go to http://localhost:8192/TestService I get unable to > find requested resource > RequestURI=/TestService/main.wsdl > > In the wsdl-first example I see there is a wsdl file in the project that > I dont have. Shouldnt the jsr-bean auto generate the wsdl and allow me > to point at it using targetService or targetEndpoint and why is it looking > for main.wsdl. Thanks for any help. > > > > > > > > > > > > -- > View this message in context: http://www.nabble.com/jsr181-auto-generation-tp21128607p2112860 > 7.html Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > >
