Thanks! I tried using ISDESCENDANTNODE, but for some reason it wasn't
working. Using your syntax worked fine.

However, there seems to be a significant performance difference
between the same query in JCR-SQL2 and XPATH

So, for example, this comes back immediately:

/jcr:root/fm:profiles/com/gmail/wbustraan/*[@fm:session =
'3b7856fb-6a5d-427d-a7d6-00af15d7178a']

While this takes about 10 seconds:

select * from [nt:base] where
isdescendantnode([/fm:profiles/com/gmail/wbustraan]) and [fm:session]=
'3b7856fb-6a5d-427d-a7d6-00af15d7178a'

Is this a known issue with the new JCR-SQL2 queries or am I doing
something wrong?

On Fri, Dec 4, 2009 at 4:12 AM, Philipp Bunge <buge@crimson.ch> wrote:
> Hi Wes
>
>> I have a bit of a dilemma. I'm working with Jackrabbit 2.0b3 and
>> trying to migrate to JCR2.0. However, since the XPATH query syntax is
>> deprecated, I'm investigating how to go about writing queries in
>> JCR-SQL2. Unfortunately, I haven't come up with many examples or
>> tutorials for the new JCR-SQL2 syntax.
>
> There really aren't many tutorial around as far as I know. I use the
> railroad diagrams that Thomas Müller created quite a lot as a
> reference however: http://www.h2database.com/jcr/grammar.html
>
>> One of the scenarios that I'd like to use frequently is searching a
>> subtree, i.e. starting at a particular node and searching all
>> descendants for certain property values. This is trivial to accomplish
>> in XPATH, but I can't figure out the correct (and efficient) way to do
>> it using SQL2. Can any one help me out with an example?
>
> You probably want something as follows:
>
> SELECT * FROM [nt:unstructured]
>  WHERE ISDESCENDANTNODE([/the/particular/node])
>  AND yourproperty = "foo"
>
>
> Cheers,
> Philipp
>

Problem solved.

setProperty with the right name but the wrong type will generate the  
exception.

javax.jcr.nodetype.ConstraintViolationException: no matching property  
definition found for {internal}privileges

I as trying to set a {internal}privileges with a Value[] containing  
String rather than Name

Ian



On 4 Dec 2009, at 18:51, Ian Boston wrote:

> Hi,
> I have a modified DefaultSecurityManager (and related classes) and I  
> am certain I have made a mistake somewhere, but on initialization I  
> get
>
> 04.12.2009 18:40:09.020 *ERROR* [SCR Component Actor]  
> org 
> .apache 
> .sling.jcr.jackrabbit.server.impl.security.standard.ACLProvider  
> Failed to set-up minimal access control for root node of workspace  
> default javax.jcr.nodetype.ConstraintViolationException: no matching  
> property definition found for {internal}privileges
>        at  
> org 
> .apache 
> .jackrabbit 
> .core 
> .nodetype 
> .EffectiveNodeType.getApplicablePropertyDef(EffectiveNodeType.java: 
> 768)
>        at  
> org 
> .apache 
> .jackrabbit 
> .core.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:905)
>        at  
> org 
> .apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.java: 
> 412)
>        at  
> org 
> .apache.jackrabbit.core.NodeImpl.internalSetProperty(NodeImpl.java: 
> 1444)
>        at  
> org 
> .apache.jackrabbit.core.NodeImpl.internalSetProperty(NodeImpl.java: 
> 1423)
>        at  
> org 
> .apache 
> .jackrabbit 
> .core 
> .DynamicProtectedItemModifier 
> .setProperty(DynamicProtectedItemModifier.java:118)
>        at  
> org 
> .apache 
> .sling 
> .jcr 
> .jackrabbit 
> .server.impl.security.standard.ACLEditor.setPolicy(ACLEditor.java:189)
>        at  
> org 
> .apache 
> .sling 
> .jcr 
> .jackrabbit 
> .server 
> .impl.security.standard.ACLProvider.initRootACL(ACLProvider.java:356)
>        at  
> org 
> .apache 
> .sling 
> .jcr 
> .jackrabbit 
> .server.impl.security.standard.ACLProvider.init(ACLProvider.java:182)
>        at  
> org 
> .apache 
> .sling 
> .jcr 
> .jackrabbit 
> .server 
> .impl 
> .security.dynamic.DynamicACLProvider.init(DynamicACLProvider.java:42)
>        at  
> org 
> .apache 
> .sling 
> .jcr 
> .jackrabbit 
> .server 
> .impl 
> .security 
> .dynamic 
> .DynamicAccessControlProviderFactoryImpl 
> .createProvider(DynamicAccessControlProviderFactoryImpl.java:103)
>        at  
> org 
> .apache 
> .jackrabbit 
> .core 
> .DynamicSecurityManager 
> .getAccessControlProvider(DynamicSecurityManager.java:425)
> at  
> org 
> .apache 
> .jackrabbit 
> .core 
> .DynamicSecurityManager.getAccessManager(DynamicSecurityManager.java: 
> 280)
>        at  
> org 
> .apache 
> .jackrabbit.core.SessionImpl.createAccessManager(SessionImpl.java:384)
>        at  
> org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:302)
>        at  
> org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:271)
>        at  
> org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java: 
> 105)
>
>
> Any ideas why or where I can look to debug. ?
>
> I think the main difference up to this point is a change in package  
> name for the ACLProvider other than that its standard. My extensions  
> only relate to the construction of permissions bitmaps.
>
> The I believe the default node types have been registered since I  
> see the log line
> 04.12.2009 18:40:01.843 *INFO* [SCR Component Actor]  
> org.apache.jackrabbit.core.nodetype.NodeTypeRegistry no custom node  
> type definitions found
>
>
> Ian
>
>

On Fri, Dec 4, 2009 at 11:28 PM, ChadDavis <chadmichaeldavis@gmail.com> wrote:
> 1) I read elsewhere that the FS is only used for some administrative
> stuff, like the search index and configuration.  Is this correct?  In
> other words, the FS isn't a part of the storage for the actual repo
> content, that's all done by the PM?
DataStore was used to store large node which is on FS. Large node
could be multimedia or large documents. Store in db is not recommended
even it could be easily store in db.

> 2) It appears as if there is no good file system backed PM . . . is
Not sure day.com's TAR PM is based on file system or not. It's best so
far from what I read from the list.

> this accurate?  The bundleFsPM is described as non-production, read
> only.  So, this kind of means that the FS is NOT a choice for backing
> the content of my repo, correct?
Default FS PM doesn't perform well and not transactional.

> 3) Is the Derby PM considered production worthy?  Any reason not to use it?
Personal I trust derby as a low overhead database with zero
administration. It's not suitable if you have strong dba person which
she/he may lose job:) You may use other db if:
* Prepared to manage database.
* Multi connection required (embedded db using single connection always)
* Cluster your db
* Huge db size
* You application will use exist db along with jackrabbit

After you made decision, you could do some basic benchmark along with
your dataset to get a feeling of how it perform.

Good luck!

-Guo

I've just read through all of the configuration information on the
jackrabbit web site.  As far as I can tell, the default settings are
pretty solid.  I don't have any requirements for storing things in a
particular db.  I have application level security that will suffice
for now.

Maybe I'm missing something in my analysis.  Are there some obvious,
to a more experienced eye, points in the default repository.xml that
just aren't up to production snuff?

In the default repository.xml, the datastore element is configured:

    <DataStore class="org.apache.jackrabbit.core.data.FileDataStore"/>

Is this all that is needed for the PM to hand off binary storage to
the datastore?  There doesn't appear to be any "wiring" of the PM, or
the Workspace, to the data store element.  I guess it's global unless
overridden somewhere?

BTW, I'm using 2.0-beta3.

On Fri, Dec 4, 2009 at 4:28 PM, ChadDavis <chadmichaeldavis@gmail.com> wrote:
> I'm reading the PersistenceManager FAQ [1].  There's a part where it
> discusses "What combination of FS and PM is the best choice?"  In
> reading through this section I have a couple of questions:
>
> 1) I read elsewhere that the FS is only used for some administrative
> stuff, like the search index and configuration.  Is this correct?  In
> other words, the FS isn't a part of the storage for the actual repo
> content, that's all done by the PM?
>
> 2) It appears as if there is no good file system backed PM . . . is
> this accurate?  The bundleFsPM is described as non-production, read
> only.  So, this kind of means that the FS is NOT a choice for backing
> the content of my repo, correct?
>
> 3) Is the Derby PM considered production worthy?  Any reason not to use it?
>
>
> http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ
>

I'm reading the PersistenceManager FAQ [1].  There's a part where it
discusses "What combination of FS and PM is the best choice?"  In
reading through this section I have a couple of questions:

1) I read elsewhere that the FS is only used for some administrative
stuff, like the search index and configuration.  Is this correct?  In
other words, the FS isn't a part of the storage for the actual repo
content, that's all done by the PM?

2) It appears as if there is no good file system backed PM . . . is
this accurate?  The bundleFsPM is described as non-production, read
only.  So, this kind of means that the FS is NOT a choice for backing
the content of my repo, correct?

3) Is the Derby PM considered production worthy?  Any reason not to use it?


http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ

Hi,
I have a modified DefaultSecurityManager (and related classes) and I  
am certain I have made a mistake somewhere, but on initialization I get

04.12.2009 18:40:09.020 *ERROR* [SCR Component Actor]  
org 
.apache.sling.jcr.jackrabbit.server.impl.security.standard.ACLProvider  
Failed to set-up minimal access control for root node of workspace  
default javax.jcr.nodetype.ConstraintViolationException: no matching  
property definition found for {internal}privileges
         at  
org 
.apache 
.jackrabbit 
.core 
.nodetype 
.EffectiveNodeType.getApplicablePropertyDef(EffectiveNodeType.java:768)
         at  
org 
.apache 
.jackrabbit 
.core.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:905)
         at  
org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.java: 
412)
         at  
org.apache.jackrabbit.core.NodeImpl.internalSetProperty(NodeImpl.java: 
1444)
         at  
org.apache.jackrabbit.core.NodeImpl.internalSetProperty(NodeImpl.java: 
1423)
         at  
org 
.apache 
.jackrabbit 
.core 
.DynamicProtectedItemModifier 
.setProperty(DynamicProtectedItemModifier.java:118)
         at  
org 
.apache 
.sling 
.jcr 
.jackrabbit 
.server.impl.security.standard.ACLEditor.setPolicy(ACLEditor.java:189)
         at  
org 
.apache 
.sling 
.jcr 
.jackrabbit 
.server 
.impl.security.standard.ACLProvider.initRootACL(ACLProvider.java:356)
         at  
org 
.apache 
.sling 
.jcr 
.jackrabbit 
.server.impl.security.standard.ACLProvider.init(ACLProvider.java:182)
         at  
org 
.apache 
.sling 
.jcr 
.jackrabbit 
.server 
.impl.security.dynamic.DynamicACLProvider.init(DynamicACLProvider.java: 
42)
         at  
org 
.apache 
.sling 
.jcr 
.jackrabbit 
.server 
.impl 
.security 
.dynamic 
.DynamicAccessControlProviderFactoryImpl 
.createProvider(DynamicAccessControlProviderFactoryImpl.java:103)
         at  
org 
.apache 
.jackrabbit 
.core 
.DynamicSecurityManager 
.getAccessControlProvider(DynamicSecurityManager.java:425)
  at  
org 
.apache 
.jackrabbit 
.core 
.DynamicSecurityManager.getAccessManager(DynamicSecurityManager.java: 
280)
         at  
org 
.apache 
.jackrabbit.core.SessionImpl.createAccessManager(SessionImpl.java:384)
         at  
org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:302)
         at  
org.apache.jackrabbit.core.SessionImpl.<init>(SessionImpl.java:271)
         at  
org.apache.jackrabbit.core.XASessionImpl.<init>(XASessionImpl.java:105)


Any ideas why or where I can look to debug. ?

I think the main difference up to this point is a change in package  
name for the ACLProvider other than that its standard. My extensions  
only relate to the construction of permissions bitmaps.

The I believe the default node types have been registered since I see  
the log line
04.12.2009 18:40:01.843 *INFO* [SCR Component Actor]  
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry no custom node  
type definitions found


Ian

> please take a look at the API and the specification.

thank you for your patience

i have it working now.

AccessControlPolicyIterator it =
adminAcm.getApplicablePolicies(testRootNode.getPath());
		while ( it.hasNext() ) {
			AccessControlPolicy acp = it.nextAccessControlPolicy();

			Privilege[] privileges = new
Privilege[]{adminAcm.privilegeFromName(Privilege.JCR_WRITE)};

			((AccessControlList)acp).addAccessControlEntry(new
PrincipalImpl(anonymous.getUserID()), privileges);


			adminAcm.setPolicy(testRootNode.getPath(), acp);
		}
		superuser.save();

Regards

Ben Short

2009/12/4 Angela Schreiber <anchela@day.com>
>
> please take a look at the API and the specification.
>
> - JCR 2.0 provides AccessControlList
> - Jackrabbit API 2.0 in addition provides JackrabbitAccessControlList
>  adding a couple of extensions.
>
> the implementation of the final JCR 2.0 will be available
> as of JR 2.0.
>
> older versions of jackrabbit (1.5, 1.6) don't reflect
> the latest version of the specification but intermediate
> states. if you are talking about JCR 2.0, please make
> sure, you refer to one of the jackrabbit 2.0-xyz releases.
>
> angela
>
> Ben Short wrote:
>>
>> Thanks Angela,
>>
>> Through a bit of trial and error I have the following which works as
>> expected.
>>
>> AccessControlPolicyIterator it =
>> adminAcm.getApplicablePolicies(testRootNode.getPath());
>> while ( it.hasNext() ) {
>> AccessControlPolicy acp = it.nextAccessControlPolicy();
>>
>> Privilege[] privileges = new
>> Privilege[]{adminAcm.privilegeFromName(Privilege.JCR_WRITE)};
>>
>> ((AbstractACLTemplate)acp).addEntry(new
>> PrincipalImpl(anonymous.getUserID()), privileges, true);
>>
>> adminAcm.setPolicy(testRootNode.getPath(), acp);
>>
>> }
>> superuser.save();
>>
>> It seems odd to me that I have to cast the AcessControlPolicy
>> to AbstractACLTemplate inorder, which is JackRabbit specific to add a new
>> entry. I wonder what the JCR 2 api dose not define an interface?
>>
>> Regards
>>
>> Ben Short
>>
>> 2009/12/4 Angela Schreiber <anchela@day.com>
>>
>>> please take a look at the API.
>>>
>>> AccessControlManager#getApplicablePolicies
>>>
>>> -> for policies that can but haven't yet been applied
>>>
>>> AccessControlManager#getPolicies
>>>
>>> -> for policies that have been applied at a given path
>>>  and can be removed again or edited/reapplied
>>>
>>> angela
>>>
>>
>

please take a look at the API and the specification.

- JCR 2.0 provides AccessControlList
- Jackrabbit API 2.0 in addition provides JackrabbitAccessControlList
   adding a couple of extensions.

the implementation of the final JCR 2.0 will be available
as of JR 2.0.

older versions of jackrabbit (1.5, 1.6) don't reflect
the latest version of the specification but intermediate
states. if you are talking about JCR 2.0, please make
sure, you refer to one of the jackrabbit 2.0-xyz releases.

angela

Ben Short wrote:
> Thanks Angela,
> 
> Through a bit of trial and error I have the following which works as
> expected.
> 
> AccessControlPolicyIterator it =
> adminAcm.getApplicablePolicies(testRootNode.getPath());
> while ( it.hasNext() ) {
> AccessControlPolicy acp = it.nextAccessControlPolicy();
> 
> Privilege[] privileges = new
> Privilege[]{adminAcm.privilegeFromName(Privilege.JCR_WRITE)};
> 
> ((AbstractACLTemplate)acp).addEntry(new
> PrincipalImpl(anonymous.getUserID()), privileges, true);
> 
> adminAcm.setPolicy(testRootNode.getPath(), acp);
> 
> }
> superuser.save();
> 
> It seems odd to me that I have to cast the AcessControlPolicy
> to AbstractACLTemplate inorder, which is JackRabbit specific to add a new
> entry. I wonder what the JCR 2 api dose not define an interface?
> 
> Regards
> 
> Ben Short
> 
> 2009/12/4 Angela Schreiber <anchela@day.com>
> 
>> please take a look at the API.
>>
>> AccessControlManager#getApplicablePolicies
>>
>> -> for policies that can but haven't yet been applied
>>
>> AccessControlManager#getPolicies
>>
>> -> for policies that have been applied at a given path
>>   and can be removed again or edited/reapplied
>>
>> angela
>>
> 

Thanks Angela,

Through a bit of trial and error I have the following which works as
expected.

AccessControlPolicyIterator it =
adminAcm.getApplicablePolicies(testRootNode.getPath());
while ( it.hasNext() ) {
AccessControlPolicy acp = it.nextAccessControlPolicy();

Privilege[] privileges = new
Privilege[]{adminAcm.privilegeFromName(Privilege.JCR_WRITE)};

((AbstractACLTemplate)acp).addEntry(new
PrincipalImpl(anonymous.getUserID()), privileges, true);

adminAcm.setPolicy(testRootNode.getPath(), acp);

}
superuser.save();

It seems odd to me that I have to cast the AcessControlPolicy
to AbstractACLTemplate inorder, which is JackRabbit specific to add a new
entry. I wonder what the JCR 2 api dose not define an interface?

Regards

Ben Short

2009/12/4 Angela Schreiber <anchela@day.com>

> please take a look at the API.
>
> AccessControlManager#getApplicablePolicies
>
> -> for policies that can but haven't yet been applied
>
> AccessControlManager#getPolicies
>
> -> for policies that have been applied at a given path
>   and can be removed again or edited/reapplied
>
> angela
>

Hi,

Ian Boston schrieb:
> Felix,
> yes thank you,
> got the update through which did as you say fix about 4 of the tests in
> Sling (and found the sling jira now).
> BTW I think the other problems I am having with {internal}privileges not
> being defined are of my own making,

ok.

> although I did notice the launch-pad
> tests are using 2.0.4-incubator of JCR Base rather than 2.0.5-SNAPSHOT
> which is in the code base so upgrading the JR API to 1.6 in the current
> trunk wont flow through. (not that it fixes any of the remaining tests)

Yes, but this doesn't matter because the jcr/base module just provides
AccessControlUtil class, which is pure API calling. This doesn't matter
whether it is 1.5 or 1.6.

In fact updating the access manager dependency to the SNAPSHOT fixed the
tests (after fixing the access manager bundle).

Regards
Felix

... end of crossposting ;-)

> Ian
> 
> (ccd dev@sling)
> 
> On 3 Dec 2009, at 20:46, Felix Meschberger wrote:
> 
>> Hi Ian
>>
>> In fact I rewrote a Sling integration test just this morning exactly
>> doing such property setting for verification purposes (the test used to
>> check the rep:principalName property which is not available as such any
>> longer).
>>
>> Regards
>> Felix
>>
>> Ian Boston schrieb:
>>> Angela,
>>> Fantastic,
>>> I misread the patch forgetting that * might be allowed.
>>> Thank you.
>>> Ian
>>>
>>> On 3 Dec 2009, at 17:44, Angela Schreiber wrote:
>>>
>>>> hi ian
>>>>
>>>> JCR-1984 addressed a problem that protected properties defined
>>>> by the user/group node types were exposed by the #getPropertyNames
>>>> and #getProperty methods, although they could not be modified
>>>> by the corresponding set/remove methods.
>>>>
>>>> this issue should not affect additional, application specific
>>>> properties that were or will be stored with a user/group.
>>>> the nodetype still allows for
>>>>
>>>> - * (UNDEFINED)
>>>> - * (UNDEFINED) multiple
>>>>
>>>> and those props should be exposed by the mentioned methods.
>>>> i'm not aware of any change that would have broken this.
>>>>
>>>> angela
>>>>
>>>>
>>>>
>>>> Ian Boston wrote:
>>>>> Hi,
>>>>> IIUC [1], post 1.6 blocks an authorizable node from holding any
>>>>> properties, other than those listed in the schema.
>>>>> How do I add and retrieve a well defined set of properties for the
>>>>> node as was possible in JR15 ?
>>>>> We have an application that stores extra group and user metadata on
>>>>> the authorizable node and I really don't want to have to rewrite it.
>>>>> Thanks
>>>>> Ian
>>>>> 1 https://issues.apache.org/jira/browse/JCR-1984
>>>>
>>>
>>>
> 
> 

please take a look at the API.

AccessControlManager#getApplicablePolicies

-> for policies that can but haven't yet been applied

AccessControlManager#getPolicies

-> for policies that have been applied at a given path
    and can be removed again or edited/reapplied

angela

Hi,

I have a really simple test case as follows:

public class UserManagerTests {
private Repository repository;
    private Session superuser;
private Session anonymous;
Node testRootNode;


@Before
    public void before() throws Exception {
        repository = new TransientRepository();
        superuser = repository.login(new SimpleCredentials("admin",
"admin".toCharArray()));
anonymous = repository.login(new SimpleCredentials("anonymous",
"anonymous".toCharArray()));
testRootNode = superuser.getRootNode().addNode("test_" +
Long.toString(System.currentTimeMillis()));
superuser.save();
}

    @After
    public void after() throws Exception {
testRootNode.remove();
superuser.save();
superuser.logout();
        superuser = null;
        repository = null;
    }

@Test
public void testUserManager() throws Exception {

AccessControlManager adminAcm = getAccessControlManager(superuser);
AccessControlManager anonAcm = getAccessControlManager(anonymous);

Assert.assertFalse(anonAcm.hasPrivileges(testRootNode.getPath(),
privilegesFromName(Privilege.JCR_WRITE)));

// something here to allow anon user to write to our test node
adminAcm.setPolicy(testRootNode.getPath(), policy);


Assert.assertTrue(anonAcm.hasPrivileges(testRootNode.getPath(),
privilegesFromName(Privilege.JCR_WRITE)));
}
}

How do I get/create a policy for the anonymous user which will allow the
anonymous user to write to the test node? All the implementations of
AccessControlPolicy are not visible to to my code.

Regards

Ben



2009/11/27 Ben Short <ben@benshort.co.uk>

> Hi,
>
> I'm trying to use the AccessControlManager to allow a user to have write
> permissions to a node. But I can't see how to create  a policy.
>
> Can anyone give me any pointers?
>
> Regards
>
> Ben Short
>

Hi,

I don't know how to represent the data in my repository.
Now i have a document node that contains a file as data ( >nt:resource) but
i want to extend the functionality for more files.
How should i represent the structure of nodes so when i want the version 1.x
of the document node i want to see the content of the files at that time.

For example if i create a new node (let's say my:file), and a document
contains one or more nodes of this type.
When i do a checkout, checkin operation (and i modify the content of one or
more my:file nodes) on the document node the version created will contain
references to the old content of the my:file nodes ?
A possibility is to make versions for every my:file node when i'm creating a
new version for the document node (so when i want the version 1.5 of the
document to take version 1.5 of the file) but i'll have problems when i'll
try to delete or add new my:file nodes
Is there another way ?

Thank you,
mitziuro

Felix,
yes thank you,
got the update through which did as you say fix about 4 of the tests  
in Sling (and found the sling jira now).
BTW I think the other problems I am having with {internal}privileges  
not being defined are of my own making, although I did notice the  
launch-pad tests are using 2.0.4-incubator of JCR Base rather than  
2.0.5-SNAPSHOT which is in the code base so upgrading the JR API to  
1.6 in the current trunk wont flow through. (not that it fixes any of  
the remaining tests)
Ian

(ccd dev@sling)

On 3 Dec 2009, at 20:46, Felix Meschberger wrote:

> Hi Ian
>
> In fact I rewrote a Sling integration test just this morning exactly
> doing such property setting for verification purposes (the test used  
> to
> check the rep:principalName property which is not available as such  
> any
> longer).
>
> Regards
> Felix
>
> Ian Boston schrieb:
>> Angela,
>> Fantastic,
>> I misread the patch forgetting that * might be allowed.
>> Thank you.
>> Ian
>>
>> On 3 Dec 2009, at 17:44, Angela Schreiber wrote:
>>
>>> hi ian
>>>
>>> JCR-1984 addressed a problem that protected properties defined
>>> by the user/group node types were exposed by the #getPropertyNames
>>> and #getProperty methods, although they could not be modified
>>> by the corresponding set/remove methods.
>>>
>>> this issue should not affect additional, application specific
>>> properties that were or will be stored with a user/group.
>>> the nodetype still allows for
>>>
>>> - * (UNDEFINED)
>>> - * (UNDEFINED) multiple
>>>
>>> and those props should be exposed by the mentioned methods.
>>> i'm not aware of any change that would have broken this.
>>>
>>> angela
>>>
>>>
>>>
>>> Ian Boston wrote:
>>>> Hi,
>>>> IIUC [1], post 1.6 blocks an authorizable node from holding any
>>>> properties, other than those listed in the schema.
>>>> How do I add and retrieve a well defined set of properties for the
>>>> node as was possible in JR15 ?
>>>> We have an application that stores extra group and user metadata on
>>>> the authorizable node and I really don't want to have to rewrite  
>>>> it.
>>>> Thanks
>>>> Ian
>>>> 1 https://issues.apache.org/jira/browse/JCR-1984
>>>
>>
>>

Jukka Zitting wrote:
> Hi,
>
> On Thu, Dec 3, 2009 at 11:28 PM, Samuel Cox <crankydillo@gmail.com> wrote:
>   
>> I'm unaware of anything outside of what is published from the Jackrabbit
>> site (this mailing list).  Does anyone else know of anything else?
>>     
>
> If there's interest, we could add a "JCR Support" section to the
> JcrLinks page [1] that Philipp already mentioned. Companies and
> individuals who offer JCR support services could list themselves
> there, so people will have easier time finding them.
>
> [1] http://wiki.apache.org/jackrabbit/JcrLinks
>   

+1

Michael
> BR,
>
> Jukka Zitting
>   

Hi,

On Thu, Dec 3, 2009 at 11:28 PM, Samuel Cox <crankydillo@gmail.com> wrote:
> I'm unaware of anything outside of what is published from the Jackrabbit
> site (this mailing list).  Does anyone else know of anything else?

If there's interest, we could add a "JCR Support" section to the
JcrLinks page [1] that Philipp already mentioned. Companies and
individuals who offer JCR support services could list themselves
there, so people will have easier time finding them.

[1] http://wiki.apache.org/jackrabbit/JcrLinks

BR,

Jukka Zitting

Hi Samuel

> We're creating a decent-sized dependency on a functioning JSR-170
> implementation (Jackrabbit).  As such, we're curious about the level of
> support we can get.
>
> I'm unaware of anything outside of what is published from the Jackrabbit
> site (this mailing list).  Does anyone else know of anything else?

Probably the only commercial provider of a dedicated JSR-170
implementation is Day with their CRX product [1]. CRX is essentially a
repackaged Jackrabbit with additional tools, a (pretty neat) TAR based
PersistenceManager and commercial support. Day actually lead the
JSR-170 and JSR-283 specifiications and a lot (most?) of the
Jackrabbit developers actually work there.

There are some other products that have JCR support, but the level and
quality of implementation is rather mixed, IMHO [2]

Cheers,
Philipp

[1] http://www.day.com/day/en/products/crx.html
[2] http://wiki.apache.org/jackrabbit/JcrLinks#Other_JCR_implementations

Hi Wes

> I have a bit of a dilemma. I'm working with Jackrabbit 2.0b3 and
> trying to migrate to JCR2.0. However, since the XPATH query syntax is
> deprecated, I'm investigating how to go about writing queries in
> JCR-SQL2. Unfortunately, I haven't come up with many examples or
> tutorials for the new JCR-SQL2 syntax.

There really aren't many tutorial around as far as I know. I use the
railroad diagrams that Thomas Müller created quite a lot as a
reference however: http://www.h2database.com/jcr/grammar.html

> One of the scenarios that I'd like to use frequently is searching a
> subtree, i.e. starting at a particular node and searching all
> descendants for certain property values. This is trivial to accomplish
> in XPATH, but I can't figure out the correct (and efficient) way to do
> it using SQL2. Can any one help me out with an example?

You probably want something as follows:

SELECT * FROM [nt:unstructured]
  WHERE ISDESCENDANTNODE([/the/particular/node])
  AND yourproperty = "foo"


Cheers,
Philipp

We're creating a decent-sized dependency on a functioning JSR-170 
implementation (Jackrabbit).  As such, we're curious about the level of 
support we can get.

I'm unaware of anything outside of what is published from the Jackrabbit 
site (this mailing list).  Does anyone else know of anything else?

Thanks.

-- 
Samuel Cox

Hi Ian

In fact I rewrote a Sling integration test just this morning exactly
doing such property setting for verification purposes (the test used to
check the rep:principalName property which is not available as such any
longer).

Regards
Felix

Ian Boston schrieb:
> Angela,
> Fantastic,
> I misread the patch forgetting that * might be allowed.
> Thank you.
> Ian
> 
> On 3 Dec 2009, at 17:44, Angela Schreiber wrote:
> 
>> hi ian
>>
>> JCR-1984 addressed a problem that protected properties defined
>> by the user/group node types were exposed by the #getPropertyNames
>> and #getProperty methods, although they could not be modified
>> by the corresponding set/remove methods.
>>
>> this issue should not affect additional, application specific
>> properties that were or will be stored with a user/group.
>> the nodetype still allows for
>>
>>  - * (UNDEFINED)
>>  - * (UNDEFINED) multiple
>>
>> and those props should be exposed by the mentioned methods.
>> i'm not aware of any change that would have broken this.
>>
>> angela
>>
>>
>>
>> Ian Boston wrote:
>>> Hi,
>>> IIUC [1], post 1.6 blocks an authorizable node from holding any
>>> properties, other than those listed in the schema.
>>> How do I add and retrieve a well defined set of properties for the
>>> node as was possible in JR15 ?
>>> We have an application that stores extra group and user metadata on
>>> the authorizable node and I really don't want to have to rewrite it.
>>> Thanks
>>> Ian
>>> 1 https://issues.apache.org/jira/browse/JCR-1984
>>
> 
> 

I have a bit of a dilemma. I'm working with Jackrabbit 2.0b3 and
trying to migrate to JCR2.0. However, since the XPATH query syntax is
deprecated, I'm investigating how to go about writing queries in
JCR-SQL2. Unfortunately, I haven't come up with many examples or
tutorials for the new JCR-SQL2 syntax.

One of the scenarios that I'd like to use frequently is searching a
subtree, i.e. starting at a particular node and searching all
descendants for certain property values. This is trivial to accomplish
in XPATH, but I can't figure out the correct (and efficient) way to do
it using SQL2. Can any one help me out with an example?

- Wes Bustraan

Angela,
Fantastic,
I misread the patch forgetting that * might be allowed.
Thank you.
Ian

On 3 Dec 2009, at 17:44, Angela Schreiber wrote:

> hi ian
>
> JCR-1984 addressed a problem that protected properties defined
> by the user/group node types were exposed by the #getPropertyNames
> and #getProperty methods, although they could not be modified
> by the corresponding set/remove methods.
>
> this issue should not affect additional, application specific
> properties that were or will be stored with a user/group.
> the nodetype still allows for
>
>  - * (UNDEFINED)
>  - * (UNDEFINED) multiple
>
> and those props should be exposed by the mentioned methods.
> i'm not aware of any change that would have broken this.
>
> angela
>
>
>
> Ian Boston wrote:
>> Hi,
>> IIUC [1], post 1.6 blocks an authorizable node from holding any  
>> properties, other than those listed in the schema.
>> How do I add and retrieve a well defined set of properties for the  
>> node as was possible in JR15 ?
>> We have an application that stores extra group and user metadata on  
>> the authorizable node and I really don't want to have to rewrite it.
>> Thanks
>> Ian
>> 1 https://issues.apache.org/jira/browse/JCR-1984
>

hi ian

JCR-1984 addressed a problem that protected properties defined
by the user/group node types were exposed by the #getPropertyNames
and #getProperty methods, although they could not be modified
by the corresponding set/remove methods.

this issue should not affect additional, application specific
properties that were or will be stored with a user/group.
the nodetype still allows for

   - * (UNDEFINED)
   - * (UNDEFINED) multiple

and those props should be exposed by the mentioned methods.
i'm not aware of any change that would have broken this.

angela



Ian Boston wrote:
> Hi,
> 
> IIUC [1], post 1.6 blocks an authorizable node from holding any 
> properties, other than those listed in the schema.
> How do I add and retrieve a well defined set of properties for the node 
> as was possible in JR15 ?
> 
> We have an application that stores extra group and user metadata on the 
> authorizable node and I really don't want to have to rewrite it.
> 
> Thanks
> Ian
> 
> 
> 1 https://issues.apache.org/jira/browse/JCR-1984
> 

Hi,

IIUC [1], post 1.6 blocks an authorizable node from holding any  
properties, other than those listed in the schema.

How do I add and retrieve a well defined set of properties for the  
node as was possible in JR15 ?

We have an application that stores extra group and user metadata on  
the authorizable node and I really don't want to have to rewrite it.

Thanks
Ian


1 https://issues.apache.org/jira/browse/JCR-1984

Hi Samuel

Have you looked at my current experiments I am doing upgrading the Sling
embedded Repository to Jackrabbit 2 in [1]. See also SLING-1212 [2]

[1]
http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/jackrabbit2upgrade
[2] https://issues.apache.org/jira/browse/SLING-1212

Regards
Felix

Samuel Cox schrieb:
> Does anyone have any experience with Jackrabbit and Equinox?
> 
> I have read the guide at
> http://cwiki.apache.org/SLING/launching-a-jcr-repository-inside-equinox.html.
> 
> 
> We currently build OSGi bundles from Jackrabbit 1.5.5 source and deploy
> them into the Felix OSGi container.  All has been going well for months.
>  However, we are soon going to migrate to Jackrabbit 1.6 in order to
> pick up the RepositoryCopier tool AND to the Equinox OSGi container.
> 
> Many thanks.
> 

On Thu, Dec 3, 2009 at 3:08 PM, Samuel Cox <crankydillo@gmail.com> wrote:
> Does anyone have any experience with Jackrabbit and Equinox?
I have no problem to run jackrabbit 2.0-alpha12 on Equinox 3.5.100

-Guo

Does anyone have any experience with Jackrabbit and Equinox?

I have read the guide at 
http://cwiki.apache.org/SLING/launching-a-jcr-repository-inside-equinox.html.

We currently build OSGi bundles from Jackrabbit 1.5.5 source and deploy 
them into the Felix OSGi container.  All has been going well for months. 
  However, we are soon going to migrate to Jackrabbit 1.6 in order to 
pick up the RepositoryCopier tool AND to the Equinox OSGi container.

Many thanks.

-- 
Samuel Cox

On Thu, Dec 3, 2009 at 11:53, Sunil Dhage <sunil.dhage@coreobjects.com> wrote:
> I have a problem regarding large binary files, which need to be versioned.
>
> Because the nodes which hold the above said binary files, they were getting stored both
at workspace and versions.
>
> After reading enough documentation, I could understand like i am missing datastore in
my repository.xml, which will be used to
> store files exceeding "minRecordLength" size and only references will be stored at workspace
and versionspace.
>
> Then I have added datastore to my repository.xml.  Please find the repository.xml attached.
>
> But the problem is now all of my binary files i.e. photos,documents are getting stored
at all the three locations.
> 1. Datastore
> 2. Workspaces,
> 3. Versions.

>From looking at the repository.xml you provided, I see that you are
using the xml persistence manager (for both workspaces and the
versions). AFAIK it doesn't cope with the datastore at all. It is very
old and only for debugging purposes, because it is not safe.

I strongly recommend you switch to a bundle persistence manager, eg.
the DerbyPersistenceManager or the H2PersistenceManager which are both
embedded and thus don't require any additional db setup or
configuration.

See http://wiki.apache.org/jackrabbit/PersistenceManagerFAQ

Note that you will have to set up the repository from scratch. If you
just remove the xml pm files, but keep the workspace directories incl.
the workspace.xml files, you will have to change the persistence
manager config in those too.

Regards,
Alex

-- 
Alexander Klimetschek
alexander.klimetschek@day.com

Hi,

I have a problem regarding large binary files, which need to be versioned.

Because the nodes which hold the above said binary files, they were getting stored both at
workspace and versions.

After reading enough documentation, I could understand like i am missing datastore in my repository.xml,
which will be used to 
store files exceeding "minRecordLength" size and only references will be stored at workspace
and versionspace.

Then I have added datastore to my repository.xml.  Please find the repository.xml attached.

But the problem is now all of my binary files i.e. photos,documents are getting stored at
all the three locations.
1. Datastore
2. Workspaces,
3. Versions.
Please find the screen shot depicting the above scenario

Can you please let me know how to make only references get stored in workspaces and versions.
I am sure there might be some parameter which will govern when to store the content and when
to store the reference of the file, which got stored at datastore.

Awaiting your response.

/Sunil Dhage

Hi Toby,

I am trying to implement the merging thing and since you have mentioned that
if a V1.3 and V1.2.1 are merged it would result in V1.4, is it right to
assume here that the node.merge() is called on V1.3 and not on 1.2.1. Also
am i right in saying that if i try to call a merge() on V1.3 i would be
getting a conflict?

I tried the same thing at my end. When i try to merge V1.3 and V1.2.1 (using
the names as per your example) i get a conflicting result. The Node Iterator
returned by merge() function contains the Node of V1.3 and has the
jcr:mergeFailed property set to V1.2.1's UUID.

I call node.doneMerge(V1.2.1) after that to mark the two versions as merged.
At this point if i check the jcr:mergeFailed property, i get a "Path does
not exist" Exception (due to which i assume that the property has been
cleared and the Nodes have been marked as merged) but when i call the
merge() on V1.3' Node i again get a Conflicting result.

Am i missing something?? If you could provide any input it would be great

On Thu, Dec 3, 2009 at 3:54 AM, Tobias Bocanegra <tripod@day.com> wrote:

> Hi,
> a branch is created when you perform a checkin on a node that has a
> base version which has successors.
> for example, if you have:
>
> v1.0 -> v1.1 -> v1.2 -> v1.3
>
> and you restore the node to v1.2 (i.e. set it's base version to 1.2),
> and then checkout, checkin, a new version v1.2.1 is created, which has
> v1.2 as predecessor and v1.2 has v1.3 and v1.2.1 as successor.
>
> although you can create branches without having a 2nd workspace, for
> merging you need one.
> so you need to have a corresponding versionable node in the 2nd
> workspace where you can merge against.
> but there is no application logic behind the merging, e.g. like in svn
> where the text files are "merged". so no content is actually merged,
> but only the 2 version branches are brought together again.
>
> in the above example, if node in ws1 has base version v1.3 and its
> corresponding node in ws2 has base version v.1.2.1 and you merge them,
> you'll get v1.4 that hase v1.3 and v1.2.1 as predecessors.
>
> hope this helps.
> regards, toby
>
>
> On Wed, Dec 2, 2009 at 5:48 PM, Luiz Fernando Teston
> <feu.teston@caravelatech.com> wrote:
> > I saw that node.checkin() just can be called once to create a new
> version.
> > Is it possible to create new parallel versions based on the same node?
> And
> > after doing some work on this different versions, is it possible to merge
> > two or more different versions to create a new merged version?
> >
> > The spec and other Jcr and Jackrabbit documentation doesn't show a
> merging
> > scenario, but it have some methods on javadoc which talks about merging.
> But
> > on the other side, the way I found to create new versions (checkin and
> > checkout on node) only permit to create version nodes on a linear way.
> >
> > Regards,
> >
> >
> > Fernando Teston
> >
> > On Tue, Dec 1, 2009 at 3:07 PM, Luiz Fernando Teston <
> > feu.teston@caravelatech.com> wrote:
> >
> >> Fellows,
> >>
> >> Is there any documentation, website or test showing few examples about
> >> versioning? I'm already using versioning on some parts of the software
> I'm
> >> working on, but now I need to do some branching behavior, and I didn't
> find
> >> any good material showing this.
> >>
> >> Best regards,
> >>
> >>
> >> Fernando Teston
> >>
> >
>



-- 
Regards

Robin Batra

Hi,

I am also having this issue.

A temporary workaround is to remove the jackrabbit directory found in
the working directory where you start your servlet engine (like TOMCAT_HOME
or JETTY_HOME).

I just filled a bug on JIRA for this problem [1].

[1] https://issues.apache.org/jira/browse/JCR-2421

-- 
Sébastien Launay

2009/12/3 anand <simer.anand88@gmail.com>:
>
> Hello Users,
>
> I was trying using jackrabbit-webapp-2.0.beta3 but after i started the
> server i move to Content Repository Setup at
> http://localhost:8080/jackrabbit-webapp-2.0-beta3/ and there i got two
> options either use existing on or create a new repository. I opted for new
> one. And the moment i click the "Create Content Repository" then it shows
> NEXT PAGE THAT IS Content Repository Exists.
>
> What could be problem?
>
> Thanks,
> simer

Hello Dennis,

it's because your using 2 times a child axis query (jcr:root and one
within the where clause) that makes it slow and. Explaining why is out
of scope for the user list, but I wrote quite some time ago a few
guidelines (most of them still valid):

http://n4.nabble.com/Explanation-and-solutions-of-some-Jackrabbit-queries-regarding-performance-td516614.html#a516614

I am not sure what nodetype jcr:content is, but suppose: my:contenttype

now, if your query would be:

//element(*,my:contenttype)[fn:lower-case(@cms:virtualPath)= '" + vpath + "']";

the query will be instant. Just take the parent node of the result and
you should be fine. Just wondering, are you building a brand new cms
on jcr? I am not sure what the @cms:virtualPath holds, but if you also
need virtual environments showing the same jcr nodes in different tree
structures you might wanna take a look here [1].

Regards Ard

[1] http://www.onehippo.org/cms7


On Thu, Dec 3, 2009 at 9:47 AM, Dennis van der Laan
<d.g.van.der.laan@rug.nl> wrote:
> Hi,
>
> It seems querying on a property is very slow on our system (running
> Jackrabbit 1.6.0): almost 1 second per query which would normally return
> 0 or 1 result.
>
> We use jcr:content nodes of type nt:unstructured to store the contents
> of a file (in the jcr:data property) and we store an array of Strings in
> a property cms:virtualPath on the same node. So basically, every file in
> our repository has the JCR path and zero or more virtual paths in the
> cms:virtualPath property. If we want to add a virtual path to a file, we
> have to check if the virtual path does not exist already. For this, we
> use an XPath query in the following code snippet:
>
> String vpath = QueryUtil.escapeForAttributeSearch(path.toLowerCase());
> String query =
> "/jcr:root//element(*,nt:hierarchyNode)[fn:lower-case(jcr:content/@cms:virtualPath)
> = '" + vpath + "']";
> Query q = queryManager.createQuery(query, Query.XPATH);
> NodeIterator ni = q.execute().getNodes();
> if (ni.getSize() == 0) {
>    throw new ItemNotFoundException("Unable to find item by virtual
> path: " + path);
> }
> else if (ni.getSize() > 1) {
>    throw new IllegalStateException("More than 1 item on virtual path: "
> + path);
> }
> else {
>    return ni.nextNode();
> }
>
> Our repository now contains around 500,000 virtual paths, more or less
> divided over 150,000 files which are evenly distributed over more than
> 1000 (nested) folders.
>
> The repository runs on an Intel Nehalem Xeon (2 x 2.5GHz) running
> Solaris 10 and the repository database (for datastore, filesystem, etc)
> runs on the same specs, on a different server, running Oracle 10g.
>
> When we try to add virtual paths in a batch (about 2000 virtual path
> properties for 1000 files) and all virtual paths already exist (so the
> above query returns 1 virtual path), we see a 100% load of the our
> Tomcat application (which means 1 core fully utilized).
>
> I would expect a JCR repository to be able to handle this kind of
> queries. How are these properties indexed? Is it possible to optimize
> the repository for this kind of queries? Or should I use a different
> query? The alternative would be to keep a different database which keeps
> track of the virtual paths, but keeping that in sync with the JCR
> repository would be a pain, at the least.
>
> Thanks for your ideas about this issue,
> Kind regards,
> Dennis van der Laan
>

Hi,

It seems querying on a property is very slow on our system (running
Jackrabbit 1.6.0): almost 1 second per query which would normally return
0 or 1 result.

We use jcr:content nodes of type nt:unstructured to store the contents
of a file (in the jcr:data property) and we store an array of Strings in
a property cms:virtualPath on the same node. So basically, every file in
our repository has the JCR path and zero or more virtual paths in the
cms:virtualPath property. If we want to add a virtual path to a file, we
have to check if the virtual path does not exist already. For this, we
use an XPath query in the following code snippet:

String vpath = QueryUtil.escapeForAttributeSearch(path.toLowerCase());
String query =
"/jcr:root//element(*,nt:hierarchyNode)[fn:lower-case(jcr:content/@cms:virtualPath)
= '" + vpath + "']";
Query q = queryManager.createQuery(query, Query.XPATH);
NodeIterator ni = q.execute().getNodes();
if (ni.getSize() == 0) {
    throw new ItemNotFoundException("Unable to find item by virtual
path: " + path);
}
else if (ni.getSize() > 1) {
    throw new IllegalStateException("More than 1 item on virtual path: "
+ path);
}
else {
    return ni.nextNode();
}

Our repository now contains around 500,000 virtual paths, more or less
divided over 150,000 files which are evenly distributed over more than
1000 (nested) folders.

The repository runs on an Intel Nehalem Xeon (2 x 2.5GHz) running
Solaris 10 and the repository database (for datastore, filesystem, etc)
runs on the same specs, on a different server, running Oracle 10g.

When we try to add virtual paths in a batch (about 2000 virtual path
properties for 1000 files) and all virtual paths already exist (so the
above query returns 1 virtual path), we see a 100% load of the our
Tomcat application (which means 1 core fully utilized).

I would expect a JCR repository to be able to handle this kind of
queries. How are these properties indexed? Is it possible to optimize
the repository for this kind of queries? Or should I use a different
query? The alternative would be to keep a different database which keeps
track of the virtual paths, but keeping that in sync with the JCR
repository would be a pain, at the least.

Thanks for your ideas about this issue,
Kind regards,
Dennis van der Laan

hi,

I'm trying to query (xpath) nodes of a specific namespace uri, but it
seems namespace-uri() and namespace-prefix() are not supported.
wlidcarding the local name part ( //prefix:* ) doesn't work either.
so, how can I do this?

also i notices an strange behavior. executing a query like this
doesn't throw exception, just no result:
//*[wrong-function-name() = 'nothing']
but executing this one results in InvalidQueryException:
//*[wrong-function-name()]
imo using mistaken function name should always result in exception.

Hello Users,

I was trying using jackrabbit-webapp-2.0.beta3 but after i started the
server i move to Content Repository Setup at
http://localhost:8080/jackrabbit-webapp-2.0-beta3/ and there i got two
options either use existing on or create a new repository. I opted for new
one. And the moment i click the "Create Content Repository" then it shows
NEXT PAGE THAT IS Content Repository Exists.

What could be problem?

Thanks,
simer
-- 
View this message in context: http://n4.nabble.com/Repository-setup-tp947389p947389.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Hi,
a branch is created when you perform a checkin on a node that has a
base version which has successors.
for example, if you have:

v1.0 -> v1.1 -> v1.2 -> v1.3

and you restore the node to v1.2 (i.e. set it's base version to 1.2),
and then checkout, checkin, a new version v1.2.1 is created, which has
v1.2 as predecessor and v1.2 has v1.3 and v1.2.1 as successor.

although you can create branches without having a 2nd workspace, for
merging you need one.
so you need to have a corresponding versionable node in the 2nd
workspace where you can merge against.
but there is no application logic behind the merging, e.g. like in svn
where the text files are "merged". so no content is actually merged,
but only the 2 version branches are brought together again.

in the above example, if node in ws1 has base version v1.3 and its
corresponding node in ws2 has base version v.1.2.1 and you merge them,
you'll get v1.4 that hase v1.3 and v1.2.1 as predecessors.

hope this helps.
regards, toby


On Wed, Dec 2, 2009 at 5:48 PM, Luiz Fernando Teston
<feu.teston@caravelatech.com> wrote:
> I saw that node.checkin() just can be called once to create a new version.
> Is it possible to create new parallel versions based on the same node? And
> after doing some work on this different versions, is it possible to merge
> two or more different versions to create a new merged version?
>
> The spec and other Jcr and Jackrabbit documentation doesn't show a merging
> scenario, but it have some methods on javadoc which talks about merging. But
> on the other side, the way I found to create new versions (checkin and
> checkout on node) only permit to create version nodes on a linear way.
>
> Regards,
>
>
> Fernando Teston
>
> On Tue, Dec 1, 2009 at 3:07 PM, Luiz Fernando Teston <
> feu.teston@caravelatech.com> wrote:
>
>> Fellows,
>>
>> Is there any documentation, website or test showing few examples about
>> versioning? I'm already using versioning on some parts of the software I'm
>> working on, but now I need to do some branching behavior, and I didn't find
>> any good material showing this.
>>
>> Best regards,
>>
>>
>> Fernando Teston
>>
>

I saw that node.checkin() just can be called once to create a new version.
Is it possible to create new parallel versions based on the same node? And
after doing some work on this different versions, is it possible to merge
two or more different versions to create a new merged version?

The spec and other Jcr and Jackrabbit documentation doesn't show a merging
scenario, but it have some methods on javadoc which talks about merging. But
on the other side, the way I found to create new versions (checkin and
checkout on node) only permit to create version nodes on a linear way.

Regards,


Fernando Teston

On Tue, Dec 1, 2009 at 3:07 PM, Luiz Fernando Teston <
feu.teston@caravelatech.com> wrote:

> Fellows,
>
> Is there any documentation, website or test showing few examples about
> versioning? I'm already using versioning on some parts of the software I'm
> working on, but now I need to do some branching behavior, and I didn't find
> any good material showing this.
>
> Best regards,
>
>
> Fernando Teston
>

Hi Thomas!

Thanks for the quick reply!

>> state of the JCR-SQL2 implementation in Jackrabbit
>
> Some features that are available in XPath are not yet available when
> using SQL-2. I don't know exactly what those feature are however.

And testing of QOM/SQL2 before a Jackrabbit 2.0 final release? It
appeared to me that the only JCR-SQL2 tests are currently parsing
tests but they only test if the queries are parsed without an
exception (the QOM tree they produce is not verified for example).
Also, are there any tests that execute QOM or SQL2 queries? I couldn't
find any, that's why I created a new test case in the last bug I
reported (JCR-2417).

Thanks again for all your work! I really appreciate it.

Cheers,
Philipp