geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (GERONIMO-362) Problem with proxies for ConnectionFactories
Date Wed, 06 Oct 2004 05:46:35 GMT

   The following issue has been closed.

   Resolver: David Jencks
       Date: Tue, 5 Oct 2004 10:45 PM

I've now updated the admin object stuff so the proxy extends the admin object implementation
class, not the interface.
View the issue:

Here is an overview of the issue:
        Key: GERONIMO-362
    Summary: Problem with proxies for ConnectionFactories
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Apache Geronimo
   Fix Fors:

   Assignee: David Jencks
   Reporter: Jeremy Boynes

    Created: Tue, 5 Oct 2004 12:00 PM
    Updated: Tue, 5 Oct 2004 10:45 PM

The ActiveMQ Connector is being deployed with the connectionfactory-interface being set to
javax.jms.ConnectionFactory which is a superclass of QueueConnectionFactory and TopicConnectionFactory.
A resource-ref that references this with the interface defined as one of the subclasses does
not work as the generated proxy does not implement the subclasses.

Being able to deploy a single instance of the superclass seems useful but we need to verify
if that is compliant. If it is, then we would also need to ensure the proxy implements the
appropriate interfaces (specifically the subclass being requested).

Adding proxies is useful in that allows access to the resource to be shut off or suspended
in repsonse to the target's lifecycle. However, in some cases those proxies may be passed
back to the resource and may cause problems unless they are unwrapped to expose the original

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message