Hi -- I'm doing the nodetype registration on the server side as a servlet.
Originally,
I did it in a separate webapp in the same tomcat server
as the jackrabbit server, then I changed it to a servlet within the
jackrabbit webapp.
I configured the servlet to load on startup after all other startup
servlets. It reads in the .CND file, checks if a nodetype
already exists, and if so, it re-registers it. If not, it just registers
it.
My client programs are able to add to the repository using these custom node
types and they show up under
jcr:system/jcr:nodeTypes in the tree.
I can add a new node type to the CND file, restart the tomcat, and the new
node type shows up in the dump on
the client side.
However, if I add a new property to an existing node type, the new property
does not show up.
I'm not sure why it would be a caching issue, because my client program is
just a little test program that can dump out all
the nodes and I run it fresh everytime.
Betty
----- Original Message -----
From: "Angela Schreiber" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, July 30, 2008 2:10 AM
Subject: Re: what does NodeTypeRegistry.reregisterNodeType() do?
In answer to the protocol question, the remote client uses the spi
webdav
interface
ah, i see. that explains it. this is probably a caching issue of the spi
layer.
the SPI layer does not support nodetype registration
anyway, since this a jackrabbit specific extension
and not part of the JCR API.
how did you register the nodetype?
please feel free to create a jira issue.
before you create an issue, i'd like to understand
how you registered the nodetype.
angela
