sparrow-devel Mailing List for INACTIVE: Sparrow: Java Data Objects (Page 3)
Status: Inactive
Brought to you by:
ikestrel
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(11) |
Nov
(27) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
(1) |
Mar
|
Apr
(14) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andy L. <aj...@as...> - 2001-10-23 04:41:23
|
That actually helped a great deal - I hadn't seen that before. On the theory that you are open to suggestions, let me share some of the design concepts I was coding to. I was working towards decoupling the primary components. I admit that my objectives were a bit aggressive, but not unachievable. I had segmented out the back end repository, the O/R mapper, the cache manager, and the transaction manager as seperate pluggable modules. One the core JDO system was in place, and stable, each of these pieces could then be indepednatly enhanced, improved, or replaced, without impact the rest. I was also working towards a bytecode enhancer implementation that was embeddable in a classsloader. Let me ask another long term question - is the objective of Sparrow to be a quality OSS JDO implementaiton? Or is it, as is the attitude with the jBoss group for example, intended to be better than its commercial competitors as well? Joel Shellman wrote: >I understand--sorry I haven't replied sooner regarding that issue. First >of all, this doesn't answer your question, but... > >A project spec was started: > >http://www.geocrawler.com/archives/3/11922/2001/5/0/5733981/ > >An owners document was also put into CVS (attached). > >As you can see there hasn't been much progress since then. > >I'm in a position now to make it a priority, though. > >No formal charter and roadmap has been put forth yet. We were still >doing preliminary work before things kind of just faded off for a while. >Let me put some ideas together and put it up on the docs at sourceforge. >I'll try to have something started there tonight or tomorrow. > >-joel > > >On Mon, 2001-10-22 at 18:37, Andy Lewis wrote: > >>At the risk of sounding pushy, has there been any planning on what >>modules are needed to complete the implementation? I saw the breakout >>from the ConvienentStore project, but has that been carried further? I >>guess what I am asking about is the charter and roadmap for the community... >> >>Joel Shellman wrote: >> >>>There is now a document up on the source forge project page with a >>>listing of bytecode manipulation libraries that we could start with. >>> >>>I have also created a survey asking which bytecode manipulation library >>>we should start with. >>> >>>I know of Maurice Perry's donated Enhancer... Are there any others to >>>consider or should we plan on starting with that? If we choose a >>>different bytecode manipulation, we can just rewrite that enhancer to >>>take advantage of it. Or we can use it as is. >>> >> >> >>_______________________________________________ >>Sparrow-devel mailing list >>Spa...@li... >>https://lists.sourceforge.net/lists/listinfo/sparrow-devel >> >> >> ------------------------------------------------------------------------ >> >> Sparrow 1.0 Features and Owners Matrix >> >> Feature Owner >> File Persistence >> Query >> Parser >> Implementation >> java.util.Collections support >> javax.jdo.Extent support >> XML Metadata >> Parser for jdo.dtd >> JDOImplHelper implementation >> JDO Instances >> PersistenceCapable implementation JS >> Bytecode enhancer JS >> Transaction support >> Persistence Management >> PersistenceManager implementation >> PersistenceManagerFactory implementation >> JDOHelper implementation >> StateManager implementation JS >> RDBMS Persistence >> Query >> Parser >> Implementation >> java.util.Collections support >> javax.jdo.Extent support >> XML Metadata >> Parser for jdo.dtd >> JDOImplHelper implementation >> JDO Instances >> PersistenceCapable implementation >> Bytecode enhancer JS >> Transaction support >> Persistence Management >> PersistenceManager implementation >> PersistenceManagerFactory implementation >> JDOHelper implementation >> StateManager implementation >> >> >> Owner Initials Owner Name >> JS Joel Shellman >> JU Jukka Uusisalo >> DC Dmitri Colebatch >> AC Albert Chow >> FR Franck Rasolo >> CK Chip Killmar >> >> >> |
From: Joel S. <jo...@ik...> - 2001-10-23 03:59:04
|
I understand--sorry I haven't replied sooner regarding that issue. First of all, this doesn't answer your question, but... A project spec was started: http://www.geocrawler.com/archives/3/11922/2001/5/0/5733981/ An owners document was also put into CVS (attached). As you can see there hasn't been much progress since then. I'm in a position now to make it a priority, though. No formal charter and roadmap has been put forth yet. We were still doing preliminary work before things kind of just faded off for a while. Let me put some ideas together and put it up on the docs at sourceforge. I'll try to have something started there tonight or tomorrow. -joel On Mon, 2001-10-22 at 18:37, Andy Lewis wrote: > At the risk of sounding pushy, has there been any planning on what > modules are needed to complete the implementation? I saw the breakout > from the ConvienentStore project, but has that been carried further? I > guess what I am asking about is the charter and roadmap for the community... > > Joel Shellman wrote: > > >There is now a document up on the source forge project page with a > >listing of bytecode manipulation libraries that we could start with. > > > >I have also created a survey asking which bytecode manipulation library > >we should start with. > > > >I know of Maurice Perry's donated Enhancer... Are there any others to > >consider or should we plan on starting with that? If we choose a > >different bytecode manipulation, we can just rewrite that enhancer to > >take advantage of it. Or we can use it as is. > > > > > > _______________________________________________ > Sparrow-devel mailing list > Spa...@li... > https://lists.sourceforge.net/lists/listinfo/sparrow-devel -- Joel Shellman iKestrel, Inc. http://www.ikestrel.com/ |
From: Andy L. <aj...@as...> - 2001-10-23 01:37:33
|
At the risk of sounding pushy, has there been any planning on what modules are needed to complete the implementation? I saw the breakout from the ConvienentStore project, but has that been carried further? I guess what I am asking about is the charter and roadmap for the community... Joel Shellman wrote: >There is now a document up on the source forge project page with a >listing of bytecode manipulation libraries that we could start with. > >I have also created a survey asking which bytecode manipulation library >we should start with. > >I know of Maurice Perry's donated Enhancer... Are there any others to >consider or should we plan on starting with that? If we choose a >different bytecode manipulation, we can just rewrite that enhancer to >take advantage of it. Or we can use it as is. > |
From: Joel S. <jo...@ik...> - 2001-10-22 13:04:55
|
There is now a document up on the source forge project page with a listing of bytecode manipulation libraries that we could start with. I have also created a survey asking which bytecode manipulation library we should start with. I know of Maurice Perry's donated Enhancer... Are there any others to consider or should we plan on starting with that? If we choose a different bytecode manipulation, we can just rewrite that enhancer to take advantage of it. Or we can use it as is. -- Joel Shellman iKestrel, Inc. http://www.ikestrel.com/ |
From: Andy L. <aj...@as...> - 2001-10-21 16:41:14
|
Sorry - you are correct. Not the enhancer - but it is, I would say, the most critical component. A possible starting point anyway. Maurice Perry wrote: >It is not a bytecode enhancer, it is a bytecode manipulation library. The >bytecode enhancer is part of Kodo, which is a commercial product. However, >it could be a good idea use this framework. > >----- Original Message ----- >From: "Andy Lewis" <aj...@as...> >To: <spa...@li...> >Sent: Sunday, October 21, 2001 4:56 PM >Subject: [Sparrow-devel] Byte Code enhancer options..o > > >>Take a look at http://sourceforge.net/projects/tt-bytecode/ >> >>This is the byte code enhancer used by the Kodo JDO implementation. It >>is stable, released, and BSD licensed. >> >> >>_______________________________________________ >>Sparrow-devel mailing list >>Spa...@li... >>https://lists.sourceforge.net/lists/listinfo/sparrow-devel >> > > >_______________________________________________ >Sparrow-devel mailing list >Spa...@li... >https://lists.sourceforge.net/lists/listinfo/sparrow-devel > |
From: Maurice P. <ma...@pe...> - 2001-10-21 15:47:41
|
It is not a bytecode enhancer, it is a bytecode manipulation library. The bytecode enhancer is part of Kodo, which is a commercial product. However, it could be a good idea use this framework. ----- Original Message ----- From: "Andy Lewis" <aj...@as...> To: <spa...@li...> Sent: Sunday, October 21, 2001 4:56 PM Subject: [Sparrow-devel] Byte Code enhancer options..o > Take a look at http://sourceforge.net/projects/tt-bytecode/ > > This is the byte code enhancer used by the Kodo JDO implementation. It > is stable, released, and BSD licensed. > > > _______________________________________________ > Sparrow-devel mailing list > Spa...@li... > https://lists.sourceforge.net/lists/listinfo/sparrow-devel > |
From: Andy L. <aj...@as...> - 2001-10-21 14:56:21
|
Take a look at http://sourceforge.net/projects/tt-bytecode/ This is the byte code enhancer used by the Kodo JDO implementation. It is stable, released, and BSD licensed. |