You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Gary Tully (Updated) (JIRA)" <ji...@apache.org> on 2011/10/26 00:34:32 UTC

[jira] [Updated] (AMQ-3560) Destinations do not implement javax.resource.Referenceable and will not be registerable in JNDI by some compliant JCA containers.

     [ https://issues.apache.org/jira/browse/AMQ-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-3560:
----------------------------

    Fix Version/s: 5.6.0

another good candidate for 5.6, should be an easy fix.
                
> Destinations do not implement javax.resource.Referenceable and will not be registerable in JNDI by some compliant JCA containers.
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3560
>                 URL: https://issues.apache.org/jira/browse/AMQ-3560
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.1
>         Environment: JBoss 7.1.0.Alpha2 / ironjacamar 1.0.4
>            Reporter: Mike G
>              Labels: destinations, jca, jndi
>             Fix For: 5.6.0
>
>
> According to the JCA spec, AdminObjects are only guaranteed to be bound in JNDI by the JCA provider if javax.resource.Referenceable is implemented.  See 13.4.2.3 "Administered Objects".  A JMS provider is free to provide AdminObjects that implement only javax.naming.Referenceable in an otherwise unmanaged environment, but a resource adapter must allow the application server/jca container to use its own ObjectFactory and call setReference() on the admin objects that need to be looked up.  See 20.6 JNDI Configuration and Lookup.
> This is a problem for users using an application server such as the current release of AS7 which will not bind AdminObjects otherwise.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira