[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Resolved] (AMQ-3560) Destinations do not implement javax.resource.Referenceable and will not
From:       "Gary Tully (JIRA)" <jira () apache ! org>
Date:       2013-07-31 16:57:49
Message-ID: JIRA.12528333.1319236243584.145211.1375289869132 () arcas
[Download RAW message or body]


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

Gary Tully resolved AMQ-3560.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.6.0)
                   5.9.0

fix in http://svn.apache.org/r1508958

example admin objects from eap standalone.xml:{code}
            ....
            <admin-objects>
              <admin-object class-name="org.apache.activemq.command.ActiveMQQueue"
                            jndi-name="jms_ee_mdb_mdb_rec_MDB_QUEUE" \
                pool-name="jms_ee_mdb_mdb_rec_MDB_QUEUE">
                <config-property \
name="PhysicalName">tck6.jms_ee_mdb_mdb_rec_MDB_QUEUE</config-property>  \
                </admin-object>
              <admin-object class-name="org.apache.activemq.command.ActiveMQQueue" \
jndi-name="MDB_QUEUE_REPLY"  pool-name="MDB_QUEUE_REPLY">
                <config-property \
name="PhysicalName">tck6.MDB_QUEUE_REPLY</config-property>  </admin-object>
              <admin-object class-name="org.apache.activemq.command.ActiveMQTopic"
                            jndi-name="jms_ee_mdb_mdb_rec_MDB_TOPIC" \
                pool-name="jms_ee_mdb_mdb_rec_MDB_TOPIC">
                <config-property \
name="PhysicalName">tck6.jms_ee_mdb_mdb_rec_MDB_TOPIC</config-property>  \
                </admin-object>
              <admin-object \
class-name="org.apache.activemq.pool.XaPooledConnectionFactory"  \
jndi-name="jms/RegularQueueConnectionFactory"  \
                pool-name="RegularQueueConnectionFactory">
                <config-property \
name="brokerUrl">tcp://localhost:61616</config-property>  <config-property \
name="tmFromJndi">true</config-property>  </admin-object>
            </admin-objects>
          </resource-adapter>

{code}
                
> 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
> Assignee: Gary Tully
> Labels: destinations, jca, jndi
> Fix For: 5.9.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
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]