geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-393) Alter connector configuration for MDBs in openejb-jar.xml
Date Tue, 26 Oct 2004 00:56:44 GMT
     [ ]
David Jencks commented on GERONIMO-393:

Eliminating the activation spec specification will be committed soon.

I'm not going to implement locating the resource adapter from the message destination link
because I'm moving the admin object deployment outside the resource adapter element, per work
on geronimo-372.  Admin objects won't be associated with a specific resource adapter, although
they will have a module name in their jsr-77 name (unless this turns out to be non-spec-compliant).

> Alter connector configuration for MDBs in openejb-jar.xml
> ---------------------------------------------------------
>          Key: GERONIMO-393
>          URL:
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: connector
>     Versions: 1.0-M2
>     Reporter: Aaron Mulder
>     Assignee: David Jencks

> It is not (ever) necessary to manually specify the activation-spec-class for a message
driven bean in openejb-jar.xml.
> Once the resource adapter has been identified, the ActivationSpec must go with a particular
messagelistener-type.  The messaging-type is always configured for the MDB (if omitted from
ejb-jar.xml, it specifically defaults to javax.jms.MessageListener), and the messagelistener-type
must be unique in the inbound-resourceadapter (due to messagelistener-type-uniqueness).  Given
the resource adapter and messaging-type, the ActivationSpec is determined as well.
> The resource adapter must still be specified in openejb-jar.xml unless the MDB uses a
message-destination-link in ejb-jar.xml (in which case the adminobject linked to identifies
the resource adapter).  Thus, the resource-adapter-name should be optional in openejb-jar.xml,
and a runtime check should be added that throws a deployment error if the resource adapter
cannot be identified (no resource-adapter-name in openejb-jar.xml and no message-destination-link
in ejb-jar.xml)

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