Tom
unread,May 18, 2009, 4:22:41 AM5/18/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jcrom
Hello,
first of all a big compliment on creating such a well working and
simple OCM tool. I have reviewed a few and this is definitely my
favourite.
The objective behind this post is to learn from the development team
what they think about the following:
- Assuming I am right, then every call to the JCROM tool will result
in a new object (or set of objects) being created, i.e. objects are
never cached and reused anywhere
- that means that for objects created through separate fromNode()
calls, the == operator will never return true.
For a project I am involved in, we are quite keen to have a per-thread
object caching mechanism that recognizes existing (i.e. previously
loaded objects) and resuses them, mainly with the aim of creating and
maintaing a coherent object graph.
We plan to do an in-house enhancement to add this to the JCROM tool.
I would be very happy to receive any feedback about this from the
development team.
Cheers
Tom
PS: One obvious difficulty in implementing the above is that the
fromNode() method takes several arguments, which result in objects
with different child activation depths. For now we assume that the
default fromNode() method is called, i.e. maximum depth and no name
filtering.