[
http://jira.jboss.com/jira/browse/JBAS-1437?page=comments#action_12345660 ]
Andrew Craig commented on JBAS-1437:
------------------------------------
As one part of this, it would be very useful if the rar-name was specified, there could be
a way of saying "relative to the current deployment level". For example, given
a -ds.xml file:
<connection-factories>
<no-tx-connection-factory>
<jndi-name>MyConnectorReference</jndi-name>
<rar-name>localConnector.rar</rar-name>
<connection-definition>test.andrew.localconnector.LocalConnectorConnectionFactory</connection-definition>
</no-tx-connection-factory>
</connection-factories>
This only works if localConnector.rar is deployed at the root server level. A better
approach would be a way of having it something like:
<connection-factories>
<no-tx-connection-factory>
<jndi-name>MyConnectorReference</jndi-name>
<rar-name>#localConnector.rar</rar-name>
<connection-definition>test.andrew.localconnector.LocalConnectorConnectionFactory</connection-definition>
</no-tx-connection-factory>
</connection-factories>
Whereby we now know to use the .rar inside the current context (i.e. either the .ear or
.sar that the .rar was located in). This way the same -ds.xml file can be used in two
separate applications without having to modify the file.
RAR MetaData Repository
-----------------------
Key: JBAS-1437
URL:
http://jira.jboss.com/jira/browse/JBAS-1437
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JCA service
Reporter: Adrian Brock
Priority: Minor
Forums Discussion Thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48681
Implement a RAR MetaData repository.
There are two use cases of this object:
* A tool wants to retrieve information about how to configure a RAR deployment
either inbound/outbound or admin object
* Avoiding the need to specify the rar-name in jboss.xml, -ds.xml or admin object
deployments when
only one rar implements the connection definition or message listener.
Design:
1) When a RAR is deployed/undeployed update the repository with information about the RAR
including
cross references by
* ConnectionDefinition
* MessageListener
* AdminObject
2) When an MDB is deployed without identifying the rar, use the repository to try to
guess the RAR
3) When a ConnectionFactory is deployed without identifying the rar, use the repository
to try to guess the RAR
4) When an AdminObject is deployed without identifying the rar, use the repository to try
to guess the RAR
The algorithm to guess the RAR is
a) Is there only one RAR implementing the object
b) If there is more than one RAR, is there a specific RAR in the same top level
deployment (EAR)
as the referencing deployment
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira