[jboss-dev-forums] [Design of POJO Server] - Re: To merge or not to merge?

[scott.stark@jboss.org]

This is what I was referring to previously about a unified api for traversing/merging the various scopes of data. This also intersects with the discussion on how overlapping annotation collections are merged. There is a tradeoff between having a framework that generally can build up something like a JndiBinding vs having to write the merge logic in terms of delgating accessors.

Given n scopes of data of types T1...Tn, and a unfied type T (which usually would be amongst T1...Tn I would expect), the ideal thing would be to have the framework piece together the type instances so that T.x was a merge ot the T1...Tn sources of the property x. How to write this without significat restrictions on how the types relates seems non-trivial at this point.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977345#3977345

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977345