You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Brent Moore (JIRA)" <ji...@apache.org> on 2008/04/02 21:05:25 UTC
[jira] Issue Comment Edited: (CXF-1497) Supplied WSDL soap:address
not being updated with actual host name when queried.
[ https://issues.apache.org/jira/browse/CXF-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584725#action_12584725 ]
bdm edited comment on CXF-1497 at 4/2/08 12:04 PM:
-----------------------------------------------------------
Glen,
Thanks for the information. I'm still not getting this to work after working through the information above (to the best of my understanding). Here are some specific comments/results to the issues you have raised:
1) Added "/services/*" as the context path for the servlet. No difference in the result.
2) a. We are not using a file named cxf-servlet.xml - it is named servletContext.xml in the classes directory so the Spring contextloaderlistener will pick it up along with a series of spring context fragments embedded in our manager jars. We are taking advantage of the contextloader's classpath wildcard feature to do this. But in looking at the cxf documentation [3] this should not be a problem.
b. url-pattern is not a valid attribute on a jaxws:endpoint element. The reference on the note #4 at [1] looks more like a metro configuration file than a cxf one - see [4] for the docs I used in creating servletContext.xml.
3) a. Changed the wsdlLocation to "WEB-INF/wsdl/EchoService.wsdl" - no difference. Also removed the annotation attribute wsdlLocation in the implementation class - no difference. Of course, removing both will give me the generated wsdl with the correct location.
b. wsdl= is not valid in the CXF context file - see [4]. I did try it just for kicks but the app would not deploy.
After doing the above I switched back to a cxf-servlet.xml file using an example from [5]. No change. I had to use the following bean definition for the service to deploy:
<jaxws:endpoint
id="EchoService"
implementor="edu.byu.ws.echo.impl.EchoServiceImpl"
address="/EchoService"
wsdlLocation="../wsdl/EchoService.wsdl" >
</jaxws:endpoint>
With a wsdlLocation of "WEB-INF/wsdl/EchoService.wsdl" the service would not deploy - it was looking in a non-existent directory in the file system for the wsdl. I also tried an address with the host name in it (see example in [4]) but that returns the "no service was found" message on wsdl query.
I am not sure where to go next. I am attaching the maven project that built the war.
[3] http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
[4] http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
[5] http://cwiki.apache.org/CXF20DOC/configuration.html
Thanks for your help.
Brent
was (Author: bdm):
Glen,
Thanks for the information. I'm still not getting this to work after working through the information above (to the best of my understanding). Here are some specific comments/results to the issues you have raised:
1) Added "/services/*" as the context path for the servlet. No difference in the result.
2) a. We are not using a file named cxf-servlet.xml - it is named servletContext.xml in the classes directory so the Spring contextloaderlistener will pick it up along with a series of spring context fragments embedded in our manager jars. We are taking advantage of the contextloader's classpath wildcard feature to do this. But in looking at the cxf documentation [3] this should not be a problem.
b. url-pattern is not a valid attribute on a jaxws:endpoint element. The reference on the note #4 at [1] looks more like a metro configuration file than a cxf one - see [4] for the docs I used in creating servletContext.xml.
3) a. Changed the wsdlLocation to "WEB-INF/wsdl/EchoService.wsdl" - no difference. Also removed the annotation attribute wsdlLocation in the implementation class - no difference. Of course, removing both will give me the generated wsdl with the correct location.
b. wsdl= is not valid in the CXF context file - see [4]. I did try it just for kicks but the app would not deploy.
After doing the above I switched back to a cxf-servlet.xml file using an example from [5]. No change. I had to use the following bean definition for the service to deploy:
<jaxws:endpoint
id="EchoService"
implementor="edu.byu.ws.echo.impl.EchoServiceImpl"
address="/EchoService"
wsdlLocation="../wsdl/EchoService.wsdl" >
</jaxws:endpoint>
With a wsdlLocation of "WEB-INF/wsdl/EchoService.wsdl" the service would not deploy - it was looking in a non-existent directory in the file system for the wsdl. I also tried an address with the host name in it (see example in [3]) but that returns the "no service was found" message on wsdl query.
I am not sure where to go next. I am attaching the maven project that built the war.
[3] http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
[4] http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
[5] http://cwiki.apache.org/CXF20DOC/configuration.html
Thanks for your help.
Brent
> Supplied WSDL soap:address not being updated with actual host name when queried.
> --------------------------------------------------------------------------------
>
> Key: CXF-1497
> URL: https://issues.apache.org/jira/browse/CXF-1497
> Project: CXF
> Issue Type: Test
> Reporter: Brent Moore
> Attachments: echo-ws.war.zip, echo-ws.zip
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.