Partition-level Transactions - Entry Processor access "other" cache.

Question

Hi there,
Playing around with Coherence 3.7 and like the look of the new Partition-level Transactions. I'm trying to implement an Entry Processor that accesses an "other" cache in order to create an audit record.
The slides from Brian's SIG presentation show the following code for an example EP doing this:
public void process(Entry entry)
// Update an entry in another cache.
((BinaryEntry)entry).getBackingMapContext(“othercache”).getBackingMap().put(“othercachekey”, value);
The problem I'm facing is the API doesn't seem to have an implementation of BinaryEntry.getBackingMapContext(String cachename). It just has a no-arg version which accesses the cache of the current entry. It's not an error just in the API docs, as the code doesn't compile either.
Any ideas what to do here?
Cheers,
Steve

Answer 1

Care to expand on that, Charlie?
Reason I ask is that since I posted my reply to JK, I noticed that I was getting classcast errors on my audit record insert in the server logs. I had to resort to the use of "converters" to get my newly created audit record into binary format before the "put" into the second (also distributed) cache was successful without errors:
BackingMapManagerContext ctx = ((BinaryEntry)entry).getContext();
ctx.getBackingMapContext("PositionAudit").getBackingMap().put(
ctx.getKeyToInternalConverter().convert(pa.getAuditId()),
ctx.getValueToInternalConverter().convert(pa));
The "PositionAudit" cache is the one I want to create a new entry in each time an EntryProcessor is invoked against Position objects in the "Position" cache. The object I'm creating for that second cache, "pa" is the newly created audit object based on data in the "position" object the entry processor is actually invoked against.
So the requirement is pretty simple, at least in my mind: Position objects in the "positions" cache get updated by an EntryProcessor. When the EntryProcessor fires, it must also write an "audit" record/object to a second cache, based upon data in the Position object just manipulated. As all of the caches are distributed caches - which store their data in Binary format, AFAIK - I still have to do the explicit conversion to binary format of my new audit object to get it successfully "put" into the audit cache.
Seems to still be quite a bit of messing around (including the KeyAssociator stuff to make sure these objects are in the same partitions in the first place for all this to work), but at least I now get "transactionally atomic" operations across both the positions and positions audit caches, something that couldn't be done from an EP prior to 3.7.
As I say, it works now. Just want to make sure I'm going about it the right way. :)
Any comments appreciated.
Cheers,
Steve