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 Amila Suriarachchi <am...@gmail.com> on 2008/02/01 06:32:16 UTC
Re: ABD Problem resolving attributeGroup ref="..." when referencing schema shares target namespace with the referenced attributeGroup
On Jan 22, 2008 2:54 PM, Jakob Færch <Ja...@jyskebank.dk> wrote:
> I'm using ADB databinding to generate client- and serverside code for a
> fairly complex collection of wsdl's and xsd's.
>
> I have run into a problem with constructions like the following (using […]
> for abbreviations added by me):
>
> File TLS_Sektion.xsd:
> <schema
> xmlns:tls="http://rep.oio.dk/tinglysning.dk/xml.schema/2008.01.01/"
> targetNamespace="
> http://rep.oio.dk/tinglysning.dk/xml.schema/2008.01.01/" […]>
> <include
> schemaLocation="TLS_BrugerformularAnvendelseAttributGruppe.xsd"/>
> <complexType name="Sektion">
> […]
> <attributeGroup
> ref="tls:BrugerformularAnvendelseAttributGruppe"/>
> </complexType>
> </schema>
>
> File TLS_BrugerformularAnvendelseAttributGruppe.xsd:
> <schema
> xmlns:tls="http://rep.oio.dk/tinglysning.dk/xml.schema/2008.01.01/"
> targetNamespace="
> http://rep.oio.dk/tinglysning.dk/xml.schema/2008.01.01/" […]>
> <include schemaLocation="TLS_FastVariabelKode.xsd"/>
> <attributeGroup name="BrugerformularAnvendelseAttributGruppe">
> <attribute name="brugerformularAnvendelse"
> type="tls:FastVariabelKodeType" use="optional"/>
> </attributeGroup>
> </schema>
>
> Similar constructs where the targetnamespace of the refering schema is
> /not/ the same as the refered attributeGroup seems to work all right.
>
> When I generate code for this, a CodeGenerationException is thrown
> indicating that the tls:BrugerformularAnvendelseAttributGruppe can not be
> dereferenced.
>
> I have debugged the code and found, that in
> org.apache.axis2.schema.SchemaCompiler#processAttributeGroupReference, the
> call to getXmlSchemaAttributeGroup doesn't seem to follow the include.
>
> I am running Axis2 1.3 under a jdk 1.4.2.
>
could you please try with a nighly build. I changed the schema resolution
logic . so that every one use the same logic.
thanks,
Amila.
> Does anyone have a suggestion for a workaround or af fix? Could this be a
> bug?
>
> Kindly,
> Jakob Færch
>
--
Amila Suriarachchi,
WSO2 Inc.