You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "more.harshal2007@gmail.com" <ha...@itshastra.com> on 2011/04/27 12:57:24 UTC
Re: JAX-WS Endpoint Configured via Spring 3.0 - No Service was
found
Is this issue resolved?
If yes, can you please post your solution. I am also facing same problem.
Thanks
--
View this message in context: http://cxf.547215.n5.nabble.com/JAX-WS-Endpoint-Configured-via-Spring-3-0-No-Service-was-found-tp3255251p4343250.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAX-WS Endpoint Configured via Spring 3.0 - No Service was
found
Posted by "more.harshal2007@gmail.com" <ha...@itshastra.com>.
Thanks,
I am still facing problem and it is due to my end point configuration
because I added transportId="http://cxf.apache.org/transports/jms" to enable
JMS communication.
and due to this i am not able to generate WSDL for web service.
Thanks.
--
View this message in context: http://cxf.547215.n5.nabble.com/JAX-WS-Endpoint-Configured-via-Spring-3-0-No-Service-was-found-tp3255251p4343403.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: JAX-WS Endpoint Configured via Spring 3.0 - No Service was found
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday, April 27, 2011 6:57:24 AM more.harshal2007@gmail.com wrote:
> Is this issue resolved?
>
> If yes, can you please post your solution. I am also facing same problem.
When deploying into a servlet container, the "address" attribute should only
be the stuff after the context, like "/WSDirectoryService", not the full URL.
We don't have control over the server/port/context and thus those parts should
not be specified.
Dan
> Thanks
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/JAX-WS-Endpoint-Configured-via-Spring-3-0-
> No-Service-was-found-tp3255251p4343250.html Sent from the cxf-user mailing
> list archive at Nabble.com.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com