bsnyder wrote: > > Yes, and that's all going to work just fine. However, you started this > discussion by saying you weren't able to access the WSDL and I > explained why. >
I guess the part that I don't understand is that a query for the WSDL from "wsdl-first" example (after removing the WSDL from the zip) still returns a WSDL generated by the JSR181 component. However, my hello project fails to retrieve a WSDL. With the SA deployed, an HTTP request for the "wsdl-first" example's WSDL (http://localhost:8192/PersonService/main.wsdl) logs the following (after the Jetty logs HTTP request): DEBUG - HttpComponent - Retrieving proxied endpoint definition DEBUG - Jsr181Component - Querying service description for ServiceEndpoint[service={http://servicemix.apache.org/samples/wsdl-first}PersonService,endpoint=PersonServiceJBIPort] DEBUG - HttpComponent - WSDL only defines a PortType, using this one The last line might indicate that the automatically generated WSDL for this SA also does not contain a wsdl:port name (maybe?) Anyway, the part of this that stands out to me is the second line, where endpoint=PersonServiceJBIPort. I've grepped for "PersonServiceJBIPort" but did not find it in any source file (neither Java nor the XML files.) A similar request for my "hello" project's WSDL fails: DEBUG - HttpComponent - Retrieving proxied endpoint definition DEBUG - HttpComponent - Could not retrieve endpoint for targetService DEBUG - HttpComponent - Could not retrieve endpoint for service/endpoint I'm trying to understand what I've (accidentally) done differently that causes the endpoint not to be found. Generating a static WSDL may be the correct approach in the long run, but right now I'd like to understand why a WSDL is generated in one case yet not in the other. -- View this message in context: http://www.nabble.com/Where%27s-my-WSDL--tp15460599s12049p15471600.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
