David Jencks wrote:
> On 2002.08.27 09:19:04 -0400 Igor Fedorenko wrote:
>
[skipped]
>>
>>How do I deploy rm specific wrapper? Am I right that there is a
>>prototype RARDeployment instance
>>(jboss.jca:service=RARDeployment,name=JBoss JDBC XATransaction
>>ResourceAdapter) that defines wrapper to be used? Should I deploy such
>>prototype for each resource manager or it is better to get rid of
>>prototype and provide all necesary info in -ds.xml?
>
>
> I'm thinking:
>
> 1. write OracleManagedConnectionFactory extending
> XAManagedConnectionFactory, with all the properties the Oracle XADataSource
> has exposed as mcf properties
>
> 2. write a ra.xml for it, listing the config-properties with, if
> appropriate, default values
>
> 3. modify connector/build.xml to package this into a oracle-xa-jdbc.rar
>
> 4. modify the xsl to process an oracle-xa-datasource element, so it will
> process exactly the config properties available for the oracle wrapper.
>
> The mbean naming is too confusing at the moment, there are 2 things
> claiming to be RARDeployments. One of them basically holds the ra.xml from
> the .rar, the other should be called a ManagedConnectionFactory. In fact
> the second can be an actual managed connectin factory instance deployed as
> an xmbean.
>
> Is this any clearer? Please ask if you have more questions.
I am new to this JCA stuff and it looks too complicated to me. Would not
it be easier to have only one RARDeployment that gets all necessary
parameters from *-ds.xml file? Keep in mind that we are talking
specifically about JDBC XA connection factories, so we can provide all
reasonable defaults with xslt template. For example, oracle-xa-ds.xml
would look like
<datasources>
<xa-datasource>
<jndi-name>OracleDS</jndi-name>
<display-name>JBoss JDBC XATransaction ResourceAdapter</display-name>
<managedconnectionfactory-class>
org.jboss.resource.adapter.jdbc.xa.oracle.OracleXAManagedConnectionFactory
</managedconnectionfactory-class>
<xa-datasource-class>
org.jboss.resource.adapter.jdbc.xa.oracle.OracleXADataSource
</xa-datasource-class>
<xa-datasource-property name="URL">
jdbc:oracle:oci8:@tc</xa-datasource-property>
<xa-datasource-property name="User">
scott
</xa-datasource-property>
<xa-datasource-property name="Password">
tiger
</xa-datasource-property>
</xa-datasource>
</datasources>
Note that this way we can have generic xslt script (i.e. no vendor
specific tags) and keep all rm specific logic in wrapped factories.
--
Igor Fedorenko
Think smart. Think automated. Think Dynamics.
www.thinkdynamics.com
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
