Re: New Commons SubProject Proposal

2006-02-18 Thread robert burrell donkin
On Fri, 2006-02-17 at 14:57 +0530, Karthik Kumar wrote:
> On 2/17/06, robert burrell donkin <[EMAIL PROTECTED]>
> wrote:
> >
> > On Wed, 2006-02-15 at 16:52 -0800, Martin Cooper wrote:
> > > Given its database-centric nature, and the fact that it's a framework,
> > this
> > > would appear to be more appropriate for the Apache DB Project:
>
> Hmm.. okay. it isn't a large framework. but, okay.

jakarta commons does bricks not frameworks

(however, it is possible that you are actually describing something
which is an adaptive bridge brick and not technically a framework)

> >
> > > http://db.apache.org/
> >
> > +1 but don't let that discourage you :)
> 
> 
> jakarta isn't really accepting sub-projects any more: we're very slowly
> > moving away from that model towards something flatter.
> >
> > - robert
> 
> 
> 
> I was specifically referring to the Commons. Well, okay! :)

it was the language that fooled me :)

sub-projects are jakarta mini-me's with separate communities, mailing
lists and so on. apache has found that sub-projects don't scale.
components are the bricks the community happens to be working on.

but martin's right that we try to push data access related proposals
towards the db project. 

- robert


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: New Commons SubProject Proposal

2006-02-17 Thread Karthik Kumar
On 2/17/06, robert burrell donkin <[EMAIL PROTECTED]>
wrote:
>
> On Wed, 2006-02-15 at 16:52 -0800, Martin Cooper wrote:
> > Given its database-centric nature, and the fact that it's a framework,
> this
> > would appear to be more appropriate for the Apache DB Project:



Hmm.. okay. it isn't a large framework. but, okay.


>
> > http://db.apache.org/
>
> +1 but don't let that discourage you :)


jakarta isn't really accepting sub-projects any more: we're very slowly
> moving away from that model towards something flatter.
>
> - robert



I was specifically referring to the Commons. Well, okay! :)



--
Karthik
http://guilt.bafsoft.net


Re: New Commons SubProject Proposal

2006-02-16 Thread robert burrell donkin
On Wed, 2006-02-15 at 16:52 -0800, Martin Cooper wrote:
> Given its database-centric nature, and the fact that it's a framework, this
> would appear to be more appropriate for the Apache DB Project:
> 
> http://db.apache.org/

+1 but don't let that discourage you :)

jakarta isn't really accepting sub-projects any more: we're very slowly
moving away from that model towards something flatter.

- robert


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: New Commons SubProject Proposal

2006-02-15 Thread Martin Cooper
Given its database-centric nature, and the fact that it's a framework, this
would appear to be more appropriate for the Apache DB Project:

http://db.apache.org/

--
Martin Cooper


On 2/15/06, Karthik Kumar <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm Karthik. I've been working with Jakarta libraries and tools for quite
> some time (including ex. Jakarta projects such as Tomcat, Ant and Struts).
> I've also used commons HTTPClient, logging and DBCP.
>
> Coming to the idea, as a person who uses JDBC, I found it very difficult
> to
> handle the reconfiguration of database connectivity for applications
> without
> having to recompile them. (JNDI configuration was probably the only other
> way to go!) Hence, I decided to work out a set of configuration and
> instancing classes that load and configure connectivity through a
> generalized, extensible framework.
>
> I've currently started off, and have a working sample framework for doing
> this. I've felt that it would be a great idea, if I could work on this
> more,
> and contribute it to the Jakarta project, as a small and useful component.
>
> I'm indicating the intended usage of connectivity here:
>
> Configurator mConfig=new PropertyConfigurator();
> //or:  Configurator mConfig=new XMLConfigurator();
>
> mConfig.configure(ConnectionManager.getInstance());
>
> mCon=ConnectionManager.getInstance().getDefaultConnection();
> mCon1=ConnectionManager.getInstance().getConnection("MySQLDBCP");
> mCon2=ConnectionManager.getInstance().getConnection("Oracle");
> mCon3=ConnectionManager.getInstance().getConnection("OracleJNDI");
>
>
> Currently, I've put up fully functional (although WIP) components (source
> and binary), which allow you a common configuration to connect through
> JDBC,
> JNDI DataSources and DBCP BasicDataSources.
>
> http://guilt.bafsoft.net/downloads/wip/
>
> I was working on Eclipse, and I'm moving the project build process to
> maven.
>
>
> Please let me know about this idea. I'm be willing to contribute my best,
> given a chance.
>
> --
> Karthik
>


New Commons SubProject Proposal

2006-02-15 Thread Karthik Kumar
Hi,

I'm Karthik. I've been working with Jakarta libraries and tools for quite
some time (including ex. Jakarta projects such as Tomcat, Ant and Struts).
I've also used commons HTTPClient, logging and DBCP.

Coming to the idea, as a person who uses JDBC, I found it very difficult to
handle the reconfiguration of database connectivity for applications without
having to recompile them. (JNDI configuration was probably the only other
way to go!) Hence, I decided to work out a set of configuration and
instancing classes that load and configure connectivity through a
generalized, extensible framework.

I've currently started off, and have a working sample framework for doing
this. I've felt that it would be a great idea, if I could work on this more,
and contribute it to the Jakarta project, as a small and useful component.

I'm indicating the intended usage of connectivity here:

Configurator mConfig=new PropertyConfigurator();
//or:  Configurator mConfig=new XMLConfigurator();

mConfig.configure(ConnectionManager.getInstance());

mCon=ConnectionManager.getInstance().getDefaultConnection();
mCon1=ConnectionManager.getInstance().getConnection("MySQLDBCP");
mCon2=ConnectionManager.getInstance().getConnection("Oracle");
mCon3=ConnectionManager.getInstance().getConnection("OracleJNDI");


Currently, I've put up fully functional (although WIP) components (source
and binary), which allow you a common configuration to connect through JDBC,
JNDI DataSources and DBCP BasicDataSources.

http://guilt.bafsoft.net/downloads/wip/

I was working on Eclipse, and I'm moving the project build process to maven.


Please let me know about this idea. I'm be willing to contribute my best,
given a chance.

--
Karthik