Jürgen, We saw the exact same thing when we upgraded to JiBX 1.2.3. There is a mention in changes.txt of a change in the naming algorithm:
6. Better naming algorithm for nested schema components (if only one child component, pass the outer name down to the child component). Regards, Ryan From: Jürgen Bockhorn <juergen.bockh...@heuboe.de<mailto:juergen.bockh...@heuboe.de>> Reply-To: JiBX users <jibx-users@lists.sourceforge.net<mailto:jibx-users@lists.sourceforge.net>> Date: Tue, 9 Aug 2011 05:56:22 -0700 To: "jibx-users@lists.sourceforge.net<mailto:jibx-users@lists.sourceforge.net>" <jibx-users@lists.sourceforge.net<mailto:jibx-users@lists.sourceforge.net>> Subject: [jibx-users] WG: Code changes after changing from JIBX 1.2.1 to 1.2.3 Hi, does the project die after I asked this question (no post since then) or does nobody else have this problem ? Regards, Jürgen Von: Jürgen Bockhorn Gesendet: Freitag, 29. Juli 2011 16:03 An: jibx-users@lists.sourceforge.net<mailto:jibx-users@lists.sourceforge.net> Betreff: Code changes after changing from JIBX 1.2.1 to 1.2.3 Hi, after switching from JIBX 1.2.1 to JIBX 1.2.3 we noticed changes in the generated code (we start from schema). Given an xsd:complexType like <xs:complexType name="complexFilter"> <xs:choice maxOccurs="unbounded"> <xs:element name="textTerm" type="tns:textFilterTerm" /> <xs:element name="numberTerm" type="tns:numberFilterTerm" /> </xs:choice> </xs:complexType> we formerly (1.2.1) get code like public class ComplexFilter {..... public static class ComplexFilterInner ( // the xs:Choice element { now (1.2.3) its public class ComplexFilter {..... public static class Choice ( // the xs:Choice element - NEW NAME { Also the method names for List access (getter/setter) changed from public List<FooBar> getFooBars() { to public List<FooBar> getFooBarList() With JIBX 1.2.1 we did ant based code generation (org.jibx.schema.codegen.CodeGen) - with JIBX 1.2.3 we do maven based code generation (maven-jibx-plugin). We are not aware of any special code generation configuration which might causes the changing behaviour. However we also could not find any documentation about this change (ReleaseNotes, ...). Can anyone confirm this modified behaviour. We would feel better on refactoring our code to the new generated JIBX code if we could eliminate other reasons but the JIBX version change. Thx in advance Jürgen
------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
