You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Guillaume Sauthier <Gu...@Bull.Net> on 2003/09/18 17:08:38 UTC
set a new endpointURL with client-config.wsdd ?
Hi All
In our effort to integrate Axis in our J2EE platform JOnAS, we have to
change the endpointURL of a generated class. The only way to do it
programmatically seems to be the getPort(URL) no ?
The problem is that from our J2EE platform view, we can just handle the
Service implementation, not the Ports, in other words, client use a
configured service/port instance (it's not his work to know the real URL
of a service).
And so my Question : How to configure the Ports endpointURL from the
encapsulating Service implementation ?
Thanks.
Re: set a new endpointURL with client-config.wsdd ?
Posted by Guillaume Sauthier <Gu...@Bull.Net>.
Thanks to respond Gary :)
Have you seen the WebServices for J2EE specification v1.1 ? In this
spec, they add a new element in servlet and ejb Deploymebnt Desc (the
component that can be WebServices client) : service-ref. This element
describe the port that the component will use (with port-component-ref
element). And the port-component-ref can specify a port-component-link,
it just say that the port used by the client is contained in the same
application unit (ear). So the URL location of this port is unknown when
we generate the Service implementation from WSDL (the Definition with a
dummy location attribute) and so we have to specify it when deploying in
the server (we can then calculate the URL of the port).
That's for the context :) Now, how things works ?
When we generate Class from WSDL, Service class are generated with the
endpointURL of the WSDL (dummy value). And when we request a port with
this Service class, this endpointURL is always used, and we have no way
to change it (no accessor, more the endpointURL field is final!).
Is it cleareer ?
Thanks
Guillaume
Gary L Peskin wrote:
>
> I would like to help answer this question but I don't really understand what
> you're asking. Are you saying that the client is requesting a certain URL
> but you want them to request a different URL? Perhaps you can handle this
> with a request handler.
>
> If you clarify what you're trying to do, I can try to help.
>
> Gary
>
> > -----Original Message-----
> > From: Guillaume.Sauthier@Bull.Net
> > [mailto:Guillaume.Sauthier@Bull.Net]
> > Sent: Thursday, September 18, 2003 8:09 AM
> > To: axis-user@ws.apache.org
> > Subject: set a new endpointURL with client-config.wsdd ?
> >
> >
> > Hi All
> >
> > In our effort to integrate Axis in our J2EE platform JOnAS,
> > we have to change the endpointURL of a generated class. The
> > only way to do it programmatically seems to be the
> > getPort(URL) no ? The problem is that from our J2EE platform
> > view, we can just handle the Service implementation, not the
> > Ports, in other words, client use a configured service/port
> > instance (it's not his work to know the real URL of a service).
> >
> > And so my Question : How to configure the Ports endpointURL
> > from the encapsulating Service implementation ?
> >
> > Thanks.
> >
RE: set a new endpointURL with client-config.wsdd ?
Posted by Gary L Peskin <ga...@firstech.com>.
I would like to help answer this question but I don't really understand what
you're asking. Are you saying that the client is requesting a certain URL
but you want them to request a different URL? Perhaps you can handle this
with a request handler.
If you clarify what you're trying to do, I can try to help.
Gary
> -----Original Message-----
> From: Guillaume.Sauthier@Bull.Net
> [mailto:Guillaume.Sauthier@Bull.Net]
> Sent: Thursday, September 18, 2003 8:09 AM
> To: axis-user@ws.apache.org
> Subject: set a new endpointURL with client-config.wsdd ?
>
>
> Hi All
>
> In our effort to integrate Axis in our J2EE platform JOnAS,
> we have to change the endpointURL of a generated class. The
> only way to do it programmatically seems to be the
> getPort(URL) no ? The problem is that from our J2EE platform
> view, we can just handle the Service implementation, not the
> Ports, in other words, client use a configured service/port
> instance (it's not his work to know the real URL of a service).
>
> And so my Question : How to configure the Ports endpointURL
> from the encapsulating Service implementation ?
>
> Thanks.
>