Title: namespaced element ref's - bug?
Thanks Arnaud.
 
Should I raise it in Bugzilla?
 

Perryn Fowler

-----Original Message-----
From: Arnaud Blandin [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 1:15 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] namespaced element ref's - bug?

Hi Perryn,

 

This is definitely a bug in the reading of the reference element. We'll fix it ASAP.


Thanks,

Arnaud

 

-----Original Message-----
From: Perryn Fowler [mailto:[EMAIL PROTECTED]]
Sent:
Thursday, June 20, 2002 8:11 AM
To: [EMAIL PROTECTED]
Subject: [castor-dev] namespaced element ref's - bug?

 

 

I am using 0.9.3.19 Source Generator using 'type' generation.

It doesnt seem to be recognizing namespacing of element refs
and includes them in the name of the element.

eg for a schema like

<schema targetNamespace="http://www.example.com/IPO"
        xmlns="http://www.w3.org/2001/XMLSchema"
        xmlns:ipo="http://www.example.com/IPO">

 <element name="purchaseOrder" type="ipo:PurchaseOrderType"/>

 <element name="comment" type="string"/>

 <complexType name="PurchaseOrderType">
  <sequence>
   <element ref="ipo:comment" minOccurs="0"/>
  </sequence>
  <attribute name="orderDate" type="date"/>
 </complexType>

</schema>

The xmlName of the comment element in PurchaseOrderType is
interpreted as "ipo:comment" rather than "comment" so that the
PurchaseOrderType class has get/setIpoComment() and more
worryingly marshalls using that name,  so you end up with
something like this once a namespace has been added.

<ns1:ipo:comment>etc etc</ns1:ipo:comment>

Is this a bug?

 


Perryn Fowler
Object Oriented Pty Ltd
(03) 9866 5266

Reply via email to