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

------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to