On Thu, 2002-05-02 at 17:33, Geir Magnusson Jr. wrote: > I hate to interrupt all the good fun over standards, bike sheds, and general > good community feelings, but I would like to solicit community opinion on > something unrelated to DVSL or Jon Stevens (both of which I like, btw...)
Thank god. > The idea would be to bring in ObjectBridge, but create a Commons-like > environment in which other projects can be brought. Call it DB-Commons as > a working name. > Anyone have any comments? I like this idea a lot. It would be great to bring together a lot of these different efforts and look at how they can work together. And you would finally have an excuse to bring poolman over (yay!). My only concern (and this is not meant as an objection) is that we be careful not to dilute/damage the projects we bring into it. OJB is an extensive and solid product on par with any of Jakarta's top level projects. A lot of people feel that torque is also of the same scale. They _can_ coexist, and work is already going on to have them work together in sensible ways and share code (the Torque query code which is moving to commons). I can see them, along with the common code they share, all our connection pools, and so on existing as a distinct organizational unit, but the key is co-existing. If we take a 'MERGE MERGE MERGE' attitude it could cause more harm then good. Merging is sensible sometimes, maybe we decide it makes sense to have only one or two connection pools rather than four, but maybe not. There is definitely room for more than one O/R mapper. But if they can share repetitive components and build community, that would be exciting! -- jt -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
