Re: [xwiki-dev] [ArchitectureV2] Model proposal

Hi everyone, On May 29, 2007, at 5:43 PM, Stéphane Laurière wrote: [snip] That's an interesting idea. However for me the relationship with JCR is not an advantage and certainly not a requirement. We want our model classes to be independent on any storage mechanism. However from a design perspective it's interesting to evaluate how the model classes could look like if they were using a Node API similar in design to the JCR (which I don't know so well but I guess it's similar to the DOM API too). I can see some pros and cons: Pros: - flexibility in that it's easy to add a new node type - genericity in that it's a hierarchical structure (a graph) and it would support nested nodes Cons: - less strongly typed API in general a more generic API vs a more business oriented API with the API I proposed. Compare Space.getDocuments() to node.getElementsByType(NodeType.DOCUMENT). Of course I guess we could add a SpaceNode class that implements the Node interface and that method could then have a getDocuments() API which internally would be implemented as getElementsByType (NodeType.DOCUMENT). There's still the problem of doing "if"s on the node type to cast to the correct specific node class. Personally I've always found the DOM API to be a real pain (which is probably why there are frameworks like JDOM, DOM4J, etc). - There are business APIs to implement too (not just navigating) and these APIs don't make much sense applied to a Node. They do make sense applied to business objects. We need to discuss this more and I need to think more about this too to evaluate the consequences. Thanks for this interesting discussion Stephane -Vincent