"What methods? The new ones?" Yes
"How do you know what they're called?" Quite easy. The data arrives in either CSV or XLS/XLSX, either way I read the column headers from the file, the setters or getters are always named "set"/"get" <columnHeader> "I just don't see what you gain here if your structure is constantly changing." What you gain is the flexibility of being able to consistently retrieve your data as entities (because they get restructured as the data shape changes) so you can continue to use pure JPA entities instead of having to add SQL or processing maps dynamically. One point I should make is that this is not because the data is "constantly changing" is it because it allows the system to accommodate changes in the shape of the incoming data set. Regards Chris -----Original Message----- From: ljnelson [mailto:[email protected]] Sent: Saturday, 25 July 2009 3:06 AM To: [email protected] Subject: Re: Dynamic entity definition creation - is it possible? On Thu, Jul 23, 2009 at 9:10 PM, crispyoz (via Nabble) < [email protected]<ml-user%[email protected]. com> > wrote: > When the server sees the new XML it parses it and does a reshape/create of > any required tables instantiate an instance of the modified/new class, I can > wait for this to complete and then call the generated class and access it's > methods. What methods? The new ones? How do you know what they're called? How does your code that calls them compile? If you're using reflection, this isn't much different from using a Map. Mind you, I'm not some kind of Map zealot :-) I just don't see what you gain here if your structure is constantly changing. Best, Laird -- View this message in context: http://n2.nabble.com/Dynamic-entity-definition-creation---is-it-possible--tp 3310100p3316923.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
