[jira] Commented: (QPID-2969) AMQConnectionFactory is not Serializable

["Andrew Kennedy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968628#action_12968628 ] 

Andrew Kennedy commented on QPID-2969:
--------------------------------------

Are you sure? See also AMQQueue, AMQDestination etc. if this is the case.

However, I believe JNDI providers can store and retrieve objects that implement one of either java.io.Serializable, java.rmi.Remote, or javax.naming.Referenceable, the last of which we implement in all JNDI storable objects. We probably *should* implement Serializable, just because there are applications (Mule springs to mind) that like to attempt to serialize AMQDestination or similar objects.

See also, for example: http://docs.jboss.com/jbossas/javadoc/4.0.5/server/org/jboss/naming/NonSerializableFactory.html

> AMQConnectionFactory is not Serializable
> ----------------------------------------
>
>                 Key: QPID-2969
>                 URL: https://issues.apache.org/jira/browse/QPID-2969
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.8
>            Reporter: Gordon Sim
>
> It should be, in order to allow it to be stored in JNDI.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org