You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mike G (Created) (JIRA)" <ji...@apache.org> on 2011/10/22 00:32:32 UTC

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

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


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

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

Posted by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3560.
-----------------------------

    Resolution: Won't Fix

This sounds like its not needed then.  Closing out
                
> 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

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

Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136173#comment-13136173 ] 

Timothy Bish commented on AMQ-3560:
-----------------------------------

ActiveMQDestination already extends JNDIBaseStorable which in turn implements Recoverable so I'm not sure what it is we are missing here.  Perhaps some addition information is needed on this.
                
> 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

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

Posted by "Timothy Bish (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136173#comment-13136173 ] 

Timothy Bish edited comment on AMQ-3560 at 10/26/11 9:26 PM:
-------------------------------------------------------------

ActiveMQDestination already extends JNDIBaseStorable which in turn implements Referencable so I'm not sure what it is we are missing here.  Perhaps some addition information is needed on this.
                
      was (Author: tabish121):
    ActiveMQDestination already extends JNDIBaseStorable which in turn implements Recoverable so I'm not sure what it is we are missing here.  Perhaps some addition information is needed on this.
                  
> 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

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

Posted by "Gary Tully (Updated) (JIRA)" <ji...@apache.org>.
     [ 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

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

Posted by "Mike G (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137155#comment-13137155 ] 

Mike G commented on AMQ-3560:
-----------------------------

JNDIBaseStorable implements javax.naming.Referenceable not javax.resource.Referenceable.

"An administered object instance, that implements ResourceAdapterAssociation
interface must ensure that its Java class and the interface type implements
javax.resource.Referenceable and java.io.Serializable interfaces. This
enables an application server to store the administered object instance in the JNDI
naming environment. Refer to Section 20.6.3, “Scenario: Referenceable” on
page 20-19 for details on the JNDI reference mechanism."

However, it does sound like this requirement is only for RA Associated objects.  On the other hand, it says do this to enable JNDI storage.  Also Ironjacamar was patched to no longer require adminobjects to implement javax.resource.Referenceable for JNDI binding, making this no longer a problem for AS7 users.  Perhaps this issue should be rejected?
                
> 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