Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of andrew.clegg@gmail.com
 designates 209.85.219.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=mvS1mPoV2c3GjyEgeZDN9qB/Sun1cYwYJzpDwEKps0dRq19O1Bds3p6WNSzZGdkdks
         ovS8UUiU+n7UMxCkSspdgtjvJNUfcyVjzFMDjMYqOggCiXTgiPgbLeL7lzqD8aBzMYvT
         bT4LbSjrJcTfUAevZoe3n02iuP3mi9cq7X+oE=
MIME-Version: 1.0
Sender: andrew.clegg@gmail.com
In-Reply-To: <200903231705.36494.dkulp@apache.org>
References: <e507996c0903231207w5f39f39l8a1a1380fcdbc252@mail.gmail.com>
	 <e507996c0903231240g409fbcd3p48bd057edc7f2944@mail.gmail.com>
	 <200903231705.36494.dkulp@apache.org>
Date: Tue, 24 Mar 2009 13:41:35 +0000
Message-ID: <e507996c0903240641i5bbc8c4cr486bf59a5c2b47b@mail.gmail.com>
Subject: Re: wsdl2java -- Resolving imported schemas with relative paths
From: Andrew Clegg <andrew@nervechannel.com>
To: Daniel Kulp <dkulp@apache.org>
Cc: users@cxf.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I'm not sure I follow you -- the service-specific schema
ws_spindlep_2_0_ws0.xsd has this line as the first element in its
schema:

<xsd:import namespace=3D"http://www.cbs.dtu.dk/ws/ws-common"
schemaLocation=3D"../common/ws_common_1_0b.xsd"/>

... which is also imported into the WSDL.

I just noticed last night though that Eclipse complains about the WSDL
having two wsdl:types elements, I'll try merging them and see if that
makes JAXB happy...

Andrew.

2009/3/23 Daniel Kulp <dkulp@apache.org>:
>
> JAXB is correct here. =A0 =A0The scheme in question (the second in the ws=
dl),
> doesn't have any imports. =A0 Thus, it cannot reference anything outside =
of
> itself. =A0 There should be an import in there.
>
> Dan
>
>
> On Mon March 23 2009 3:40:22 pm Andrew Clegg wrote:
>> Actually, I think my previous suspicion about the cause of the problem
>> may be a red herring.
>>
>> I've downloaded all three files:
>>
>> http://www.cbs.dtu.dk/ws/SpindleP/SpindleP_2_0_ws0.wsdl
>> http://www.cbs.dtu.dk/ws/SpindleP/ws_spindlep_2_0_ws0.xsd
>> http://www.cbs.dtu.dk/ws/common/ws_common_1_0b.xsd
>>
>> and saved them into one local directory, changed the schemaLocation
>> elements to just refer to the filenames without any path prefixes:
>>
>> <xsd:import
>> namespace=3D"http://www.cbs.dtu.dk/ws/ws-common"
>> schemaLocation=3D"ws_common_1_0b.xsd"
>> />
>>
>> and invoked wsdl2java like so:
>>
>> wsdl2java SpindleP_2_0_ws0.wsdl
>>
>> and I still get:
>>
>> WSDLToJava Error: Thrown by JAXB : undefined simple or complex type
>> 'spindlep:seqlookup'
>>
>> This service works fine in SoapUI, I've sent, received and validated
>> messages OK, so I'm a bit stuck... Is there some magic incantation
>> that gets wsdl2java to honour imported schemas?
>>
>> Any suggestions greatly appreciated!
>>
>> Andrew.
>>
>> 2009/3/23 Andrew Clegg <andrew@nervechannel.com>:
>> > Hi,
>> >
>> > I'm trying to write a JAXB/JAXWS client for this service:
>> >
>> > http://www.cbs.dtu.dk/ws/SpindleP/ws_spindlep_2_0_ws0.xsd
>> >
>> > Just using wsdl2java on that URL with no extra parameters gives this
>> > error:
>> >
>> > WSDLToJava Error: Thrown by JAXB : undefined simple or complex type
>> > 'spindlep:seqlookup'
>> >
>> > ... presumably because all the types in use in that WSDL are defined
>> > in imported schemas with relative paths:
>> >
>> > <xsd:import
>> > namespace=3D"http://www.cbs.dtu.dk/ws/ws-common"
>> > schemaLocation=3D"../common/ws_common_1_0b.xsd"
>> > />
>> > <xsd:import
>> > namespace=3D"http://www.cbs.dtu.dk/ws/ws-spindlep"
>> > schemaLocation=3D"ws_spindlep_2_0_ws0.xsd"
>> > />
>> >
>> > ... so I tried supplying a JAXB catalog (SpindleP.cat) as described he=
re:
>> >
>> > https://jaxb.dev.java.net/guide/Fixing_broken_references_in_schema.htm=
l
>> >
>> > This contains the following lines:
>> >
>> > PUBLIC "http://www.cbs.dtu.dk/ws/ws-common"
>> > "http://www.cbs.dtu.dk/ws/common/ws_common_1_0b.xsd"
>> > PUBLIC "http://www.cbs.dtu.dk/ws/ws-spindlep"
>> > "http://www.cbs.dtu.dk/ws/SpindleP/ws_spindlep_2_0_ws0.xsd"
>> >
>> > I know those XSD URLs work (you can check them yourself...). But when
>> > I re-ran wsdl2java like this:
>> >
>> > wsdl2java -catalog SpindleP.cat
>> > http://www.cbs.dtu.dk/ws/SpindleP/SpindleP_2_0_ws0.wsdl
>> >
>> > ... I got exactly the same error. Weirdly, even with -verbose, there's
>> > no indication that wsdl2java is trying and failing to read the
>> > imported schemas. It's as if it's completely ignoring the catalog
>> > file.
>> >
>> > Any idea what I'm doing wrong? I also tried using SYSTEM paths rather
>> > than PUBLIC in the catalog file, same result. Also tried both CXF 2.2
>> > and 2.1.4 with no difference.
>> >
>> > I could probably contact the maintainers of that service and get them
>> > to provide a URL instead of a relative path, and for now I'll just
>> > download and modify the appropriate files myself. But it's a bit of a
>> > shame if it doesn't work as designed, especially since SoapUI just
>> > resolves the locations for me automatically. If this is unexpected
>> > behaviour, let me know and I'll JIRA it.
>> >
>> > Thanks,
>> >
>> > Andrew.
>> >
>> > --
>> >
>> > :: http://biotext.org.uk/ ::
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>


--=20
:: http://biotext.org.uk/ ::