Yes, I did get your comments - was just very busy today. It might be easier for us if you could make a new 'snapshot release'.
If you do so, please let me know what I have to do to get it. Thanks for your help, Ted -----Original Message----- From: Werner Guttmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 14, 2007 3:50 PM To: [email protected] Subject: Re: [castor-user] Substitution group issues Hi, Please see inline. Werner Troccola, Ted PEO C3T PM BC Viecore wrote: > > Werner, > > I'm a little confused. > > Looking at our schema, I see <xs:element name="comment" > type="xs:string" />. > > Also, I see > > <xs:complexType name="clothing-type"> > <xs:complexContent> > <xs:extension base="po:product-type"> > <xs:sequence> > <xs:element name="color"> > <xs:simpleType> > <xs:restriction base="xs:token"> > <xs:enumeration value="red"/> > <xs:enumeration value="blue"/> > <xs:enumeration value="green"/> > </xs:restriction> > </xs:simpleType> > </xs:element> > </xs:sequence> > </xs:extension> > </xs:complexContent> > </xs:complexType> > > which has an internal element named color that is a xs:simpleType. > > So, my question is... when you say "simple types" do you mean > "xs:simpleType" or things like xs:string? > > And, although I might know before you respond, would changing > everything to be a xs:complexType be a work around while you come up > with a final solution? > > Also, is there a way I can get these patches you mentioned? We'd like > to try some more experimenting. Basically, as I have committed these patches to SVN trunk, feel free to get the latest code from SVN and build the binaries yourself. If that's actually not an option, I am always in the position to make a new snapshot release available at the Codehaus snapshot repository. I hope you don't mind that I will address your other questions in a separate email. > > Thanks, > > > -----Original Message----- From: Werner Guttmann > [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 > 11:05 AM To: [email protected] Subject: AW: [castor-user] > Substitution group issues > > Can you please create a new Jira issue at > > http://jira.codehaus.org/browse/CASTOR > > and attach all relevant files, including XML schema(s), binding file, > castorbuilder.properties, etc. > > Thanks in advance Werner > >> -----Ursprüngliche Nachricht----- Von: Troccola, Ted PEO C3T PM BC >> Viecore [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 10. >> Mai 2007 16:55 An: '[email protected]' Betreff: RE: >> [castor-user] Substitution group issues >> >> We have set the automaticConflictResolution=true and left >> automaticConflictResolutionTypeSuffix=By. >> >> We still have the same problems. >> >> -----Original Message----- From: Werner Guttmann >> [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 >> 4:24 AM To: [email protected] Subject: AW: [castor-user] >> Substitution group issues >> >> For substitution groups to work properly (in all cases), a special >> property (concerning automatic name conflict resolution needs to be >> enabled). >> >> Werner >> >>> -----Ursprüngliche Nachricht----- Von: Troccola, Ted PEO C3T PM BC >>> Viecore [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 09. >>> Mai 2007 15:44 An: '[email protected]' Betreff: RE: >>> [castor-user] Substitution group issues >>> >>> >>> >>> We experience the problem when using the default >>> castor-builder.properties in the castor-1.1.1-codegen.jar file. >>> >>> >>> Thanks, T >>> >>> -----Original Message----- From: Werner Guttmann >>> [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 08, 2007 5:33 PM >>> To: [email protected] Subject: Re: [castor-user] Substitution >>> group issues >>> >>> What's the builder properties you are using ? >>> >>> Werner >>> >>> Troccola, Ted PEO C3T PM BC Viecore wrote: >>>> We are using castor-1.1.1, and java build 1.4.2_12-b03. >>>> >>>> We have attached a schema and instance document that uses >>>> substitution >>> groups. >>>> We successfully generate Castor classes with the following >>>> command: >>>> >>>> java -cp >>>> xerces-J_1.4.0.jar;commons-logging-1.1.jar;castor-1.1.1-xml.jar;ca >>>> st or -1.1.1-codegen.jar >>>> org.exolab.castor.builder.SourceGeneratorMain -i EasyPo.xsd >>>> -package po >>>> >>>> However, when we try to unmarshall the attached xml we get Castor >>> Exceptions: >>>> unable to find FieldDescriptor for 'book' in ClassDescriptor of >>>> invoice-header{F ile: [not available]; line: 29; column: 20} >>>> >>>> For some reason, Castor doesn't like 'book' - however, if book is >>> replaced by product - everything works fine. However, that is >>> invalid xml (product is abstract). In fact, ship-comment has the >>> same problem. It would appear that the substitution groups are not >>> being Castorized properly, or perhaps we're doing something wrong? >>>> PurchaseOrder vcList = new PurchaseOrder(); >>>> >>>> try { >>>> >>>> Unmarshaller unmar = new Unmarshaller(PurchaseOrder.class); >>>> >>>> vcList = (PurchaseOrder) unmar.unmarshal( new InputSource( new >>>> StringReader( xmlBuf.toString() ) ) >>> ); >>>> } catch (Exception e) { ... } >>>> >>>> Compile: javac -classpath .\castor-1.1.1-xml.jar SendXMLFile.java >>>> Run: java -classpath .\castor-1.1.1-xml.jar SendXMLFile >>>> >>>> Has anyone been able to get substitution groups working? >>>> >>>> Thanks, >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------ >>>> -- -- -- >>>> >>>> ------------------------------------------------------------------ >>>> -- - To unsubscribe from this list please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe from this list please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> -------------------------------------------------------------------- >>> - To unsubscribe from this list please visit: >>> >>> http://xircles.codehaus.org/manage_email >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
