Title: Marshalling attributes problem...
I downloaded CVS snapshot version of castor v0.9.3.
HC.
-----Original Message-----
From: Arnaud Blandin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 21, 2001 7:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] Marshalling attributes problem...

Hy Henry,
 
you should try the CVS version, I think it is fixed for a while now.
If you are using the CVS version, it seems like a bug.

Let me know so that I can update our bugzilla,

Arnaud
-----Original Message-----
From: Henry Chin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 21, 2001 4:16 PM
To: [EMAIL PROTECTED]
Subject: [castor-dev] Marshalling attributes problem...

Hi,
  I have in my schema file the following complexType

   <xs:complexType name="ProgramType">
      <xs:choice maxOccurs="unbounded">
         <xs:element name="add"          type="actionType" minOccurs="0"/>
         <xs:element name="delete"       type="deleteType" minOccurs="0"/>
         <xs:element name="redeploy"     type="actionType" minOccurs="0"/>
         <xs:element name="update"       type="actionType" minOccurs="0"/>
      </xs:choice>
      <xs:attribute name="version" type="VersionType" use="required"/>
   </xs:complexType>

When I marshal my object out to XML, the version attribute is not shown.  I found out that the SourceGenerator creates two classes (and the associated descriptor classes) called ProgramType.java and ProgramTypeItem.java.  My attribute "version" is located inside ProgramTypeItem.java.  From a descriptor perspective ProgramTypeItem.java is considered to be a container (set to true).  The marshaller does not output objects that are containers.

Is there a way to get around this problem so that either:
1) SourceGenerator creates the "version" attribute inside ProgramType.java and not ProgramTypeItem.java.  I would think this would be easier.

2) To change the marshaller so that container objects are created.  However, I think this would cause more problems.

Regards,
HC.

Reply via email to