Hi Wes :)
There is a thread that we started not too long ago on the topic. The way
we have handled it is by creating our own instance of a cache manager
for JBoss that is able to mark beans as dirty (thus are reloaded through
ejbLoad on the next call). We have JMS setup so that our "traditionnal"
application posts messages to the cache manager when making changes.
A similar approach could be taken using triggers in the tables concerned
I think... As long as your database allows you to call on external
functions in triggers (as MS SQL does).
Feel free to ask more questions if you aren't sure what the heck I'm
talking about :)
HTH,
Daniel
-----Message d'origine-----
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Envoy� : 26 avril, 2001 14:03
� : [EMAIL PROTECTED]
Objet : [JBoss-user] External Data Modification
I know I've seen some discussion of this in the past, but it never
affected
me until today, and I am having no luck searching the archives. I
would
like to know the best way to handle non-EJB modifications to the
underlying
data of an Entity Bean. The bean is not reloaded until it is over aged.
I
would apprecate hearing from anyone else who has encountered this
problem.
Wes
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
