I have an entity bean which is marked as NonShared with commit option A. a new backend application is coming up which can update the data via direct jdbc calls. this happens rarely but when that will happen my entity bean if already cached will get out of sync with the change updated . I have two options here.
1. Make the entity bean shared so that it can come in sync with database. 2. Stop updating via direct jdbc calls, go via ejb only. But I am thinking, if I can invalidate the cache for that particular bean through an api call But do not know how to do it or there is some other better option? My Jboss is in non-cluster mode. thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030471#4030471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030471 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
