Hi Mani
Mani wrote:
>
> Hi Joel,
> >Yes. You can also recieve messages, but you have to do it in a pseudo EJB >client -
>not
> >a nice solution. Later EJB specs will clarify this.
> So I've to use a Unix Damon or NT service that will get the message from JMS and
>send it to the EnterpriseBean that is running within the EJBContainer?
Or something like this. You could run the message monitor in the same VM as the
EJB container (don't confuse an EJB container with a VM - one VM can run multiple
EJB containers, and other java code which is not as restricted as code running
'within' the container).
>
> >Data consistancy.
> Can you explain more about the "Data consistency"?
If your EJB is not listening to JMS messages from other sources changing data in
the global business model then the EJB server may end up caching data which is not
consistant with the data in the underlying datastores. Similarly if a client is
using weak consistancy (copying all the relevent data from a bean down to the
client side) and the EJB copy of the data changes you need to be able to asyncronously
notify the client that an update has occurred. This may be done via versioning
the data in EJBs and either JMS notification or client based polling to detect changes.
>
> -Mani
Hope this clarifies the situation.
Joel Crisp, Senior Java Architect, SUN PS Java Center UK
===========================================================================
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".
