1 Mar 2007 03:44
Re: Internationalization of property values
Brian Thompson <elephantium <at> gmail.com>
2007-03-01 02:44:45 GMT
2007-03-01 02:44:45 GMT
The way I see it, you have three options: Option 1: Separate nodes, one for each language. If you maintain separate workspaces (again, one for each language), you can create the initial movie node and clone() it to the other language workspaces. Each language-version of the movie node will then share the same UUID, making lookups easier (just log in to the appropriate workspace when you're looking for a particular language's version of movie data). If you don't go with multiple workspaces, it gets trickier - you could build a logical linked list with node references, but that seems harder to deal with. Option 2: One movie node, multiple child nodes for languages. Create all the child nodes as the same type (movie:properties or something similar), and put your properties on the child nodes. Option 3: Make each property multi-valued. This keeps all language versions of each property all in the same place, simplifying insertion and retrieval. The downside is that, every time you retrieve any property, you are forced to retrieve all language versions of it. Hope this helps, -Brian Waldemar Baraldi wrote: > Hi all, > > I want my nodes to have internationalizable properties. Let's say a node(Continue reading)
> We also would like to modify apache jackrabbit's authentication mechanism
> (or chain a custom JAAS module) to use our custom authentication service.
The easiest way would be to use a custom JAAS module, as Jackrabbit
supports JAAS authentication.
> Our goal will be to have a JSR-170 repository with lots of user spaces
> where each user would be able to see their files and in certain folders our
> users would be able to put files which would trigger certain application
> logic.
>
> Is this possible?, is apache jackrabbit our choice?
Sounds like a good match for Jackrabbit.
BR,
RSS Feed