In attempting to use the strip-suffixes codegen option to remove the word
"Type" from the end of my complex types.  However, some of my complex types
have the word "Type" in the name as well as a "Type" suffix.  In this case,
JiBX seems to recursively remove the suffix.  In the following example, I
would expect to end up with "VehicleType" and "Vehicle".  Instead, I end up
with "Vehicle" (two instances of "Type" removed) and "Vehicle1" (one
instances of "Type" removed and class renamed to avoid conflict).  This is
definitely not what I want.

Is this by design?  Is there a way around this or do I have to code my own
name converter?     

<xsd:complexType name="VehicleTypeType">
                <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                                <xsd:attribute name="Id" type="xsd:int" 
use="required" />
                        </xsd:extension>
                </xsd:simpleContent>
        </xsd:complexType>

<xsd:complexType name="VehicleType">
                <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                                <xsd:attribute name="Id" type="int" 
use="required" />
                        </xsd:extension>
                </xsd:simpleContent>
        </xsd:complexType>

        
-- 
View this message in context: 
http://www.nabble.com/strip-suffixes-is-recursive--tp25513244p25513244.html
Sent from the jibx-users mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users

Reply via email to