jeff wrote:
> it is my understanding that the jaxrpc servlet should respond with the
> wsdl if passed the argument WSDL, e.g. ...
>
> http://server.com/endpoint?WSDL
If deployed correctly, you should be able to go to
http://server.com/endpoint by itself and see a welcome page. Try that as
well as Arun's suggestion of checking the wsdl when you do see it in a
browser.
>
> in my jaxrpc-ri.xml, i have the wsdl="/foo.wsdl" specified on my
> endpoint. assuming my endpoint is in the web app "bar". if i hit:
The wsdl file should be in the WEB-INF directory in your war file, so
you should have wsdl="/WEB-INF/foo.wsdl" in the jaxrpc-ri.xml file. See
if that helps at all.
> i see the xml wsdl file, so it is properly installed in the web
> container.
Not necessarily. Note that going to
http://somepath/foo.wsdl does *not*
show you the same wsdl file that is sent by the jaxrpc servlet. It shows
you the base wsdl file that the servlet will use to produce a final one,
but the fact that you can see the raw file in a browser doesn't mean
it's in the right place for the servlet.
(The reason the servlet fiddles with it is to transform the location
attribute. This allows you to deploy the same war file on server1.com
and server2.com and the location will be transformed properly when a
client makes a request for the wsdl file. --it's also why it's ok to
deploy a war file with wsdl location="REPLACE_WITH_ACTUAL_URL".)
> please respond to me directly [...]
(bcc'ed to make sure you'd get it but avoid extra copies from replies.)
Cheers,
Bobby Bissett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net