By namespaces do you mean Java packages? (in my case I have
gov.loc.www.zing.cql, gov.loc.www.zing.srw.diagnostic, etc.) or
namespaces in the actual generated XML on the wire (in which case it
doesn't matter what they are called, and the prefixes are generated on
the fly by the Axis webservice container)
Matthew
> -----Original Message-----
> From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]]
> On Behalf Of Fred Petter Pedersen
> Sent: 05 April 2004 11:14
> To: [log in to unmask]
> Subject: Re: Problems with Axis and JBuilder
>
> Yes! I have now an SRW Service up and running. But Axis has
> made three namespaces namely tns2, tns3 and tns4 which I
> would liked to be srw, xcql and diag respectively.
> The WSDL is generated everytime I rebuild so I guess this
> could be set somewhere??
>
> Regards Fred.
>
> -----Original Message-----
> From: Matthew J. Dovey [mailto:[log in to unmask]]
> Sent: 2. april 2004 17:30
> To: [log in to unmask]
> Subject: Re: Problems with Axis and JBuilder
>
> Fred,
>
> In JBuilderX
>
> In the web services designer click on the icon that looks
> like a document with a star and wheel on it, and click import from URL
>
> This will give you a WSDLService1 box. Click on WSDLService1.
> You'll get a dialog box with a label input WSDL file. Put
> http://www.loc.gov/z3950/agency/zing/srw/srw-sample-service.wsdl.
>
> Finally click on the Server checkbox
>
> Then build the project
>
> Unfortunately the Axis in JbuilderX will give the error
> reported by Alan (_whereInListType0 not found - I still use
> JBuilder 8 as my primary development IDE and this exhibit
> this bug). A quick fix is to rename the class _whereInList to
> _whereInListType0 (yes - that is the Axis bug, it calls the
> class _whereInList, but then uses _whereInListType0 in the
> other generated code!).
>
> However, you could also try using the new draft schemas at
> http://samantha.oucs.ox.ac.uk:8080/srw1-1/srw-sample-service.w
> sdl where I've now included a workaround for this.
>
> For your own server you should make a local version of
> srw-sample-service.wsdl - make sure that the import includes
> the full url of the srw-bindings.wsdl on the LoC site, and
> modify the URL endpoint of your service accordingly.
>
> Matthew
>
|