[Jboss-dev-forums] [Design of JBossXB] - Re: Supporting non-default ctors

[<sco...@jb...>]

Even for the container solution, it would seem that we should support a more java bean approach via a jbxb:class container attribute:


  |   <xs:element name="module-option">
  |     <xs:complexType mixed="true">
  |        <xsd:annotation>
  |           <xsd:appinfo>
  |              <jbxb:class container="org.jboss.test.xml.mbeanserver.ModuleOptionContainer"
  | accessor="instantiate"/>
  |           </xsd:appinfo>
  |        </xsd:annotation>
  |       <xs:sequence>
  |         <xs:any minOccurs="0" maxOccurs="1" namespace="##other" />
  |       </xs:sequence>
  |       <xs:attribute name="name" use="required" type="xs:string"/>
  |     </xs:complexType>
  |   </xs:element>
  | 

where ModuleOptionContainer would not implement any specific interface. Its has a non-arg ctor as is treated the same as any other class except that on completion of the element its associated with, the jbossxb layer would invoke the method referenced by the accessor to retrieve the actual object binding. All this avoids is having to deal with the explicit handling of attributes and elements.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3882413#3882413

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3882413