Since we have this thread going, I had a related question.
A while back I was discussing issues related to caching data in a Stateful
session bean that communicates with many Entity beans. For good measure,
let's say the entity bean(EB) is used by more than one "client"- in addition
to the Stateful session bean(SSB). In other words(IOW:-), the SSB does not
know when the EB data is changed without making an explicit method call.
Could JMS help here?
If the stateful session bean wants to make sure it's cached data doesn't get
stale, it could just listen for the "data updated" event. The message could
even contain the new data.
Thus, data consistency is achieved by just one-trip: Entity Bean to Stateful
Session Bean.
It's also asynchronous. It's also different from the "usual way" in which
EJB apps are modeled in the sense that we have an Entity Bean communicating
with the session bean(albeit indirectly).
The immediately obvious problem is that this would(could?) break the
one-client/one-Stateful session bean requirement, and hence might(will?)
throw an exception. And even if it did, is there a way to still achieve what
I'm thinking here?
Could someone less clueless in the EJB/JMS integration issues please
enlighten me:~?
Thanks for your input,
Murali Krishna Devarakonda
e: [EMAIL PROTECTED]
===========================================================================
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".
