Hi Siva,
On 03/14/2013 03:58 PM, Sivakumar Thyagarajan wrote:
>> * Proxy implements all public business methods of the actual message
>> endpoint class
>
> The current Message Inflow contracts enable asynchronous message
> delivery and through the generic MEF and MessageEndpoint interfaces
> enable this delivery to any message endpoint. The MDB scenario is just
> one standard example of an asynchronous message listener in the EE
> platform, but the message inflow contracts are not tied to MDBs.
>
> Therefore, the behaviour of the MDB container (as in requirements on the
> proxy of the MDB that it returns as a MessageEndpoint) is best defined
> in the MDB spec. Our Message Inflow spec would only describe the general
> requirements that is valid for all types of MessageEndpoints (and ensure
> that these requirements doesn't prevent the new MDB container
> requirements).
>
But adding the getEndpointClass() to MessageEndpointFactory will require
other implementations to follow the above requirement.
So this should be explicit in the spec text IMHO.
Best regards,
Jesper