[JBoss-dev] Reorganizing connector/jbosscx
Hi, I'm reorganizing the connector/pool stuff so it makes more sense. 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) --jms (soon) -connectionmanager --jboss -security (already there) adapter and connectionmanager are moved from pool. 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. [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.] 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. Any problems with this? Any comments? david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Reorganizing connector/jbosscx
1 1/2 more things: (correction below) Marc has been pushing to simply remove XADataSourceLoader and JDBCDataSourceLoader and have everyone convert to ConnectionFactoryLoaders by hand. Anyone object? If we don't remove it, what do we do with it? put it in a deprecated package??? david jencks On 2001.09.06 12:52:51 -0400 David Jencks wrote: Hi, I'm reorganizing the connector/pool stuff so it makes more sense. 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) --jms (soon) -connectionmanager --jboss -security (already there) adapter and connectionmanager are moved from pool. 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. I meant ConnectionManagerFactories [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.] 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. Any problems with this? Any comments? 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
Re: [JBoss-dev] Reorganizing connector/jbosscx
on 1-09-06 18.52, David Jencks at [EMAIL PROTECTED] wrote: 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. Maybe then use the 1.6.1 version of hsql ? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Reorganizing connector/jbosscx
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? 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. [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? 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. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Reorganizing connector/jbosscx
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
Re: [JBoss-dev] Reorganizing connector/jbosscx
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 This is a better use of java packages to seperate namespace. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Reorganizing connector/jbosscx
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. That would be great. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
