That sounds fine to me. In the Hibernate integration most (I think all) calls involve a
long tree of structural nodes with a single "data" node at the bottom. Two
different custom data versions, one for structural, one for the "data" node. It
should be simple for me to implement an optimized Map for that use case; i.e. this
approach shouldn't cost much and will eliminate a lot of hassles.
Do you want a Map, or perhaps an interface:
| public interface DataVersionProvider {
|
| DataVersion getDataVersion(Fqn fqn);
|
| }
|
| If that's the only call JBC is going to make, it would be much simpler to write an
optimized version of that vs. Map, where to be correct I'd have to implement a bunch
of operations that I don't think would be invoked.
|
| We could provide a simple helper impl that takes a Map in the constructor and
delegates to Map.get(Fqn).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163664#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...