I'm trying to implement some code to work with Oracle XML types. That being said, I need to do it as a BMP as accessing sys.xmltype from oracle requires a special oracle-specific library.
I can easily do the database part, but where I'm getting stumped is I would like to use commit-option A, or maybe even D...
This would be in a cluster of hosts, so when one updates the EJB the others need to flush their cache. Is this supported in JBoss 3.2.3?
Or maybe there's a better way to handle it? Possibly by somehow explicitly expiring the other entity instances via a custom mbean + clustercall?
I see the JGCacheInvalidationBridge in the cluster.xml, but my BMPs (using default BMP commit option, not sure what that is) do seem to always think they are current on each node.
And, yes, the cluster is indeed established (our services explicitly complain if they are the only one in the cluster)
Hope that made sense... -David
Sorry, ignore that post.
For some reason I was completely missing the cache invalidation section of the clustering guide.