Re: DB JDO new project
Ah, I see, thanks for explaining to me :) Oliver On Tue, 7 Dec 2004 14:01:09 -0500, Brian McCallister [EMAIL PROTECTED] wrote: OJB supports a JDO interface via a plugin to the JDO 1.0.X reference implementation (which is SCSL, non-commercial variant) so is basically useless right now. This same RI is part of the initial codebase for this project, so the OJB JDO 1.0.X interface can actually become useful =) -Brian On Dec 7, 2004, at 12:01 PM, Oliver Zeigermann wrote: Doesn't ORB already support JDO? Oliver On Tue, 07 Dec 2004 08:47:19 -0800, Craig Russell [EMAIL PROTECTED] wrote: Hi, The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. I've attached the proposal. Perhaps you can suggest the next step for me to pursue? Thanks, Craig -- Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DB JDO new project
Craig, I see that the JDO 1.0 RI is coming to the ASF, development on JDO 2.0 will commence, using the JDO 1.0 code as a starting point, and the source for JDO 2.0 has not yet been developed except in prototype form by expert group members, but the JDO 2.0 Reference Implementation will be developed outside Apache (in SourceForge under the JPOX project). Will the ASF have a certified JDO 2 implementation? --- Noel smime.p7s Description: S/MIME cryptographic signature
DB JDO new project
Hi, The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. I've attached the proposal. Perhaps you can suggest the next step for me to pursue? Thanks, Craig --Title: JDO Proposal - Incubator Wiki JDO Proposal UserPreferences Incubator Wiki FrontPage RecentChanges TitleIndex WordIndex SiteNavigation HelpContents Apache ApacheWiki MoinMoin Proposal for new project JDO 19 Nov 2004, Craig Russell (craig dot russell at sun dot com) (updated 23 Nov 2004) (0) rationale Java Data Objects (JDO) is being proposed as a sub-project within the DB top-level project. JDO is an interface-based domain-object-to-database programming model developed as a standard extension of Java under the Java Community Process. It separates persistence programming into two different areas: the domain object model and the persistence interface. The domain object model has no references to the persistence interface; and the persistence interface has no references to the domain object model. Application code uses the persistence interface to query, create, and delete persistent instances, and delegates business logic to domain code. This separation of concerns allows independent development of domain objects that represent database entities and application persistence code that interacts with the JDO interface. JDO is designed for programmers who focus on their object model and the object view of data. Interfaces are provided that allow users to manage data stored in the data store without programming to any database-specific interfaces. The JDO query language is based on Java, and the protocols for managing data abstract such notions as transactional cache, transaction initiation and completion, and data creation, deletion, and update. Applications can be developed without any database-specific code and can be migrated among JDO implementations. Currently, the JDO 1.0 final release specification is available for download from the Java Specification Request 12 web site under a standard Sun Specification License. The Reference Implementation is based on a btree file system and does not support relational databases for object storage, and is licensed under Sun's Sun Community Source License. The Technology Compatibility Kit is based on JavaTest, a proprietary test framework developed by Sun, and is licensed bundled with a support agreement. JDO 2.0 is under development as Java Specification Request 243 and is in Early Draft status. The jar files, Reference Implementation, and Technology Compatibility Kit have not yet been developed. The plan is to migrate the existing JDO 1.0 code base, including the API, RI, and TCK to Apache. Subsequently, development on JDO 2.0 will commence, using the JDO 1.0 code as a starting point. The API and TCK will be implemented entirely as Apache sub-projects. The licenses will be changed to be Apache licenses. The JDO 2.0 Reference Implementation will be developed outside Apache (in SourceForge under the JPOX project). The license will be Apache 2.0 from the beginning. Subsequently, we will attempt to integrate with the persistence engine currently under development for Geronimo EJB. This engine, known as Tranql, will be investigated as the common persistence engine for both EJB and JDO in the J2EE 1.5 timeframe. The binding to Tranql will be done as a separate sub-project in the Apache JDO project. (0.1) criteria Meritocracy: We plan to do everything possible to encourage an environment that supports a meritocracy. One of the lessons that the JDO experts have learned is that meritocracies don't just evolve from good intentions; they require actively asking the community for help, listing/specifying the work that needs to be done, and keeping track of and encouraging members of the community who make any contributions. The committer list for this proposal includes people who will specifically be responsible for doing the work necessary to foster a meritocracy. Community: From the inception of the JDO expert group in 1999, expertise has been solicited from the community, which has directed the evolution of the API. There is already a strong base of persistence expertise, and a community of users and vendors who regularly use such forums as JDOCentral. This project should help us build a new community at Apache. Core Developers: Half of the initial committers are key members of Sun's JDO development, test, and project management team. The rest are non-Sun developers who have had significant experience with the framework or the technologies it is built upon. Some of these committers are contributing to this project on behalf of their employer, some of them are self-employed consultants, and some of them are just contributing as individuals. Three of them have
Re: DB JDO new project
Doesn't ORB already support JDO? Oliver On Tue, 07 Dec 2004 08:47:19 -0800, Craig Russell [EMAIL PROTECTED] wrote: Hi, The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. I've attached the proposal. Perhaps you can suggest the next step for me to pursue? Thanks, Craig -- Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DB JDO new project
On Wednesday 08 December 2004 00:47, Craig Russell wrote: The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. Very interesting :o) Btw, what is the Apache JSR license and the Apache TCK license ?? Cheers Niclas -- +--//---+ / http://www.dpml.net / / http://niclas.hedhman.org / +--//---+ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DB JDO new project
Hi Niclas, The JSR license is a proposed Apache license for use with Java Community Process (JCP) Reference Implementation projects. http://jcp.org The TCK license is a proposed Apache license for use with JCP Technology Compatibility Kit projects. Since JDO is a JSR http://java.sun.com/products/jdo/ and http://jcp.org/aboutJava/communityprocess/final/jsr012/index2.html, it needs these licenses. The licenses are special only in that they require that if a derivative work is produced, you cannot call the derived work the JDO RI or the JDO TCK. We don't otherwise restrict what you can do with the code. Regards, Craig On Dec 7, 2004, at 9:19 AM, Niclas Hedhman wrote: On Wednesday 08 December 2004 00:47, Craig Russell wrote: The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. Very interesting :o) Btw, what is the Apache JSR license and the Apache TCK license ?? Cheers Niclas -- +--//---+ / http://www.dpml.net / / http://niclas.hedhman.org / +--//---+ Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: DB JDO new project
OJB supports a JDO interface via a plugin to the JDO 1.0.X reference implementation (which is SCSL, non-commercial variant) so is basically useless right now. This same RI is part of the initial codebase for this project, so the OJB JDO 1.0.X interface can actually become useful =) -Brian On Dec 7, 2004, at 12:01 PM, Oliver Zeigermann wrote: Doesn't ORB already support JDO? Oliver On Tue, 07 Dec 2004 08:47:19 -0800, Craig Russell [EMAIL PROTECTED] wrote: Hi, The DB project voted to adopt JDO last week-end, and they suggested I contact you to set up the resources for the project. I've attached the proposal. Perhaps you can suggest the next step for me to pursue? Thanks, Craig -- Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DB JDO new project
Hi all, I have done some work with TranQL (have started an object persister around it that does what it's supposed to do) and I'd like to help out with this. best, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
