geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (GERONIMO-362) Problem with proxies for ConnectionFactories
Date Tue, 05 Oct 2004 22:24:32 GMT
The following comment has been added to this issue:

     Author: David Jencks
    Created: Tue, 5 Oct 2004 3:24 PM
I've modified connection factory  deployment so you can specify more interfaces you want the
proxy to implement.  Heres an example of the xml excerpted from a geronimo-ra.xml

                    <config-property-setting name="OutboundStringProperty1">newvalue1</config-property-setting>

I plan to modify the admin object handling back to return a proxy, but the proxy will extend
the (javabean) admin object class rather than interface.
View this comment:

View the issue:

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

     Status: Unassigned
   Priority: Major

    Project: Apache Geronimo

   Reporter: Jeremy Boynes

    Created: Tue, 5 Oct 2004 12:00 PM
    Updated: Tue, 5 Oct 2004 3:24 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