Jukka Zitting <jukka.zitting <at> gmail.com> writes: > > Hi, > [...] To be able to use the Jackrabbit-specific > features you need to use the JackrabbitClientAdapterFactory [1] and > JackrabbitServerAdapterFactory [2] classes in your client and server > code instead of the standard ClientAdapterFactory and > ServerAdapterFactory classes. The reason for this is to keep the > jackrabbit-api dependency optional for clients and servers that don't > need or implement this functionality. > > [1] http://jackrabbit.apache.org/api/1.3/org/apache/jackrabbit/rmi/jackrabbit/JackrabbitClientAdapterFactory.html > [2] http://jackrabbit.apache.org/api/1.3/org/apache/jackrabbit/rmi/jackrabbit/JackrabbitServerAdapterFactory.html > > BR, > > Jukka Zitting >
Hi, I also have to register custom nodetypes over RMI, but as their behaviour is dynamically generated into the java code, they are built like NodeTypeDef and then registered with NodeTypeRegistry#registerNodeType(NodeTypeDef). However the NodeTypeRegistry doesn't seem to be accessible with the JackrabbitNodeTypeManager. Would it be possible to "RMI-ze" the NodeTypeRegistry, or must I convert the NodeTypeDefs to an XML stream which I will be able to register with JackrabbitNodeTypeManager.html#registerNodeTypes() - although the second way seems counter-productive ? I have a second question: in order to get the JackrabbitNodeTypeManager, I'm using the Jackrabbit adaptaters factories, but the repository is deployed as a Tomcat webapp so I don't know where to change the server code to make it use the JackrabbitServerAdaptaterFactory ? Thanks, Corentin
