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 changes updated .
I have two options here.
1. Make the enetity 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 But do not know how to do it or there is some other better option?
Jboss in non-cluster mode.
You'll have better luck posting on the EJB forum. The JBoss Cache project isn't used in EJB2 entity caching.