On Sun, Mar 23, 2008 at 7:57 PM, Jervis Liu <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 24, 2008 at 5:39 AM, Kalle Korhonen <
> [EMAIL PROTECTED]>
> > On Sat, Mar 22, 2008 at 10:47 PM, Glen Mazza <[EMAIL PROTECTED]>
> > > machine locally, running wsdl2java and then coding your SOAP client
> > > using the wsdl2java artifacts generated, similar to here[1]. Once
> done,
> > > any missing XSD's from the server should no longer be a concern for
> you.
> > But it is a concern. I have the generated service stubs, but if I create
> > service by specifying the the server url (Service.create(new
> > URL("http://<http://some.server/service?wsdl>..."),
> > it'll try to fetch the xsds and fails because of that. The same doesn't
> > happen if I point to a wsdl from classpath. I need to be able to specify
> > the
> > service location in code,
>
> You've got it almost right. You need to point your client to use a local
> copy of wsdl file and xsds etc. But you do not need to hard code the wsdl
> location in your client. Take a look into any CXF sample, for example,
> samples\hello_world. You can see the WSDL location is passed in from
> command
> line or from ant script as below:
>
I think you misunderstood what we are talking about here; not the the wsdl
location but the location of the service (port) (and originally, how
references to imported resources can and should be resolved).
Kalle
