Hi
 
I do not know if any others have faced the upgrade problem with moving from version 0.9.2 to 0.9.3. I am using Castor strictly as a java source generation tool.
 
I have an entity User which can have multiple addresses. And the schema I am using has remained identical throughout.
 
Version 0.9.2 generated code for the above entity as:
        1. setAddress(Address[] objAddress);
and   2. setAddress(Address vAddress, int iIndex);
 
This was used by us as a team on all our other development.
 
Now when I tried to move to Version 0.9.3 the same code is now being generated as:
        1. setAddress(Address[] objAddress);
and   2. setAddress(int iIndex, Address vAddress);
 
Since we are so far gone along the project this is going to cause heavy integration issues with all source having to change to meet the new method calls.
This sort of inconsistency between versions would also lead us to get trapped into using an older version, even though the newer versions may offer much more
by way of functionality. There is the promise of being to remove deprecation warnings on org.xml.SAX.DocumentHandler e.g.
 
Could the developers take a look at this and resolve it? Or else give an easy solution to make the new code get generated the way it was?
 
I am not sure if there are others in the field facing similar issues with using the tool.
 
Regards
C.P.Krishnan
 
 

Reply via email to