On Feb 13, 2008 5:43 PM, nate roe <[EMAIL PROTECTED]> wrote: > > > 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.
Because the WSDL in the wsdl-first example is static. It's not dynamically generated by ServiceMix. > 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.) That's the thing - the WSDL is *not* automatically generated, it's static. See the WSDL here the following directory: wsdl-first/wsdl-first-jsr181-su/src/main/resources/person.wsdl > 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. This is because you have not provided a WSDL file. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache Camel - http://activemq.org/camel/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Blog: http://bruceblog.org/
