jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sudhan <s.kan...@gmail.com>
Subject Re: drawbacks to using custom types?
Date Mon, 21 May 2007 17:22:40 GMT


I am having same doubts as mentioned in this thread. Initially i was using
nt:file and nt:unstructured nodes, but due to some requirements I had to
extend these with my custom types. Now my problem is that how to communicate
through WebDav. Like i am using DavExplorer and had written python script to
create nodes and update them aswell.

Before it used to creates those standard nodes through these tools. But now
it is not creating custom nodes. Is it something related to collection and
noncollection defined in config.xml. By the way i am using Jackrabbit
through RMI.

So how can I create those custom node types through WebDav.

appreciate any help.



rhodebump wrote:
> Most of my node types map well to the nt:folder/nt:resource nodetypes,
> however, there are a few string properties that I need to store.  For
> example, "displayName" or "description"
> I understand how I can define these as properties for my custom node
> types, but if I do, do I lose the ability to manage these nodes from
> webdav or other interfaces?  
> Would it be better to define these as properties on my custom nodetype?
> Or
> Sould I create a nt:folder and for each of the values that I want to store
> (description, displayName), I create a nt:file to store this information.
> Another way of asking the question is, What editing tools to you give up
> when you go with a custom nodetype, is it better to stick with the base
> types?
> Thanks very much.
> Phillip

View this message in context: http://www.nabble.com/drawbacks-to-using-custom-types--tf3790446.html#a10723190
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message