On Thursday, April 28, 2011 11:19:12 AM Harshal wrote: > Can you please let me know what is JMS-spec URL i.e. an y format/ > example like(http://servername:port/applicationname)
In the distribution, there is an samples/jms-spec-demo that shows how you can configure the JMS stuff in the wsdl as well as via the URL. There is also the "java-first-jms" sample that can show how to do all the jms stuff without the wsdl. There is information about the JMS url schema at: http://cxf.apache.org/docs/soap-over-jms-10-support.html Dan > > Really need this. to invoke web method. > > Thnaks. > > On 2011-04-28 02:12, Daniel Kulp wrote: > > The HTTP servlet only displays the endpoints/wsdl's for the those that > > are exposed via that servlet. Thus, the JMS endpoints wouldn't be > > there. > > > > There was a small discussion about changing the service list to use the > > Bus level ServiceRegistry instead of the list registered on the HTTP > > transport, but no work went into that. However, that still wouldn't > > provide the WSDL, just the qname and URL of the service. With 2.4.0, > > the wsdl is provided by an interceptor on the chain and that would just > > be triggered off the JMS endpoint directly. I know the JMS transport > > can be used for some "REST LIKE" things so it likely would require > > little work to get it so you could use a JMS-Spec URL to obtain the wsdl > > by just adding the ?wsdl flag to it. If you'd like to pursue that > > option as well, I be happy to provide pointers. :-) > > > > > > > > Dan > > > > On Wednesday, April 27, 2011 5:01:47 AM more.harshal2...@gmail.com wrote: > >> Hi All, > >> I am newbie for CXF web service. > >> > >> I have sample hello web service which is developed using CXF and > >> successfully able to get WSDL using for HTTP/Soap transport. > >> > >> But when I am doing modification to JMS transport it is no giving any > >> WSDL to generate client. > >> showing No services have been found. message when adding > >> transportId="http://cxf.apache.org/transports/jms"; in end point > >> configuration. > >> > >> > >> Need help to resolve this issue. > >> > >> -- > >> View this message in context: > >> http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId > >> -h ttp-cxf-apache-org-transports-jms-tp4343106p4343106.html Sent from > >> the cxf-dev mailing list archive at Nabble.com. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com
