This is not entirely true. You can enable the ability to register new
nodetypes via RMI. For jackrabbit 1.3, it requires a little extra work on
the part of setting up the RMI server in Jackrabbit. For Jackrabbit 1.3.1,
the may have already done what is necessary to enable these features. I
have not tested this in 1.3.1 yet.
Please refer to:
http://www.nabble.com/Reregistering-Node-Types-in-RMI-tf4253117.html
to see how to setup the ability to create new NodeTypes via RMI. Please
post any questions there. Thanks.
Christoph Kiehl wrote:
>
> Hi,
>
> on the user list the question arose whether it is possible to reregister
> node types via RMI. Currently JackrabbitNodeTypeManager doesn't expose
> NodeTypeManagerImpl.registerNodeTypes(InputStream, String, boolean)
> which allows to enable reregistration.
> There are two options to implement this feature:
>
> 1. Extend JackrabbitNodeTypeManager with another method (might be the
> signature from above or a "reregister()" methode)
> 2. Change the default behaviour of
> NodeTypeManagerImpl.registerNodeTypes(InputStream, String) to always try
> to reregister node types.
>
> I'm in favour of option two because
>
> a) I don't want to add more methods to JackrabbitNodeTypeManager if
> avoidable because node type registration will change anyway with JCR 2.0.
> b) I think it's more natural. If I try to register a node type I do this
> because I want this node type to be registered and not because I want to
> check if it is already registered and get an exception back if it is.
> There are other ways to find out if a node type is registered. Is there
> any reason not just try to reregister existing nodetypes by default?
>
> Cheers,
> Christoph
>
>
>
--
View this message in context: http://www.nabble.com/Nodetype-reregistration-and-JackrabbitNodeTypeManager-tf4254590.html#a12114957
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
|