Simplified TranQL data source and AMQ connection factory?

[Dain Sundstrom]

What do you think about creating simplified, large-grained factory  
beans for a TranQL data source and an AMQ connection factory?  I'm  
thinking of an object that is configured like this:

   <bean id="dataSource" class="org.jencks.factory.TranQLDataSource">
     <property name="driverName" value="org.hsqldb.jdbcDriver"/>
     <property name="url" value="jdbc:hsqldb:."/>
     <property name="user" value="sa"/>
     <property name="password" value=""/>

     <property name="transactionManager" ref="transactionManager"/>
     <property name="poolMaxSize" value="25"/>
     <property name="transaction" value="xa"/>
   </bean>

   <bean id="jmsConnectionFactory"  
class="org.jencks.factory.ActiveMQConnectionFactory">
     <property name="serverUrl" value="vm://localhost"/>
     <property name="userName" value="foo"/>
     <property name="password" value="bar"/>

     <property name="transactionManager" ref="transactionManager"/>
     <property name="poolMaxSize" value="25"/>
     <property name="transaction" value="xa"/>
   </bean>

I'm thinking we create a subclass of the  
ActiveMQManagedConnectionFactory and Tranql DataSourceMCF that adds  
the properties from ConnectionManagerFactoryBean.  Then when getObject
() is called, we call super.getObject() to get the MCF, create a  
conection manager, and then return mcf.createConnectionFactory
(connectionManager).

This will reduce the most common usages to two beans: transaction  
manager and data source or jms cf.

I think we may be able to do the same for message driven POJOs.

Anyway, should I take a crack at implementing these, or has someone  
else already done this.

-dain

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[James.Strachan]

Sounds great to me! Folks have often struggled to configure Jencks
particularly when doing inbound & outbound stuff - so I'm all for
making more clever factory beans so that the things most users want
just work unless they explicitly override properties etc.

The simpler the XML is for users to use Jencks the better IMHO.


On 8/3/06, Dain Sundstrom <dain@...> wrote:

> What do you think about creating simplified, large-grained factory
> beans for a TranQL data source and an AMQ connection factory?  I'm
> thinking of an object that is configured like this:
>
>    <bean id="dataSource" class="org.jencks.factory.TranQLDataSource">
>      <property name="driverName" value="org.hsqldb.jdbcDriver"/>
>      <property name="url" value="jdbc:hsqldb:."/>
>      <property name="user" value="sa"/>
>      <property name="password" value=""/>
>
>      <property name="transactionManager" ref="transactionManager"/>
>      <property name="poolMaxSize" value="25"/>
>      <property name="transaction" value="xa"/>
>    </bean>
>
>    <bean id="jmsConnectionFactory"
> class="org.jencks.factory.ActiveMQConnectionFactory">
>      <property name="serverUrl" value="vm://localhost"/>
>      <property name="userName" value="foo"/>
>      <property name="password" value="bar"/>
>
>      <property name="transactionManager" ref="transactionManager"/>
>      <property name="poolMaxSize" value="25"/>
>      <property name="transaction" value="xa"/>
>    </bean>
>
> I'm thinking we create a subclass of the
> ActiveMQManagedConnectionFactory and Tranql DataSourceMCF that adds
> the properties from ConnectionManagerFactoryBean.  Then when getObject
> () is called, we call super.getObject() to get the MCF, create a
> conection manager, and then return mcf.createConnectionFactory
> (connectionManager).
>
> This will reduce the most common usages to two beans: transaction
> manager and data source or jms cf.
>
> I think we may be able to do the same for message driven POJOs.
>
> Anyway, should I take a crack at implementing these, or has someone
> else already done this.
>
> -dain
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email