I'll work on that too, then.
Do we want to add some info for the common transaction params?
I mean, this is common between the XA/local transactional connectors, so we might break it out, or we can just treat it as another property and not give it special typing.
I think the current ideas are adequate, although maybe we want to add more typing info. What do you think?
- <xsl:when test="track-connection-by-tx">
- <xsl:when test="(xa-transaction) and (track-connection-by-tx)"> <attribute name="TrackConnectionByTx">true</attribute> <attribute name="LocalTransactions">false</attribute> </xsl:when> - <xsl:when test="(xa-transaction)"> <attribute name="TrackConnectionByTx">false</attribute> <attribute name="LocalTransactions">false</attribute> </xsl:when>
Please restate your question.
"We still need the connection properties (passed the jdbc driver)
or xa datasource properties (to configure the xads)"
Do you want to call:
Or do you want to call:
TxMetaData txmd = new TxMetaData();
The first is the most generic, which I think would be adequate.
TrackConnectionByTx is a pooling parameter. Nothing to do with properties.
It is only loosly related with transaction support in that
1) It is obviously irrelevent for NoTx
2) Must be true for LocalTx
Ah. Okay. I think I get how this needs to be chopped up now. I'm going to work on programmatically creating Factory, Pool, and ConnectionManager using the new metadata.
I noticed the RAR deployer is pretty different between 3.2.4RC2 and jboss-head. Which one should I be coding/testing against? I can do current now and head later, but you may just want to skip to head. Doesn't matter to me.
Is the RARDeployment class one of the main ones I'm going to have to rework? It appears so, but it uses a DeploymentInfo passed into its constructor.
Just looking at the dependency tree in the generated jboss-service.xml (from the XSL), RARDeployment comes before the Pool and the ConnectionManager in the order of things.
What I'm doing is letting the RARDeployer be set up using XML, then starting programmatically from there.
Talk to you later,
Okay, I'm trying to register, create, and start a ManagedConnectionFactory (connectionmanager.RARDeployment) programmatically.
I'm getting fairly close, but when it tries to find my test connection factory class, it can't find it.
I've added the .rar to deploy, and the MBean is there (I do a MBeanServer.isRegistered() on its ObjectName.
2004-06-22 20:24:32,348 ERROR [org.jboss.resource.connectionmanager.RARDeployment] Could not find ManagedConnectionFactory class: org.jboss.test.jca.adapter.TestManagedConnectionFactory
Do I need to be using a specific classloader somehow, or is there a way for an MBean for OldRARDeployment to be registered w/o loading the classes? I thought RARDeployer did that, but I'll check.
I'm using a pretty custom configuration, somewhat akin to Andy Oliver's unit test stuff, and I just stuff all the necessary MBeans in the top-level/default jboss-service.xml. This could be the source of my problem as well.