You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by "more.harshal2007@gmail.com" <ha...@itshastra.com> on 2011/04/27 11:01:47 UTC
NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
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-http-cxf-apache-org-transports-jms-tp4343106p4343106.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
I have just finished the example.
See:
http://svn.apache.org/repos/asf/cxf/trunk/distribution/src/main/release/samples/jms_spring_config/
Christian
Am 28.04.2011 17:07, schrieb Christian Schneider:
> Sadly there currently is no demo project in the distribution. I will
> add one and commit it to trunk.
> I used the jms config feature a lot where I worked before but I do not
> have access to that code. So I will write a new demo that is very
> similar to the wsdl-first demo.
>
> Christian
>
>
> Am 28.04.2011 16:28, schrieb more.harshal2007@gmail.com:
>> If possible, can you please share this sample project.
>> Email Id: harshal.more@itshastra.com
>>
>> Thanks.
>>
>>
>>
>> --
>> View this message in context:
>> http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346622.html
>> Sent from the cxf-dev mailing list archive at Nabble.com.
>>
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
Sadly there currently is no demo project in the distribution. I will add
one and commit it to trunk.
I used the jms config feature a lot where I worked before but I do not
have access to that code. So I will write a new demo that is very
similar to the wsdl-first demo.
Christian
Am 28.04.2011 16:28, schrieb more.harshal2007@gmail.com:
> If possible, can you please share this sample project.
> Email Id: harshal.more@itshastra.com
>
> Thanks.
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346622.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
If possible, can you please share this sample project.
Email Id: harshal.more@itshastra.com
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346622.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
I simply set the correct queue and connectionfactory settings by hand
and do not use the wsdl for more than code generation.
Btw. You can nicely do the codegen using the maven cxf codegen plugin.
So you can include the code generation in your build process.
Christian
Am 28.04.2011 14:36, schrieb more.harshal2007@gmail.com:
> I did the same.
>
> means, removed all JMS setting and get the WSDL which used http transport.
> Generate the clients in java through SOAPUI tool and reconfigure the web
> service project for the JMS.
>
> After this modification I am trying to invoke the web service method but the
> WSDL URL is the same i.e.
> http://servername:portName/projectName/servicename?WSDL.
>
> and giving error 'The server sent HTTP status code 404: Not Found' as web
> service is not using http transport.
>
> So the question is what WSDL URL your using to invoke web service method?
>
> Thanks.
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346345.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
I am not Using ActiveMQ but using weblogic JMS Server.
so I did the configuration properties for weblogic.
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="weblogic.jndi.WLInitialContextFactory"/>
<jms:JMSNamingProperty name="java.naming.provider.url"
value="t3://localhost:7001"/>
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346363.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
I did the same.
means, removed all JMS setting and get the WSDL which used http transport.
Generate the clients in java through SOAPUI tool and reconfigure the web
service project for the JMS.
After this modification I am trying to invoke the web service method but the
WSDL URL is the same i.e.
http://servername:portName/projectName/servicename?WSDL.
and giving error 'The server sent HTTP status code 404: Not Found' as web
service is not using http transport.
So the question is what WSDL URL your using to invoke web service method?
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346345.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi,
do you really need a WSDL with a jms endpoint? I usally used wsdls with
soap/http endpoints or even just the portType to create code and then
simply configure the transport using the spring config. For example you
can use the jmsConfigFeature on a service
without a special jms port and it still works.
See: http://cxf.apache.org/docs/using-the-jmsconfigfeature.html
Christian
Am 28.04.2011 11:00, schrieb more.harshal2007@gmail.com:
> Thanks for your response.
>
> I really need this. Can you please Provide these pointers?
>
> You mention regarding JMS-Spec URL to obtain the wsdl by just adding the
> ?wsdl.
>
> I am not getting this point.
> I am writing http://serverName:portName/projectName/jms://?wsdl but not
> getting any WSDL.
>
> Is it possible for you to provide JMS Spec URL?
>
> Waiting for response.
>
> Thanks.
>
>
>
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346053.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
I think It need to modify my beans.xml.
To edit address property of my Endpoint. right?
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346057.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
Thanks for your response.
I really need this. Can you please Provide these pointers?
You mention regarding JMS-Spec URL to obtain the wsdl by just adding the
?wsdl.
I am not getting this point.
I am writing http://serverName:portName/projectName/jms://?wsdl but not
getting any WSDL.
Is it possible for you to provide JMS Spec URL?
Waiting for response.
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4346053.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
Thanks for your suggestion.
Really Thanks Guys.
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358543.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
When you think of sharing such information in wsdl you should always
take into account that you typically have several stages in a company
develeopment environment.
So you either have to provide one endpoint per stage (e.g. dev, test,
prod) or you only provide an endpoint for dev.
I mostly opted for the last option. So the jms information in the wsdl
was there to document e.g. the queue name but in the code the jms
server, queue name, ... were set in spring and used placeholders. So the
admin could change the setting at deployment time or even at runtime.
Christian
Am 29.04.2011 11:18, schrieb more.harshal2007@gmail.com:
> Thanks to Both of you.
> I am done with the client generation, able to invkoe web method.
> But I don't have the way so that WSDL can viewable with web service
> consumers.
>
> So what I am thinking is like,
> Share WSDL with Http transport and JMS JNDI URI path with the web service
> consumers, so that they can invoke web service using JMS. but modify the
> endpoint for JMS.
>
> Need you thoughts and suggetions.
>
> Thanks.
> Harshal--
> View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358299.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Christian Schneider <ch...@die-schneider.net>.
Not really. I have a prototype for a http2jms bridge on my site though.
http://www.liquid-reality.de/display/liquid/HTTP2JMSBridge
You may want to try this together with soap ui.
Christian
Am 29.04.2011 12:07, schrieb more.harshal2007@gmail.com:
> What are testing tool for JMS web service.
>
> I am trying soap UI HermesJMS tool but unable to do the settings.
>
> If you have some testig tool or other than java classes.
>
> Please let me know.
>
> Thanks.--
> View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358397.html
> Sent from the cxf-dev mailing list archive at Nabble.com.
>
--
----
http://www.liquid-reality.de
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
What are testing tool for JMS web service.
I am trying soap UI HermesJMS tool but unable to do the settings.
If you have some testig tool or other than java classes.
Please let me know.
Thanks.--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358397.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
Thanks to Both of you.
I am done with the client generation, able to invkoe web method.
But I don't have the way so that WSDL can viewable with web service
consumers.
So what I am thinking is like,
Share WSDL with Http transport and JMS JNDI URI path with the web service
consumers, so that they can invoke web service using JMS. but modify the
endpoint for JMS.
Need you thoughts and suggetions.
Thanks.
Harshal--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4358299.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Daniel Kulp <dk...@apache.org>.
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.harshal2007@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
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Harshal <Ha...@itshastra.com>.
Can you please let me know what is JMS-spec URL i.e. an y format/
example like(http://servername:port/applicationname)
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.harshal2007@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.
--
CONFIDENTIALITY NOTICE
This information contains confidential and/or privileged material and is only transmitted for the intended recipient. Any review, retransmission, conversion to hard copy, copying, reproduction, circulation, publication, dissemination or other use of, or taking of any action, or omission to take action, in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this message in error, please contact the sender and delete the material from any computer, disk drive, diskette, or other storage device or media.
Re: NOT getting WSDL when adding transportId="http://cxf.apache.org/transports/jms"
Posted by Daniel Kulp <dk...@apache.org>.
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.harshal2007@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
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: NOT getting WSDL when adding
transportId="http://cxf.apache.org/transports/jms"
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
My bean.xml like
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xmlns:beans="http://www.springframework.org/schema/beans"
xmlns:jms="http://cxf.apache.org/transports/jms"
xmlns:p="http://www.springframework.org/schema/p"
xmlns:jaxrs="http://cxf.apache.org/jaxrs"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd
http://cxf.apache.org/transports/jms
http://cxf.apache.org/schemas/configuration/jms.xsd">
<import resource="classpath:META-INF/cxf/cxf-extension-jms.xml"/>
<jaxws:endpoint
id="CustomerService"
address="jms://"
implementor="com.example.customerservice.impl.CustomerServiceImpl"
transportId="http://cxf.apache.org/transports/jms"
bindingUri=""
>
</jaxws:endpoint>
<jms:destination
name="{http://impl.customerservice.example.com/}CustomerPort.jms-destination">
<jms:address destinationStyle="topic"
jndiConnectionFactoryName="jms/ConnectionFactory"
jndiDestinationName="jms/Topic">
<jms:JMSNamingProperty name="java.naming.factory.initial"
value="weblogic.jndi.WLInitialContextFactory"/>
<jms:JMSNamingProperty name="java.naming.provider.url"
value="t3://localhost:7001"/>
</jms:address>
</jms:destination>
</beans>
--
View this message in context: http://cxf.547215.n5.nabble.com/NOT-getting-WSDL-when-adding-transportId-http-cxf-apache-org-transports-jms-tp4343106p4343120.html
Sent from the cxf-dev mailing list archive at Nabble.com.