I found the problem, the portName attribute in the @WebService
annotation on my implementation had an incorrect value. Also, if the
portName attribute is not specified the same behavior occurs. I tried
this on Metro and wasn't able to cause the same behavior.
Thanks for the help,
Brent
Dan
Brent,
On Tuesday 01 April 2008, Brent Moore wrote:
> I've created a JIRA [1] with an attached war for an echo service that
> exhibits the behavior I'm talking about. If I understand you
> correctly, the "bogushost" address should be replaced with the real
> address of the service. But at least
It seems that with the three services listed below the wsdl files are
part of a repository of available services hosted on a different site
than the actual service itself. In that context it makes sense that
the services don't match the url of the wsdl. But if a service is
asked for it's wsdl
I haven't given this much thought before but I'm not sure why it matters
what the address is in the WSDL that is sent from the service to the
client. By virtue of the fact that the client accessed the service
using the ...?wsdl URL in order to get the WSDL to begin with, it
already knows what URL
Dan,
I've created a JIRA [1] with an attached war for an echo service that
exhibits the behavior I'm
talking about. If I understand you correctly, the "bogushost" address
should be replaced with the real address of the service. But at least
on my tomcat 5.5.23 it doesn't happen.
Once it d
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 req
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 (spr
Hi,
I think you can configure endpoint address by spring, you can change it
in spring configure file according to different development cycle phase.
[1] for more details
[1]http://cwiki.apache.org/CXF20DOC/jax-ws-configuration.html
Freeman
bdm wrote:
I'm looking for suggestions for a "best
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]
I'm looking for suggestions for a "best practice" in how we accomplish moving
our CXF code through the various parts of our development lifecycle - i.e.
development, test, and production. We have divided these responsibilities
among three hosts - ws-dev, ws-tst, and ws (production). We also pref
10 matches
Mail list logo
