RE: Federations [was: Re: Incubation of iBATIS Data Mapper]

> -Original Message- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > > I agree on the federation idea, which Berin adopted for the XML TLP, but > please note that the XML Federation has no impact on TLP issues for the > Board. The federation idea is about fostering tighter collaboratio

Re: Federations [was: Re: Incubation of iBATIS Data Mapper]

On Aug 10, 2004, at 1:15 PM, Noel J. Bergman wrote: TLP reporting is a corporate structure issue, whereas federation is about sharing resources (e.g., web-site and mail domain) and community building. Exactly! -Brian - To uns

RE: Federations [was: Re: Incubation of iBATIS Data Mapper]

Brian McCallister wrote: > J Aaron Farr wrote: > > We're seeing a general explosion of new TLP's in Apache or subprojects > > graduating to TLP level. IMHO at some point we're going to reach a > > critical mass where it will no longer be very feasible for the Board > > to directly handle so many TL

Federations [was: Re: Incubation of iBATIS Data Mapper]

[mailto:[EMAIL PROTECTED] Sent: Tuesday, August 10, 2004 7:13 AM To: [EMAIL PROTECTED] Subject: RE: Incubation of iBATIS Data Mapper Since there does seem to be interest in reviewing a proposal from iBATIS, I've setup a draft in the Incubator wiki. http://wiki.apache.org/incubator/IbatisPro

RE: Incubation of iBATIS Data Mapper

> -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 10, 2004 7:13 AM > To: [EMAIL PROTECTED] > Subject: RE: Incubation of iBATIS Data Mapper > > Since there does seem to be interest in reviewing a proposal from iBATIS, > I

Re: Incubation of iBATIS Data Mapper

To answer Clinton's question - I have very little knowledge or interest in either OJB or Torque. IMO, having any sort of oversight of those projects would be pointless. >From what I have seen of them, they both take very different philisophical approaches to interacting with data than iBATIS. Pers

RE: Incubation of iBATIS Data Mapper

Since there does seem to be interest in reviewing a proposal from iBATIS, I've setup a draft in the Incubator wiki. http://wiki.apache.org/incubator/IbatisProposal Based on the discussion here, I've included a section on whether to apply as TLP or subproject. The iBATIS scope is a

RE: Incubation of iBATIS Data Mapper

Original Message- > From: Clinton Begin [mailto:[EMAIL PROTECTED] > Sent: Monday, August 09, 2004 5:15 PM > To: [EMAIL PROTECTED] > Subject: Re: Incubation of iBATIS Data Mapper > > > >> I don't believe anyone has a strong inclination one way or the other.

Re: Incubation of iBATIS Data Mapper

>> I don't believe anyone has a strong inclination one way or the other. I'll jump off the fence into a yard. :-) I'd prefer to see iBATIS as a TPL for the reasons Ted has laid out. I don't think joining the DB project would benefit either team. >> The key question would be whether members of t

Re: Incubation of iBATIS Data Mapper

On Mon, 9 Aug 2004, Ted Husted wrote: if [...] overseeing a DB product with non-Java implementations is not an issue There is nothing Java specific about the Apache DB charter, indeed the DB proposal specicially calls out a language-agnostic approach.

Re: Incubation of iBATIS Data Mapper

On Mon, 09 Aug 2004 10:09:31 -0400, Brian McCallister wrote: > > I cannot speak for the whole DB PMC, but I am pretty confident that > the project would be quite happy to provide a hat peg and help as > needed =) I'd love to see iBATIS join the DB project, and this > seems the natural home for it,

[OT] Re: Incubation of iBATIS Data Mapper

Sorry for the double post, guess moderator let posting from my unsubbed account through! -Brian On Aug 9, 2004, at 10:10 AM, Brian McCallister wrote: +1 for this incubation, either joining db or as its own TLP wearing my DB PMC hat =) On Aug 9, 2004, at 9:31 AM, Ted Husted wrote: It's true that

Re: Incubation of iBATIS Data Mapper

+1 for this incubation, either joining db or as its own TLP wearing my DB PMC hat =) On Aug 9, 2004, at 9:31 AM, Ted Husted wrote: It's true that we are all database/data persistence technologies, but, in my experience, there is much more to an Apache product than technology. My own concern as

Re: Incubation of iBATIS Data Mapper

+1 for this incubation, either joining db or as its own TLP wearing my DB PMC hat =) On Aug 9, 2004, at 9:31 AM, Ted Husted wrote: It's true that we are all database/data persistence technologies, but, in my experience, there is much more to an Apache product than technology. My own concern as

RE: Incubation of iBATIS Data Mapper

On Mon, 09 Aug 2004 00:15:22 -0400, Noel J. Bergman wrote: > And you might want to talk with our DB project and see what interest also comes from >there. It's true that we are all database/data persistence technologies, but, in my experience, there is much more to an Apache product than technolo

Re: Incubation of iBATIS Data Mapper

Hi Noel, Thanks for your response. For those who may not be familiar with iBATIS, it is a persistence tool. More specifically, it is a Data Mapper (PoEAA, Fowler). iBATIS is not an Object Relational Mapper, however many people find it does a better job of isolating the object model from the dat

RE: Incubation of iBATIS Data Mapper

Clinton, I see that you have Ted Husted and Harish Krishnaswamy backing your Incubation, as well as other enthusiastic people. I see that our Jakarta Commons Mapper project(http://jakarta.apache.org/commons/sandbox/mapper/) has support for iBatis as well as other data mappers. And you might want

Incubation of iBATIS Data Mapper [text/plain]

iBATIS is a unique framework for mapping objects to database queries. Many agree that iBATIS is simpler and more flexible than object relational mapping tools, and is particular good with complex databases. The Java framework is freely distributed, ASF licensed, open source

Incubation of iBATIS Data Mapper

iBATIS is a unique framework for mapping objects to database queries. Many agree that iBATIS is simpler and more flexible than object relational mapping tools, and is particular good with complex databases. The Java framework is freely distributed, ASF licensed, open source