Mark, My understanding of Custom nodes may not be the best and Actually people on the group can help me correct it if it is wrong.
Custom Nodes is similiar to "User Defined Datatype" in RDBMS. You define storage , functions available etc. on the newly created Data Type- One may also includes functions to process the same. It seems JSR 283 is supposed to work in this direction. "- Improvement of content repository interoperability through the addition of new standardized node types ,including node types for meta information and internationalization." >Is there any reason there isn't an >element for specifying the custom node definition file location >there, and possibly the "Reader" type used to process the file? Yes, if there is Custom Node e.g. "DRM file" and you know the content will always confirm to XrML XSD, One may wish to have "Render" which will display the node content in some standard way- may be different XSLT transforms depending on where the content needs to be display.etc. Or May be add a property "Renderer" to custom Node which stores info about the rendering program. I think it is possible to do extent "Exo - ECM " to do the same. Benjamin Mestrallet from exo platform may be able to guide you further . :) Chand -----Original Message----- From: Mark Slater [mailto:] Sent: Saturday, February 18, 2006 10:49 PM To: jackrabbit-dev@incubator.apache.org Subject: Best Practice: defining custom nodes I've got my repository's custom nodes defined, and I have no problem reading them in (I'm using Jackrabbit's xml.NodeTypeReader) and adding them to the repository. The question I have is, where is the best place to do this? I'd love to be able to specify my custom nodes, or at least the file location, in a config file someplace, and have Jackrabbit read them in automatically if/when it has to create the repository for the first time. What I don't want to be doing is trying to add them every time I get a Session since they only need to be configured once. What is the current Best Practice for adding custom nodes to the repository when it is created? From what I can tell, the specification of the Repository configuration DTD has been left entirely up to the implementation. Thanks, Mark
