On 2001.09.06 15:10:13 -0400 Toby Allsopp wrote:
> On Thu, Sep 06, 2001 at 12:52:51PM -0400, David Jencks wrote:
> > Hi,
> > 
> > I'm reorganizing the connector/pool stuff so it makes more sense.
> 
> Hooray!
> 
> > Here's my proposed directory structure
> > 
> > under org/jboss/resource
> > 
> > -adapter
> > --jdbccommon (classes shared between 2 jdbc wrapper rar's)
> > --jdbclocal (classes for jdbc non xa wrapper)
> > --jdbcxa (classes for jdbc xa wrapper)
> 
> Perhaps
> -adapter
> --jdbc
> ---local
> ---xa
> ?
> Not important, on the whole.
> 
> > --jms (soon)
> 
> I'm not completely sure that I like the actual resource adapters
> as part of JBossCX.  Nah, actually, as long as they're built into
> separate RARs I don't mind at all.  Don't mind me.
> 
> > -connectionmanager
> > --jboss
> > 
> > -security (already there)
> > 
> > adapter and connectionmanager are moved from pool.
> 
> So JBossPool still exists and contains the generic object pooling
> code?

Yes, its a pretty small package now.  Someone suggested moving it into
server, I don't have arguments one way or another.  One step at a time.
> 
> > I want to make jbosscx contain everything except the adapters (which
> turn
> > into .rars and are deployed separately).  I want to make jbosscx into a
> > .sar containing the mbean configuration for RARDeployer and the 3
> > connectionmanagerfactoryloaders.
> 
> Cool.  I'm not really happy with the name
> ConnectionManagerFactoryLoader; it sounds and looks too much like
> ConnectionFactoryLoader.  If you have a better idea for the name
> of this, please feel free to change it.

I agree.  Between ConnectionManagerFactory, ManagedConnectionFactory,
ConnectionFactory.....
everything has the same words in different orders!!!
I don't have a better idea.  I'm hoping with the
ConnectionManagerFactoryLoader hidden in a sar and all user
ConnectionFactoryLoader configuration in separate *-service.xml files no
one will see the ConnectionManagerFactoryLoader and get confused ;-)
> 
> > [As a possible future step I'd like to rewrite the
> > ConnectionManagerFactoryLoader stuff to avoid the x license, share
> common
> > code, and eliminate the distinction between ConnectionManager and
> > JBossConnectionManager.  Maybe even implement the
> JBossConnectionListener
> > stuff so you don't have to get each connection within a transaction.] 
> 
> I'm not sure what you mean about the X license. CMFL is LGPL.  Are
> you referring to the CMs themselves? 
yes I got confused (see commentary above)
> 
> JBossConnectionManager only exists so the the Minerva connection
> managers could be independent of JBoss.  Kill kill kill.
> 
> > In a related issue, I'd like to make the hypersonic/defaultds
> configuration
> > into a hsql-service.xml or possibly a sar including the hypersonic
> database
> > itself.
> 
> Sounds good.
> 
> Toby.
> 

Thanks
david jencks
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to