-
-
2. Re: JCA1.0 with JBOSS4.X
jason1 Mar 21, 2005 7:13 PM (in response to ecoray)Hi,
Could we get more descriptive about what needs to be modified for 1.0 to deploy in JBoss 4.0.1?
I am struggling converting my JCA 1.0 descriptor as described in the jboss-upgrade4.pdf and the Wiki. They describe 2 changes to make:
1. Change <adaptor-display-name> to <rar-name>
2. Add <connection-definition>YOUR CF INTERFACE HERE</connection-definition>
However, after this change, it blows on deployment. I've turned on TRACE logging for org.jboss.resource and it tells me nothing.
17:03:56,917 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss.jca:name=ArcSDEConnector,service=TxCM
state: CONFIGURED
I Depend On: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionPool
jboss.jca:service=CachedConnectionManager
jboss:service=TransactionManager
Depends On Me: jboss.jca:name=ArcSDEConnector,service=ConnectionFactoryBinding
ObjectName: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionPool
state: CONFIGURED
I Depend On: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionFactory
Depends On Me: jboss.jca:name=ArcSDEConnector,service=TxCM
ObjectName: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionFactory
state: CONFIGURED
I Depend On: jboss.jca:name='ArcSDE JCA Adapter',service=RARDeployment
Depends On Me: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionPool
ObjectName: jboss.jca:name=ArcSDEConnector,service=ConnectionFactoryBinding
state: CONFIGURED
I Depend On: jboss.jca:name=ArcSDEConnector,service=TxCM
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.jca:name='ArcSDE JCA Adapter',service=RARDeployment
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionFactory -
3. Re: JCA1.0 with JBOSS4.X
adrian.brock Mar 21, 2005 7:32 PM (in response to ecoray)The clue is in the question....
"jason@cdot" wrote:
1. Change <adaptor-display-name> to <rar-name>
....
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.jca:name='ArcSDE JCA Adapter',service=RARDeployment
state: NOTYETINSTALLED
I Depend On:
Depends On Me: jboss.jca:name=ArcSDEConnector,service=ManagedConnectionFactory
do you really have a rar file named "ArcSDE JCA Adapter", I would expect it
to end in .rar (at least if you expect it to be deployed as a rar by JBoss)?
If you feel it is not descriptive enough, you are free to go through all the pages
on the WIKI and improve them:
http://www.jboss.org/wiki/Wiki.jsp?page=HowDoIDeployMyResourceAdapter
http://www.jboss.org/wiki/Wiki.jsp?page=ConfigConnectionFactory
http://www.jboss.org/wiki/Wiki.jsp?page=DSdotXML
etc...
You can even provide a new page that shows step by step how to perform certain tasks. -
4. Re: JCA1.0 with JBOSS4.X
jason1 Mar 22, 2005 11:44 AM (in response to ecoray)Thanks, Adrian. That worked for me. I also made improvements to the Wiki as you requested.
Specifically, I detailed:
1.) rar-name is not "logical", but the real file name. Logical vs. actual can be confusing especially since other deployment descriptors like EJB use ejb-name as a totally logical name.
2.) connection-definition is the ConnectionFactory interface, not implementation class. This was not evident in the previous Wiki posting unless you check the JavaDoc on JmsConnectionFactory and see it is an interface.
3.) Made a note that the DTD for jboss-ds_1_0.dtd lists neither rar-name nor connection-definition in it, which is completely confusing!!! and how to work around this short-coming. -
5. Re: JCA1.0 with JBOSS4.X
adrian.brock Mar 23, 2005 1:26 PM (in response to ecoray)"jason@cdot" wrote:
3.) Made a note that the DTD for jboss-ds_1_0.dtd lists neither rar-name nor connection-definition in it, which is completely confusing!!! and how to work around this short-coming.
They would have been better named
jboss-ds_3_2.dtd and jboss-ds_4_0.dtd
The reference to the spec level is an indirect mapping
and a function of what each version supports
not the one you should use based on your targetted api.