Hi,
digged down in the NullPointerException and found the following :
When I swich to Castor-1.0 , get a NullPointerException , series.getId() is NULL .
Putting a null in Hashtable gives me a null pointer.
Hashtable modelTypes = new Hashtable();
modelTypes.put(series.getId(), modelType);
When I use Castor-0.8.11 , surprisingly, I get the value of series.getId() as the intended one .. and the code works fine ...
In the earlier code , unmarshaling is done in both cases , using this :
response = um.unmarshal(new InputSource(new FileReader(xmlFile)));
If you have any clues, please let me know , why I am getting a NULL value for a field when using Castor-1.0
Have a nice weekend.
Amol
On 5/5/06, Werner Guttmann <[EMAIL PROTECTED]> wrote:
Amol,if you wanted, please feel free to post the stack trace ...Werner
From: Amol Sawant [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 05. Mai 2006 03:53
To: user@castor.codehaus.org; dev@castor.codehaus.org
Subject: Re: [castor-user] Castor upgrade from 0.8.11 to 1.0
Thank you Amigos.Here are some specific questions:In the application we are using Castor XML only for data binding purpose.Started migration feasibility test today. After replacing Castor-0.8.11 by Castor-1.0 jar, there are no compilation time errors. I checked the method signatures and found to be the same.But at Runtime, I get a NullPointerException from code, still digging down into it...My question is :1) Do I need to recreate the mappings when I migrate to Castor-1.0 jar?2) Shall I do step by step iterative migration, that is , first migrating to earlier castor versions and later to 1.0 ?Your response is highly appreciated.Best regards,Amol Sawant
On 5/4/06, Clovis Wichoski < [EMAIL PROTECTED]> wrote:Hi, Amol,
I'm the user that Ralf means, ;), today i'm using castor 0.9.4.3, i cant migrate, to version 1.0 because i use long transactions and many complex objects graph, well, then the migration depends on how complex is your objects and how you control transactions, the better way is make a test, create the maps, change any import dependencies, and test with the version 1.0 if all works in your application, your migration are fine, if not, report any of the problems that the dev can solve or show you the steps to a possible workaround.
Hope that this help.
Best regards
Clóvis
