> <code-example-using-jms />
>
> >I'm confused by this. Can you please explain to me what is so bad with
> >using JMS to solve this?
>
>
> The problem is that the code example is only valid in the client, it cannot
> be used
> inside an entity bean. So we must implement an RMI-or-like front-end that
> manages entity beans and JMS, and therefore lose all the nice container
> features.
Can you explain why an EJB-bean cannot use this code? I think it can.
If you are thinking about the EJB Permission-restrictions, forget that.
It doesn't apply here, since the JMS-implementation has the required
permissions.
Are there any other reasons?
regards,
Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
