JiBX

upperCase/lowerCase problem in code generation

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: JiBX 1.2.3
  • Fix Version/s: None
  • Component/s: CodeGen
  • Labels:
    None
  • Number of attachments :
    0

Description

When generating code from schema elements with a name that has only one character like

<xs:complexType name="fooBar">
  <xs:sequence>
    <xs:element name="x" type="xs:double" minOccurs="0" >
  </xs:sequence>
</xs:complexType>

the generated class member will be uppercased.

private Double X;

That causes trouble when extending the CodeGeneration because 

public void valueAdded(String basename, boolean collect, String type,
    FieldDeclaration field, MethodDeclaration getmeth,
    MethodDeclaration setmeth, String descript, IClassHolder holder)

will get the original lowercase basename which will not be a valid member of the generated class.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Klaus Claszen added a comment -

additional description:

The valuedAdded method belongs to the org.jibx.schema.codegen.extend.ClassDecorator interface which has to be implemented by custom class decorators.

Show
Klaus Claszen added a comment - additional description: The valuedAdded method belongs to the org.jibx.schema.codegen.extend.ClassDecorator interface which has to be implemented by custom class decorators.
Hide
Permalink
Klaus Claszen added a comment -

The problem also occurs if an element has one lowerCase character which is followed by an upperCase character, like 'zOrder' in the following example

<xs:complexType name="fooBar">
	<xs:sequence>
		<xs:element name="time" type="xs:dateTime" minOccurs="0" />
		<xs:element name="segmentId" type="xs:int" minOccurs="1" />
		<xs:element name="zOrder" type="xs:double" minOccurs="0" />
	</xs:sequence>
</xs:complexType>

The code generation will generate a member which starts with an upperCase character:

private Double ZOrder;

but the basename provided in the ClassDecorator.valueAdded method will be 'zOrder' and thus will not match the member name.

Show
Klaus Claszen added a comment - The problem also occurs if an element has one lowerCase character which is followed by an upperCase character, like 'zOrder' in the following example <xs:complexType name= "fooBar" > <xs:sequence> <xs:element name= "time" type= "xs:dateTime" minOccurs= "0" /> <xs:element name= "segmentId" type= "xs:int" minOccurs= "1" /> <xs:element name= "zOrder" type= "xs:double" minOccurs= "0" /> </xs:sequence> </xs:complexType> The code generation will generate a member which starts with an upperCase character: private Double ZOrder; but the basename provided in the ClassDecorator.valueAdded method will be 'zOrder' and thus will not match the member name.

People

  • Assignee:
    Unassigned
    Reporter:
    Klaus Claszen
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: