Menu
▾
▴
xorm-devel
|
From: Wes B. <we...@ca...> - 2006-02-09 16:11:36
|
I'm thinking of switching XORM future development to have the following dependencies: * Add requirement for JDK 1.5 and clean up code in ways this allows * Add requirement for JDO 2.0, now that there is an API JAR available. Most of the 2.0 methods would be initially non-functional, but some key ones, like PersistenceManager.newInstance(), would replace XORM proprietary methods where applicable. * Include the POJQ project for compilable queries. This would replace the experimental CodeQuery framework in XORM today, and remove the need for BCEL. These changes should all be backward compatible for users, provided that they recompile against the JDO2 jar (which alters the argument types and return types of some methods). I don't see XORM being a particularly active project, or hoping to surpass much larger open source projects like JPOX (the JDO 2.0 reference implementation) in terms of overall implementation of the JDO spec, but this allows us to align its usage with the features that have been standardized in JDO 2 and maintain focus on implementing those features which we feel are most important and applicable to our projects, or those that we're interesting in looking at from an experimental point of view. Thoughts? Wes |
|
From: Dan C. <da...@ch...> - 2006-02-09 16:14:28
|
+1 )_( Dan ----- Original Message ----- From: "Wes Biggs" <we...@ca...> To: <xor...@li...> Sent: Thursday, February 09, 2006 8:11 AM Subject: [Xorm-devel] XORM major revisions > I'm thinking of switching XORM future development to have the following > dependencies: > > * Add requirement for JDK 1.5 and clean up code in ways this allows > * Add requirement for JDO 2.0, now that there is an API JAR available. > Most of the 2.0 methods would be initially non-functional, but some key > ones, like PersistenceManager.newInstance(), would replace XORM > proprietary methods where applicable. > * Include the POJQ project for compilable queries. This would replace the > experimental CodeQuery framework in XORM today, and remove the need for > BCEL. > > These changes should all be backward compatible for users, provided that > they recompile against the JDO2 jar (which alters the argument types and > return types of some methods). > > I don't see XORM being a particularly active project, or hoping to surpass > much larger open source projects like JPOX (the JDO 2.0 reference > implementation) in terms of overall implementation of the JDO spec, but > this allows us to align its usage with the features that have been > standardized in JDO 2 and maintain focus on implementing those features > which we feel are most important and applicable to our projects, or those > that we're interesting in looking at from an experimental point of view. > > Thoughts? > > Wes > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Xorm-devel mailing list > Xor...@li... > https://lists.sourceforge.net/lists/listinfo/xorm-devel > |
|
From: Harry E. <ha...@gm...> - 2006-02-09 22:18:58
|
Not super hip on JDK 1.5, in general (God, I'm becoming a curmudgeon), but other than that, this sounds like the right way to go. I think the switch to JDK 1.5 is right as well, but I don't have to like it. +1 On 2/9/06, Dan Checkoway <da...@ch...> wrote: > +1 > > )_( Dan > > ----- Original Message ----- > From: "Wes Biggs" <we...@ca...> > To: <xor...@li...> > Sent: Thursday, February 09, 2006 8:11 AM > Subject: [Xorm-devel] XORM major revisions > > > > I'm thinking of switching XORM future development to have the following > > dependencies: > > > > * Add requirement for JDK 1.5 and clean up code in ways this allows > > * Add requirement for JDO 2.0, now that there is an API JAR available. > > Most of the 2.0 methods would be initially non-functional, but some key > > ones, like PersistenceManager.newInstance(), would replace XORM > > proprietary methods where applicable. > > * Include the POJQ project for compilable queries. This would replace = the > > experimental CodeQuery framework in XORM today, and remove the need for > > BCEL. > > > > These changes should all be backward compatible for users, provided tha= t > > they recompile against the JDO2 jar (which alters the argument types an= d > > return types of some methods). > > > > I don't see XORM being a particularly active project, or hoping to surp= ass > > much larger open source projects like JPOX (the JDO 2.0 reference > > implementation) in terms of overall implementation of the JDO spec, but > > this allows us to align its usage with the features that have been > > standardized in JDO 2 and maintain focus on implementing those features > > which we feel are most important and applicable to our projects, or tho= se > > that we're interesting in looking at from an experimental point of view= . > > > > Thoughts? > > > > Wes > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > > _______________________________________________ > > Xorm-devel mailing list > > Xor...@li... > > https://lists.sourceforge.net/lists/listinfo/xorm-devel > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > Xorm-devel mailing list > Xor...@li... > https://lists.sourceforge.net/lists/listinfo/xorm-devel > |
Thanks for helping keep SourceForge clean.
X