cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: WSDL First Development Cycle - specifically wsdl:port address question
Date Tue, 01 Apr 2008 16:15:16 GMT

If the client is grabbing the wsdl view the ?wsdl flag to the endpoint, 
it SHOULD be getting a modified wsdl that has the proper address in it.   
If that's not the case, that might be a bug, but it's probably a 
configuration issue as I know we have several tests that test this (and 
the TCK requires it to work).  Thus, I'd probably like to see a war that 
demonstrates this.

Also, the client can always be reconfigured post-creation to hit any url 
you give it.   It DOESN'T need to use the url in the wsdl.   If the 
container can provide a new URL, just set the ENDPOINT_ADDRESS_PROPERY 
thing on the client's request context and it will use that address 


On Tuesday 01 April 2008, bdm wrote:
> Glen,
> Thanks for the response but I may not have been clear on what I'm
> trying to accomplish.
> In our normal development life cycle, once code (a .war file in this
> case) leaves development for test and production we do not change
> anything in the code or the accompanying configuration files (spring
> context, etc).  All of the differences in the environments (database
> connections, etc) are handled by the container - tomcat in this case. 
> We would like to implement the same type of configuration with our web
> service deployments.
> In [1] - the last sentence of note 4 reads - "Note the URL specified
> in the wsdl:port section (under wsdl:service) is ignored by the
> servlet container. It is used, however, by the web service client
> which reads in this WSDL to determine where to route the requests."
> This is exactly the problem.  Yes the web service deploys correctly
> and the servlet container ignores the address given in the provided
> WSDL.  But, the WSDL is delivered unmodified to any requesting client
> with the address given in the WSDL and not the address of the service.
>  I tried this yesterday one last time before posting to the list using
> 2.0.4 of CXF.
> I'm not sure if that is a bug or a feature, I'm just trying to figure
> out how to implement our standard practice given the current behavior
> of CXF.
> Brent
> Glen Mazza-2 wrote:
> > Note #4 of here[1] shows how the WSDL URL is created when you deploy
> > to an application server; as you can see, what you have in the wsdl
> > file is pretty much ignored web-service provider side.
> >
> > For the client, it is just an issue of modifying the
> > ENDPOINT_ADDRESS_PROPERTY as shown in Step #7 here[2].  You can use
> > Spring Dependency Injection for that if helpful.
> >
> > Glen
> >
> > [1]
> > [2]

J. Daniel Kulp
Principal Engineer, IONA

View raw message