[jboss-jira] [JBoss JIRA] Resolved: (JBJCA-19) RAR MetaData Repository

[Jesper Pedersen (JIRA)]

     [ https://issues.jboss.org/browse/JBJCA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesper Pedersen resolved JBJCA-19.
----------------------------------

    Resolution: Out of Date


> RAR MetaData Repository
> -----------------------
>
>                 Key: JBJCA-19
>                 URL: https://issues.jboss.org/browse/JBJCA-19
>             Project: IronJacamar
>          Issue Type: Task
>          Components: Core
>            Reporter: Adrian Brock
>            Assignee: Jesper Pedersen
>            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira