search

javaee / ejb-spec

See javax.ejb project for API. Contains legacy issues only.
https://github.com/javaee/javax.ejb
6 stars 1 forks source link

Allow listener method to always be determined at runtime by resource adapter #126

Open glassfishrobot opened 9 years ago

glassfishrobot commented 9 years ago

This is intended to be the next step in MDB/connector improvements following the implementation of #60 in EJB 3.2.

In EJB 3.2, section 5.6.5 "Message-Driven Bean with No-Methods Listener Interface" added support for a new type of MDB, one in which the listener method had no methods. In this case the proxy supplied to the resource adapter by the createEndpoint method exposed all the public methods of the bean class.

This allows the callback method to be determined by the resource adapter at runtime, by examining annotations on each method.

However this feature is only available if the MDB implements a no-methods listener interface. This restriction was added purely because this feature was added late in the development EJB 3.2 and it was considered "risky" to make it available in other cases..

It proposed that this restriction now be removed, so that the proxy supplied to the resource adapter by the createEndpoint method exposes all the public methods of the bean class, irrespective of what the listener interface is or whether there is a "listener" interface at all.

This change would then allow the JMS specification to define a set of new annotations for JMS MDBs without the need to define a no-method listener interface.

Affected Versions

[3.2]

glassfishrobot commented 9 years ago

Reported by @nigeldeakin

glassfishrobot commented 9 years ago

@nigeldeakin said: See also #115 (Flexible Connector Scanning)

glassfishrobot commented 9 years ago

@nigeldeakin said: Note that if a MDB does not implement a listener interface then the EJB container cannot use this to work out what resource adapter to use. This is another reason why a standard way is needed to specify the resource adapter used by a MDB (logged as #127).

glassfishrobot commented 9 years ago

Was assigned to mvatkina

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA EJB_SPEC-126

arjantijms commented 7 years ago

@dblevins @nigeldeakin Unfortunately nothing at all seems to have been done for this during the entire cycle of EE 8.

What do you all think, how to continue with this?