From jira-events at lists.jboss.org  Wed Apr  1 11:17:45 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 11:17:45 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-337) Namespace Registries
 Create Two Nodes at /jcr:system/dna:namespaces
In-Reply-To: <13698106.1238076323288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7452092.1238599066488.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460028#action_12460028 ] 

Randall Hauch commented on DNA-337:
-----------------------------------

Applied the patch.

> Namespace Registries Create Two Nodes at /jcr:system/dna:namespaces
> -------------------------------------------------------------------
>
>                 Key: DNA-337
>                 URL: https://jira.jboss.org/jira/browse/DNA-337
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-337.patch
>
>
> After initializing a repository and creating a session, the system creates two nodes (same name siblings) at /jcr:system/dna:namespaces.  This confounds the RepositoryNodeTypeManagers attempts to assign a primary type to either dna:namespaces node as the definition of the dna:system type (the primary type for /jcr:system) does not allow SNS for the dna:namespaces node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 11:19:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 11:19:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-337) Namespace Registries
 Create Two Nodes at /jcr:system/dna:namespaces
In-Reply-To: <13698106.1238076323288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32300045.1238599162782.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-337.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved.

> Namespace Registries Create Two Nodes at /jcr:system/dna:namespaces
> -------------------------------------------------------------------
>
>                 Key: DNA-337
>                 URL: https://jira.jboss.org/jira/browse/DNA-337
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-337.patch
>
>
> After initializing a repository and creating a session, the system creates two nodes (same name siblings) at /jcr:system/dna:namespaces.  This confounds the RepositoryNodeTypeManagers attempts to assign a primary type to either dna:namespaces node as the definition of the dna:system type (the primary type for /jcr:system) does not allow SNS for the dna:namespaces node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 11:46:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 11:46:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-338) Definitions That
 Allow SNS Are Not Used For Nodes Without SNS
In-Reply-To: <14866962.1238078002336.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15190182.1238600782364.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460035#action_12460035 ] 

Randall Hauch commented on DNA-338:
-----------------------------------

Did not apply the patch, since it copied the same logic of DefinitionCache.allChildNodeDefinitions(Name childName, boolean requireSns) into JcrNodeType.allChildNodeDefinitions (rather than just calling the same DefinitionCache method).  The patch would have not have changed the behavior.  However, a few argument names were corrected (from "propertyName" to "childName"); likely due to a copy/paste error.

> Definitions That Allow SNS Are Not Used For Nodes Without SNS
> -------------------------------------------------------------
>
>                 Key: DNA-338
>                 URL: https://jira.jboss.org/jira/browse/DNA-338
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-338.patch
>
>
> Currently, RepositoryNodeTypeManager.findChildNodeDefinition will not consider definitions that allow SNS if the child node does not require SNS.  That is, if a new child node is added (and, hence, does not yet have any SNS) to a parent node that would only allow the child node with SNS (i.e., there's not definition that supports the child without SNS), findChildNodeDefinition returns null.
> Section 6.7.7 (regarding child node definitions) in the JCR 1.0 spec reads (in part) that the child node definition indicates "[w]hether this child node can have same-name siblings, meaning that the parent node can have more than one child node of this name."  I may be reading too much into the use of the word "can" instead of "must", but I think that SNS definitions allow for a single node, just like multi-valued property definitions support a multi-valued property that happens to have one value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 11:48:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 11:48:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-338) Definitions That
 Allow SNS Are Not Used For Nodes Without SNS
In-Reply-To: <14866962.1238078002336.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8569918.1238600902619.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-338.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


I'm going to mark this as resolved, but please reopen it if I've missed something.

> Definitions That Allow SNS Are Not Used For Nodes Without SNS
> -------------------------------------------------------------
>
>                 Key: DNA-338
>                 URL: https://jira.jboss.org/jira/browse/DNA-338
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-338.patch
>
>
> Currently, RepositoryNodeTypeManager.findChildNodeDefinition will not consider definitions that allow SNS if the child node does not require SNS.  That is, if a new child node is added (and, hence, does not yet have any SNS) to a parent node that would only allow the child node with SNS (i.e., there's not definition that supports the child without SNS), findChildNodeDefinition returns null.
> Section 6.7.7 (regarding child node definitions) in the JCR 1.0 spec reads (in part) that the child node definition indicates "[w]hether this child node can have same-name siblings, meaning that the parent node can have more than one child node of this name."  I may be reading too much into the use of the word "can" instead of "must", but I think that SNS definitions allow for a single node, just like multi-valued property definitions support a multi-valued property that happens to have one value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 12:10:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 12:10:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-338) Definitions That Allow
 SNS Are Not Used For Nodes Without SNS
In-Reply-To: <14866962.1238078002336.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12502726.1238602222593.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-338:
------------------------------

    Attachment: DNA-338-the-fix.patch


I believe the reason the patch did not include an effective change was that Brian had multiple changes brewing in his workspace (see DNA-339).  The actual correction for this behavior was buried in RepositoryNodeTypeManager.findChildNodeDefinition(...), where the boolean determining whether SNS were required was computed incorrectly.  See the attached "DNA-338-the-fix.patch", which was applied.

> Definitions That Allow SNS Are Not Used For Nodes Without SNS
> -------------------------------------------------------------
>
>                 Key: DNA-338
>                 URL: https://jira.jboss.org/jira/browse/DNA-338
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-338-the-fix.patch, DNA-338.patch
>
>
> Currently, RepositoryNodeTypeManager.findChildNodeDefinition will not consider definitions that allow SNS if the child node does not require SNS.  That is, if a new child node is added (and, hence, does not yet have any SNS) to a parent node that would only allow the child node with SNS (i.e., there's not definition that supports the child without SNS), findChildNodeDefinition returns null.
> Section 6.7.7 (regarding child node definitions) in the JCR 1.0 spec reads (in part) that the child node definition indicates "[w]hether this child node can have same-name siblings, meaning that the parent node can have more than one child node of this name."  I may be reading too much into the use of the word "can" instead of "must", but I think that SNS definitions allow for a single node, just like multi-valued property definitions support a multi-valued property that happens to have one value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 12:52:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 12:52:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-339) JCR Type
 Registration and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24356973.1238604742514.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460047#action_12460047 ] 

Randall Hauch commented on DNA-339:
-----------------------------------

I like the approach of using templates (ala 283).  Is there a way to change the NodeTypeSource-approach to use the new registration mechanism?  Seems like that might clean up things quite a bit.

I also do like where you are going with refactoring of findPropertyDefinition to use Predicates.  However, I'm not convinced it's better.  One goal I had with the old design was that the logic was very obvious and "in your face" (not masked by a lot of method calls), and I deemed this as more beneficial than the ugliness of the duplication.  So while the new approach gets rid of the duplication, it doesn't really keep the "in your face" logic.  Plus, the new approach doesn't reduce the number of lines (385 new vs 373 old).  Besides, I'd prefer for this change to be pulled out into a different patch (or even a different issue).

Also, considering the size of the change to support registration and unregistration, would it be better to not address thread-safety in the same patch?  Also, although using a thread-safe container would be beneficial, we made need to use an explicit ReadWriteLock if the thread-safe container doesn't offer the required level of atomicity.

Requiring users to oder the types to be registered is a perfectly valid assumption, I think.  At least for now, since it'd likely keep the implementation much more simplistic.

One thing we're going to have to address is that we can't update existing JcrNodeType objects.  So, if a supertype is changed (re-registered), we really need to rebuild all of the node types that extend it.  Unfortunately this is the only way to truly have immutable objects.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-339_RFC.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 13:28:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 1 Apr 2009 13:28:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-339) JCR Type
 Registration and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32607155.1238606902286.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460052#action_12460052 ] 

Brian Carothers commented on DNA-339:
-------------------------------------

I agree that NodeTypeSources should switch to templates (and, eventually, to sets of CND files).  I just want to get this first part checked in first.

I will pull out the predicate approach in the next patch.  When I started refactoring that, I expected type registration to have slightly different needs than it turned out to have.

I am fine with not putting thread-safety into the patch.  I will pull out the half-hearted and totally non-working attempt.

We don't currently allowUpdates in the patch that I'm getting ready to submit, so the modification issue can be deferred.


> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-339_RFC.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 18:05:36 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 1 Apr 2009 18:05:36 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-340) Projection of Node
 Types onto System View
Message-ID: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>

Projection of Node Types onto System View
-----------------------------------------

                 Key: DNA-340
                 URL: https://jira.jboss.org/jira/browse/DNA-340
             Project: DNA
          Issue Type: Feature Request
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers
            Priority: Minor


It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 18:07:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 1 Apr 2009 18:07:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-340) Projection of Node
 Types onto System View
In-Reply-To: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26899410.1238623642275.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-340:
--------------------------------

    Attachment: DNA-340.patch


Added patch that projects node types onto /jcr:system/jcr:nodeTypes at workspace creation time.  No support for updating the mapping is provided as there is no way to modify type definitions at runtime at this time.

> Projection of Node Types onto System View
> -----------------------------------------
>
>                 Key: DNA-340
>                 URL: https://jira.jboss.org/jira/browse/DNA-340
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-340.patch
>
>
> It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  1 18:28:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 1 Apr 2009 18:28:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-194) Implement update JCR
	capability
In-Reply-To: <19952894.1218050517308.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15434932.1238624902945.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460129#action_12460129 ] 

Randall Hauch commented on DNA-194:
-----------------------------------

Implemented Node.addNode(...) methods and Node.save().  Some enhancements to the Request classes were required to allow the SessionCache to easily figure out whether a request affected a particular branch.  Also enabled one TCK unit test.

> Implement update JCR capability
> -------------------------------
>
>                 Key: DNA-194
>                 URL: https://jira.jboss.org/jira/browse/DNA-194
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>            Reporter: Johnny Verhaeg
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-194-session-cache.patch, DNA-194_move_value_cast.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 14:54:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 14:54:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-194) Implement update JCR
	capability
In-Reply-To: <19952894.1218050517308.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8523110.1238698462468.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460335#action_12460335 ] 

Randall Hauch commented on DNA-194:
-----------------------------------

Added more support for Node.setProperty(...), and enabled several TCK unit tests.

> Implement update JCR capability
> -------------------------------
>
>                 Key: DNA-194
>                 URL: https://jira.jboss.org/jira/browse/DNA-194
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>            Reporter: Johnny Verhaeg
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-194-session-cache.patch, DNA-194_move_value_cast.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 15:04:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 15:04:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-340) Projection of Node
 Types onto System View
In-Reply-To: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20749273.1238699062278.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460336#action_12460336 ] 

Randall Hauch commented on DNA-340:
-----------------------------------

Applied the patch, which stores the node type information in the repository graph, with one exception.  For various reasons (including those related to performance of running so many TCK unit tests), we want to be able to have a JcrRepository configuration property that says whether the node types should be stored in the graph.  So, the "batch.execute()" line was commented out at the end of the RepositoryNodeTypeManager.projectOnto(Graph,Path) method.  This essentially prevents the node types from being added, but still ensures that the "/jcr:system/dna:nodeTypes" node exists.

Leaving this issue open until the configuration option is addressed.

> Projection of Node Types onto System View
> -----------------------------------------
>
>                 Key: DNA-340
>                 URL: https://jira.jboss.org/jira/browse/DNA-340
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-340.patch
>
>
> It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 15:18:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 15:18:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-309) Design URLs and
 rerepresentations, leaving room for future UI features and maybe WebDAV
In-Reply-To: <14708676.1237392922690.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1869175.1238699920909.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460338#action_12460338 ] 

Randall Hauch commented on DNA-309:
-----------------------------------

Another interesting discussion regarding the Sun Cloud API (Tim Bray) and responses (including Roy Fielding): http://www.infoq.com/news/2009/04/post-state-appropriate

> Design URLs and rerepresentations, leaving room for future UI features and maybe WebDAV
> ---------------------------------------------------------------------------------------
>
>                 Key: DNA-309
>                 URL: https://jira.jboss.org/jira/browse/DNA-309
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Web Application
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.5
>
>
> For right now, we need URLs for just publishing and un-publishing content.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 15:49:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 2 Apr 2009 15:49:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-340) Projection of Node
 Types onto System View
In-Reply-To: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11334541.1238701762277.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-340:
--------------------------------

    Attachment: DNA-340_disable_project_node_types_feature.patch


Here's a patch that adds the concept of "Settings" at the JcrRepository level (presumably to eventually be configured through the JNDIObjectFactory that creates the repository).

The first setting allows one to enable the projection of node types, which is disabled by default.  The patch does enable the projection for the Hudson TCK runs.

There are a couple of misc. cleanup lines in the patch as well.

> Projection of Node Types onto System View
> -----------------------------------------
>
>                 Key: DNA-340
>                 URL: https://jira.jboss.org/jira/browse/DNA-340
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-340.patch, DNA-340_disable_project_node_types_feature.patch
>
>
> It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 16:16:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 16:16:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-340) Projection of Node
 Types onto System View
In-Reply-To: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8610994.1238703383831.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460355#action_12460355 ] 

Randall Hauch commented on DNA-340:
-----------------------------------

Applied the 2nd patch, which adds support to JcrRepository for configurable options, with a single option as to whether or not the node types should be projected under "/jcr:system/dna:nodeTypes".  Minor change from the patch was to reorder the constructor parameters of JcrRepository to match the other existing constructor.

> Projection of Node Types onto System View
> -----------------------------------------
>
>                 Key: DNA-340
>                 URL: https://jira.jboss.org/jira/browse/DNA-340
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-340.patch, DNA-340_disable_project_node_types_feature.patch
>
>
> It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 16:41:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 16:41:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-340) Projection of Node
 Types onto System View
In-Reply-To: <13443575.1238623536348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14687016.1238704882442.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-340.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Changed the name of JcrRepository.Settings to JcrRepository.Options, added a mechanism for setting up defaults, and added a public method to get the unmodifiable options map.  Also changed JcrWorkspace to use the repository's options map (rather than a custom boolean constructor parameter) to determine whether it should project the node types as content.

Marking issue as resolved, since this address the main concern.

> Projection of Node Types onto System View
> -----------------------------------------
>
>                 Key: DNA-340
>                 URL: https://jira.jboss.org/jira/browse/DNA-340
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-340.patch, DNA-340_disable_project_node_types_feature.patch
>
>
> It may be useful if DNA projected its JCR node types onto the system view in a manner analogous to the way that permanent namespace mappings are projected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 17:21:10 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 17:21:10 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
Message-ID: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>

Graph API behavior when removing all property values doesn't reflect that of JCR
--------------------------------------------------------------------------------

                 Key: DNA-341
                 URL: https://jira.jboss.org/jira/browse/DNA-341
             Project: DNA
          Issue Type: Bug
          Components: API, Graph, JCR
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Priority: Critical
             Fix For: 0.4


Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:

    Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
    property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
    within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
    value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 

However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 17:21:10 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 17:21:10 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28403042.1238707270794.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch reassigned DNA-341:
---------------------------------

    Assignee: Randall Hauch


> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  2 17:50:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 2 Apr 2009 17:50:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12757117.1238709022974.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460371#action_12460371 ] 

Randall Hauch commented on DNA-341:
-----------------------------------

The Graph API currently has a RemovePropertiesRequest that takes a set of property names to be removed.  (This could be optimized to have another RemovePropertyRequest that would be optionally supported, with a default implementation in the RequestProcessor that would use RemovePropertiesRequest.)  However, it is also possible to use UpdatePropertiesRequest, and the expected behavior is currently to remove any property with no values.

This latter behavior could be changed to make UpdatePropertiesRequest purely update (no remove), and require the use of RemovePropertiesRequest for any remove operations.  I'm not sure what the impact of this would be in terms of existing connectors or components that use the Graph interface.

Another option would be to continue to allow UpdatePropertiesRequest to define removal operations, but to distinguish between setting a property to have no values versus removing the property.  The former could be accomplished by using an empty array, while the latter could be defined by a null array reference.

Either way, there is likely to be an impact on existing connectors, components that directly use the requests (e.g., the Graph API implementation), and maybe even higher-level components.  Fortunately, there have already been significant changes to the request and connector framework within this release, so the impact to JBoss DNA users is not much different than is current for 0.4.


> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr  3 16:35:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 3 Apr 2009 16:35:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22399394.1238790922614.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460564#action_12460564 ] 

Randall Hauch commented on DNA-341:
-----------------------------------

The UpdatePropertiesRequest and RemovePropertiesRequest probably need to be combined.  The pros:
- It clearly and singularly defines the semantics (a remove is a remove, a set is a set, etc.)
- Reduce by one the number of RequestProcessor.process(...) methods that an implementation must provide.
- Separate requests may mean very similar code in process(UpdatePropertiesRequest) and process(RemovePropertiesRequest), so combining means that connectors are less likely to have duplicate code
- Combining means that more property changes (adds, sets, and removes) are handled in one RequestProcessor.process(...) method, which for some connector implementations could be far more efficient than if there were multiple process(...) method invocations (e.g., one invocation with an UpdatePropertiesRequest and a second for a RemovePropertiesRequest).
- Allows for the existing Graph optimization to reuse a single request for adjacent add/set/remove operations on the same node
- Any future optimization logic (request planning) might be simpler with a single merged request than with separate kinds of requests
- We can introduce other optional requests (those where the corresponding RequestProcessor.process(...) method has a default implementation) that have more optimal structures for a single operation.

The cons:
- Existing connectors have to be changed.  (This may be moot anyway, since they have to be changed to some degree in order to fix this issue.)
- The combined request may have a larger size for doing only one operation

> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr  3 21:48:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 3 Apr 2009 21:48:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-342) Wrong Values is Cast
 When Setting Property with Castable Type
Message-ID: <1614046.1238809702274.JavaMail.jira@cloud.prod.atl2.jboss.com>

Wrong Values is Cast When Setting Property with Castable Type
-------------------------------------------------------------

                 Key: DNA-342
                 URL: https://jira.jboss.org/jira/browse/DNA-342
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers


If one sets a property with a single value that is not the same as the required type of the definition but is castable to the required type of the definition (e.g., setting a binary property with a string value), SessionCache.setProperty tries to convert the JcrValue object (which ends up converting JcrValue.toString) instead of the converting the value that the JcrValue object wraps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr  3 21:52:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 3 Apr 2009 21:52:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-342) Wrong Values is Cast
 When Setting Property with Castable Type
In-Reply-To: <1614046.1238809702274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10343879.1238809942271.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-342:
--------------------------------

    Attachment: DNA-342.patch


Trivial patch to fix the defect.

> Wrong Values is Cast When Setting Property with Castable Type
> -------------------------------------------------------------
>
>                 Key: DNA-342
>                 URL: https://jira.jboss.org/jira/browse/DNA-342
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-342.patch
>
>
> If one sets a property with a single value that is not the same as the required type of the definition but is castable to the required type of the definition (e.g., setting a binary property with a string value), SessionCache.setProperty tries to convert the JcrValue object (which ends up converting JcrValue.toString) instead of the converting the value that the JcrValue object wraps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sun Apr  5 16:22:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 5 Apr 2009 16:22:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
Message-ID: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>

TCK Tests for Node Mixin Modification Methods Fail
--------------------------------------------------

                 Key: DNA-343
                 URL: https://jira.jboss.org/jira/browse/DNA-343
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers


The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sun Apr  5 16:41:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 5 Apr 2009 16:41:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27326556.1238964082410.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-343:
--------------------------------

    Attachment: DNA-342.patch


Attaching patch that takes a stab the missing functionality.  

In addition to the usual rules required by the JCR 1.0 specification, the canAddMixin and addMixin methods enforce internal consistency by requiring that:
     * No properties defined by the mixin type can have the same name as any property defined by the node's primary type or any of its existing mixin types.
     * No child nodes defined by the mixin type can have the same name as any child node defined by the node's primary type or any of its existing mixin types.
     * If the node has a current residual definition for child nodes and/or properties, all nodes and properties that share a name with a child node definition or property definition from the new mixin type must be compatible with the definition provided by the new mixin type.

The removeMixin imposes the following rule in addition to those required by the JCR 1.0 specification:
     * A mixin type can be removed if and only if all of the node's existing child nodes and properties would still have a valid definition from the node's primary type or other mixin types. In practice, this means that either the node must have a residual definition compatible with any of the remaining child nodes or properties that currently use a definition from the to-be-removed mixin type or all of the child nodes and properties that use a definition from the to-be-removed mixin type must be removed prior to calling this method.

The known issue is that it does not update the session cache correctly, so child nodes (or properties) that used to use a residual definition but should use a definition from the mixin type after it has been added still use the residual definition.  I'm looking for feedback on that front.

> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-342.patch, DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sun Apr  5 16:41:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 5 Apr 2009 16:41:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17673552.1238964082448.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-343:
--------------------------------

    Attachment: DNA-343.patch


Please disregard the previous attachment (but not the comment).  DNA-343.patch is the appropriate patch for this JIRA issue.

> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-342.patch, DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sun Apr  5 20:06:23 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 5 Apr 2009 20:06:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-344)
 JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per
 Specification
Message-ID: <10604558.1238976383222.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification
--------------------------------------------------------------------------------------

                 Key: DNA-344
                 URL: https://jira.jboss.org/jira/browse/DNA-344
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers


Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type.  We currently defer all casts of the value and do not fail fast.

This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sun Apr  5 20:08:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 5 Apr 2009 20:08:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-344)
 JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per
 Specification
In-Reply-To: <10604558.1238976383222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31669656.1238976502559.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-344:
--------------------------------

    Attachment: DNA-344.patch


Here's a crude, but effective patch for the defect.  In practice, I wonder if doing an eager conversion to the correct type for JcrValue's internal value would allow us to remove a bunch of the conditional "pre-casts" in JcrValue.withTypeAndValue.

> JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-344
>                 URL: https://jira.jboss.org/jira/browse/DNA-344
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-344.patch
>
>
> Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type.  We currently defer all casts of the value and do not fail fast.
> This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr  6 10:38:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 6 Apr 2009 10:38:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-342) Wrong Values is Cast
 When Setting Property with Castable Type
In-Reply-To: <1614046.1238809702274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2017046.1239028702406.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-342.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied patch to correct the use of a wrong variable.

> Wrong Values is Cast When Setting Property with Castable Type
> -------------------------------------------------------------
>
>                 Key: DNA-342
>                 URL: https://jira.jboss.org/jira/browse/DNA-342
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-342.patch
>
>
> If one sets a property with a single value that is not the same as the required type of the definition but is castable to the required type of the definition (e.g., setting a binary property with a string value), SessionCache.setProperty tries to convert the JcrValue object (which ends up converting JcrValue.toString) instead of the converting the value that the JcrValue object wraps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr  6 10:40:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 6 Apr 2009 10:40:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4397667.1239028822599.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-343:
------------------------------

    Attachment:     (was: DNA-342.patch)


> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr  6 10:40:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 6 Apr 2009 10:40:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21086917.1239028822652.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460744#action_12460744 ] 

Randall Hauch commented on DNA-343:
-----------------------------------

Removed the DNA-342.patch attachment, which was for a different issue.

> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr  6 11:57:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 6 Apr 2009 11:57:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-344)
 JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per
 Specification
In-Reply-To: <10604558.1238976383222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10418417.1239033442280.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460772#action_12460772 ] 

Randall Hauch commented on DNA-344:
-----------------------------------

Applied the patch.  Yes, it probably is better to do an eager conversion.  Leaving this issue open for discussion or for another patch for the eager conversion.

> JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-344
>                 URL: https://jira.jboss.org/jira/browse/DNA-344
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-344.patch
>
>
> Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type.  We currently defer all casts of the value and do not fail fast.
> This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr  6 17:23:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 6 Apr 2009 17:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-344)
 JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per
 Specification
In-Reply-To: <10604558.1238976383222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29815269.1239053002292.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-344:
--------------------------------

    Attachment: DNA-344_no_extra_conversion.patch


Uploaded a second patch (delta from the first) that removes the now-extraneous extra conversion in JcrValue.asType.  Since JcrSession.getValueFactory.create(String, int) now eagerly converts the given value to the appropriate native type, our JcrValues should always have a native type that corresponds to their JCR PropertyType.

All dna-jcr tests still pass.

> JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-344
>                 URL: https://jira.jboss.org/jira/browse/DNA-344
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-344.patch, DNA-344_no_extra_conversion.patch
>
>
> Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type.  We currently defer all casts of the value and do not fail fast.
> This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 17:21:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 17:21:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24106255.1239139283613.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-341:
------------------------------

    Attachment: DNA-341.patch


Attached a patch that changes the connector API.  Specifically the semantics and a few method signatures of UpdatePropertiesRequest class were changed to no longer assume that an empty property should be removed; rather, the names of properties that are to be removed are tracked explicitly, and the number of values in a property no longer has any relationship to whether the property is to be removed.  All connectors were changed to apply these new semantics.

A number of other changes to the connector API were made.  New SetPropertyRequest and RemovePropertyRequest requests types were added as being more efficient when a single property is being set or removed.  These are optional requests, meaning that the RequestProcessor has default implementations for the corresponding "process" methods that convert the reqeusts to UpdatedPropertiesRequest.  Thus, a connector doesn't have to implement these, but it may be more efficient for it to do so.

Also, the Graph batch implementation was improved to optimize adjacent calls to set/remove properties on the same node.  In other words, if a batch is used to set a property on node A and then is immediately used to set another property on the same node, the batch will combine the two requests.  However, this optimization does not apply if any other operations are performed between the set/remove property operations.

Finally, a minor error was found and corrected in how the connector unit tests reported the (trivial) metrics for creating nodes. The total times (line 2) were correct, but the average and the times for additional nodes (line 3) were all incorrect.

> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-341.patch
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 17:23:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 17:23:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2719123.1239139415366.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461100#action_12461100 ] 

Randall Hauch commented on DNA-341:
-----------------------------------

The patch also removes the RemovedPropertiesRequest, since it didn't offer any benefit over UpdatePropertiesRequest (and since it is simpler to only have one).  All connectors were updated to reflect these semantics.

> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-341.patch
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 18:25:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 18:25:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-344)
 JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per
 Specification
In-Reply-To: <10604558.1238976383222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12664170.1239143122291.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-344.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the second patch, which closes out this issue.

> JcrSession.getValueFactory.create(String, int) Does Not Fail Fast as per Specification
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-344
>                 URL: https://jira.jboss.org/jira/browse/DNA-344
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-344.patch, DNA-344_no_extra_conversion.patch
>
>
> Section 7.1.5.3 of the JCR 1.0.1 specification (pg 199) indicates that ValueFactory.create(String value, int propertyType) should throw a ValueFormatException if value cannot be converted to the correct type.  We currently defer all casts of the value and do not fail fast.
> This prevents one of the test cases in the L2 TCK test ValueFactoryTest from passing successfully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 18:31:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 18:31:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28609654.1239143482303.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461111#action_12461111 ] 

Randall Hauch commented on DNA-343:
-----------------------------------

After discussing with Brian, we came to the conclusion that this state is a good first implementation, which errs on the side of being more strict.  Committed the patch in rev 812.

> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 18:36:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 18:36:31 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-341) Graph API behavior
 when removing all property values doesn't reflect that of JCR
In-Reply-To: <20108870.1238707270723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18665557.1239143791053.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-341.
-------------------------------

    Resolution: Done


Marking as resolved.

> Graph API behavior when removing all property values doesn't reflect that of JCR
> --------------------------------------------------------------------------------
>
>                 Key: DNA-341
>                 URL: https://jira.jboss.org/jira/browse/DNA-341
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Graph, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-341.patch
>
>
> Section 4.7.3 of the JSR-170 specification (version 1.0.1) states:
>     Every property must have a value. The range of property states does not include having a "null value", or "no value". Setting a 
>     property to "null" is equivalent to removing that property. In the case of multi-value properties, the setting of a particular value 
>     within the array to null results in the removal of that value and the compacting of the array. As a result it is possible to have a multi- 
>     value property with no values (an empty array). See 7.1.5 Adding and Writing Properties. 
> However, currently the Graph API and connector behavior is such that whenever a property is updated (or set) to no values, the property is removed automatically.  This means that it is not possible for the Graph API or connectors to support a multi-valued JCR property with no values.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 20:51:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 7 Apr 2009 20:51:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-345)
 JcrMultiValueProperty.setValues(null) Doesn't Remove Property
Message-ID: <25197101.1239151882277.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrMultiValueProperty.setValues(null) Doesn't Remove Property 
--------------------------------------------------------------

                 Key: DNA-345
                 URL: https://jira.jboss.org/jira/browse/DNA-345
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers


Minor bug that keeps SetValueStringTest in JR TCK from fully passing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 21:44:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 7 Apr 2009 21:44:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-345)
 JcrMultiValueProperty.setValues(null) Doesn't Remove Property
In-Reply-To: <25197101.1239151882277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19101486.1239155062301.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-345:
--------------------------------

    Attachment: DNA-345.patch


Trivial fix for trivial bug.  

> JcrMultiValueProperty.setValues(null) Doesn't Remove Property 
> --------------------------------------------------------------
>
>                 Key: DNA-345
>                 URL: https://jira.jboss.org/jira/browse/DNA-345
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-345.patch
>
>
> Minor bug that keeps SetValueStringTest in JR TCK from fully passing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 21:55:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 7 Apr 2009 21:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-345)
 JcrMultiValueProperty.setValues(null) Doesn't Remove Property
In-Reply-To: <25197101.1239151882277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29242500.1239155722358.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-345:
--------------------------------

    Attachment: DNA-345_works.patch


Er, here's a patch that actually works.  Sorry.

> JcrMultiValueProperty.setValues(null) Doesn't Remove Property 
> --------------------------------------------------------------
>
>                 Key: DNA-345
>                 URL: https://jira.jboss.org/jira/browse/DNA-345
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-345.patch, DNA-345_works.patch
>
>
> Minor bug that keeps SetValueStringTest in JR TCK from fully passing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 23:06:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 23:06:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-345)
 JcrMultiValueProperty.setValues(null) Doesn't Remove Property
In-Reply-To: <25197101.1239151882277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25823006.1239159982274.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461147#action_12461147 ] 

Randall Hauch commented on DNA-345:
-----------------------------------

Applied the "works" patch, and also uncommented a few more TCK unit tests after additional corrections to the AbstractJcrNode.setProperty implementations.

> JcrMultiValueProperty.setValues(null) Doesn't Remove Property 
> --------------------------------------------------------------
>
>                 Key: DNA-345
>                 URL: https://jira.jboss.org/jira/browse/DNA-345
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-345.patch, DNA-345_works.patch
>
>
> Minor bug that keeps SetValueStringTest in JR TCK from fully passing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr  7 23:08:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 7 Apr 2009 23:08:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-345)
 JcrMultiValueProperty.setValues(null) Doesn't Remove Property
In-Reply-To: <25197101.1239151882277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16270500.1239160102282.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-345.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved, since this issue is fixed.

> JcrMultiValueProperty.setValues(null) Doesn't Remove Property 
> --------------------------------------------------------------
>
>                 Key: DNA-345
>                 URL: https://jira.jboss.org/jira/browse/DNA-345
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-345.patch, DNA-345_works.patch
>
>
> Minor bug that keeps SetValueStringTest in JR TCK from fully passing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  8 10:08:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 8 Apr 2009 10:08:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-346) JR TCK Tests for
 SetPropertyStringTest and SetPropertyValueTest Fail
Message-ID: <887215.1239199702275.JavaMail.jira@cloud.prod.atl2.jboss.com>

JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail
--------------------------------------------------------------------

                 Key: DNA-346
                 URL: https://jira.jboss.org/jira/browse/DNA-346
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.4
            Reporter: Brian Carothers


The L2 TCK tests SetPropertyStringTest and SetPropertyValueTest fail.  Opening this defect as a placeholder for the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr  8 10:14:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 8 Apr 2009 10:14:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-346) JR TCK Tests for
 SetPropertyStringTest and SetPropertyValueTest Fail
In-Reply-To: <887215.1239199702275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26402782.1239200062370.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-346:
--------------------------------

    Attachment: DNA-346.patch


Fixed a couple of minor defects that were keeping the tests from passing as per Javadoc in section 7.1.5 of the 1.0.1 spec.

- Added code to "compact" value arrays, that is, Node.setProperty(String, Value[]) and Node.setProperty(String, Value[], int) should ignore any null values in the value array.
- Added code (AbstractJcrNode.checkType) to throw a ValueFormatException if the values in the value arrays in Node.setProperty(String, Value[]) and Node.setProperty(String, Value[], int) are not all of the same type.  The spec permits coercing the values into the type expected by the property, but it does not permit different types of values in the array.
- Added code (AbstractJcrNode.checkCardinalityOfExistingProperty) to throw a ValueFormatException if one attempts to set a multi-valued value onto an existing single-valued array (or vice versa) directly through the node.

> JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail
> --------------------------------------------------------------------
>
>                 Key: DNA-346
>                 URL: https://jira.jboss.org/jira/browse/DNA-346
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>         Attachments: DNA-346.patch
>
>
> The L2 TCK tests SetPropertyStringTest and SetPropertyValueTest fail.  Opening this defect as a placeholder for the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-339) JCR Type Registration
 and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27313779.1239305975641.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-339:
------------------------------

        Fix Version/s: 0.4
    Affects Version/s: 0.3
                           (was: 0.4)


> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_RFC.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-346) JR TCK Tests for
 SetPropertyStringTest and SetPropertyValueTest Fail
In-Reply-To: <887215.1239199702275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23785305.1239305975601.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-346:
------------------------------

        Fix Version/s: 0.4
    Affects Version/s: 0.3
                           (was: 0.4)


> JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail
> --------------------------------------------------------------------
>
>                 Key: DNA-346
>                 URL: https://jira.jboss.org/jira/browse/DNA-346
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-346.patch
>
>
> The L2 TCK tests SetPropertyStringTest and SetPropertyValueTest fail.  Opening this defect as a placeholder for the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-335) DNA's NodeTypeManager
 implementation does not allow multiple definitions
 with the same name
In-Reply-To: <21319415.1237837222292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13317139.1239305975725.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-335:
------------------------------

        Fix Version/s: 0.4
    Affects Version/s: 0.3


> DNA's NodeTypeManager implementation does not allow multiple definitions with the same name
> -------------------------------------------------------------------------------------------
>
>                 Key: DNA-335
>                 URL: https://jira.jboss.org/jira/browse/DNA-335
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-335-definitionsWithSameName.patch, DNA-335_clean_type_source.patch, DNA-335_overriding_definitions.patch
>
>
> The JCR Specification (version 1.0.1) does not preclude that there may be multiple property definitions with the same name, or that there may be multiple child definitions with the same name.  JCR 1.0 (version 1.0.1) DOES say that there may be multiple residual definitions with the same name.  However, the draft version of the JSR-283 specification does have a new section 4.7.15 that specifically addresses and allows multiple definitions with the same name, as long as they are distinguishable from the other definitions with the same name (for property definitions, this means the type must be different; for child node definitions, this means the required primary types attribute).
> There are a number of places where the logic is expecting a single property definition (or child definition) given a node type and a definition name.  This is obviously flawed.  Also, our logic to select the "best" property definition or "best" child node definition doesn't seem to be correct, in that it tends to favor less-restricted definitions that are lower in the type hierarchy rather than very good matching definitions higher in the type hierarchy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5469374.1239305975683.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-343:
------------------------------

        Fix Version/s: 0.4
    Affects Version/s: 0.3
                           (was: 0.4)


> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-285) Pass all Level 1 TCK
	unit tests
In-Reply-To: <18642947.1235148944956.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4974990.1239305975776.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-285:
------------------------------

        Fix Version/s: 0.4
    Affects Version/s: 0.3


> Pass all Level 1 TCK unit tests
> -------------------------------
>
>                 Key: DNA-285
>                 URL: https://jira.jboss.org/jira/browse/DNA-285
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-285_basic.patch
>
>
> We don't currently pass all of the Level 1 TCK unit tests.  See dna-jcr/src/test/java/org/jboss/dna/jcr/JackrabbitJcrTckTest.java, and specifically the JcrLevelOneTestSuite nested class.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:41 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:41 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-335) DNA's NodeTypeManager
 implementation does not allow multiple definitions
 with the same name
In-Reply-To: <21319415.1237837222292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25958640.1239305981525.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-335:
------------------------------

    Component/s: JCR


> DNA's NodeTypeManager implementation does not allow multiple definitions with the same name
> -------------------------------------------------------------------------------------------
>
>                 Key: DNA-335
>                 URL: https://jira.jboss.org/jira/browse/DNA-335
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-335-definitionsWithSameName.patch, DNA-335_clean_type_source.patch, DNA-335_overriding_definitions.patch
>
>
> The JCR Specification (version 1.0.1) does not preclude that there may be multiple property definitions with the same name, or that there may be multiple child definitions with the same name.  JCR 1.0 (version 1.0.1) DOES say that there may be multiple residual definitions with the same name.  However, the draft version of the JSR-283 specification does have a new section 4.7.15 that specifically addresses and allows multiple definitions with the same name, as long as they are distinguishable from the other definitions with the same name (for property definitions, this means the type must be different; for child node definitions, this means the required primary types attribute).
> There are a number of places where the logic is expecting a single property definition (or child definition) given a node type and a definition name.  This is obviously flawed.  Also, our logic to select the "best" property definition or "best" child node definition doesn't seem to be correct, in that it tends to favor less-restricted definitions that are lower in the type hierarchy rather than very good matching definitions higher in the type hierarchy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:39:41 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:39:41 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-285) Pass all Level 1 TCK
	unit tests
In-Reply-To: <18642947.1235148944956.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25838125.1239305981481.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-285:
------------------------------

    Component/s: JCR


> Pass all Level 1 TCK unit tests
> -------------------------------
>
>                 Key: DNA-285
>                 URL: https://jira.jboss.org/jira/browse/DNA-285
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-285_basic.patch
>
>
> We don't currently pass all of the Level 1 TCK unit tests.  See dna-jcr/src/test/java/org/jboss/dna/jcr/JackrabbitJcrTckTest.java, and specifically the JcrLevelOneTestSuite nested class.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr  9 15:47:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 9 Apr 2009 15:47:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-339) JCR Type
 Registration and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6996783.1239306442409.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461558#action_12461558 ] 

Randall Hauch commented on DNA-339:
-----------------------------------

The specification requires that all node types (directly or indirectly) extend "nt:base".  As such, it would be nice to automatically supply this supertype if not already explicit in the node type, as opposed to rejecting the node type and reporting the error (after all, we would be able to automatically fix the problem).  As Brian says, this is akin to Java making all classes inherit the standard object methods.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_RFC.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 12:00:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 12:00:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-347) JcrQuery.storeAsNode
 Is Not Implemented
Message-ID: <16817278.1239379222408.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrQuery.storeAsNode Is Not Implemented
---------------------------------------

                 Key: DNA-347
                 URL: https://jira.jboss.org/jira/browse/DNA-347
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


JcrQuery.storeAsNode currently throws an UnsupportedRepositoryOperationException as per spec for L1-only JCR repositories.  Since the intent clearly seems to be that DNA will support L2 functionality (and since the addNode method has been implemented), this would need to change to actually store the query in the given node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 12:03:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 12:03:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-347) JcrQuery.storeAsNode
 Is Not Implemented
In-Reply-To: <16817278.1239379222408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29373907.1239379402278.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-347:
--------------------------------

    Attachment: DNA-347.patch


Patch that implements the functionality and adds the test.  I had to hand-edit the patch to exclude some other in-flight code.  Please let me know if it does not apply correctly.

> JcrQuery.storeAsNode Is Not Implemented
> ---------------------------------------
>
>                 Key: DNA-347
>                 URL: https://jira.jboss.org/jira/browse/DNA-347
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-347.patch
>
>
> JcrQuery.storeAsNode currently throws an UnsupportedRepositoryOperationException as per spec for L1-only JCR repositories.  Since the intent clearly seems to be that DNA will support L2 functionality (and since the addNode method has been implemented), this would need to change to actually store the query in the given node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 18:48:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 18:48:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-348)
 AbstractJcrNode.checkin and
 .checkout Throws the Wrong Exception Type
Message-ID: <6689208.1239403702268.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode.checkin and .checkout Throws the Wrong Exception Type
---------------------------------------------------------------------

                 Key: DNA-348
                 URL: https://jira.jboss.org/jira/browse/DNA-348
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


Section 8.2.14.1 of the 1.0.1 spec says that Node.checkin() and Node.checkout(): "If this node is not versionable, an UnsupportedRepositoryOperationException is thrown."

AbstractJcrNode currently throws an UnsupportedOperationException.  This causes about 12 tests to fail in the (currently commented out) SerializationTest in the JR TCK tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 18:54:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 18:54:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-348)
 AbstractJcrNode.checkin and
 .checkout Throws the Wrong Exception Type
In-Reply-To: <6689208.1239403702268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4138853.1239404062986.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-348:
--------------------------------

    Attachment: DNA-348.patch


Changed exception thrown by both methods.  Can't uncomment SerializationTest yet due to other failures.

> AbstractJcrNode.checkin and .checkout Throws the Wrong Exception Type
> ---------------------------------------------------------------------
>
>                 Key: DNA-348
>                 URL: https://jira.jboss.org/jira/browse/DNA-348
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-348.patch
>
>
> Section 8.2.14.1 of the 1.0.1 spec says that Node.checkin() and Node.checkout(): "If this node is not versionable, an UnsupportedRepositoryOperationException is thrown."
> AbstractJcrNode currently throws an UnsupportedOperationException.  This causes about 12 tests to fail in the (currently commented out) SerializationTest in the JR TCK tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 20:29:33 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 20:29:33 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-349)
 AbstractJcrNode.addNode Does Not
 Add jcr:uuid Property if Primary Type Extends mix:referenceable
Message-ID: <2028950.1239409773454.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable
------------------------------------------------------------------------------------------------

                 Key: DNA-349
                 URL: https://jira.jboss.org/jira/browse/DNA-349
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor
         Attachments: DNA-349.patch

If a node is loaded from the repository with a primary type that has mix:referenceable as a supertype, the mandatory, protected jcr:uuid property is properly set.  If a new node is added with the same primary type, the jcr:uuid property is not set.  

When the TCK tests are changed to use a default node type which has mix:referenceable as a supertype (which must be done to make the tests in SetValueNodeTest pass), this issue causes NodeAddMixinTest.testAddMixinReferenceable to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 10 20:29:33 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 10 Apr 2009 20:29:33 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-349)
 AbstractJcrNode.addNode Does Not
 Add jcr:uuid Property if Primary Type Extends mix:referenceable
In-Reply-To: <2028950.1239409773454.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7906958.1239409773494.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-349:
--------------------------------

    Attachment: DNA-349.patch


Here's a patch that corrects the issue.  I've tested it locally with an extra type registered with the uncommitted type registration code. 

> AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable
> ------------------------------------------------------------------------------------------------
>
>                 Key: DNA-349
>                 URL: https://jira.jboss.org/jira/browse/DNA-349
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-349.patch
>
>
> If a node is loaded from the repository with a primary type that has mix:referenceable as a supertype, the mandatory, protected jcr:uuid property is properly set.  If a new node is added with the same primary type, the jcr:uuid property is not set.  
> When the TCK tests are changed to use a default node type which has mix:referenceable as a supertype (which must be done to make the tests in SetValueNodeTest pass), this issue causes NodeAddMixinTest.testAddMixinReferenceable to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 11 09:21:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 11 Apr 2009 09:21:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-350)
 RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for
 Protected Items if skipProtected is True.
Message-ID: <12016621.1239456082741.JavaMail.jira@cloud.prod.atl2.jboss.com>

RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for Protected Items if skipProtected is True.
--------------------------------------------------------------------------------------------------------------------

                 Key: DNA-350
                 URL: https://jira.jboss.org/jira/browse/DNA-350
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


Currently, the RepositoryNodeTypeManager.findBest{Property|ChildNode}Definition methods have the line:
                    if (skipProtected && definition.isProtected()) continue;

The problem arises in that SessionCache.NodeEditor uses the existence of a definition as the indicator that a property can be set (and, respectively, that a child node can be added).  Node types (e.g. nt:unstructured), that have a protected property (e.g., jcr:primaryType) and a residual property will return the residual definition for findBestPropertyDefinition for the property jcr:primaryType if skipProtected = true.  In practice, this means that the protected property will be writable, which violates the spec and causes two TCK tests that test this condition to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 11 09:23:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 11 Apr 2009 09:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-350)
 RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for
 Protected Items if skipProtected is True.
In-Reply-To: <12016621.1239456082741.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25596043.1239456202282.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-350:
--------------------------------

    Attachment: DNA-350.patch


Changed all the places where skipProtected is checked to return null (no valid definition can be obtained) if skipProtected is true instead of continuing and possibly picking up a residual definition for the protected property.  This causes two more test cases in the TCK NodeTest class to pass, but other failures prevent uncommenting it at this time.

> RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for Protected Items if skipProtected is True.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-350
>                 URL: https://jira.jboss.org/jira/browse/DNA-350
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-350.patch
>
>
> Currently, the RepositoryNodeTypeManager.findBest{Property|ChildNode}Definition methods have the line:
>                     if (skipProtected && definition.isProtected()) continue;
> The problem arises in that SessionCache.NodeEditor uses the existence of a definition as the indicator that a property can be set (and, respectively, that a child node can be added).  Node types (e.g. nt:unstructured), that have a protected property (e.g., jcr:primaryType) and a residual property will return the residual definition for findBestPropertyDefinition for the property jcr:primaryType if skipProtected = true.  In practice, this means that the protected property will be writable, which violates the spec and causes two TCK tests that test this condition to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 15:16:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 13 Apr 2009 15:16:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-346) JR TCK Tests for
 SetPropertyStringTest and SetPropertyValueTest Fail
In-Reply-To: <887215.1239199702275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <686124.1239650182365.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-346.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Applied the patch.  A few minor changes were made, including generating useful error messages for the ValueFormatExceptions, and computing the Name objects only once.

> JR TCK Tests for SetPropertyStringTest and SetPropertyValueTest Fail
> --------------------------------------------------------------------
>
>                 Key: DNA-346
>                 URL: https://jira.jboss.org/jira/browse/DNA-346
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-346.patch
>
>
> The L2 TCK tests SetPropertyStringTest and SetPropertyValueTest fail.  Opening this defect as a placeholder for the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 15:22:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 13 Apr 2009 15:22:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-347) JcrQuery.storeAsNode
 Is Not Implemented
In-Reply-To: <16817278.1239379222408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29734043.1239650542833.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-347.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch, which implements the JcrQuery.storeAsNode(...) method.  Minor change to look up the root node directly if the parent was the root.

> JcrQuery.storeAsNode Is Not Implemented
> ---------------------------------------
>
>                 Key: DNA-347
>                 URL: https://jira.jboss.org/jira/browse/DNA-347
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-347.patch
>
>
> JcrQuery.storeAsNode currently throws an UnsupportedRepositoryOperationException as per spec for L1-only JCR repositories.  Since the intent clearly seems to be that DNA will support L2 functionality (and since the addNode method has been implemented), this would need to change to actually store the query in the given node.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 15:24:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 13 Apr 2009 15:24:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-348)
 AbstractJcrNode.checkin and
 .checkout Throws the Wrong Exception Type
In-Reply-To: <6689208.1239403702268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28766541.1239650662280.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-348.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch as is.

> AbstractJcrNode.checkin and .checkout Throws the Wrong Exception Type
> ---------------------------------------------------------------------
>
>                 Key: DNA-348
>                 URL: https://jira.jboss.org/jira/browse/DNA-348
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-348.patch
>
>
> Section 8.2.14.1 of the 1.0.1 spec says that Node.checkin() and Node.checkout(): "If this node is not versionable, an UnsupportedRepositoryOperationException is thrown."
> AbstractJcrNode currently throws an UnsupportedOperationException.  This causes about 12 tests to fail in the (currently commented out) SerializationTest in the JR TCK tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 15:29:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 13 Apr 2009 15:29:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-349)
 AbstractJcrNode.addNode Does Not
 Add jcr:uuid Property if Primary Type Extends mix:referenceable
In-Reply-To: <2028950.1239409773454.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12078932.1239650962385.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-349.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch, which works as is.

> AbstractJcrNode.addNode Does Not Add jcr:uuid Property if Primary Type Extends mix:referenceable
> ------------------------------------------------------------------------------------------------
>
>                 Key: DNA-349
>                 URL: https://jira.jboss.org/jira/browse/DNA-349
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-349.patch
>
>
> If a node is loaded from the repository with a primary type that has mix:referenceable as a supertype, the mandatory, protected jcr:uuid property is properly set.  If a new node is added with the same primary type, the jcr:uuid property is not set.  
> When the TCK tests are changed to use a default node type which has mix:referenceable as a supertype (which must be done to make the tests in SetValueNodeTest pass), this issue causes NodeAddMixinTest.testAddMixinReferenceable to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 15:31:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 13 Apr 2009 15:31:35 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-350)
 RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for
 Protected Items if skipProtected is True.
In-Reply-To: <12016621.1239456082741.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19489718.1239651095542.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-350.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch.

> RepoistoryNodeTypeManager.findBest*Definition Returns Wrong Definition for Protected Items if skipProtected is True.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-350
>                 URL: https://jira.jboss.org/jira/browse/DNA-350
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-350.patch
>
>
> Currently, the RepositoryNodeTypeManager.findBest{Property|ChildNode}Definition methods have the line:
>                     if (skipProtected && definition.isProtected()) continue;
> The problem arises in that SessionCache.NodeEditor uses the existence of a definition as the indicator that a property can be set (and, respectively, that a child node can be added).  Node types (e.g. nt:unstructured), that have a protected property (e.g., jcr:primaryType) and a residual property will return the residual definition for findBestPropertyDefinition for the property jcr:primaryType if skipProtected = true.  In practice, this means that the protected property will be writable, which violates the spec and causes two TCK tests that test this condition to fail.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 13 17:18:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 13 Apr 2009 17:18:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-339) JCR Type Registration
 and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31359401.1239657502289.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-339:
--------------------------------

    Attachment: DNA-new_type_registration.patch


Version of the earlier patch that seeks to address the feedback provided and changes the basic approach from being *Template-based (a la JSR-283) to being based on NodeTypeSources like our current built-in types.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_RFC.patch, DNA-new_type_registration.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 10:51:23 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 10:51:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-351) Performance Test for
	JCR Access
Message-ID: <17102645.1239720683173.JavaMail.jira@cloud.prod.atl2.jboss.com>

Performance Test for JCR Access
-------------------------------

                 Key: DNA-351
                 URL: https://jira.jboss.org/jira/browse/DNA-351
             Project: DNA
          Issue Type: Feature Request
          Components: JCR, Testing
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


It may be helpful to have some performance harness in place to help test the speed of JCR read and write access in a manner analogous to the ConnectorReadableTests and ConnectorWritableTests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 10:53:39 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 10:53:39 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-351) Performance Test for
	JCR Access
In-Reply-To: <17102645.1239720683173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29623350.1239720819487.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-351:
--------------------------------

    Attachment: DNA-351.patch


Added basic tests for reads and writes over JCR content graphs of various widths.

> Performance Test for JCR Access
> -------------------------------
>
>                 Key: DNA-351
>                 URL: https://jira.jboss.org/jira/browse/DNA-351
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-351.patch
>
>
> It may be helpful to have some performance harness in place to help test the speed of JCR read and write access in a manner analogous to the ConnectorReadableTests and ConnectorWritableTests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 12:13:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 14 Apr 2009 12:13:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-339) JCR Type
 Registration and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11900082.1239725603047.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462131#action_12462131 ] 

Randall Hauch commented on DNA-339:
-----------------------------------

Applying the patch, with some very minor modifications (particularly, some additional JavaDoc in NodeDefinitionId and PropertyDefinitionId).  

The Key classes in JcrPropertyDefinition and JcrNodeDefinition should be replaced with PropertyDefinitionId and NodeDefinitionId, respectively, but this can be done in another change set.  The current approach works, but may actually not match the specification.  (The JavaDoc added to the *DefinitionId classes helps to explain what information exactly is used to distinguish the definitions, and the Key classes use a different set of information.)

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_RFC.patch, DNA-new_type_registration.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 12:43:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 14 Apr 2009 12:43:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-351) Performance Test for
	JCR Access
In-Reply-To: <17102645.1239720683173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4229174.1239727417404.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462141#action_12462141 ] 

Randall Hauch commented on DNA-351:
-----------------------------------

Applied the patch.  Nice work.

> Performance Test for JCR Access
> -------------------------------
>
>                 Key: DNA-351
>                 URL: https://jira.jboss.org/jira/browse/DNA-351
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-351.patch
>
>
> It may be helpful to have some performance harness in place to help test the speed of JCR read and write access in a manner analogous to the ConnectorReadableTests and ConnectorWritableTests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 12:43:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 14 Apr 2009 12:43:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-351) Performance Test for
	JCR Access
In-Reply-To: <17102645.1239720683173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9875503.1239727417451.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-351.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved.

> Performance Test for JCR Access
> -------------------------------
>
>                 Key: DNA-351
>                 URL: https://jira.jboss.org/jira/browse/DNA-351
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-351.patch
>
>
> It may be helpful to have some performance harness in place to help test the speed of JCR read and write access in a manner analogous to the ConnectorReadableTests and ConnectorWritableTests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 15:29:23 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 15:29:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-339) JCR Type Registration
 and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20141844.1239737363334.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-339:
--------------------------------

    Attachment: DNA-339_no_key_class.patch


Based on feedback, added patch to remove the JcrNodeDefinition.Key and JcrPropertyDefinition.Key classes.  Also added in test cases for type registration.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_no_key_class.patch, DNA-339_RFC.patch, DNA-new_type_registration.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 16:08:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 14 Apr 2009 16:08:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-339) JCR Type
 Registration and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15925217.1239739702302.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462190#action_12462190 ] 

Randall Hauch commented on DNA-339:
-----------------------------------

Applying the "no key" patch, which removes the Key nested class from JcrNodeDefinition and JcrPropertyDefinition and instead uses the (existing) NodeDefinitionId and PropertyDefinitionId.  The patch also adds test cases for type registration.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-339_no_key_class.patch, DNA-339_RFC.patch, DNA-new_type_registration.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 16:08:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 14 Apr 2009 16:08:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-339) JCR Type Registration
 and Unregistration
In-Reply-To: <17047195.1238348722448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31405594.1239739702481.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-339.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Marking this as resolved, since this issue is largely finished.  Future changes/enhancements/improvements should be tracked under new issues.

> JCR Type Registration and Unregistration
> ----------------------------------------
>
>                 Key: DNA-339
>                 URL: https://jira.jboss.org/jira/browse/DNA-339
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-339_no_key_class.patch, DNA-339_RFC.patch, DNA-new_type_registration.patch
>
>
> It would be useful for DNA to support type registration and unregistration (a la JSR 2.0 (draft) spec section 6.10).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:30:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:30:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-352) Version Tests in
 SerializationTest Fail Due to TCK Bug
Message-ID: <26784500.1239759022271.JavaMail.jira@cloud.prod.atl2.jboss.com>

Version Tests in SerializationTest Fail Due to TCK Bug
------------------------------------------------------

                 Key: DNA-352
                 URL: https://jira.jboss.org/jira/browse/DNA-352
             Project: DNA
          Issue Type: Bug
          Components: JCR, Testing
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


The JackRabbit TCK that DNA currently uses to help gauge JCR compliance contains several tests (e.g., SerializationTest) that test whether the repository supports versioning by calling canAddMixin("mix:versionable") on a node instead of checking Repository.getDescriptor(Repository.OPTION_VERSIONING_SUPPORTED).  These tests expect the canAddMixin call to return false if the repository does not support versioning.

However, in section 4.11 of the 1.0.1 specification, the behavior of repositories that do not support versioning is defined differently: "A node is versionable if and only if it has been assigned the mixin type mix:versionable, otherwise it is nonversionable. Repositories that do not support versioning will simply not provide this mixin type, whereas repositories that do support versioning must provide it."

Based on this, DNA needs to disable the built-in mix:versionable type.  It probably makes sense to disable nt:versionHistory, nt:version, etc. as well.  However, to make the tests pass, canAddMixin will need to be changed to return false when given "mix:versionable" as an argument.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:40:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:40:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-352) Version Tests in
 SerializationTest Fail Due to TCK Bug
In-Reply-To: <26784500.1239759022271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32721537.1239759622386.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-352:
--------------------------------

    Attachment: DNA-352.patch


Patch that adds the behavior described above (removed version-related built-in node types, modified canAddMixin, modified test that had coincidental dependency on one of the version built-in types)

> Version Tests in SerializationTest Fail Due to TCK Bug
> ------------------------------------------------------
>
>                 Key: DNA-352
>                 URL: https://jira.jboss.org/jira/browse/DNA-352
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-352.patch
>
>
> The JackRabbit TCK that DNA currently uses to help gauge JCR compliance contains several tests (e.g., SerializationTest) that test whether the repository supports versioning by calling canAddMixin("mix:versionable") on a node instead of checking Repository.getDescriptor(Repository.OPTION_VERSIONING_SUPPORTED).  These tests expect the canAddMixin call to return false if the repository does not support versioning.
> However, in section 4.11 of the 1.0.1 specification, the behavior of repositories that do not support versioning is defined differently: "A node is versionable if and only if it has been assigned the mixin type mix:versionable, otherwise it is nonversionable. Repositories that do not support versioning will simply not provide this mixin type, whereas repositories that do support versioning must provide it."
> Based on this, DNA needs to disable the built-in mix:versionable type.  It probably makes sense to disable nt:versionHistory, nt:version, etc. as well.  However, to make the tests pass, canAddMixin will need to be changed to return false when given "mix:versionable" as an argument.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:42:40 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:42:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-353)
 JcrSession.exportSystemView Does
 Not Handle skipBinary = true Properly
Message-ID: <350568.1239759761773.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrSession.exportSystemView Does Not Handle skipBinary = true Properly
----------------------------------------------------------------------

                 Key: DNA-353
                 URL: https://jira.jboss.org/jira/browse/DNA-353
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


Per 1.0.1 specification, exportSystemView is supposed to handle the skipBinary property like this: "If skipBinary is true then any properties of PropertyType.BINARY will be serialized as if they are empty. That is, the existence of the property will be serialized, but its content will not appear in the serialized output (the <sv:value> element will have no content). Note that in the case of multi-value BINARY properties, the number of values in the property will be reflected in the serialized output, though they will all be empty."

JcrSession.exportSystemView currently omits all reference to binary properties if skipBinary is true.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:48:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:48:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-353)
 JcrSession.exportSystemView Does
 Not Handle skipBinary = true Properly
In-Reply-To: <350568.1239759761773.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27395789.1239760102286.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-353:
--------------------------------

    Attachment: DNA-353.patch


Added patch that corrects behavior of exportSystemView.  This gets tested in the TCK SerializationTest

> JcrSession.exportSystemView Does Not Handle skipBinary = true Properly
> ----------------------------------------------------------------------
>
>                 Key: DNA-353
>                 URL: https://jira.jboss.org/jira/browse/DNA-353
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-353.patch
>
>
> Per 1.0.1 specification, exportSystemView is supposed to handle the skipBinary property like this: "If skipBinary is true then any properties of PropertyType.BINARY will be serialized as if they are empty. That is, the existence of the property will be serialized, but its content will not appear in the serialized output (the <sv:value> element will have no content). Note that in the case of multi-value BINARY properties, the number of values in the property will be reflected in the serialized output, though they will all be empty."
> JcrSession.exportSystemView currently omits all reference to binary properties if skipBinary is true.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:53:37 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:53:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-354)
 JcrSession.hasPendingChanges Is Not Implemented
Message-ID: <641117.1239760417925.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrSession.hasPendingChanges Is Not Implemented
-----------------------------------------------

                 Key: DNA-354
                 URL: https://jira.jboss.org/jira/browse/DNA-354
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Brian Carothers
            Priority: Minor


The JcrSession.hasPendingChanges method is currently hard-coded to return false.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 14 21:55:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 14 Apr 2009 21:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-354)
 JcrSession.hasPendingChanges Is Not Implemented
In-Reply-To: <641117.1239760417925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15346209.1239760522297.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-354:
--------------------------------

    Attachment: DNA-354.patch


Patch to check session cache for the existence of changed nodes.

> JcrSession.hasPendingChanges Is Not Implemented
> -----------------------------------------------
>
>                 Key: DNA-354
>                 URL: https://jira.jboss.org/jira/browse/DNA-354
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-354.patch
>
>
> The JcrSession.hasPendingChanges method is currently hard-coded to return false.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 08:32:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 08:32:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-352) Version Tests in
 SerializationTest Fail Due to TCK Bug
In-Reply-To: <26784500.1239759022271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5862073.1239798745194.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462316#action_12462316 ] 

Randall Hauch commented on DNA-352:
-----------------------------------

Applied the patch that removes the version-related built-in node types, modifies the canAddMixin(...) method, modifies test that had coincidental dependency on one of the version built-in types.  This change was needed because of what appears to be incorrect behavior in the TCK unit tests.

> Version Tests in SerializationTest Fail Due to TCK Bug
> ------------------------------------------------------
>
>                 Key: DNA-352
>                 URL: https://jira.jboss.org/jira/browse/DNA-352
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-352.patch
>
>
> The JackRabbit TCK that DNA currently uses to help gauge JCR compliance contains several tests (e.g., SerializationTest) that test whether the repository supports versioning by calling canAddMixin("mix:versionable") on a node instead of checking Repository.getDescriptor(Repository.OPTION_VERSIONING_SUPPORTED).  These tests expect the canAddMixin call to return false if the repository does not support versioning.
> However, in section 4.11 of the 1.0.1 specification, the behavior of repositories that do not support versioning is defined differently: "A node is versionable if and only if it has been assigned the mixin type mix:versionable, otherwise it is nonversionable. Repositories that do not support versioning will simply not provide this mixin type, whereas repositories that do support versioning must provide it."
> Based on this, DNA needs to disable the built-in mix:versionable type.  It probably makes sense to disable nt:versionHistory, nt:version, etc. as well.  However, to make the tests pass, canAddMixin will need to be changed to return false when given "mix:versionable" as an argument.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 08:34:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 08:34:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-352) Version Tests in
 SerializationTest Fail Due to TCK Bug
In-Reply-To: <26784500.1239759022271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17289602.1239798865929.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-352.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved.

> Version Tests in SerializationTest Fail Due to TCK Bug
> ------------------------------------------------------
>
>                 Key: DNA-352
>                 URL: https://jira.jboss.org/jira/browse/DNA-352
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-352.patch
>
>
> The JackRabbit TCK that DNA currently uses to help gauge JCR compliance contains several tests (e.g., SerializationTest) that test whether the repository supports versioning by calling canAddMixin("mix:versionable") on a node instead of checking Repository.getDescriptor(Repository.OPTION_VERSIONING_SUPPORTED).  These tests expect the canAddMixin call to return false if the repository does not support versioning.
> However, in section 4.11 of the 1.0.1 specification, the behavior of repositories that do not support versioning is defined differently: "A node is versionable if and only if it has been assigned the mixin type mix:versionable, otherwise it is nonversionable. Repositories that do not support versioning will simply not provide this mixin type, whereas repositories that do support versioning must provide it."
> Based on this, DNA needs to disable the built-in mix:versionable type.  It probably makes sense to disable nt:versionHistory, nt:version, etc. as well.  However, to make the tests pass, canAddMixin will need to be changed to return false when given "mix:versionable" as an argument.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 08:43:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 08:43:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-353)
 JcrSession.exportSystemView Does
 Not Handle skipBinary = true Properly
In-Reply-To: <350568.1239759761773.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3299978.1239799410083.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-353.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch.

> JcrSession.exportSystemView Does Not Handle skipBinary = true Properly
> ----------------------------------------------------------------------
>
>                 Key: DNA-353
>                 URL: https://jira.jboss.org/jira/browse/DNA-353
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-353.patch
>
>
> Per 1.0.1 specification, exportSystemView is supposed to handle the skipBinary property like this: "If skipBinary is true then any properties of PropertyType.BINARY will be serialized as if they are empty. That is, the existence of the property will be serialized, but its content will not appear in the serialized output (the <sv:value> element will have no content). Note that in the case of multi-value BINARY properties, the number of values in the property will be reflected in the serialized output, though they will all be empty."
> JcrSession.exportSystemView currently omits all reference to binary properties if skipBinary is true.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 08:51:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 08:51:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-354)
 JcrSession.hasPendingChanges Is Not Implemented
In-Reply-To: <641117.1239760417925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30035829.1239799890423.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-354.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch (with changes) that implements this method by checking the SessionCache for unsaved (pending) changes.  The patch had checked the 'changes' map to determine whether there were changes, but this misses deletes.  Added a method to SessionCache that determines whether there are any pending changes, and implemented this method by checking whether there are any pending operations.

> JcrSession.hasPendingChanges Is Not Implemented
> -----------------------------------------------
>
>                 Key: DNA-354
>                 URL: https://jira.jboss.org/jira/browse/DNA-354
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-354.patch
>
>
> The JcrSession.hasPendingChanges method is currently hard-coded to return false.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 10:15:34 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 10:15:34 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-354)
 JcrSession.hasPendingChanges Is Not Implemented
In-Reply-To: <641117.1239760417925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24702241.1239804938201.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462341#action_12462341 ] 

Randall Hauch commented on DNA-354:
-----------------------------------

Previous changes that were made in addition to the patch did not properly implement the hasPendingChanges method.  When doing this, it was discovered that SessionCache was incorrectly creating it's Graph.Batch instance to not use the SessionCache's request builder (which used the cache's list of requests, allowing SessionCache.save(UUID) to play with the pending requests to save only those that affect the branch below the supplied UUID).  

This commit corrects the implementation, and all tests now pass.

> JcrSession.hasPendingChanges Is Not Implemented
> -----------------------------------------------
>
>                 Key: DNA-354
>                 URL: https://jira.jboss.org/jira/browse/DNA-354
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-354.patch
>
>
> The JcrSession.hasPendingChanges method is currently hard-coded to return false.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 10:22:03 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 10:22:03 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-355) Wrong Exception Thrown
 When Creating Reference Value from Non-Referenceable Node
Message-ID: <23856855.1239805325665.JavaMail.jira@cloud.prod.atl2.jboss.com>

Wrong Exception Thrown When Creating Reference Value from Non-Referenceable Node
--------------------------------------------------------------------------------

                 Key: DNA-355
                 URL: https://jira.jboss.org/jira/browse/DNA-355
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Brian Carothers
            Priority: Minor


When invoking JcrSession.getValueFactories.createValue(Node)  with a non-referenceable node as an argument, UnsupportedRepositoryOperationException is thrown (from node.getUUID(), per spec).  The 1.0.1 spec for createValue(Node) indicates that it should throw a RepositoryException if its argument is not referenceable.  The relevant section is 7.1.5.3 with the Javadoc: "A RepositoryException is thrown if the specified Node is not referenceable, the current Session is no longer active, or another error occurs."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 10:23:37 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 10:23:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-355) Wrong Exception Thrown
 When Creating Reference Value from Non-Referenceable Node
In-Reply-To: <23856855.1239805325665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18262834.1239805419774.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-355:
--------------------------------

    Attachment: DNA-355.patch


Attached patch and modified tests as needed.

> Wrong Exception Thrown When Creating Reference Value from Non-Referenceable Node
> --------------------------------------------------------------------------------
>
>                 Key: DNA-355
>                 URL: https://jira.jboss.org/jira/browse/DNA-355
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-355.patch
>
>
> When invoking JcrSession.getValueFactories.createValue(Node)  with a non-referenceable node as an argument, UnsupportedRepositoryOperationException is thrown (from node.getUUID(), per spec).  The 1.0.1 spec for createValue(Node) indicates that it should throw a RepositoryException if its argument is not referenceable.  The relevant section is 7.1.5.3 with the Javadoc: "A RepositoryException is thrown if the specified Node is not referenceable, the current Session is no longer active, or another error occurs."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 10:29:08 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 10:29:08 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-355) Wrong Exception
 Thrown When Creating Reference Value from Non-Referenceable Node
In-Reply-To: <23856855.1239805325665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2620588.1239805749881.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-355.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch, which corrects JcrSession.getValueFactories.createValue(Node) witto throw a RepositoryException (rather than an UnsupportedRepositoryOperationException) when a non-referenceable node is given as an argument, and which modifies some unit tests as needed.

> Wrong Exception Thrown When Creating Reference Value from Non-Referenceable Node
> --------------------------------------------------------------------------------
>
>                 Key: DNA-355
>                 URL: https://jira.jboss.org/jira/browse/DNA-355
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-355.patch
>
>
> When invoking JcrSession.getValueFactories.createValue(Node)  with a non-referenceable node as an argument, UnsupportedRepositoryOperationException is thrown (from node.getUUID(), per spec).  The 1.0.1 spec for createValue(Node) indicates that it should throw a RepositoryException if its argument is not referenceable.  The relevant section is 7.1.5.3 with the Javadoc: "A RepositoryException is thrown if the specified Node is not referenceable, the current Session is no longer active, or another error occurs."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 14:17:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 14:17:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-356) Need to Throw
 ItemExistsException if addNode Call Fails Due to SNS
Message-ID: <11429781.1239819442276.JavaMail.jira@cloud.prod.atl2.jboss.com>

Need to Throw ItemExistsException if addNode Call Fails Due to SNS
------------------------------------------------------------------

                 Key: DNA-356
                 URL: https://jira.jboss.org/jira/browse/DNA-356
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


According to the  section 7.1.4 of the 1.0.1 specification (in the documentation for Node.addNode:)
"An ItemExistsException will be thrown either immediately (by this method), or on save, if an item at the specified path already exists and same-name siblings are not allowed."


DNA treats this as a generic case where no valid definition exists and throw a ConstraintViolationException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 14:20:34 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 14:20:34 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-356) Need to Throw
 ItemExistsException if addNode Call Fails Due to SNS
In-Reply-To: <11429781.1239819442276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16807305.1239819634638.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-356:
--------------------------------

    Attachment: DNA-356.patch


Added patch that performs additional check to see if node definition lookup failed solely due to lack of SNS-allowed definition.

> Need to Throw ItemExistsException if addNode Call Fails Due to SNS
> ------------------------------------------------------------------
>
>                 Key: DNA-356
>                 URL: https://jira.jboss.org/jira/browse/DNA-356
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-356.patch
>
>
> According to the  section 7.1.4 of the 1.0.1 specification (in the documentation for Node.addNode:)
> "An ItemExistsException will be thrown either immediately (by this method), or on save, if an item at the specified path already exists and same-name siblings are not allowed."
> DNA treats this as a generic case where no valid definition exists and throw a ConstraintViolationException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 14:37:23 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 14:37:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-357) Hide
 dna:nodeDefinition Property from Users
Message-ID: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>

Hide dna:nodeDefinition Property from Users
-------------------------------------------

                 Key: DNA-357
                 URL: https://jira.jboss.org/jira/browse/DNA-357
             Project: DNA
          Issue Type: Feature Request
          Components: JCR
            Reporter: Brian Carothers
            Priority: Minor


dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.

Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 14:43:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 14:43:30 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-357) Hide
 dna:nodeDefinition Property from Users
In-Reply-To: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17385376.1239821010908.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-357:
--------------------------------

    Attachment: DNA-357.patch


Patch that never returns dna:nodeDefinition property from session cache.  It does not do anything to prevent users from trying to set it though, which seems wrong.

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-357.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 18:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 18:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-358) Break the
 XmlHandler.Destination
 into an area where it can be reused by other importers
Message-ID: <27677490.1239835042271.JavaMail.jira@cloud.prod.atl2.jboss.com>

Break the XmlHandler.Destination into an area where it can be reused by other importers
---------------------------------------------------------------------------------------

                 Key: DNA-358
                 URL: https://jira.jboss.org/jira/browse/DNA-358
             Project: DNA
          Issue Type: Task
          Components: API, Graph
    Affects Versions: 0.3
            Reporter: Randall Hauch
             Fix For: 0.4


The XmlHandler class has a nested interface called "Destination" that provides a useful abstraction from a real graph for other kinds of importers.  This and the implementations should be extracted into the "org.jboss.dna.graph.io" package, where the can be reused.  The GraphImporter class could also be moved to this package, since the primary mechanism for importing XML is via Graph.importXml(...).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 18:42:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 18:42:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-358) Break the
 XmlHandler.Destination
 into an area where it can be reused by other importers
In-Reply-To: <27677490.1239835042271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2540740.1239835342595.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-358.
-------------------------------

    Resolution: Done


Pulled the Destination interface and the current implementations into a new 'org.jboss.dna.graph.io' package.  Move the GraphImporter class and it's test case into the same package.

> Break the XmlHandler.Destination into an area where it can be reused by other importers
> ---------------------------------------------------------------------------------------
>
>                 Key: DNA-358
>                 URL: https://jira.jboss.org/jira/browse/DNA-358
>             Project: DNA
>          Issue Type: Task
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XmlHandler class has a nested interface called "Destination" that provides a useful abstraction from a real graph for other kinds of importers.  This and the implementations should be extracted into the "org.jboss.dna.graph.io" package, where the can be reused.  The GraphImporter class could also be moved to this package, since the primary mechanism for importing XML is via Graph.importXml(...).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 21:51:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 15 Apr 2009 21:51:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-357) Hide
 dna:nodeDefinition Property from Users
In-Reply-To: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <696442.1239846682350.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462495#action_12462495 ] 

Randall Hauch commented on DNA-357:
-----------------------------------

I'm fine with hiding it, though we need to do a little better about not letting users modify it.  In essence, it needs to be protected property (in the editing sense).  

The JCR spec doesn't really say it's invalid to add additional properties to "nt:base", but it does say (section 6.7.22.2) that "An implementation may extend the definition of any predefined node type by adding supertypes to those defined in this specification."  Since we cannot add mixins to "nt:base", I would think we could add "dna:nodeDefinition" to nt:base as a protected, non-mandatory (optional), and autoCreated property.  So even though we continue to hide it the property, having the property definition prevents users from setting it on a node (whether or not one is already there).

Thoughts?

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-357.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 22:34:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 22:34:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
Message-ID: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>

Session.refresh and Node.refresh Methods Not Supported
------------------------------------------------------

                 Key: DNA-359
                 URL: https://jira.jboss.org/jira/browse/DNA-359
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Brian Carothers
            Priority: Minor


Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 22:42:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 22:42:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24600742.1239849742281.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-359:
--------------------------------

    Attachment: DNA-359.patch


Patch that adds refresh(boolean) and refresh(UUID, boolean) methods to session cache and ties them into appropriate JCR refresh methods.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 22:56:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 22:56:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-357) Hide
 dna:nodeDefinition Property from Users
In-Reply-To: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31166991.1239850582358.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-357:
--------------------------------

    Attachment: DNA-357_new_mixin.patch


I like the thought of directly extending nt:base, but it caused us to fail PredefinedNodeTypeTest.testBase.

The spec does give us the option to have nt:base have a supertype (e.g., referenceable).  Here's a patch that adds a new mixin type (dna:defined) with the dna:definition property and is a supertype of nt:base.  This patch would be applied in addition to the original patch.  I made the property protected tp keep users from accidentally corrupting it but not autocreated or mandatory as I did not want to add any guarantees about its availability in the API.

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-357.patch, DNA-357_new_mixin.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 23:22:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 23:22:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-360) JcrSession.importXml
 and getContentHandler Are Not Implemented
Message-ID: <20596679.1239852142737.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrSession.importXml and getContentHandler Are Not Implemented
--------------------------------------------------------------

                 Key: DNA-360
                 URL: https://jira.jboss.org/jira/browse/DNA-360
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


JcrSession.importXml and getContentHandler are currently stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 23:28:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 23:28:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-360) JcrSession.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20596679.1239852142737.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15770986.1239852502281.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-360:
--------------------------------

    Attachment: DNA-360.patch


Adds JcrContentHandler and ties it in to the session import methods.  Also overloads addNode to support passing in a UUID for the new node (as required by spec when importing for certain values of ImportUUIDBehavior).

Also uncomments several tests in the TCK that now pass fully.  SerializationTest, in particular, required a lot of additional configuration for the TCK repository.

Also split out the different credentials in the repository instead of reusing the same credentials for all access levels.

> JcrSession.importXml and getContentHandler Are Not Implemented
> --------------------------------------------------------------
>
>                 Key: DNA-360
>                 URL: https://jira.jboss.org/jira/browse/DNA-360
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-360.patch
>
>
> JcrSession.importXml and getContentHandler are currently stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 23:39:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 23:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-361) SessionCache Throws
 Wrong Exception Type For Invalid Item State
Message-ID: <28138183.1239853162272.JavaMail.jira@cloud.prod.atl2.jboss.com>

SessionCache Throws Wrong Exception Type For Invalid Item State
---------------------------------------------------------------

                 Key: DNA-361
                 URL: https://jira.jboss.org/jira/browse/DNA-361
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


When the session cache attempts to save a node (or the entire session) and another operation has modified the state of the repository such that one or more of the nodes to be saved has an invalid path, an InvalidItemStateException should be thrown.  Currently, the graph layer PathNotFoundException is wrapped in a JCR PathNotFoundException instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 15 23:43:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 15 Apr 2009 23:43:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-361) SessionCache Throws
 Wrong Exception Type For Invalid Item State
In-Reply-To: <28138183.1239853162272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20274508.1239853402278.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-361:
--------------------------------

    Attachment: DNA-361.patch


Attached patch to change the wrapping exception type.  A few lines from the refresh patch are in there as well and can be ignored.

> SessionCache Throws Wrong Exception Type For Invalid Item State
> ---------------------------------------------------------------
>
>                 Key: DNA-361
>                 URL: https://jira.jboss.org/jira/browse/DNA-361
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-361.patch
>
>
> When the session cache attempts to save a node (or the entire session) and another operation has modified the state of the repository such that one or more of the nodes to be saved has an invalid path, an InvalidItemStateException should be thrown.  Currently, the graph layer PathNotFoundException is wrapped in a JCR PathNotFoundException instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 00:15:55 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 16 Apr 2009 00:15:55 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-362) AbstractJcrItem.isNew
 and isModified Are Not Implemented
Message-ID: <21053950.1239855355493.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrItem.isNew and isModified Are Not Implemented
--------------------------------------------------------

                 Key: DNA-362
                 URL: https://jira.jboss.org/jira/browse/DNA-362
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


The implementations of AbstractJcrItem.isNew and isModified are not implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 00:34:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 16 Apr 2009 00:34:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-362) AbstractJcrItem.isNew
 and isModified Are Not Implemented
In-Reply-To: <21053950.1239855355493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32777362.1239856462347.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-362:
--------------------------------

    Attachment: DNA-362.patch


Attached patch that makes the following changes:
- Hoists isNew and isModified from AbstractJcrItem to AbstractJcrNode/Property and makes them dependent on nodeInfo().isNew/Modified and propertyInfo().isNew/Modified respectively
- Adds isNew/isModified to NodeInfo interface, made them both always return false for ImmutableNodeInfo, and added argument to ChangedNodeInfo to indicate whether it was changed because it is a new child node or because it had its own children modified
- Adds isNew/isModified fields/methods/ctor args to PropertyInfo and populates them based on where the PropertyInfo is created
- Uncomments some TCK test cases that now fully pass

> AbstractJcrItem.isNew and isModified Are Not Implemented
> --------------------------------------------------------
>
>                 Key: DNA-362
>                 URL: https://jira.jboss.org/jira/browse/DNA-362
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-362.patch
>
>
> The implementations of AbstractJcrItem.isNew and isModified are not implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 10:00:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 10:00:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-356) Need to Throw
 ItemExistsException if addNode Call Fails Due to SNS
In-Reply-To: <11429781.1239819442276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18302276.1239890422435.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-356.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch that changes SessionCache.NodeEditor.addNode(...) to throw an ItemExistsException if the node cannot be added because an item at the specified path already exists and same-name siblings are not allowed, per the specification (see the JIRA issue for the details).  An additional lookup of the child node definition is performed, but this isn't a problem since it is already an error case and the extra work is justified to provide more useful information in the exception.

> Need to Throw ItemExistsException if addNode Call Fails Due to SNS
> ------------------------------------------------------------------
>
>                 Key: DNA-356
>                 URL: https://jira.jboss.org/jira/browse/DNA-356
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-356.patch
>
>
> According to the  section 7.1.4 of the 1.0.1 specification (in the documentation for Node.addNode:)
> "An ItemExistsException will be thrown either immediately (by this method), or on save, if an item at the specified path already exists and same-name siblings are not allowed."
> DNA treats this as a generic case where no valid definition exists and throw a ConstraintViolationException.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 10:14:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 10:14:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-357) Hide
 dna:nodeDefinition Property from Users
In-Reply-To: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29260070.1239891280595.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462587#action_12462587 ] 

Randall Hauch commented on DNA-357:
-----------------------------------

Applied both patches.  The first hides the "dna:nodeDefinition" property from the JCR layer (meaning it might exist in the graph layer, but won't appear as properties of JCR nodes).  The second patch adds to "nt:base" a property definition for a "dna:nodeDefinition" property that is protected and not mandatory (nor autocreated).  The spec is not clear as to whether a JCR implementation can add properties to "nt:base" (the required supertype of all node types), the spec is clear that an implementation can add properties to any of the built-in node types through mixins.  Therefore, the second patch actually adds this new definition to "nt:base" by having "nt:base" extend the new "dna:defined" mixin, which has the new "dna:nodeDefinition" property definition.  

Because the "dna:nodeDefinition" is protected, JCR clients will not be allowed to define another property with this name, nor will they be able to set the property (using a residual definition) to any value.  All this validation is done through the normal process, requiring no code specific to "dna:nodeDefinition".  

Nicely done!  This is a great demonstration on how node types, node definitions, and property definitions can be used to enforce a structure while having no additional validation code.

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-357.patch, DNA-357_new_mixin.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 10:14:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 10:14:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-357) Hide
 dna:nodeDefinition Property from Users
In-Reply-To: <21889892.1239820643548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16938471.1239891280654.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-357.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved, since all the points were addressed.

> Hide dna:nodeDefinition Property from Users
> -------------------------------------------
>
>                 Key: DNA-357
>                 URL: https://jira.jboss.org/jira/browse/DNA-357
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-357.patch, DNA-357_new_mixin.patch
>
>
> dna:nodeDefinition is a bit of an odd duck.  It is set on every property but doesn't always have a valid JCR definition.  This breaks an export-import round trip as the property cannot be set during import.  It also breaks a few TCK tests that assume a jcr:xmltext node only has two properties (jcr:primaryType and jcr:xmlcharacters), but that's really a TCK defect.
> Can we just suppress this property at the JCR layer?  It would still be available for internal use but would not appear to end users.  Alternatively, we should modify our definition for nt:base to include it as a protected property - this solution may violate the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 10:59:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 10:59:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12764337.1239893962281.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462601#action_12462601 ] 

Randall Hauch commented on DNA-359:
-----------------------------------

Applied the patch that implements the Session.refresh and Node.refresh by adding two SessionCache.refresh methods (one to refresh all contents, the other to refresh only those items below a branch).  

However, there is one case that the patch doesn't handle (well), and that is when a node is removed from a branch, refreshing that branch will not refresh the removed node.  This is because in SessionCache.refresh(UUID, boolean), the logic collecting the UUIDs in the branch first uses the cachedNodes, and only if there is no cached node info will it look in the changes.  The logic instead needs to look first in the changedNodes, and to use the children from the ChangedNodeInfo (which may contain nodes that were newly added or moved from another node), but then also must get the UUIDs of the nodes that were removed from the ChangedNodeInfo.  (This latter step can be done by adding a method to ChangedNodeInfo, since ChangedNodeInfo already has a reference to the original, or cached, NodeInfo and can compute the UUIDs of the removed nodes.  We don't care whether they are moved somewhere else or deleted; we want to refresh them either way.)  Only if there is no ChangedNodeInfo should the refresh logic look in the cachedNodes.



> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



From jira-events at lists.jboss.org  Thu Apr 16 11:27:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 11:27:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-360) JcrSession.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20596679.1239852142737.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1474312.1239895643140.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-360.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved, since the Session methods are implemented and tested.

> JcrSession.importXml and getContentHandler Are Not Implemented
> --------------------------------------------------------------
>
>                 Key: DNA-360
>                 URL: https://jira.jboss.org/jira/browse/DNA-360
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-360.patch
>
>
> JcrSession.importXml and getContentHandler are currently stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 11:27:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 11:27:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-360) JcrSession.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20596679.1239852142737.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9622560.1239895642948.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462608#action_12462608 ] 

Randall Hauch commented on DNA-360:
-----------------------------------

Applied the patch, which implements Session.importXml and getContentHandler.  SerializationTest was commented back out (relative to the patch), since it tests the similar methods in Workspace, and these are not yet implemented.

> JcrSession.importXml and getContentHandler Are Not Implemented
> --------------------------------------------------------------
>
>                 Key: DNA-360
>                 URL: https://jira.jboss.org/jira/browse/DNA-360
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-360.patch
>
>
> JcrSession.importXml and getContentHandler are currently stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 11:31:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 11:31:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-361) SessionCache Throws
 Wrong Exception Type For Invalid Item State
In-Reply-To: <28138183.1239853162272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23310536.1239895897310.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462613#action_12462613 ] 

Randall Hauch commented on DNA-361:
-----------------------------------

Applied the patch (minus the duplicate lines from a previous patch).

> SessionCache Throws Wrong Exception Type For Invalid Item State
> ---------------------------------------------------------------
>
>                 Key: DNA-361
>                 URL: https://jira.jboss.org/jira/browse/DNA-361
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-361.patch
>
>
> When the session cache attempts to save a node (or the entire session) and another operation has modified the state of the repository such that one or more of the nodes to be saved has an invalid path, an InvalidItemStateException should be thrown.  Currently, the graph layer PathNotFoundException is wrapped in a JCR PathNotFoundException instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 11:33:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 11:33:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-361) SessionCache Throws
 Wrong Exception Type For Invalid Item State
In-Reply-To: <28138183.1239853162272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15783921.1239896002283.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-361.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


> SessionCache Throws Wrong Exception Type For Invalid Item State
> ---------------------------------------------------------------
>
>                 Key: DNA-361
>                 URL: https://jira.jboss.org/jira/browse/DNA-361
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-361.patch
>
>
> When the session cache attempts to save a node (or the entire session) and another operation has modified the state of the repository such that one or more of the nodes to be saved has an invalid path, an InvalidItemStateException should be thrown.  Currently, the graph layer PathNotFoundException is wrapped in a JCR PathNotFoundException instead.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:09:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 12:09:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-362)
 AbstractJcrItem.isNew and isModified Are Not Implemented
In-Reply-To: <21053950.1239855355493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15293354.1239898162353.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462626#action_12462626 ] 

Randall Hauch commented on DNA-362:
-----------------------------------

Applied the patch, but rather than have ChangedNodeInfo contain a boolean that says whether its new, there is now a NewNodeInfo (that extends ChangedNodeInfo) that IMO makes it more obvious that this is a new node and clears up the places in SessionCache that instantiate it.

> AbstractJcrItem.isNew and isModified Are Not Implemented
> --------------------------------------------------------
>
>                 Key: DNA-362
>                 URL: https://jira.jboss.org/jira/browse/DNA-362
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-362.patch
>
>
> The implementations of AbstractJcrItem.isNew and isModified are not implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:09:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 12:09:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-362) AbstractJcrItem.isNew
 and isModified Are Not Implemented
In-Reply-To: <21053950.1239855355493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23580879.1239898162390.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-362.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


> AbstractJcrItem.isNew and isModified Are Not Implemented
> --------------------------------------------------------
>
>                 Key: DNA-362
>                 URL: https://jira.jboss.org/jira/browse/DNA-362
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-362.patch
>
>
> The implementations of AbstractJcrItem.isNew and isModified are not implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:19:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 12:19:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-277) Fix all text files in
 source code to have consistent line feeds
In-Reply-To: <21710954.1232404263947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5795752.1239898762327.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch reopened DNA-277:
-------------------------------



We still need to fix all the existing code.

> Fix all text files in source code to have consistent line feeds
> ---------------------------------------------------------------
>
>                 Key: DNA-277
>                 URL: https://jira.jboss.org/jira/browse/DNA-277
>             Project: DNA
>          Issue Type: Task
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Johnny Verhaeg
>            Priority: Minor
>             Fix For: 0.4
>
>
> Currently, all of the text files in our source code have a mixture of carriage returns and line feeds.  And, our DNA preferences (for Eclipse) did not specify any special handling, so each developer's settings were used (and likely were the default settings for the platform).  Regardless of the preference settings, however, Eclipse editors always keep the line termination characters used in each particular file, so if a file was created on Windows, it will have \r\n for all lines, even when that file is modified on Linux or OS X.  There are a few cases where a file seems to have a mixture of line terminations.
> We should probably have a consistent line terminator in all files, and that terminator should probably be '\n', which is the line terminator on *nix, for a couple of reasons.  First, the JBoss.org SVN repository is hosted on Linux, and being consistent probably helps somewhat.  Second, some tools (including Git) rely upon the '\n' character for determining line feeds, so that rules out the Mac style line feeds ('\r').  Third, there really is no need to store multiple characters.
> We need to verify that the converting all files to use Unix line terminators is acceptable.  If so, we need to convert all of the files (that need it), update the Eclipse preferences, and have all developers make sure their Eclipse preference settings are correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:21:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 12:21:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-264) Connectors may need to
 determine the MIME type for content
In-Reply-To: <22148120.1228432116535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19216252.1239898882296.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-264:
------------------------------

          Component/s: Connectors
        Fix Version/s: 0.4
    Affects Version/s: 0.3


> Connectors may need to determine the MIME type for content
> ----------------------------------------------------------
>
>                 Key: DNA-264
>                 URL: https://jira.jboss.org/jira/browse/DNA-264
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> Some connectors may need to be able to determine the MIME type for content, and there's currently no way in the connector API to do that.  The 'dna-graph' project does have MimeTypeDetector interface, but that's meant as a lower-level interface for an implementation.  MimeType was designed to be the main entry point for general components, but that's currently in 'dna-repository' (and connectors don't currently require that).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:23:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 12:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-48) Development and testing
 kit for connectors
Message-ID: <15392863.1239899002427.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-48:
-----------------------------

        Summary: Development and testing kit for connectors  (was: Development and testing kit for federation connectors)
    Description: Developing connectors will require some documentation and test harnesses that simplifies the task of creating and testing connectors.  This should include unit tests that verify the connectors' behavior matches that expected by DNA, and that can be used to check for regression.  Ideally this would also include a way to execute performance tests.  (was: Developing federation connectors will require some documentation and test harnesses that simplifies the task of creating and testing connectors.  This should include unit tests that verify the connectors' behavior matches that expected by DNA, and that can be used to check for regression.  Ideally this would also include a way to execute performance tests.)


> Development and testing kit for connectors
> ------------------------------------------
>
>                 Key: DNA-48
>                 URL: https://jira.jboss.org/jira/browse/DNA-48
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors, Federation, Testing
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>
> Developing connectors will require some documentation and test harnesses that simplifies the task of creating and testing connectors.  This should include unit tests that verify the connectors' behavior matches that expected by DNA, and that can be used to check for regression.  Ideally this would also include a way to execute performance tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 12:43:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 16 Apr 2009 12:43:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20939510.1239900202282.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-359:
--------------------------------

    Attachment: DNA-359_check_for_removed_nodes.patch


Implemented patch as described in previous comment.  Thanks for catching that!

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 13:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 13:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-363) Define node types via
	CND files
Message-ID: <17835701.1239903442317.JavaMail.jira@cloud.prod.atl2.jboss.com>

Define node types via CND files
-------------------------------

                 Key: DNA-363
                 URL: https://jira.jboss.org/jira/browse/DNA-363
             Project: DNA
          Issue Type: Feature Request
          Components: JCR
    Affects Versions: 0.3
            Reporter: Randall Hauch


Our JCR implementation should allow users to define the node types (with their property definitions and child node definitions) via CND files.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 13:44:57 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 13:44:57 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-363) Define node types
	via CND files
In-Reply-To: <17835701.1239903442317.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1242392.1239903923642.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462730#action_12462730 ] 

Randall Hauch commented on DNA-363:
-----------------------------------

The first step is to create a CND parser.  Using ANTLR 3 is probably by far the best approach, since that will require little of our code and will provide an excellent lexer/parser.  However, that means that we'd have a dependency on 'antlr-runtime.jar'.  This is probably acceptable (other libraries also have this, including Hibernate and Drools, to name just two).

However, considering that we also want to have a CND sequencer, it doesn't make sense that the JCR implementation should be a dependency of this sequencer.  Therefore, we should probably move the CND reading (and eventually generation) into a separate "dna-cnd" project that will depend on ANTLR (runtime) and "dna-graph".

This CND reader could also behave as a graph importer, writing the node type content to a org.jboss.dna.graph.io.Destination instance and using the JCR-prescribed "nt:nodeType", "nt:propertyDefinition", and "nt:childNodeDefinition" structures.  This would allow use to import the CND node types into a graph, whether that's a temporary in-memory repository (which is then processed by some other component), a real JCR repository (e.g., under the "/jcr:system"), or a configuration repository.  It also would be very straightforward to wrap this in a sequencer.  (We might even consider having a StreamSequencer subclass that wraps the SequencerOutput with a Destination, making it very easy to implement a sequencer from an importer.)

> Define node types via CND files
> -------------------------------
>
>                 Key: DNA-363
>                 URL: https://jira.jboss.org/jira/browse/DNA-363
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>
> Our JCR implementation should allow users to define the node types (with their property definitions and child node definitions) via CND files.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 16 13:52:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 16 Apr 2009 13:52:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-363) Define node types
	via CND files
In-Reply-To: <17835701.1239903442317.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4393224.1239904342280.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462731#action_12462731 ] 

Randall Hauch commented on DNA-363:
-----------------------------------

The first step of several.  This change moves some of the names in the JCR-related lexicons from the "dna-jcr" project's lexicons into the "dna-graph" project's corresponding lexicons.  

Also added to the "nt:nodeType" and "nt:propertyDefinition" node types in JcrBuiltinNodeTypeSource were several additional property definitions new in JSR-283 .  However, because the JSR-170 TCK unit tests are checking that only the JSR-170 property definitions are there, these new definitions have been commented out for the time being.  (JSR-283 also makes all of the property definitions on "nt:nodeType", "nt:propertyDefinition", and "nt:childNodeDefinition" to be protected, though JSR-170 TCK unit tests are checking that they are not.  These also were left as not being protected so that we are JSR-170 compliant.)

> Define node types via CND files
> -------------------------------
>
>                 Key: DNA-363
>                 URL: https://jira.jboss.org/jira/browse/DNA-363
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>
> Our JCR implementation should allow users to define the node types (with their property definitions and child node definitions) via CND files.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:19:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:19:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24487740.1239977962780.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462877#action_12462877 ] 

Randall Hauch commented on DNA-359:
-----------------------------------

Applied the second patch, which corrects how the nodes under the refreshed node are computed (to also take into account nodes that were removed from the subgraph).

I think we're still missing some information. Consider a node 'C' that is originally under node 'A', and during a session it is moved under node 'B'.  If 'A' is refreshed, then the current logic will refresh 'A' (by throwing out its local changes) so that it now contains 'C' again (or would if it is re-read, as the cache is filled lazily).  However, since 'B' has been changed in the session to contain 'C', that information is now out of date.  I haven't found where the spec specifically addresses this situation, but I'd expect we should throw an exception (maybe InvalidItemStateException, but probably RepositoryException for 'other problem').

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:21:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:21:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6949534.1239978082333.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-359:
------------------------------

    Attachment: DNA-363-handle-moves.patch


Attached a patch that figures out whether any nodes that were removed from the branch were not deleted (meaning they were moved to another branch).  Note that this does handle the case where a node was moved to another parent within the branch being refreshed.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:21:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:21:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29532296.1239978082374.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-359:
------------------------------

    Attachment:     (was: DNA-363-handle-moves.patch)


> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:21:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:21:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13680208.1239978082513.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-359:
------------------------------

    Attachment: DNA-359-handle-moves.patch


Attached a patch (with correct name) that figures out whether any nodes that were removed from the branch were not deleted (meaning they were moved to another branch).  Note that this does handle the case where a node was moved to another parent within the branch being refreshed.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:23:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <232709.1239978202311.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462880#action_12462880 ] 

Randall Hauch commented on DNA-359:
-----------------------------------

Committed the last patch.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:25:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:25:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11095996.1239978322301.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462882#action_12462882 ] 

Randall Hauch commented on DNA-359:
-----------------------------------

Added a short-circuit for 'refresh(UUID,boolean)' that checks whether the supplied UUID is that of the root, and if so 'refresh(boolean)' is called since it is significantly more efficient.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 17 10:25:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 17 Apr 2009 10:25:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-359) Session.refresh and
 Node.refresh Methods Not Supported
In-Reply-To: <1511520.1239849264185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25862908.1239978322665.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-359.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Marking as resolved, since all known scenarios are handled.

> Session.refresh and Node.refresh Methods Not Supported
> ------------------------------------------------------
>
>                 Key: DNA-359
>                 URL: https://jira.jboss.org/jira/browse/DNA-359
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-359-handle-moves.patch, DNA-359.patch, DNA-359_check_for_removed_nodes.patch
>
>
> Session.refresh and AbstractJcrNode.refresh methods are stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 18 06:40:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 18 Apr 2009 06:40:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-364) Session.move Is Not
	Implemented
Message-ID: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>

Session.move Is Not Implemented
-------------------------------

                 Key: DNA-364
                 URL: https://jira.jboss.org/jira/browse/DNA-364
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Brian Carothers


JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 18 06:42:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 18 Apr 2009 06:42:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2733510.1240051343338.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-364:
--------------------------------

    Attachment: DNA-364.patch


Attached patch implements almost all of the spec and does, in fact, pass the TCK tests in SessionTest.  

The unhandled case is when move is used to rename the node.  This case will be addressed in a future patch.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>         Attachments: DNA-364.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 18 06:45:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 18 Apr 2009 06:45:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-365) Workspace.importXml and
 getContentHandler Are Not Implemented
Message-ID: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>

Workspace.importXml and getContentHandler Are Not Implemented
-------------------------------------------------------------

                 Key: DNA-365
                 URL: https://jira.jboss.org/jira/browse/DNA-365
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 18 07:13:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 18 Apr 2009 07:13:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-365) Workspace.importXml and
 getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4073188.1240053202882.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-365:
--------------------------------

    Attachment: DNA-365.patch


Attached a patch with an approach that almost works.  Salient features are:

- Added a method to JcrSession to create a Graph.Batch from the current session graph
- Added a method to SessionCache to specify a Graph.Batch to be used with a SessionCache.NodeEditor.  The returned NodeEditor will queue all operations into the given Graph.Batch, allowing the original caller to execute that batch outside of the default SessionCache context.
- Moved most validation logic from setProperty and addMixin in AbstractJcrNode and JcrMultiValueProperty into corresponding methods in SessionCache.NodeEditor, allowing these operations to be (relatively) simply performed on a user-specified Graph.Batch.
- Modified JcrContentHandler to directly invoke these methods on SessionCache.NodeEditor
- Modified JcrContentHandler to specify a Graph.Batch directly when saving in workspace mode.  Combined with the previous change, this allows direct writes to the persistence layer when in workspace mode.
- Added implementation of getContentHandler and importXml in JcrWorkspace.

However, the patch causes some regressions.  The DNA layer does not distinguish between single-valued and multi-valued properties at this time.  The JCR spec mandates that the two be treated differently and makes them generally incompatible.  It is possible for a node type to allow a property with a given name to be either single-valued or multi-valued (e.g., the residual definition on nt:unstructured).  

When the SessionCache loads a property from the persistence layer, it tried to use the node type to determine whether the property is single-valued or multi-valued in the JCR sense.  If the node type does not allow SessionCache to distinguish the cardinality of the property by name, SessionCache heuristically determines the cardinality based on the current number of values for the property (1 value => JcrSingleValuedProperty, else => JcrMultiValuedProperty).

This leads to the following pathological case:
1. Get a reference to a node with a primary type that does not always disambiguate between property cardinality based on name alone (e.g., nt:unstructured)
2. Call setProperties(String, Value[]) on the node with a Value array of length 1 and a non-null value.  DNA correctly infers that you are setting a multi-valued property based on the usage of the multi-valued setter.
3. Save the node, persisting the property (and its single value) to the repository.  This also flushes the node and its properties from SessionCache, forcing a reload from persistence on the next access.
4. Call node.setProperty(String, String).  This should throw a ValueFormatException as mandated by the spec when a called attempts to set a single value on multi-valued property.  However, recall that SessionCache flushed the reference on save and had to reload the node and infer the cardinality of its properties.  Based on the single-value set on the property, DNA was forced to assume that the property was single-valued and this call will succeed.

To address this issue and complete the fix, two issues need to be addressed.  

First, a mechanism for deterministically separating single-valued properties from multi-valued properties must be created.  This may be as simple as appending '*' to the names of multi-valued properties.  Next, the cardinality check in SessionCache.NodeEditor.setProperty(Name, Value[], int, boolean) needs to be uncommented, to resume proper cardinality checks.

Apologies in advance if the patch is a little off.  I had to hand-edit out some of the Session.move changes.



> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-365.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 10:52:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 20 Apr 2009 10:52:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-366) Allow child node to be
 reordered in the Graph API
Message-ID: <13518264.1240239142560.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow child node to be reordered in the Graph API
-------------------------------------------------

                 Key: DNA-366
                 URL: https://jira.jboss.org/jira/browse/DNA-366
             Project: DNA
          Issue Type: Feature Request
          Components: API, Connectors, Graph
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


The Graph API doesn't really allow the child nodes to be reordered.  This feature is required for the JCR implementation

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:27:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:27:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-367)
 AbstractJcrNode.getReferences() Is Incorrect
Message-ID: <21712574.1240252042628.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode.getReferences() Is Incorrect
--------------------------------------------

                 Key: DNA-367
                 URL: https://jira.jboss.org/jira/browse/DNA-367
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


AbstractJcrNode.getReferences currently returns all of the reference properties in that node.  According to section 6.2.3 of the 1.0.1 specification, it is supposed to return all _other_ nodes that refer to it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:29:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:29:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-368) Referenced Nodes Can
	Be Deleted
Message-ID: <27124321.1240252162271.JavaMail.jira@cloud.prod.atl2.jboss.com>

Referenced Nodes Can Be Deleted
-------------------------------

                 Key: DNA-368
                 URL: https://jira.jboss.org/jira/browse/DNA-368
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


There is not currently a check in AbstractJcrNode.remove() to see if the node (or any of its child nodes) are targets of references.  Per section 7.1.6 of the 1.0.1 specification, this should cause a ReferentialIntegrityException to be thrown.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:31:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:31:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
Message-ID: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>

Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
----------------------------------------------------------------------

                 Key: DNA-369
                 URL: https://jira.jboss.org/jira/browse/DNA-369
             Project: DNA
          Issue Type: Bug
            Reporter: Brian Carothers


Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:41:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:41:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-370) JcrWorkspace.clone Is
 Not Implemented
Message-ID: <1486867.1240252882274.JavaMail.jira@cloud.prod.atl2.jboss.com>

JcrWorkspace.clone Is Not Implemented
-------------------------------------

                 Key: DNA-370
                 URL: https://jira.jboss.org/jira/browse/DNA-370
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


JcrWorkspace.clone is not yet implemented.  This may not be important/useful for 0.4.  AbstractJcrNode.getCorrespondingNodePath is also not yet implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:50:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:50:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-371) No Default JAAS
	Implementation
Message-ID: <11596321.1240253422276.JavaMail.jira@cloud.prod.atl2.jboss.com>

No Default JAAS Implementation
------------------------------

                 Key: DNA-371
                 URL: https://jira.jboss.org/jira/browse/DNA-371
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


DNA security is currently based on JAAS concepts, but DNA does not ship with any type of JAAS implementation for use outside of an existing server that could somehow pass Credentials into DNA.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 14:54:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 20 Apr 2009 14:54:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-372) Session.impersonate and
 Session.checkPermission Are Not Implemented
Message-ID: <9512717.1240253662803.JavaMail.jira@cloud.prod.atl2.jboss.com>

Session.impersonate and Session.checkPermission Are Not Implemented
-------------------------------------------------------------------

                 Key: DNA-372
                 URL: https://jira.jboss.org/jira/browse/DNA-372
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


Both methods need to be implemented to pass all of the JR TCK L2 tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 15:11:01 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 20 Apr 2009 15:11:01 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-363) Define node types
	via CND files
In-Reply-To: <17835701.1239903442317.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13206186.1240254661359.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463265#action_12463265 ] 

Randall Hauch commented on DNA-363:
-----------------------------------

Added a new 'dna-cnd' project containing a graph importer that reads JCR CND files and populates a repository with the content (based upon the JCR 'nt:nodeType', 'nt:propertyDefinition', and 'nt:childNodeDefinition').

This new project uses ANTLR 3.1.3, which is not yet in the JBoss Maven repository.  I've already committed this newer version of ANTLR (with source) to the Maven repository using SVN, but it does not yet appear via HTTP.  As soon as it is, we should change DNA's main POM.xml to include the new 'dna-cnd' project as a module.

> Define node types via CND files
> -------------------------------
>
>                 Key: DNA-363
>                 URL: https://jira.jboss.org/jira/browse/DNA-363
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>
> Our JCR implementation should allow users to define the node types (with their property definitions and child node definitions) via CND files.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 20 16:22:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 20 Apr 2009 16:22:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-363) Define node types
	via CND files
In-Reply-To: <17835701.1239903442317.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20955767.1240258942278.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463278#action_12463278 ] 

Randall Hauch commented on DNA-363:
-----------------------------------

Changed the DNA CND Sequencer to use the new CND importer.

> Define node types via CND files
> -------------------------------
>
>                 Key: DNA-363
>                 URL: https://jira.jboss.org/jira/browse/DNA-363
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>
> Our JCR implementation should allow users to define the node types (with their property definitions and child node definitions) via CND files.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 10:36:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 10:36:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-373) Provide OSGi
 information in archives (via META-INF/MANIFEST.MF files)
Message-ID: <5343833.1240324600751.JavaMail.jira@cloud.prod.atl2.jboss.com>

Provide OSGi information in archives (via META-INF/MANIFEST.MF files)
---------------------------------------------------------------------

                 Key: DNA-373
                 URL: https://jira.jboss.org/jira/browse/DNA-373
             Project: DNA
          Issue Type: Feature Request
          Components: Development Environment, Documentation
            Reporter: Randall Hauch
            Priority: Minor
             Fix For: Future Releases


If the JBoss DNA JAR files each included a META-INF/MANIFEST.MF file, our existing JARs could be used as OSGi bundles within an OSGi class loader environment (for example within Eclipse), while they continue to work outside of an OSGI environment.

Another option is to create a single OSGi bundle containing the top-level archives and OSGi bundles for each of our extensions.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 11:03:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 11:03:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
Message-ID: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>

Multiplicity of some properties may change when saved and reloaded from the graph
---------------------------------------------------------------------------------

                 Key: DNA-374
                 URL: https://jira.jboss.org/jira/browse/DNA-374
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 11:34:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 11:34:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
In-Reply-To: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31334669.1240328062464.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463463#action_12463463 ] 

Randall Hauch commented on DNA-374:
-----------------------------------

There are two things that conspire to cause this problem.  The first is that JCR distinguishes between single-valued and multi-valued properties and does not allow a single-valued property to be changed with the multi-valued methods (e.g., the Property.setValues(...) methods or the Node.setProperty(...) that takes multiple values) - or vice versa.  The multiplicity of a property has a huge impact on which API methods may be used.

The second is that the DNA graph layer does not have this distinction.  The DNA graph API is significantly smaller and easier to use without having this distinction, and it allows any property to be set to any values.  After all, the DNA graph API was designed as a lower-level and more simplistic graph model that didn't come with a lot of overhead or baggage.

Therefore, since the DNA graph layer doesn't maintain this distinction, the JCR implementation currently determines when a node is read in the most applicable property definition for each property.  Many times there is only one applicable property definition.  For example, if the property has no values or has more than one value, then it is obvious that a multi-valued property definition must be chosen.  (The property types may also affect which property definition is selected.)

However, there are times when multiple property definitions apply.  One frequent case is "nt:unstructured", which has both a single-valued residual property definition and a multi-valued residual property definition.  Multiple applicable property definitions complicate the determination and selection of an appropriate property definition, and sometimes results in a property definition being selected (when a node is read in) that may not match the definition that was used to create the property.  

This is the case when a property is created to be multi-valued (via using JCR's setters for multiple values) but only has one single value, and both a single-valued and multi-valued property definition are available.  When the parent node is saved, the property definition is not saved, and when reading the node back in our JCR implementation (specifically SessionCache) reads this property and attempts to determine the most appropriate property definition.  Because there is one value and single- and multi-valued property definitions, SessionCache does not know which property definition to choose.  Currently, the single-valued property definition is used when the property has only one value.  

Note that we'd have the same problem even if we'd change SessionCache to pick the multi-valued property definition, and the client created a single-valued property.  In this case, our implementation would read the graph and assign the multi-valued property definition.  Therefore, it is not sufficient to change how SessionCache determines the most appropriate property definition.  The problem is that we're losing information that is not persisted in the graph and that cannot always be recovered accurately.

There are a few options:
1) Change the DNA graph layer to distinguish between single-valued and multi-valued properties.  This would be a big change to the graph API and connectors, because it adds a lot of subtle semantics.  Plus, it may snowball to needing property types and therefore node types.  Since the DNA graph layer was intended to be a lower-level and more generic graph model, adding all this complexity can hopefully be avoided.
2) Change the DNA graph layer to support "metadata" on each property, but to not define in the graph layer what this metadata might be.  For example, the JCR layer could use this metadata to say whether the property is single-valued or multi-valued.  This approach is far less intrusive, but it does add a "meta-level" to the existing graph model, and this "meta-level" would not be handled the same by the connectors or the graph API as the existing nodes and properties.  Essentially we'd be duplicating some of the functionality by allowing properties to have "meta-properties".
3) Do not change the DNA graph layer at all, but change the JCR implementation to use other properties on the node to store this additional information. We're already doing that with "dna:nodeDefinition", which stores the name of the child node definition in the parent's node type (primary or mixins) that was used to create the node.  This "dna:nodeDefinition" property is defined on DNA's node type for "nt:base" (actually, a mixin that "nt:base" extends), and is marked as "protected" meaning clients may not set that property through the JCR API.  But we're also hiding that property by not including it in the set of properties exposed by the JCR API.  So this option just extends this already-used approach to be used to capture enough information to be able to properly determine the property definition for each property.

So, option #3 appears to be the most appealing.  The only question is: what information should be stored?  Should we store the ID of the property definition for each property?  Or can we store only the names of the multi-valued properties that have exactly one value?  Or, maybe we store only the names of the multi-valued properties that have exactly one value and that have a single-valued property definition?

I don't think it's worth storing the ID of the property definitions for all properties.  That's just overkill, and in many situations it is not required.  But at the other extreme, a change in the node types might mean that we cannot always recover a property definition if we only store the names of the multi-valued properties with one value that use a multi-valued property definition that also have a similarly-named single-valued property definition.

Therefore, I think the correct approach is to store the names of the multi-valued properties that have a single value.  This information, coupled with the existing value(s) for each property, can then allow us to always figure out when should a property should be treated as a single-valued property or a multi-valued property.

> Multiplicity of some properties may change when saved and reloaded from the graph
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-374
>                 URL: https://jira.jboss.org/jira/browse/DNA-374
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 11:36:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 11:36:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
In-Reply-To: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15515287.1240328182470.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-374:
------------------------------

    Priority: Blocker  (was: Major)


> Multiplicity of some properties may change when saved and reloaded from the graph
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-374
>                 URL: https://jira.jboss.org/jira/browse/DNA-374
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>
> This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 11:46:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 11:46:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-375) Enhance
 MoveBranchRequest to take a
 new name, analogous to how CopyBranchRequest works
Message-ID: <14887345.1240328782522.JavaMail.jira@cloud.prod.atl2.jboss.com>

Enhance MoveBranchRequest to take a new name, analogous to how CopyBranchRequest works
--------------------------------------------------------------------------------------

                 Key: DNA-375
                 URL: https://jira.jboss.org/jira/browse/DNA-375
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Critical
             Fix For: 0.4


CopyBranchRequest has a desiredNameForCopy that is used to specify the name for the new copy, which may be null if the original name is to be used.  MoveBranchRequest should also have a desiredNewName that, if provided, would also rename the node.

This change will affect all of the existing connectors that support updates, but it does close a gap in the Graph functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 11:55:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 11:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-376) Add request to change
 the order of a child node (or nodes) relative to the other children
Message-ID: <21590252.1240329322777.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add request to change the order of a child node (or nodes) relative to the other children
-----------------------------------------------------------------------------------------

                 Key: DNA-376
                 URL: https://jira.jboss.org/jira/browse/DNA-376
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Critical
             Fix For: 0.4


The current DNA Graph model does support ordered children, and while rename can be used to change the order of same-name-siblings, there currently is no way to change the order of the child nodes.  This is required to fully implement the JCR API.

JCR handles this functionality by provided a method that essentially changes the position of a single child node.  The "Node.orderBefore(String childNameToBeMoved, String nameOfChildAtPosition)" can be used by calling on the parent node and supplying the name (with SNS index if needed) of the child to be moved and the name of the child before which the other child is to be moved.

This same model can be used for the graph request.  It also would allow adding in the future another optional request that would contain multiple reorders, and that could be implemented in RequestProcessor to break into multiple ReorderChildRequest instances.

The existing (writable) connectors will all be affected, since this will be a new mandatory request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 12:03:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 12:03:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-252) Complete support for
 events to the connector framework
In-Reply-To: <18635643.1227126756412.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2457188.1240329802506.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-252:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


> Complete support for events to the connector framework
> ------------------------------------------------------
>
>                 Key: DNA-252
>                 URL: https://jira.jboss.org/jira/browse/DNA-252
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.5
>
>
> The connector's support for events is incomplete.  There is the ability to add listeners to connections, but there are no methods on the listeners and no definition of what an event is.  This needs to be compatible with the Requests and JCR's event listeners.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 12:13:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 21 Apr 2009 12:13:29 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-371) No Default JAAS
	Implementation
In-Reply-To: <11596321.1240253422276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15350644.1240330409686.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463477#action_12463477 ] 

Randall Hauch commented on DNA-371:
-----------------------------------

I'm not convinced DNA needs to ship with any JAAS implementation, but we certainly do need to have tests that verify we do work with a JAAS implementation.  We also probably want to enhance the documentation to show how to set up, configure, and use a JAAS implementation.  The JBoss IDTrust project is the JAAS implementation within JBoss AS/EAP, and would be a good implementation to use for our examples.

> No Default JAAS Implementation
> ------------------------------
>
>                 Key: DNA-371
>                 URL: https://jira.jboss.org/jira/browse/DNA-371
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>
> DNA security is currently based on JAAS concepts, but DNA does not ship with any type of JAAS implementation for use outside of an existing server that could somehow pass Credentials into DNA.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 17:45:34 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 17:45:34 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10453795.1240350334146.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-369:
--------------------------------

    Attachment: DNA-369.patch


Attached a patch that conservatively checks all child nodes and properties of changed nodes before they are saved.  The approach is conservative in that is does not consider the dna:nodeDefinition property on the node in case the definition for the node has been modified.  Although the API does not currently allow modification of existing node types, this is a planned feature and a requirement for JCR 2.0 implementation.  This patch does not eliminate the race condition between adding a child item based on a definition that is being modified, but it does reduce the window of time in which that error can occur.

The patch also adds a save-time check that all mandatory properties and nodes are populated.  This is a requirement of the specification.

Finally, the patch adds some node types and configuration properties to the JR TCK to enable a few of the tests that depend on very specific properties to pass.

Apologies for the patch including a few gibberish lines of the Session.move patch in SessionCache.save.

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>         Attachments: DNA-369.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 17:55:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 17:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6167124.1240350922275.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-369:
--------------------------------

    Attachment: DNA-369_works.patch


Previous version left off a few required files.  Please disregard and use _works patch instead.  Sorry.

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>         Attachments: DNA-369.patch, DNA-369_works.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 18:12:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 18:12:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-377)
 AbstractJcrNode.addNode(String
 relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
Message-ID: <29025426.1240351942486.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode.addNode(String relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
--------------------------------------------------------------------------------------------------------

                 Key: DNA-377
                 URL: https://jira.jboss.org/jira/browse/DNA-377
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers


The TCK test NodeTest.testAddNodeConstraintViolationExceptionProperty fails because DNA throws a PathNotFoundException instead of a ConstraintViolationException when the test attempts to add a child node at the relative path "prop1/node2".  By spec, DNA needs to throw a ConstraintViolationException if relPath contains a property.  However, DNA currently only checks for the existence of a property if the relative path has more than 2 segments.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 18:14:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 18:14:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-377)
 AbstractJcrNode.addNode(String
 relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
In-Reply-To: <29025426.1240351942486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14034541.1240352062279.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-377:
--------------------------------

    Attachment: DNA-377.patch


Patch adds case to handle relative path consisting of exactly 2 segments.

> AbstractJcrNode.addNode(String relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-377
>                 URL: https://jira.jboss.org/jira/browse/DNA-377
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-377.patch
>
>
> The TCK test NodeTest.testAddNodeConstraintViolationExceptionProperty fails because DNA throws a PathNotFoundException instead of a ConstraintViolationException when the test attempts to add a child node at the relative path "prop1/node2".  By spec, DNA needs to throw a ConstraintViolationException if relPath contains a property.  However, DNA currently only checks for the existence of a property if the relative path has more than 2 segments.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 18:18:33 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 18:18:33 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27633449.1240352313028.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-58:
-------------------------------

    Attachment: DNA-58_component_properties.patch


DNA-58_component_properties.patch extends existing ComponentConfig class to optionally contain a mapping of property names to values and modifies ComponentLibrary to dynamically set these properties on the component with these values after instantiation.



> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 21 18:26:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 21 Apr 2009 18:26:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11754013.1240352782300.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-58:
-------------------------------

    Attachment: DNA-58_builder_engine.patch


DNA-58_builder_engine.patch implements a previous patch from rhauch.  Adds DnaConfiguration, a declarative method for specifying repositories, sequencers, mime type detectors, and their respective configurations.  Also adds a partial implementation of DnaEngine, a class to coordinate the activities of the respective repositories.

This patch does not fully address the defect as it lacks (at a minimum):
- A mechanism to configure the DnaEngine through XML (easy - once DnaConfiguration/DnaEngine are near final)
- An implementation of ObservationService - this will likely be a prerequisite for automated sequencer execution (hard - may require refactor of ObservationService to remove JCR dependencies)

Hopefully, this will at least turn out to be a useful basis for further discussion.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:35:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:35:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-137) Using ANTLR,
 create grammar for CND file specification
In-Reply-To: <18585137.1213369113197.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10144850.1240389337856.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-137.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch  (was: Dan Florian)


Completed as part of DNA-163.

> Using ANTLR, create grammar for CND file specification
> ------------------------------------------------------
>
>                 Key: DNA-137
>                 URL: https://jira.jboss.org/jira/browse/DNA-137
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:35:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:35:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-138) Create unit tests for
 the generated lexer/parser classes
In-Reply-To: <18194064.1213369233199.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30083436.1240389337912.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-138.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch  (was: Dan Florian)


Completed as part of DNA-163.

> Create unit tests for the generated lexer/parser classes
> --------------------------------------------------------
>
>                 Key: DNA-138
>                 URL: https://jira.jboss.org/jira/browse/DNA-138
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:35:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:35:37 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-140) Create CND sequencer
 making use of the CND lexer/parser
In-Reply-To: <7706739.1213372353707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19870814.1240389337951.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-140.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Completed as part of DNA-163.

> Create CND sequencer making use of the CND lexer/parser
> -------------------------------------------------------
>
>                 Key: DNA-140
>                 URL: https://jira.jboss.org/jira/browse/DNA-140
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-141) Generated
 lexer/parser code should include suppress warnings annotation
In-Reply-To: <19992729.1213372593213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13435232.1240389442522.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-141.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Completed as part of DNA-163.

> Generated lexer/parser code should include suppress warnings annotation
> -----------------------------------------------------------------------
>
>                 Key: DNA-141
>                 URL: https://jira.jboss.org/jira/browse/DNA-141
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-142) Grammar should parse
 namespace mappings into a prefix and a URI
In-Reply-To: <6992159.1213372593265.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18775328.1240389442560.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-142.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Completed as part of DNA-163.

> Grammar should parse namespace mappings into a prefix and a URI
> ---------------------------------------------------------------
>
>                 Key: DNA-142
>                 URL: https://jira.jboss.org/jira/browse/DNA-142
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-143) Create tests for
 child node
 definition counts and quoted strings in the grammar unit tests
In-Reply-To: <27351052.1213372843347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17768487.1240389442605.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-143.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Completed as part of DNA-163.

> Create tests for child node definition counts and quoted strings in the grammar unit tests
> ------------------------------------------------------------------------------------------
>
>                 Key: DNA-143
>                 URL: https://jira.jboss.org/jira/browse/DNA-143
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-143) Create tests for child
 node definition counts and quoted strings in the grammar unit tests
In-Reply-To: <27351052.1213372843347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26029963.1240389442897.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-143:
------------------------------

    Comment: was deleted


> Create tests for child node definition counts and quoted strings in the grammar unit tests
> ------------------------------------------------------------------------------------------
>
>                 Key: DNA-143
>                 URL: https://jira.jboss.org/jira/browse/DNA-143
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-143) Create tests for
 child node
 definition counts and quoted strings in the grammar unit tests
In-Reply-To: <27351052.1213372843347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4471009.1240389442942.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463652#action_12463652 ] 

Randall Hauch commented on DNA-143:
-----------------------------------

Completed as part of DNA-363.

> Create tests for child node definition counts and quoted strings in the grammar unit tests
> ------------------------------------------------------------------------------------------
>
>                 Key: DNA-143
>                 URL: https://jira.jboss.org/jira/browse/DNA-143
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:37:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:37:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-144) Parser should throw
 exception if parsing of CND does not complete successfully
In-Reply-To: <4760832.1213373673207.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32847844.1240389442999.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-144.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Completed as part of DNA-363.

> Parser should throw exception if parsing of CND does not complete successfully
> ------------------------------------------------------------------------------
>
>                 Key: DNA-144
>                 URL: https://jira.jboss.org/jira/browse/DNA-144
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-142) Grammar should parse
 namespace mappings into a prefix and a URI
In-Reply-To: <6992159.1213372593265.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32425572.1240389562643.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-142:
------------------------------

    Comment: was deleted


> Grammar should parse namespace mappings into a prefix and a URI
> ---------------------------------------------------------------
>
>                 Key: DNA-142
>                 URL: https://jira.jboss.org/jira/browse/DNA-142
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-142) Grammar should parse
 namespace mappings into a prefix and a URI
In-Reply-To: <6992159.1213372593265.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3973426.1240389562688.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463654#action_12463654 ] 

Randall Hauch commented on DNA-142:
-----------------------------------

Completed as part of DNA-363.

> Grammar should parse namespace mappings into a prefix and a URI
> ---------------------------------------------------------------
>
>                 Key: DNA-142
>                 URL: https://jira.jboss.org/jira/browse/DNA-142
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-141) Generated lexer/parser
 code should include suppress warnings annotation
In-Reply-To: <19992729.1213372593213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21064444.1240389562730.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-141:
------------------------------

    Comment: was deleted


> Generated lexer/parser code should include suppress warnings annotation
> -----------------------------------------------------------------------
>
>                 Key: DNA-141
>                 URL: https://jira.jboss.org/jira/browse/DNA-141
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-140) Create CND sequencer
 making use of the CND lexer/parser
In-Reply-To: <7706739.1213372353707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6241838.1240389562982.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463656#action_12463656 ] 

Randall Hauch commented on DNA-140:
-----------------------------------

Completed as part of DNA-363.

> Create CND sequencer making use of the CND lexer/parser
> -------------------------------------------------------
>
>                 Key: DNA-140
>                 URL: https://jira.jboss.org/jira/browse/DNA-140
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-141) Generated
 lexer/parser code should include suppress warnings annotation
In-Reply-To: <19992729.1213372593213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3499753.1240389562879.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463655#action_12463655 ] 

Randall Hauch commented on DNA-141:
-----------------------------------

Completed as part of DNA-363.

> Generated lexer/parser code should include suppress warnings annotation
> -----------------------------------------------------------------------
>
>                 Key: DNA-141
>                 URL: https://jira.jboss.org/jira/browse/DNA-141
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-140) Create CND sequencer
 making use of the CND lexer/parser
In-Reply-To: <7706739.1213372353707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29406265.1240389562928.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-140:
------------------------------

    Comment: was deleted


> Create CND sequencer making use of the CND lexer/parser
> -------------------------------------------------------
>
>                 Key: DNA-140
>                 URL: https://jira.jboss.org/jira/browse/DNA-140
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-138) Create unit tests for
 the generated lexer/parser classes
In-Reply-To: <18194064.1213369233199.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33498068.1240389563029.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-138:
------------------------------

    Comment: was deleted


> Create unit tests for the generated lexer/parser classes
> --------------------------------------------------------
>
>                 Key: DNA-138
>                 URL: https://jira.jboss.org/jira/browse/DNA-138
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-138) Create unit tests
 for the generated lexer/parser classes
In-Reply-To: <18194064.1213369233199.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15893473.1240389563078.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463657#action_12463657 ] 

Randall Hauch commented on DNA-138:
-----------------------------------

Completed as part of DNA-363.

> Create unit tests for the generated lexer/parser classes
> --------------------------------------------------------
>
>                 Key: DNA-138
>                 URL: https://jira.jboss.org/jira/browse/DNA-138
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-137) Using ANTLR,
 create grammar for CND file specification
In-Reply-To: <18585137.1213369113197.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14362517.1240389563122.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-137:
------------------------------

    Comment: was deleted


> Using ANTLR, create grammar for CND file specification
> ------------------------------------------------------
>
>                 Key: DNA-137
>                 URL: https://jira.jboss.org/jira/browse/DNA-137
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-137) Using ANTLR,
 create grammar for CND file specification
In-Reply-To: <18585137.1213369113197.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28399217.1240389563165.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463658#action_12463658 ] 

Randall Hauch commented on DNA-137:
-----------------------------------

Completed as part of DNA-363.

> Using ANTLR, create grammar for CND file specification
> ------------------------------------------------------
>
>                 Key: DNA-137
>                 URL: https://jira.jboss.org/jira/browse/DNA-137
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers
>    Affects Versions: 0.2
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-73) Sequence CND files
In-Reply-To: <31448608.1211385239690.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11401654.1240389563288.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-73.
------------------------------

    Resolution: Done
      Assignee: Randall Hauch  (was: Dan Florian)


Completed as part of DNA-363.

> Sequence CND files
> ------------------
>
>                 Key: DNA-73
>                 URL: https://jira.jboss.org/jira/browse/DNA-73
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Johnny Verhaeg
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> Create a sequencer for JCR CND files.  This sequencer should be integral to the DNA product (i.e., not an optional add-on sequencer).  May want to use ANTLR to define the grammar, lex, and parse.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:45:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:45:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-262) JCR-Level 2: Support
 persistent namespace changes
In-Reply-To: <19418054.1227540456463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26795101.1240389922337.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-262.
-------------------------------

    Fix Version/s: 0.4
                       (was: Future Releases)
       Resolution: Done
         Assignee: Randall Hauch


Actually resolved by DNA-286.

> JCR-Level 2: Support persistent namespace changes
> -------------------------------------------------
>
>                 Key: DNA-262
>                 URL: https://jira.jboss.org/jira/browse/DNA-262
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> JCR Level 2 requires support for persisting changes to namespaces in the repository.  We can already support that with all of our connectors, since they're all able to store the namespace URIs for the content.  In fact, none of them currently store or use the prefixes.
> However, one thing DNA still doesn't have is the ability to manage the namespace prefixes in the connectors.  This probably will entail having a NamespaceRegistry implementation that can use a connector to populate the namespace registry.  This is a little tricky, tho, since the NamespaceRegistry is part of the ExecutionContext, which is passed to the connector's "execute(ExecutionContext,Request)" method.  So, while it is ideal that these namespace management methods are just additional requests, the dependency graph may imply that the namespace management methods need to be added to the RepositoryConnector interface.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:49:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:49:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-375) Enhance
 MoveBranchRequest to take
 a new name, analogous to how CopyBranchRequest works
In-Reply-To: <14887345.1240328782522.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2551406.1240390162284.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-375.
-------------------------------

    Resolution: Done


Changed the connector API's MoveBranchRequest to have a new desiredName() field, and changed the writable connectors to implement these new semantics.  Also expose this through the Graph API.  Added several tests to the connector unit test framework to test for these additional move behaviors.

> Enhance MoveBranchRequest to take a new name, analogous to how CopyBranchRequest works
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-375
>                 URL: https://jira.jboss.org/jira/browse/DNA-375
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>
> CopyBranchRequest has a desiredNameForCopy that is used to specify the name for the new copy, which may be null if the original name is to be used.  MoveBranchRequest should also have a desiredNewName that, if provided, would also rename the node.
> This change will affect all of the existing connectors that support updates, but it does close a gap in the Graph functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:55:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-268) Add performance tests
 to the connector testing framework.
In-Reply-To: <19969579.1231362194133.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28788741.1240390522461.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-268.
-------------------------------

    Fix Version/s: 0.4
                       (was: Future Releases)
       Resolution: Duplicate Issue


> Add performance tests to the connector testing framework.
> ---------------------------------------------------------
>
>                 Key: DNA-268
>                 URL: https://jira.jboss.org/jira/browse/DNA-268
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>
> We already have a series of unit tests that verify functionality, but we should add unit tests (or integration-level tests) that measure performance of the connectors (including speed metrics, volume metrics, etc.).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:57:34 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:57:34 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-26) Extract EXIF metadata
 from JPEG files
Message-ID: <13376022.1240390654471.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463662#action_12463662 ] 

Randall Hauch commented on DNA-26:
----------------------------------

Note that the current image sequencer (in the "dna-sequencer-images" project) currently extracts the basic image metadata, and does not extract the EXIF metadata.

> Extract EXIF metadata from JPEG files
> -------------------------------------
>
>                 Key: DNA-26
>                 URL: https://jira.jboss.org/jira/browse/DNA-26
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Priority: Optional
>             Fix For: Future Releases
>
>
> The image sequencer extracts basic metadata from PNG, BMP, JPEG, GIF and other image files.  Enhance this sequencer to extract EXIF metadata for JPEG files.  
> Drew Noake's metadata extractor (http://www.drewnoakes.com/code/exif/index.html) seems to be a widely used library for extracting EXIF metadata, and has support for a number of cameras.  This library does not appear to be in a any of the Maven 2 repositories, and Drew does not specify the Maven coordinates.  The package structure is "com.drew.*", but Aduna has it in its Maven 2 repository (http://repository.aduna-software.org/maven2/com/drewnoakes/metadata-extractor/) under "com.drewnoakes" (which is Drew's domain).
> The EXIF metadata is organized as tags under directories.  See a sample output of EXIF metadata at http://www.drewnoakes.com/code/exif/sampleOutput.html.  This could be mapped to JCR by having a child node (of type "exif:directory") named for each directory (e.g., "EXIF").  Should the tags be stored as properties on each directory node (not a great mapping from the tag names to property names, and not really very extensible but probably easier to use), or as child nodes (of type "exit:tag" ?) with properties for the tag name, hex value, and description (value)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 04:59:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 04:59:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-343) TCK Tests for Node
 Mixin Modification Methods Fail
In-Reply-To: <30232623.1238962942269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13839221.1240390762913.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-343.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


The patch resolves the issue.

> TCK Tests for Node Mixin Modification Methods Fail
> --------------------------------------------------
>
>                 Key: DNA-343
>                 URL: https://jira.jboss.org/jira/browse/DNA-343
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-343.patch
>
>
> The TCK tests for canAddMixin, addMixin, and removeMixin don't work yet.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:05:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:05:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-301) Most state managed
 within the
 Workspace should be shared among multiple Session instances
In-Reply-To: <27883920.1237263876479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6673112.1240391122437.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-301.
-------------------------------

    Fix Version/s: 0.4
                       (was: 0.5)
       Resolution: Done
         Assignee: Randall Hauch


This was done as part of DNA-302.

> Most state managed within the Workspace should be shared among multiple Session instances
> -----------------------------------------------------------------------------------------
>
>                 Key: DNA-301
>                 URL: https://jira.jboss.org/jira/browse/DNA-301
>             Project: DNA
>          Issue Type: Task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> Our current JcrWorkspace implementation is created to be used only by the one JcrSession instance associated with it.  Currently, each Session would have it's own Workspace implementation, each of which would have its own copy of the namespace registry and node type manager.  
> However, one common use case for JCR involves creating many Session instances for the same workspace (e.g., this is the web app scenario).  This means that we'd have a lot of Workspace instances (same number as Session instances) each with their own copy of the data.  In fact, the node type manager should actually be "owned" (at least logically) by the repository, per section 6.7.9: "There is one node type registry per repository, therefore the NodeTypeManager is not workspace-specific; it provides introspection methods for the global, repository-wide set of available node types."
> Therefore, a number of things that are currently in the JcrWorkspace implementation should be pulled out and reused for all JcrWorkspace instances created by the JcrRepository for the same logical workspace.  This issue captures the set of tasks that are involved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:07:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:07:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-302) Make
 JcrNodeTypeManager not dependent on JcrSession
In-Reply-To: <26976618.1237264222615.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28466808.1240391242844.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-302.
-------------------------------

    Fix Version/s: 0.4
                       (was: 0.5)
       Resolution: Done
         Assignee: Randall Hauch


The patch resolved the issue.

> Make JcrNodeTypeManager not dependent on JcrSession
> ---------------------------------------------------
>
>                 Key: DNA-302
>                 URL: https://jira.jboss.org/jira/browse/DNA-302
>             Project: DNA
>          Issue Type: Sub-task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-302.patch
>
>
> The JcrNodeTypeManager should not be dependent upon a JcrSession instance.  Most of the methods (including those in JcrNodeType, JcrNodeDefinition, and JcrPropertyDefinition) only need an ExecutionContext.  JcrNodeDefinition.getDefaultPrimaryType() seems to depend upon the NodeTypeManager to dynamically look up a type (there may be others).  This main mean that the JcrNodeTypeManager needs a method to allow adding types from a JcrNodeTypeSource (rather than a JcrNodeTypeSource be passed into the constructor).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:07:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:07:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-301) Most state managed
 within the
 Workspace should be shared among multiple Session instances
In-Reply-To: <27883920.1237263876479.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25160432.1240391242676.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-301:
------------------------------

    Comment: was deleted


> Most state managed within the Workspace should be shared among multiple Session instances
> -----------------------------------------------------------------------------------------
>
>                 Key: DNA-301
>                 URL: https://jira.jboss.org/jira/browse/DNA-301
>             Project: DNA
>          Issue Type: Task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> Our current JcrWorkspace implementation is created to be used only by the one JcrSession instance associated with it.  Currently, each Session would have it's own Workspace implementation, each of which would have its own copy of the namespace registry and node type manager.  
> However, one common use case for JCR involves creating many Session instances for the same workspace (e.g., this is the web app scenario).  This means that we'd have a lot of Workspace instances (same number as Session instances) each with their own copy of the data.  In fact, the node type manager should actually be "owned" (at least logically) by the repository, per section 6.7.9: "There is one node type registry per repository, therefore the NodeTypeManager is not workspace-specific; it provides introspection methods for the global, repository-wide set of available node types."
> Therefore, a number of things that are currently in the JcrWorkspace implementation should be pulled out and reused for all JcrWorkspace instances created by the JcrRepository for the same logical workspace.  This issue captures the set of tasks that are involved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:07:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:07:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-303) The workspace
 NamespaceRegistry implementation should be shared
In-Reply-To: <28165566.1237264582270.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7217534.1240391242920.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-303.
-------------------------------

    Fix Version/s: 0.4
                       (was: 0.5)
       Resolution: Done
         Assignee: Randall Hauch


The patch resolved the issue.

> The workspace NamespaceRegistry implementation should be shared
> ---------------------------------------------------------------
>
>                 Key: DNA-303
>                 URL: https://jira.jboss.org/jira/browse/DNA-303
>             Project: DNA
>          Issue Type: Sub-task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> The JcrWorkspace class currently uses the GraphNamespaceRegistry, which implements DNA's NamespaceRegistry implementation on top of namespace mappings stored in a graph.  While this works for a single ExecutionContext, having a shared implementation for multiple JcrWorkspace objects means that the update methods need to be done with the ExecutionContext of the user making the changes.  This would require changing the design a fair amount.
> The NamespaceRegistry implementation would also need to be thread-safe.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:11:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:11:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-365) Workspace.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9485339.1240391482282.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-365.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Duplicate Issue


See DNA-360, which appears to have the same patch.

> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-365.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:13:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:13:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-365) Workspace.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5885332.1240391602469.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch reopened DNA-365:
-------------------------------

      Assignee: Randall Hauch


Incorrectly marked as a duplicate.

> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-365.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:23:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-377)
 AbstractJcrNode.addNode(String
 relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
In-Reply-To: <29025426.1240351942486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5753505.1240392202298.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-377.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch that handles a path of exactly 2 segments, so that the proper exception is thrown.

> AbstractJcrNode.addNode(String relPath) Throws Wrong Exception if relPath Has Form PropertyName/NodeName
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-377
>                 URL: https://jira.jboss.org/jira/browse/DNA-377
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-377.patch
>
>
> The TCK test NodeTest.testAddNodeConstraintViolationExceptionProperty fails because DNA throws a PathNotFoundException instead of a ConstraintViolationException when the test attempts to add a child node at the relative path "prop1/node2".  By spec, DNA needs to throw a ConstraintViolationException if relPath contains a property.  However, DNA currently only checks for the existence of a property if the relative path has more than 2 segments.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:25:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:25:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-101) potential user
 confusion between
 org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces
 and similar javax.jcr interfaces
In-Reply-To: <10266579.1212511460536.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8322971.1240392322749.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-101.
-------------------------------

    Resolution: Won't Fix


The current design works very well, and (as mentioned) is intentionally similar to the JCR model.  This, coupled with the fact that a client will not see this while using the JCR API, means that we don't need or want to change the current design.

> potential user confusion between org.jboss.dna.spi.graph ValueFactory and ValueFormatException interfaces and similar javax.jcr interfaces
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-101
>                 URL: https://jira.jboss.org/jira/browse/DNA-101
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph
>    Affects Versions: 0.2
>            Reporter: Greg Haber
>            Priority: Trivial
>
> The new org.jboss.dna.spi.graph.ValueFactory and package org.jboss.dna.spi.graph.ValueFormatException interfaces may be potentially confusing to users that are using both DNA and the underlying JCR APIs in the same code.  This is because there are interfaces with exactly the same names, and with very similar purposes (the JCR interfaces deal with instances of the javax.jcr.Value class, where the DNA interfaces are for standard Java objects), in the javax.jcr package.  We should think about changing the names of the DNA interfaces to avoid such potential confusion.  This is a very minor issue, I would not object if we decided to leave the interface names unchanged.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:43:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:43:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26991905.1240393402633.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463689#action_12463689 ] 

Randall Hauch commented on DNA-364:
-----------------------------------

Applied the patch.  Since DNA-375 (enhanced move with rename) is now completed, the rest of this issue could be worked.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>         Attachments: DNA-364.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:55:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3787721.1240394122575.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-369:
------------------------------

    Fix Version/s: 0.4


Targeted to 0.4.

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-369.patch, DNA-369_works.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 05:55:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 05:55:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14012309.1240394122611.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-364:
------------------------------

    Fix Version/s: 0.4


Targeted to 0.4.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-364.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 06:02:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 06:02:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-371) No Default JAAS
	Implementation
In-Reply-To: <11596321.1240253422276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23931874.1240394542471.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-371:
------------------------------

    Fix Version/s: 0.5


Targeted to 0.5. However, if something can/should be addressed in 0.4, feel free.

> No Default JAAS Implementation
> ------------------------------
>
>                 Key: DNA-371
>                 URL: https://jira.jboss.org/jira/browse/DNA-371
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.5
>
>
> DNA security is currently based on JAAS concepts, but DNA does not ship with any type of JAAS implementation for use outside of an existing server that could somehow pass Credentials into DNA.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 06:02:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 06:02:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-367)
 AbstractJcrNode.getReferences() Is Incorrect
In-Reply-To: <21712574.1240252042628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31263030.1240394542509.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-367:
------------------------------

    Fix Version/s: 0.5


Targeted to 0.5. However, if something can/should be addressed in 0.4, feel free.

> AbstractJcrNode.getReferences() Is Incorrect
> --------------------------------------------
>
>                 Key: DNA-367
>                 URL: https://jira.jboss.org/jira/browse/DNA-367
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.5
>
>
> AbstractJcrNode.getReferences currently returns all of the reference properties in that node.  According to section 6.2.3 of the 1.0.1 specification, it is supposed to return all _other_ nodes that refer to it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 06:02:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 06:02:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-370) JcrWorkspace.clone Is
 Not Implemented
In-Reply-To: <1486867.1240252882274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29815736.1240394542546.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-370:
------------------------------

    Fix Version/s: 0.5


Targeted to 0.5. However, if something can/should be addressed in 0.4, feel free.

> JcrWorkspace.clone Is Not Implemented
> -------------------------------------
>
>                 Key: DNA-370
>                 URL: https://jira.jboss.org/jira/browse/DNA-370
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.5
>
>
> JcrWorkspace.clone is not yet implemented.  This may not be important/useful for 0.4.  AbstractJcrNode.getCorrespondingNodePath is also not yet implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 06:02:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 06:02:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-368) Referenced Nodes Can
	Be Deleted
In-Reply-To: <27124321.1240252162271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31501289.1240394542587.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-368:
------------------------------

    Fix Version/s: 0.5


Targeted to 0.5. However, if something can/should be addressed in 0.4, feel free.

> Referenced Nodes Can Be Deleted
> -------------------------------
>
>                 Key: DNA-368
>                 URL: https://jira.jboss.org/jira/browse/DNA-368
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.5
>
>
> There is not currently a check in AbstractJcrNode.remove() to see if the node (or any of its child nodes) are targets of references.  Per section 7.1.6 of the 1.0.1 specification, this should cause a ReferentialIntegrityException to be thrown.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 06:02:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 06:02:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-372) Session.impersonate and
 Session.checkPermission Are Not Implemented
In-Reply-To: <9512717.1240253662803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24418591.1240394542631.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-372:
------------------------------

    Fix Version/s: 0.5


Targeted to 0.5. However, if something can/should be addressed in 0.4, feel free.

> Session.impersonate and Session.checkPermission Are Not Implemented
> -------------------------------------------------------------------
>
>                 Key: DNA-372
>                 URL: https://jira.jboss.org/jira/browse/DNA-372
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.5
>
>
> Both methods need to be implemented to pass all of the JR TCK L2 tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 08:41:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 22 Apr 2009 08:41:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6020328.1240404082516.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-369:
--------------------------------

    Attachment: DNA-369_AbstractJcrNode.patch


Added missing piece of patch

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-369.patch, DNA-369_AbstractJcrNode.patch, DNA-369_works.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 09:29:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 22 Apr 2009 09:29:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-365) Workspace.importXml and
 getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26638984.1240406962344.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-365:
--------------------------------

    Attachment: DNA-365_take_2.patch


Re-based version of previous patch.

> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-365.patch, DNA-365_take_2.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 09:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 09:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28867102.1240407562545.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463792#action_12463792 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Applied the first patch ("") and a small part of the second (""), which enhanced ComponentConfig to allow properties that are set reflectively on the components when they are instantiated.  Subclasses of ComponentConfig were also modified, as were the test cases.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 09:39:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 09:39:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4702802.1240407562596.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-58:
-----------------------------

    Comment: was deleted


> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 09:39:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 09:39:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10939332.1240407563275.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463793#action_12463793 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Applied the first patch ("DNA-58_component_properties.patch") and a small part of the second ("DNA-58_builder_engine.patch"), which enhanced ComponentConfig to allow properties that are set reflectively on the components when they are instantiated.  Subclasses of ComponentConfig were also modified, as were the test cases.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 10:06:23 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 22 Apr 2009 10:06:23 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28015331.1240409183151.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12463809#action_12463809 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Applied the second patch, which added DnaConfiguration and DnaEngine classes (along with test cases), and the MimeTypeDetectorConfig class (and its test cases).

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 22 11:23:22 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 22 Apr 2009 11:23:22 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22071584.1240413802296.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-364:
--------------------------------

    Attachment: DNA-364_delta_with_rename.patch


Used rhauch's latest graph feature (thanks!) to implement renaming on Session.move calls.  Added unit test to check this since JR TCK doesn't exercise this capability.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-364.patch, DNA-364_delta_with_rename.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 11:17:41 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 11:17:41 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
Message-ID: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>

XML Graph Importer should support importing multi-valued properties 
--------------------------------------------------------------------

                 Key: DNA-378
                 URL: https://jira.jboss.org/jira/browse/DNA-378
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
            Reporter: Randall Hauch
             Fix For: 0.4


The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.

The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.

This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.

Here's an example:

<cars>
  <car jcr:name="Mini">
    <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
    <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
  </car>
</cars>

I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 11:56:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 11:56:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-379) Graph API should allow
 adding and removing property values
Message-ID: <22467685.1240502200326.JavaMail.jira@cloud.prod.atl2.jboss.com>

Graph API should allow adding and removing property values
----------------------------------------------------------

                 Key: DNA-379
                 URL: https://jira.jboss.org/jira/browse/DNA-379
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


The Graph API should allow adding a value to an existing property without having to first read the property.  The same thing for removing a value (if it is there).  This is needed especially when working with batch operations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 12:24:41 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 12:24:41 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-380) The inflector is not
 lowercasing the first character in the 'camelCase(...)' method
Message-ID: <27635523.1240503881084.JavaMail.jira@cloud.prod.atl2.jboss.com>

The inflector is not lowercasing the first character in the 'camelCase(...)' method
-----------------------------------------------------------------------------------

                 Key: DNA-380
                 URL: https://jira.jboss.org/jira/browse/DNA-380
             Project: DNA
          Issue Type: Bug
          Components: Common
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


The Inflector.camelCase(...) method takes a boolean to say whether the first character should be uppercased.  When 'false' was provided as a parameter, the method was not lowercasing the first character (as the JavaDoc says it should).  This makes Inflector.lowerCamelCase(...) not work properly when the first character is already uppercase.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 12:26:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 12:26:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-380) The inflector is not
 lowercasing the first character in the 'camelCase(...)' method
In-Reply-To: <27635523.1240503881084.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20296729.1240504000693.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-380.
-------------------------------

    Resolution: Done


Corrected the camelCase(...)  method to lowercase the first character per the JavaDoc.

> The inflector is not lowercasing the first character in the 'camelCase(...)' method
> -----------------------------------------------------------------------------------
>
>                 Key: DNA-380
>                 URL: https://jira.jboss.org/jira/browse/DNA-380
>             Project: DNA
>          Issue Type: Bug
>          Components: Common
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> The Inflector.camelCase(...) method takes a boolean to say whether the first character should be uppercased.  When 'false' was provided as a parameter, the method was not lowercasing the first character (as the JavaDoc says it should).  This makes Inflector.lowerCamelCase(...) not work properly when the first character is already uppercase.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 12:28:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 12:28:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-381) The Graph API should
 allow creating a node if it does not already exist
Message-ID: <16301981.1240504120262.JavaMail.jira@cloud.prod.atl2.jboss.com>

The Graph API should allow creating a node if it does not already exist
-----------------------------------------------------------------------

                 Key: DNA-381
                 URL: https://jira.jboss.org/jira/browse/DNA-381
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


The Graph API does not provide a way to create a node if it does not already exist.  This capability is already supported in the connector API, so it should be available to the Graph API users.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 12:30:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 12:30:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-381) The Graph API should
 allow creating a node if it does not already exist
In-Reply-To: <16301981.1240504120262.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20292526.1240504240425.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-381.
-------------------------------

    Resolution: Done


Added "createIfMissing(...)" methods that mirror the "create(...)" methods, but which use a different NodeConflictBehavior setting.

> The Graph API should allow creating a node if it does not already exist
> -----------------------------------------------------------------------
>
>                 Key: DNA-381
>                 URL: https://jira.jboss.org/jira/browse/DNA-381
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> The Graph API does not provide a way to create a node if it does not already exist.  This capability is already supported in the connector API, so it should be available to the Graph API users.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 12:44:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 12:44:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15485500.1240505080190.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464144#action_12464144 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Refactored the DnaConfiguration to make use of the graph repository for storing the configuration.  When used, the DnaConfiguration instance persists all the information to this graph, where it can be read and used.  A "save()" method was added to allow the code using the DnaConfiguration instance to control when the content is updated.  (This also simplified the unit testing, since it's very easy to check the graph content after the DnaConfiguration methods are used.)  The DnaEngine was then updated to read the configuration repository content and to instantiate and set up the services.

This "configuration repository" defaults to an in-memory repository, but can be set up to use a particular RepositorySource instance (that has already been set up) or to reflectively create an instance given the class name, optional class loader, and various (implementation-specific) Java bean properties.  

This means that in the simplest case, one can simply create a DnaConfiguration and configure the sequencers, sources, detectors, etc.  It also makes it very simple to "read" an XML file with the configuration, since that just uses the XML graph importer.  But using a configuration repository shines in the more advanced cases, such as when a process participates in a cluster.  Here, the process can create a DnaConfiguration, very easily set it up to use a shared (and remote) configuration repository (that already has the content), and without any other work immediately build the DnaEngine.

Using a graph as the configuration repository also means that any changes to the configuration could be monitored via graph events, allowing the DnaEngine to monitor any changes and dynamically alter its services.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:10:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:10:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21208701.1240510240187.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464154#action_12464154 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Changed DnaConfiguration to make it more tolernant of changes to the source pointing to the configuration repository.  In particular, this allows the DnaEngine to obtain an immutable definition of the configuration source, which allows the engine to properly access the source even if the DnaConfiguration instance is changed.

The DnaEngine was also refactored to pull into a nested scanner class the code that reads the configuration content.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:14:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:14:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32166526.1240510480259.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464155#action_12464155 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Minor change to allow a subclass to define the SessionFactory used by the SequencingService.  The configuration for the JCR engine may need to provide its own SessionFactory implementation (or instance).

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:19:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:19:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-335) DNA's NodeTypeManager
 implementation does not allow multiple definitions
 with the same name
In-Reply-To: <21319415.1237837222292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27383844.1240510780223.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-335.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Marking as resolved, since all issue has been addressed.

> DNA's NodeTypeManager implementation does not allow multiple definitions with the same name
> -------------------------------------------------------------------------------------------
>
>                 Key: DNA-335
>                 URL: https://jira.jboss.org/jira/browse/DNA-335
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-335-definitionsWithSameName.patch, DNA-335_clean_type_source.patch, DNA-335_overriding_definitions.patch
>
>
> The JCR Specification (version 1.0.1) does not preclude that there may be multiple property definitions with the same name, or that there may be multiple child definitions with the same name.  JCR 1.0 (version 1.0.1) DOES say that there may be multiple residual definitions with the same name.  However, the draft version of the JSR-283 specification does have a new section 4.7.15 that specifically addresses and allows multiple definitions with the same name, as long as they are distinguishable from the other definitions with the same name (for property definitions, this means the type must be different; for child node definitions, this means the required primary types attribute).
> There are a number of places where the logic is expecting a single property definition (or child definition) given a node type and a definition name.  This is obviously flawed.  Also, our logic to select the "best" property definition or "best" child node definition doesn't seem to be correct, in that it tends to favor less-restricted definitions that are lower in the type hierarchy rather than very good matching definitions higher in the type hierarchy.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:46:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:46:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-365) Workspace.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23688902.1240512400263.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464162#action_12464162 ] 

Randall Hauch commented on DNA-365:
-----------------------------------

Applied the patches from this issue and DNA-369.  Unfortunately, they couldn't easily be applied separately.

Note that several TCK unit tests had to be commented out (relative to the patch), since they must be testing behavior that is not yet committed to trunk.  (There were a few regressions, but it looks like they're actually related to DNA-374.)

> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-365.patch, DNA-365_take_2.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:46:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:46:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22099829.1240512400304.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464163#action_12464163 ] 

Randall Hauch commented on DNA-369:
-----------------------------------

Applied the patches from this issue and DNA-365.  Unfortunately, they couldn't easily be applied separately.

Note that several TCK unit tests had to be commented out (relative to the patch), since they must be testing behavior that is not yet committed to trunk.  (There were a few regressions, but it looks like they're actually related to DNA-374.)

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-369.patch, DNA-369_AbstractJcrNode.patch, DNA-369_works.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:46:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:46:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-369) Nodes Can Be Saved
 Without Mandatory Properties or Child Nodes Present
In-Reply-To: <11848421.1240252282707.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15141730.1240512400346.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-369.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Marking as resolved.

> Nodes Can Be Saved Without Mandatory Properties or Child Nodes Present
> ----------------------------------------------------------------------
>
>                 Key: DNA-369
>                 URL: https://jira.jboss.org/jira/browse/DNA-369
>             Project: DNA
>          Issue Type: Bug
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-369.patch, DNA-369_AbstractJcrNode.patch, DNA-369_works.patch
>
>
> Item.save() (or Session.save()) should throw a ConstraintViolationException if any of the items to be saved is missing a mandatory property or child node (per section 7.1.1.6 and SessionTest.testSaveConstraintViolationException in the JR TCK tests)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 14:46:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 14:46:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-365) Workspace.importXml
 and getContentHandler Are Not Implemented
In-Reply-To: <20529069.1240051522414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2277770.1240512400381.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-365.
-------------------------------

    Resolution: Done


Marking as resolved.

> Workspace.importXml and getContentHandler Are Not Implemented
> -------------------------------------------------------------
>
>                 Key: DNA-365
>                 URL: https://jira.jboss.org/jira/browse/DNA-365
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-365.patch, DNA-365_take_2.patch
>
>
> Workspace.importXml and getContentHandler are not implemented.  Adding these methods would require DNA to support direct writes (q.v. section 7.1.3.7 of the 1.0.1 specification).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:41:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:41:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22619529.1240515700584.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464180#action_12464180 ] 

Randall Hauch commented on DNA-364:
-----------------------------------

Applied the patch.  Some changes were required, as the before code was a little different than the patch was expecting.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-364.patch, DNA-364_delta_with_rename.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:41:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:41:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17952885.1240515700652.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-364.
-------------------------------

    Resolution: Done


Resolved the issue, since it is all implemented and tested.

> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-364.patch, DNA-364_delta_with_rename.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:41:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:41:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-364) Session.move Is Not
	Implemented
In-Reply-To: <9553144.1240051225309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24304925.1240515700736.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch reassigned DNA-364:
---------------------------------

    Assignee: Randall Hauch


> Session.move Is Not Implemented
> -------------------------------
>
>                 Key: DNA-364
>                 URL: https://jira.jboss.org/jira/browse/DNA-364
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-364.patch, DNA-364_delta_with_rename.patch
>
>
> JcrSession does not yet implement Session.move per JCR spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:48:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:48:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-285) Pass all Level 1 TCK
	unit tests
In-Reply-To: <18642947.1235148944956.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22292597.1240516120189.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-285:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


We still need to pass the query-related methods, since we have no query implementation at the moment.  Pushing to 0.5.

> Pass all Level 1 TCK unit tests
> -------------------------------
>
>                 Key: DNA-285
>                 URL: https://jira.jboss.org/jira/browse/DNA-285
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.5
>
>         Attachments: DNA-285_basic.patch
>
>
> We don't currently pass all of the Level 1 TCK unit tests.  See dna-jcr/src/test/java/org/jboss/dna/jcr/JackrabbitJcrTckTest.java, and specifically the JcrLevelOneTestSuite nested class.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:50:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:50:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-194) Implement update JCR
	capability
In-Reply-To: <19952894.1218050517308.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16711947.1240516240244.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-194.
-------------------------------

    Resolution: Done


I'm going to mark this as completed, since all of the work involving adding an implementation for update has been done.  There may be small pieces of functionality (or bugs), but those should be addressed as specific issues.

> Implement update JCR capability
> -------------------------------
>
>                 Key: DNA-194
>                 URL: https://jira.jboss.org/jira/browse/DNA-194
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>            Reporter: Johnny Verhaeg
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: dna-194-session-cache.patch, DNA-194_move_value_cast.patch
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:52:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:52:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-46) DNA should provide a
 JCR 1.0 API (JSR-170) implementation
Message-ID: <17840223.1240516360489.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-46:
-----------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since DNA-285 was also pushed.  We've made gargantuan progress in 0.4, but we do have a few things left.

> DNA should provide a JCR 1.0 API (JSR-170) implementation
> ---------------------------------------------------------
>
>                 Key: DNA-46
>                 URL: https://jira.jboss.org/jira/browse/DNA-46
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, JCR
>    Affects Versions: 0.2
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.5
>
>
> DNA should provide a JCR 1.0 API (JSR-170) implementation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-240) code test case for
 SVNRepositoryConnection used  for connection
In-Reply-To: <31126753.1224577100902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18725713.1240516491051.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-240:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> code test case for SVNRepositoryConnection used  for connection
> ---------------------------------------------------------------
>
>                 Key: DNA-240
>                 URL: https://jira.jboss.org/jira/browse/DNA-240
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.4
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.5
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-36) Federate content from
	SVN
Message-ID: <10861727.1240516491109.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-36:
-----------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> Federate content from SVN
> -------------------------
>
>                 Key: DNA-36
>                 URL: https://jira.jboss.org/jira/browse/DNA-36
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.4
>            Reporter: Randall Hauch
>            Assignee: Serge Emmanuel Pagop
>            Priority: Minor
>             Fix For: 0.5
>
>
> Create a connector for the federation engine that contributes and exposes content stored in a source control management (SCM) system into the federated repository.  This would enable integration of files managed by SVN (or CVS, etc.) to be accessible via JCR.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-175) ESB message sequencer
 has a dependency that doesn't exist in the JBoss repository
In-Reply-To: <25320161.1215630386958.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33323455.1240516491166.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-175:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> ESB message sequencer has a dependency that doesn't exist in the JBoss repository
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-175
>                 URL: https://jira.jboss.org/jira/browse/DNA-175
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>            Reporter: Johnny Verhaeg
>            Assignee: Stefano Maestri
>            Priority: Critical
>             Fix For: 0.5
>
>
> The dependency in the pom is to jbossesb-rosetta.jar/jbossesb-rosetta-dep/4.3

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <30742804.1240516491210.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-37:
-----------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Sergiy Litsenko
>            Priority: Minor
>             Fix For: 0.5
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-239) code test case for
 SVNRepositorySource used to manage the repos. content
In-Reply-To: <1909384.1224576860902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15289527.1240516491247.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-239:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> code test case for SVNRepositorySource used to manage the repos. content
> ------------------------------------------------------------------------
>
>                 Key: DNA-239
>                 URL: https://jira.jboss.org/jira/browse/DNA-239
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.4
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.5
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 15:54:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 15:54:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-78) Sequence ESB message
 for governance purposes
In-Reply-To: <18283595.1211833782319.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11894465.1240516491297.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-78:
-----------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Pushing to 0.5, since they are not critical for 0.4 and because we're approaching the end of 0.4.  If the assignee thinks it can be finished before the 0.4 release, please note here and notify the team.

> Sequence ESB message for governance purposes
> --------------------------------------------
>
>                 Key: DNA-78
>                 URL: https://jira.jboss.org/jira/browse/DNA-78
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Stefano Maestri
>            Assignee: Stefano Maestri
>             Fix For: 0.5
>
>
> Sequence message from ESB message store can give useful informations from a SOA Governance point of view

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 16:20:40 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 23 Apr 2009 16:20:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-382) Workspace.move Is Not
	Supported
Message-ID: <10413648.1240518040428.JavaMail.jira@cloud.prod.atl2.jboss.com>

Workspace.move Is Not Supported
-------------------------------

                 Key: DNA-382
                 URL: https://jira.jboss.org/jira/browse/DNA-382
             Project: DNA
          Issue Type: Bug
    Affects Versions: 0.3
            Reporter: Brian Carothers


JcrWorkspace.move is stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 16:26:40 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 23 Apr 2009 16:26:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-382) Workspace.move Is Not
	Supported
In-Reply-To: <10413648.1240518040428.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25806638.1240518400171.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-382:
--------------------------------

    Attachment: DNA-382.patch


Attached patch based on Session.move implementation

> Workspace.move Is Not Supported
> -------------------------------
>
>                 Key: DNA-382
>                 URL: https://jira.jboss.org/jira/browse/DNA-382
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>         Attachments: DNA-382.patch
>
>
> JcrWorkspace.move is stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 16:35:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 16:35:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-382) Workspace.move Is Not
	Supported
In-Reply-To: <10413648.1240518040428.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10703318.1240518940676.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-382.
-------------------------------

    Fix Version/s: 0.4
       Resolution: Done
         Assignee: Randall Hauch


Applied the patch to implement Workspace.move

> Workspace.move Is Not Supported
> -------------------------------
>
>                 Key: DNA-382
>                 URL: https://jira.jboss.org/jira/browse/DNA-382
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-382.patch
>
>
> JcrWorkspace.move is stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 16:37:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 16:37:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-382) Workspace.move Is Not
	Supported
In-Reply-To: <10413648.1240518040428.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10213487.1240519060177.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-382:
------------------------------

    Component/s: JCR


> Workspace.move Is Not Supported
> -------------------------------
>
>                 Key: DNA-382
>                 URL: https://jira.jboss.org/jira/browse/DNA-382
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-382.patch
>
>
> JcrWorkspace.move is stubbed in.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 17:39:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 17:39:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-379) Graph API should allow
 adding and removing property values
In-Reply-To: <22467685.1240502200326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <772247.1240522780507.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-379:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)
         Assignee:     (was: Randall Hauch)


> Graph API should allow adding and removing property values
> ----------------------------------------------------------
>
>                 Key: DNA-379
>                 URL: https://jira.jboss.org/jira/browse/DNA-379
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.5
>
>
> The Graph API should allow adding a value to an existing property without having to first read the property.  The same thing for removing a value (if it is there).  This is needed especially when working with batch operations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 23 17:53:40 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 23 Apr 2009 17:53:40 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1254382.1240523620247.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464256#action_12464256 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Minor change to allow the configuration to have more than one PathExpression in any sequencer.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 24 05:36:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 24 Apr 2009 05:36:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16005933.1240565806519.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464323#action_12464323 ] 

Brian Carothers commented on DNA-378:
-------------------------------------

Can we agree on the limitation that all properties so defined must come before any child nodes?

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Fri Apr 24 08:55:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 24 Apr 2009 08:55:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <567985.1240577746736.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464364#action_12464364 ] 

Randall Hauch commented on DNA-378:
-----------------------------------

Yes, that's a reasonable assumption if we need to make it.  Eventually I'd prefer that we allow them in any order, but DNA-379 may actually make this pretty straightforward (since the "characters" could be implemented to simply add a value without having to enqueue the results).  If so, then link this as depending upon DNA-379 and push this to 0.5.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 25 07:31:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 25 Apr 2009 07:31:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10398647.1240659106627.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464487#action_12464487 ] 

Brian Carothers commented on DNA-378:
-------------------------------------

It's the same limitation that JCR importing imposes.  

You did hit on the key reason - there doesn't seem to be a way to add a property to an existing node through the Graph API.  One can never create a node until one reaches the corresponding end tag.  In the pathological case, that means that you're basically building a DOM tree in memory before you commit anything to the graph.  It's not debilitating, but it is suboptimal.

I'm happy to proceed any of the 3 ways (only accept properties before child nodes, build the graph in memory prior to committing it, wait for -379 and 0.5).  Please just let me know what you prefer.

Thanks!

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 25 07:31:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 25 Apr 2009 07:31:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22943265.1240659106665.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464488#action_12464488 ] 

Brian Carothers commented on DNA-378:
-------------------------------------

It's the same limitation that JCR importing imposes.  

You did hit on the key reason - there doesn't seem to be a way to add a property to an existing node through the Graph API.  One can never create a node until one reaches the corresponding end tag.  In the pathological case, that means that you're basically building a DOM tree in memory before you commit anything to the graph.  It's not debilitating, but it is suboptimal.

I'm happy to proceed any of the 3 ways (only accept properties before child nodes, build the graph in memory prior to committing it, wait for -379 and 0.5).  Please just let me know what you prefer.

Thanks!

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 25 17:37:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 25 Apr 2009 17:37:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-383) dna-jcr-tck Project
 Keeps Getting Out Of Sync With dna-jcr Project
Message-ID: <19923214.1240695466393.JavaMail.jira@cloud.prod.atl2.jboss.com>

dna-jcr-tck Project Keeps Getting Out Of Sync With dna-jcr Project
------------------------------------------------------------------

                 Key: DNA-383
                 URL: https://jira.jboss.org/jira/browse/DNA-383
             Project: DNA
          Issue Type: Bug
          Components: JCR, Testing
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor
             Fix For: 0.4


The dna-jcr-tck project currently has its own local copy of the InMemoryRepositoryStub and repositoryStubImpl.properties.  If these two files are not kept in sync with their corresponding copies in dna-jcr, the TCK tests results will skew (generally in a negative direction).  It would be helpful to either keep syncing them up or remove the redundant files and fix the dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Sat Apr 25 17:46:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 25 Apr 2009 17:46:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-383) dna-jcr-tck Project
 Keeps Getting Out Of Sync With dna-jcr Project
In-Reply-To: <19923214.1240695466393.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22398656.1240696006374.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-383:
--------------------------------

    Attachment: DNA-383.patch


Patch to remove the redundant files in dna-jcr-tck and fix the POM.

- Hoists InMemoryRepositoryStub out of JcrTckTest in dna-jcr
- Fixes repositoryStubImpl.properties in dna-jcr to point to new repository stub class
- Removes repositoryStubImpl.properties and InMemoryRepositoryStub from dna-jcr-tck
- Fixes dna-jcr-tck POM to incorporate test JAR from dna-jcr project to pick up the two files from dna-jcr


> dna-jcr-tck Project Keeps Getting Out Of Sync With dna-jcr Project
> ------------------------------------------------------------------
>
>                 Key: DNA-383
>                 URL: https://jira.jboss.org/jira/browse/DNA-383
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-383.patch
>
>
> The dna-jcr-tck project currently has its own local copy of the InMemoryRepositoryStub and repositoryStubImpl.properties.  If these two files are not kept in sync with their corresponding copies in dna-jcr, the TCK tests results will skew (generally in a negative direction).  It would be helpful to either keep syncing them up or remove the redundant files and fix the dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 14:42:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 14:42:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
In-Reply-To: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12402045.1240857766461.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-374:
------------------------------

    Attachment: DNA-374.patch


Added a patch that fixes this issue by maintaining a hidden property to store the names of the properties that use multi-valued definitions but that have only one value.  This property is persisted as required, but is also cleaned up if it is empty or no longer needed.

The patch also moves the "dna:nodeDefinition" and this new property into a new "dnaint" namespace.  This allows some of the code to just check the namespace to know whether properties should be hidden from the JCR view.

> Multiplicity of some properties may change when saved and reloaded from the graph
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-374
>                 URL: https://jira.jboss.org/jira/browse/DNA-374
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>         Attachments: DNA-374.patch
>
>
> This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 14:46:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 14:46:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
In-Reply-To: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6533002.1240858006503.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464678#action_12464678 ] 

Randall Hauch commented on DNA-374:
-----------------------------------

Committed the patch, which also added in a number of commented-out TCK unit tests.

> Multiplicity of some properties may change when saved and reloaded from the graph
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-374
>                 URL: https://jira.jboss.org/jira/browse/DNA-374
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>         Attachments: DNA-374.patch
>
>
> This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 14:46:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 14:46:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-374) Multiplicity of some
 properties may change when saved and reloaded from the graph
In-Reply-To: <15664130.1240326202512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26310450.1240858006578.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-374.
-------------------------------

    Resolution: Done


Marking as resolved, since this does address the issue and is hopefully complete.  If not, feel free to reopen this issue.

> Multiplicity of some properties may change when saved and reloaded from the graph
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-374
>                 URL: https://jira.jboss.org/jira/browse/DNA-374
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>         Attachments: DNA-374.patch
>
>
> This problem arises when a client uses the multi-valued setter methods in the JCR API to create on a node a new property with a single value, to save the node, and then to continue working with the property (again, using the multi-valued setter or getter methods).  When the property is created, an appropriate multi-valued property definition will be chosen from those available on the node's primary type (and mixin types, if there are any).  However, after the save, the property may node have a single-valued property definition.  And since JCR does not allow a single-valued property to be changed via the multi-valued setters, the result is an exception when the client attempts to set the property using the multi-valued setters.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 14:58:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 14:58:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-383) dna-jcr-tck Project
 Keeps Getting Out Of Sync With dna-jcr Project
In-Reply-To: <19923214.1240695466393.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17846655.1240858726872.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-383.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Applied the patch, which removes the redundant files in dna-jcr-tck and fixes the POM.

> dna-jcr-tck Project Keeps Getting Out Of Sync With dna-jcr Project
> ------------------------------------------------------------------
>
>                 Key: DNA-383
>                 URL: https://jira.jboss.org/jira/browse/DNA-383
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Testing
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: DNA-383.patch
>
>
> The dna-jcr-tck project currently has its own local copy of the InMemoryRepositoryStub and repositoryStubImpl.properties.  If these two files are not kept in sync with their corresponding copies in dna-jcr, the TCK tests results will skew (generally in a negative direction).  It would be helpful to either keep syncing them up or remove the redundant files and fix the dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 15:22:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 15:22:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22023738.1240860166391.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464689#action_12464689 ] 

Randall Hauch commented on DNA-378:
-----------------------------------

Brian, did you mean to say "there doesn't seem a way to add a property VALUE ..." ?  The current graph API does allow you to set a property on a node, even if that node was created in a previous request (even if they're in the same batch).  For example, I can create a node (maybe supplying a handful of properties), and then call setProperty(x).on(samePath) and that will work just fine.  In fact, if setProperty is called right after the create, then the set property request even get merged into create request.  The graph API currently doesn't allow adding a value to a property; this is the heart of DNA-379.

The importer should already be keeping track of the path given the current stack, and you should always be able to set a property on the node (even after any child elements have just been finished).  The only tricky part is that to handle multi-valued properties (i.e., where each value is represented by a different child element's content), then the importer might have to keep a map of the properties set via child elements (and overwrite them if additional child elements are read with additional values for a property), and set them only when the element is ended.  If I'm correct, then it shouldn't matter whether the property child elements come before child elements, or in what order the property child elements appear.
It just means that the importer has to maintain a stack of properties for each "incomplete node" (or do this on the existing stack).

Waiting for DNA-379 would allow this to work without having to maintain the properties in the stack, since the processing of each child node (with content) would mean just adding that value to the property with the given name.  I agree it would be easier.  The only question is whether it's worth doing DNA-379 in 0.4.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 16:15:48 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 16:15:48 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-366) Allow child node to be
 reordered in the Graph API
In-Reply-To: <13518264.1240239142560.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15460557.1240863348372.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch closed DNA-366.
-----------------------------

    Resolution: Duplicate Issue


> Allow child node to be reordered in the Graph API
> -------------------------------------------------
>
>                 Key: DNA-366
>                 URL: https://jira.jboss.org/jira/browse/DNA-366
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Connectors, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> The Graph API doesn't really allow the child nodes to be reordered.  This feature is required for the JCR implementation

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 16:17:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 16:17:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-376) Add request to change
 the order of a child node (or nodes) relative to the other children
In-Reply-To: <21590252.1240329322777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22415986.1240863466346.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-376:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)
         Priority: Blocker  (was: Critical)


Pushing to 0.5 and raising the priority.

> Add request to change the order of a child node (or nodes) relative to the other children
> -----------------------------------------------------------------------------------------
>
>                 Key: DNA-376
>                 URL: https://jira.jboss.org/jira/browse/DNA-376
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.5
>
>
> The current DNA Graph model does support ordered children, and while rename can be used to change the order of same-name-siblings, there currently is no way to change the order of the child nodes.  This is required to fully implement the JCR API.
> JCR handles this functionality by provided a method that essentially changes the position of a single child node.  The "Node.orderBefore(String childNameToBeMoved, String nameOfChildAtPosition)" can be used by calling on the parent node and supplying the name (with SNS index if needed) of the child to be moved and the name of the child before which the other child is to be moved.
> This same model can be used for the graph request.  It also would allow adding in the future another optional request that would contain multiple reorders, and that could be implemented in RequestProcessor to break into multiple ReorderChildRequest instances.
> The existing (writable) connectors will all be affected, since this will be a new mandatory request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 21:49:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 21:49:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-384) Trouble compiling Java
 sequencer using Eclipse JDT and its dependencies
Message-ID: <14867062.1240883386419.JavaMail.jira@cloud.prod.atl2.jboss.com>

Trouble compiling Java sequencer using Eclipse JDT and its dependencies
-----------------------------------------------------------------------

                 Key: DNA-384
                 URL: https://jira.jboss.org/jira/browse/DNA-384
             Project: DNA
          Issue Type: Bug
          Components: Sequencers
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.4


The "dna-sequencer-java" project compiles with errors with newer versions of the Eclipse JDT because of dependency issues (some dependencies are not in the JBoss Maven 2 repository).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Mon Apr 27 21:51:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 27 Apr 2009 21:51:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-384) Trouble compiling
 Java sequencer using Eclipse JDT and its dependencies
In-Reply-To: <14867062.1240883386419.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12372215.1240883506350.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-384.
-------------------------------

    Resolution: Done


Adjusted the Eclipse JDT dependency fragments, removing some of its dependencies that remain unused in the "dna-sequencer-java" project.

> Trouble compiling Java sequencer using Eclipse JDT and its dependencies
> -----------------------------------------------------------------------
>
>                 Key: DNA-384
>                 URL: https://jira.jboss.org/jira/browse/DNA-384
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>
> The "dna-sequencer-java" project compiles with errors with newer versions of the Eclipse JDT because of dependency issues (some dependencies are not in the JBoss Maven 2 repository).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 08:39:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 08:39:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15123169.1240922386704.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-378:
--------------------------------

    Attachment: DNA-378.patch


Attached patch that supports this capability.  It's a bit clunky, but it does handle some fairly complex cases with nested content, multi-valued properties, etc. as in this example:

<car name="Infiniti G37">
    <maker>Infiniti</maker>
    <category>Turbocharged</category>
    <driver name="Tony Stewart" />
    <property jcr:name="model">G37</property>
    <category>My <![CDATA[Sedan]]></category>
</car>

This may allow -379 to be further deferred.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-378.patch
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 10:27:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 10:27:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-385) Documentation Updates
	for 0.4
Message-ID: <9441389.1240928866337.JavaMail.jira@cloud.prod.atl2.jboss.com>

Documentation Updates for 0.4
-----------------------------

                 Key: DNA-385
                 URL: https://jira.jboss.org/jira/browse/DNA-385
             Project: DNA
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 0.3
            Reporter: Brian Carothers
             Fix For: 0.4


We need to update all of the documentation to reflect the changes made for 0.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 10:29:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 10:29:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-385) Documentation Updates
	for 0.4
In-Reply-To: <9441389.1240928866337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29395406.1240928986354.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-385:
--------------------------------

    Attachment: DNA-385.patch


Here's my checklist from my reasonably brief review of the docs.

Getting started
1. Checked
2. Checked
3. Didn't check
4. Depends on Repository config
5. Depends on Repository config
6. Checked (I don't think this changed)
7. Could be updated	

Reference Guide
1. Checked
2. Checked
3. Needs review by someone who understands maven classloader
4. Checked
5. Needs documentation for new repository types, Table 5.4 may need to be updated with new request types
6. Checked
7. Checked
8. Skimmed
9. Depends on Repository config
10. Checked - I didn't add anything to call out the TCK test behavior
11. Checked

> Documentation Updates for 0.4
> -----------------------------
>
>                 Key: DNA-385
>                 URL: https://jira.jboss.org/jira/browse/DNA-385
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-385.patch
>
>
> We need to update all of the documentation to reflect the changes made for 0.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 11:05:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 28 Apr 2009 11:05:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-385) Documentation
	Updates for 0.4
In-Reply-To: <9441389.1240928866337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12568561.1240931146351.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464810#action_12464810 ] 

Randall Hauch commented on DNA-385:
-----------------------------------

Applied the patch that updated some of the content in the Getting Started and Reference Guide documents.  The remaining work still needs to be done.

> Documentation Updates for 0.4
> -----------------------------
>
>                 Key: DNA-385
>                 URL: https://jira.jboss.org/jira/browse/DNA-385
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-385.patch
>
>
> We need to update all of the documentation to reflect the changes made for 0.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 15:33:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 15:33:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33117661.1240947226355.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-378:
--------------------------------

    Attachment: DNA-378_redux.patch


Better patch.  This replaces the first one and cleans up a minor bug in BatchRequestBuilder.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-378.patch, DNA-378_redux.patch
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 18:26:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 18:26:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-386) AbstractJcrNode
 Javadoc Throws Clause Are Out Of Sync
In-Reply-To: <26338193.1240957486430.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19822804.1240957606343.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-386:
--------------------------------

    Attachment: DNA-386.patch


Attached patch

> AbstractJcrNode Javadoc Throws Clause Are Out Of Sync
> -----------------------------------------------------
>
>                 Key: DNA-386
>                 URL: https://jira.jboss.org/jira/browse/DNA-386
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation, JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: 0.4
>
>         Attachments: DNA-386.patch
>
>
> Some of the methods in AbstractJcrNode still have Javadoc for the UnsupportedOperationException that they used to throw.  According to a quick text search of all the places where "@throws Unsupported" occurs in dna-jcr, this is the only file with this type of erroneous Javadoc.
> I also marked off the getReferences method as it is not implemented per spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Tue Apr 28 18:24:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 28 Apr 2009 18:24:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-386) AbstractJcrNode
 Javadoc Throws Clause Are Out Of Sync
Message-ID: <26338193.1240957486430.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode Javadoc Throws Clause Are Out Of Sync
-----------------------------------------------------

                 Key: DNA-386
                 URL: https://jira.jboss.org/jira/browse/DNA-386
             Project: DNA
          Issue Type: Bug
          Components: Documentation, JCR
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Optional
             Fix For: 0.4


Some of the methods in AbstractJcrNode still have Javadoc for the UnsupportedOperationException that they used to throw.  According to a quick text search of all the places where "@throws Unsupported" occurs in dna-jcr, this is the only file with this type of erroneous Javadoc.

I also marked off the getReferences method as it is not implemented per spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 08:54:47 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 08:54:47 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-387) Federation connector
 does not
 support updates, which are required when using with the JCR implementation
Message-ID: <8703527.1241009687374.JavaMail.jira@cloud.prod.atl2.jboss.com>

Federation connector does not support updates, which are required when using with the JCR implementation
--------------------------------------------------------------------------------------------------------

                 Key: DNA-387
                 URL: https://jira.jboss.org/jira/browse/DNA-387
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Examples
    Affects Versions: 0.3
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.4


Our JCR implementation updates the "/jcr:system/dna:namespaces" and "/jcr:system/nodeTypes" areas as the namespaces and node types change, respectively.  The federation connector doesn't support updates, and using the federation connector with our JCR results in errors running the repository examples for the Getting Started guide.

These updates follow a specific and limited pattern: all of the updates are within a single projection, and in these cases the update requests can be transformed and sent down to the one connector for the projection.  This very limited scenario would go a long way, and its pretty straightforward.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 08:58:49 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 08:58:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-282) Federation connector
 improperly
 handles root-level node with one projection of a non-root node from a
 single source
In-Reply-To: <33025480.1234478264160.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9886148.1241009929870.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-282.
-------------------------------

    Resolution: Done


Corrected the connector to properly handle root-level nodes in this particular case.  The problem was in how the UUIDs were being handled.  Fixed a couple of other minor issues as well.  

Found another issue while getting the Getting Started repository examples running (see DNA-387).

> Federation connector improperly handles root-level node with one projection of a non-root node from a single source
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-282
>                 URL: https://jira.jboss.org/jira/browse/DNA-282
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>
> The federation connector currently has a problem when configured to project a non-root node from a single source into the root node of the federated repository.  The cache always has a root node with a specific UUID, and the single source's non-root node has a different UUID, so when the federation connector attempts to project that non-root node from the source into the root node of the federated repository, the cache is unable to store the node with the UUID from the source.
> This problem arose when working on DNA-281 - the test cases were changed to use the InMemory connector rather than the SimpleRepositorySource connector (used for testing only).  The simple implementation didn't maintain UUIDs, whereas the in-memory implementation does.  (This is one of the problems with using a "mock" or non-production implementation in tests.)
> So, although the code compiles, several of the federation connector's tests fail, and the problem also affects several of the JCR unit tests and the Getting Started repository example.  Therefore, after these are fixed, the corresponding projects need to be added back into the POM file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 10:11:01 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 10:11:01 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-388)
 AbstractJcrNode.getReferences() is incorrectly implemented
Message-ID: <22672318.1241014261711.JavaMail.jira@cloud.prod.atl2.jboss.com>

AbstractJcrNode.getReferences() is incorrectly implemented
----------------------------------------------------------

                 Key: DNA-388
                 URL: https://jira.jboss.org/jira/browse/DNA-388
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Randall Hauch
             Fix For: 0.5


The getReferences() call is not implemented according to spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 10:14:51 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 10:14:51 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-386) AbstractJcrNode
 Javadoc Throws Clause Are Out Of Sync
In-Reply-To: <26338193.1240957486430.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33107328.1241014491407.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-386.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Removed the "@throws UnsupportedOperationException always" line from the JavaDoc of several methods.  These lines were leftovers from when the methods were indeed not implemented.

> AbstractJcrNode Javadoc Throws Clause Are Out Of Sync
> -----------------------------------------------------
>
>                 Key: DNA-386
>                 URL: https://jira.jboss.org/jira/browse/DNA-386
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation, JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Optional
>             Fix For: 0.4
>
>         Attachments: DNA-386.patch
>
>
> Some of the methods in AbstractJcrNode still have Javadoc for the UnsupportedOperationException that they used to throw.  According to a quick text search of all the places where "@throws Unsupported" occurs in dna-jcr, this is the only file with this type of erroneous Javadoc.
> I also marked off the getReferences method as it is not implemented per spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 10:24:50 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 10:24:50 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-388)
 AbstractJcrNode.getReferences() is incorrectly implemented
In-Reply-To: <22672318.1241014261711.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9411406.1241015091361.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464984#action_12464984 ] 

Randall Hauch commented on DNA-388:
-----------------------------------

Changed the method (for 0.4) to throw an UnsupportedOperationException, since the method is not implemented correctly.  Also commented out some unit tests that were testing these methods.

> AbstractJcrNode.getReferences() is incorrectly implemented
> ----------------------------------------------------------
>
>                 Key: DNA-388
>                 URL: https://jira.jboss.org/jira/browse/DNA-388
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>             Fix For: 0.5
>
>
> The getReferences() call is not implemented according to spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 10:30:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 10:30:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-386) AbstractJcrNode
 Javadoc Throws Clause Are Out Of Sync
In-Reply-To: <26338193.1240957486430.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26636723.1241015446990.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464987#action_12464987 ] 

Randall Hauch commented on DNA-386:
-----------------------------------

The attached patch included some changes that were unrelated to this issue.  Those fragments were applied and committed under DNA-376 and DNA-388.

> AbstractJcrNode Javadoc Throws Clause Are Out Of Sync
> -----------------------------------------------------
>
>                 Key: DNA-386
>                 URL: https://jira.jboss.org/jira/browse/DNA-386
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation, JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Optional
>             Fix For: 0.4
>
>         Attachments: DNA-386.patch
>
>
> Some of the methods in AbstractJcrNode still have Javadoc for the UnsupportedOperationException that they used to throw.  According to a quick text search of all the places where "@throws Unsupported" occurs in dna-jcr, this is the only file with this type of erroneous Javadoc.
> I also marked off the getReferences method as it is not implemented per spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Wed Apr 29 10:33:47 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 29 Apr 2009 10:33:47 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-376) Add request to
 change the order
 of a child node (or nodes) relative to the other children
In-Reply-To: <21590252.1240329322777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27226225.1241015628642.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12464991#action_12464991 ] 

Randall Hauch commented on DNA-376:
-----------------------------------

Added a partial implementation of the AbstractJcrNode.orderBefore(...) method, though this partial implementation is never reached because the method still throws an UnsupportedOperationException.  This partial implementation should be completed when the Graph API has support for reordering children.

> Add request to change the order of a child node (or nodes) relative to the other children
> -----------------------------------------------------------------------------------------
>
>                 Key: DNA-376
>                 URL: https://jira.jboss.org/jira/browse/DNA-376
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.5
>
>
> The current DNA Graph model does support ordered children, and while rename can be used to change the order of same-name-siblings, there currently is no way to change the order of the child nodes.  This is required to fully implement the JCR API.
> JCR handles this functionality by provided a method that essentially changes the position of a single child node.  The "Node.orderBefore(String childNameToBeMoved, String nameOfChildAtPosition)" can be used by calling on the parent node and supplying the name (with SNS index if needed) of the child to be moved and the name of the child before which the other child is to be moved.
> This same model can be used for the graph request.  It also would allow adding in the future another optional request that would contain multiple reorders, and that could be implemented in RequestProcessor to break into multiple ReorderChildRequest instances.
> The existing (writable) connectors will all be affected, since this will be a new mandatory request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 00:33:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 00:33:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-387) Federation connector
 does not
 support updates, which are required when using with the JCR implementation
In-Reply-To: <8703527.1241009687374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6421574.1241066026673.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465135#action_12465135 ] 

Randall Hauch commented on DNA-387:
-----------------------------------

Added support for writes in limited scenarios (when the nodes being changed are within a single projection), and addressed a couple of issues related to the handling of UUIDs in the federation connector.  Added more unit tests, verifying the behavior is correct.  Also corrected a few errors in CopyBranchRequest, MoveBranchRequest, and CreateNodeRequest.  

Finally, the repository examples (from the Getting Started document) were corrected to use our JCR implementation.  This allowed the parent POM to again include these examples as subprojects.

> Federation connector does not support updates, which are required when using with the JCR implementation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-387
>                 URL: https://jira.jboss.org/jira/browse/DNA-387
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Examples
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>
> Our JCR implementation updates the "/jcr:system/dna:namespaces" and "/jcr:system/nodeTypes" areas as the namespaces and node types change, respectively.  The federation connector doesn't support updates, and using the federation connector with our JCR results in errors running the repository examples for the Getting Started guide.
> These updates follow a specific and limited pattern: all of the updates are within a single projection, and in these cases the update requests can be transformed and sent down to the one connector for the projection.  This very limited scenario would go a long way, and its pretty straightforward.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 00:33:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 00:33:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-387) Federation connector
 does not
 support updates, which are required when using with the JCR implementation
In-Reply-To: <8703527.1241009687374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23566495.1241066026718.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-387.
-------------------------------

    Resolution: Done


This issue appears to be resolved, therefore marking as such.

> Federation connector does not support updates, which are required when using with the JCR implementation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-387
>                 URL: https://jira.jboss.org/jira/browse/DNA-387
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Examples
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>
> Our JCR implementation updates the "/jcr:system/dna:namespaces" and "/jcr:system/nodeTypes" areas as the namespaces and node types change, respectively.  The federation connector doesn't support updates, and using the federation connector with our JCR results in errors running the repository examples for the Getting Started guide.
> These updates follow a specific and limited pattern: all of the updates are within a single projection, and in these cases the update requests can be transformed and sent down to the one connector for the projection.  This very limited scenario would go a long way, and its pretty straightforward.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 07:44:02 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 30 Apr 2009 07:44:02 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-105) Sequence content
 from delimited text files
In-Reply-To: <25062773.1212612560463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26513250.1241091842644.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465180#action_12465180 ] 

Brian Carothers commented on DNA-105:
-------------------------------------

Would it be best to sequence the entire file (which could easily contain multiple megabytes of data) or just a sample (perhaps the first N rows)?

> Sequence content from delimited text files
> ------------------------------------------
>
>                 Key: DNA-105
>                 URL: https://jira.jboss.org/jira/browse/DNA-105
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Greg Haber
>            Priority: Minor
>
> It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file.  A sequencer to capture this metadata could be useful,and should be straightforward to implement.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 07:48:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 30 Apr 2009 07:48:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-388)
 AbstractJcrNode.getReferences() is incorrectly implemented
In-Reply-To: <22672318.1241014261711.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15815632.1241092126381.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465181#action_12465181 ] 

Brian Carothers commented on DNA-388:
-------------------------------------

I think that this is a duplicate of DNA-367.

> AbstractJcrNode.getReferences() is incorrectly implemented
> ----------------------------------------------------------
>
>                 Key: DNA-388
>                 URL: https://jira.jboss.org/jira/browse/DNA-388
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>            Reporter: Randall Hauch
>             Fix For: 0.5
>
>
> The getReferences() call is not implemented according to spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 11:32:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 11:32:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21838696.1241105566893.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465239#action_12465239 ] 

Randall Hauch commented on DNA-58:
----------------------------------

Refactored the DnaConfiguration class to use more interfaces and to move those interfaces (and reusable implementations) into a Configurator class that uses generics.  DnaConfiguration instantiates a configurator, but also implements some of the high-level interfaces by delegating them to the wrapped configurator instance.  This allows DnaConfiguration to appear to be doing the configurating, but in reality it is the wrapped builder that is doing it.  Also, DnaConfiguration (or other components) can choose which "aspects" of configuration it is to expose by inheriting controlling which higher-level interfaces are implemented.  Since delegation is used, this works very well.

This is a more complicated design, but it is far more extensible and reusable.  A JcrConfiguration class was also created that works in the same way as DnaConfiguration, except that it uses a different type parameter (so all the interfaces return JcrConfiguration).  It thus gets to reuse all of the Configurator logic.  However, JcrConfiguration doesn't implement all of the "aspects", essentially hiding certain services (e.g., sequencers, since they don't yet work with our implementation).

This change also made a few minor corrections to the JavaDoc and visibility modifiers on the classes in the 'org.jboss.dna.jcr' package.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 12:17:47 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 12:17:47 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31011286.1241108267375.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-378.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Marking as resolved, since the feature was implemented.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-378.patch, DNA-378_redux.patch, DNA-378_round_3.patch
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 14:19:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 14:19:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-277) Fix all text files
 in source code to have consistent line feeds
In-Reply-To: <21710954.1232404263947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5776466.1241115586359.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465281#action_12465281 ] 

Randall Hauch commented on DNA-277:
-----------------------------------

Used Eclipse to convert line endings to Unix, which removes the CR and forces all files to have a LF line terminator.  Also added a README_COMMITTERS.txt file that specifies what should be added to a developer's subversion configuration to ensure files are always uploaded with the correct terminators.

> Fix all text files in source code to have consistent line feeds
> ---------------------------------------------------------------
>
>                 Key: DNA-277
>                 URL: https://jira.jboss.org/jira/browse/DNA-277
>             Project: DNA
>          Issue Type: Task
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Johnny Verhaeg
>            Priority: Minor
>             Fix For: 0.4
>
>
> Currently, all of the text files in our source code have a mixture of carriage returns and line feeds.  And, our DNA preferences (for Eclipse) did not specify any special handling, so each developer's settings were used (and likely were the default settings for the platform).  Regardless of the preference settings, however, Eclipse editors always keep the line termination characters used in each particular file, so if a file was created on Windows, it will have \r\n for all lines, even when that file is modified on Linux or OS X.  There are a few cases where a file seems to have a mixture of line terminations.
> We should probably have a consistent line terminator in all files, and that terminator should probably be '\n', which is the line terminator on *nix, for a couple of reasons.  First, the JBoss.org SVN repository is hosted on Linux, and being consistent probably helps somewhat.  Second, some tools (including Git) rely upon the '\n' character for determining line feeds, so that rules out the Mac style line feeds ('\r').  Third, there really is no need to store multiple characters.
> We need to verify that the converting all files to use Unix line terminators is acceptable.  If so, we need to convert all of the files (that need it), update the Eclipse preferences, and have all developers make sure their Eclipse preference settings are correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 11:36:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 11:36:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-389) Change Getting Started
 examples to use the DnaConfiguration and JcrConfiguration components
Message-ID: <5837059.1241105806747.JavaMail.jira@cloud.prod.atl2.jboss.com>

Change Getting Started examples to use the DnaConfiguration and JcrConfiguration components
-------------------------------------------------------------------------------------------

                 Key: DNA-389
                 URL: https://jira.jboss.org/jira/browse/DNA-389
             Project: DNA
          Issue Type: Task
          Components: Documentation, Examples
            Reporter: Randall Hauch
             Fix For: 0.5


The DnaConfiguration and JcrConfiguration components were created previously (see DNA-58), but the Getting Started examples and document (and Reference Guide document) need to be changed to use them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 14:15:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 14:15:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-277) Fix all text files
 in source code to have consistent line feeds
In-Reply-To: <21710954.1232404263947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11656036.1241115346445.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465280#action_12465280 ] 

Randall Hauch commented on DNA-277:
-----------------------------------

The following command will list the files that have the incorrect line ending:

find . -name \*.java -or -name \*.xml -or -name \*.txt -or -name \*.xsd | xargs file | grep ' line terminators' | cut -d":" -f1

> Fix all text files in source code to have consistent line feeds
> ---------------------------------------------------------------
>
>                 Key: DNA-277
>                 URL: https://jira.jboss.org/jira/browse/DNA-277
>             Project: DNA
>          Issue Type: Task
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Johnny Verhaeg
>            Priority: Minor
>             Fix For: 0.4
>
>
> Currently, all of the text files in our source code have a mixture of carriage returns and line feeds.  And, our DNA preferences (for Eclipse) did not specify any special handling, so each developer's settings were used (and likely were the default settings for the platform).  Regardless of the preference settings, however, Eclipse editors always keep the line termination characters used in each particular file, so if a file was created on Windows, it will have \r\n for all lines, even when that file is modified on Linux or OS X.  There are a few cases where a file seems to have a mixture of line terminations.
> We should probably have a consistent line terminator in all files, and that terminator should probably be '\n', which is the line terminator on *nix, for a couple of reasons.  First, the JBoss.org SVN repository is hosted on Linux, and being consistent probably helps somewhat.  Second, some tools (including Git) rely upon the '\n' character for determining line feeds, so that rules out the Mac style line feeds ('\r').  Third, there really is no need to store multiple characters.
> We need to verify that the converting all files to use Unix line terminators is acceptable.  If so, we need to convert all of the files (that need it), update the Eclipse preferences, and have all developers make sure their Eclipse preference settings are correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 14:19:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 14:19:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-277) Fix all text files in
 source code to have consistent line feeds
In-Reply-To: <21710954.1232404263947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6117422.1241115586398.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-277.
-------------------------------

    Resolution: Done


Marking as resolved, since this should be done.

> Fix all text files in source code to have consistent line feeds
> ---------------------------------------------------------------
>
>                 Key: DNA-277
>                 URL: https://jira.jboss.org/jira/browse/DNA-277
>             Project: DNA
>          Issue Type: Task
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Johnny Verhaeg
>            Priority: Minor
>             Fix For: 0.4
>
>
> Currently, all of the text files in our source code have a mixture of carriage returns and line feeds.  And, our DNA preferences (for Eclipse) did not specify any special handling, so each developer's settings were used (and likely were the default settings for the platform).  Regardless of the preference settings, however, Eclipse editors always keep the line termination characters used in each particular file, so if a file was created on Windows, it will have \r\n for all lines, even when that file is modified on Linux or OS X.  There are a few cases where a file seems to have a mixture of line terminations.
> We should probably have a consistent line terminator in all files, and that terminator should probably be '\n', which is the line terminator on *nix, for a couple of reasons.  First, the JBoss.org SVN repository is hosted on Linux, and being consistent probably helps somewhat.  Second, some tools (including Git) rely upon the '\n' character for determining line feeds, so that rules out the Mac style line feeds ('\r').  Third, there really is no need to store multiple characters.
> We need to verify that the converting all files to use Unix line terminators is acceptable.  If so, we need to convert all of the files (that need it), update the Eclipse preferences, and have all developers make sure their Eclipse preference settings are correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 18:12:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 18:12:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-385) Documentation
	Updates for 0.4
In-Reply-To: <9441389.1240928866337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4800520.1241129566355.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465308#action_12465308 ] 

Randall Hauch commented on DNA-385:
-----------------------------------

Reviewed and edited both documents to bring everything up to the current state of the code.  Most parts were still accurate, but there were a number of places there were minor changes and quite a few sections that needed more work.

Pending errors or other changes/suggestions, the docs are complete and accurate for this release.

> Documentation Updates for 0.4
> -----------------------------
>
>                 Key: DNA-385
>                 URL: https://jira.jboss.org/jira/browse/DNA-385
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-385.patch
>
>
> We need to update all of the documentation to reflect the changes made for 0.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 19:53:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 30 Apr 2009 19:53:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-385) Documentation Updates
	for 0.4
In-Reply-To: <9441389.1240928866337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17222358.1241135626349.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-385:
--------------------------------

    Attachment: DNA-385_review.patch


I reviewed all of the changes from r870 (but did not try to run the code samples).  I only came up with some minor wordsmithing, as noted in the attached patch DNA-385_review.patch.

> Documentation Updates for 0.4
> -----------------------------
>
>                 Key: DNA-385
>                 URL: https://jira.jboss.org/jira/browse/DNA-385
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.4
>
>         Attachments: DNA-385.patch, DNA-385_review.patch
>
>
> We need to update all of the documentation to reflect the changes made for 0.4.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 13:33:59 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 30 Apr 2009 13:33:59 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-390) BatchRequestBuilder
 Property/Create Folding Behavior
Message-ID: <28485819.1241112839899.JavaMail.jira@cloud.prod.atl2.jboss.com>

BatchRequestBuilder Property/Create Folding Behavior
----------------------------------------------------

                 Key: DNA-390
                 URL: https://jira.jboss.org/jira/browse/DNA-390
             Project: DNA
          Issue Type: Feature Request
          Components: API, Graph
    Affects Versions: 0.3
            Reporter: Brian Carothers
            Priority: Minor


BatchRequestBuilder currently attempts to consolidate multiple set property and create calls for the same node into a single set property or create statement.  The consolidation process does not seem to respect SNS though.

For example:

1. Create a node at /a/b
2. Set some properties on the node at location /a/b
3. Create another node at /a/b (same-name sibling)
4. Set some other properties on the node at location /a/b 

The consolidation process sets the properties from step 4 onto the node created at step 1.  This overwrites the properties from step 2 where the property names are the same.

There are a few workarounds in place right now.  One is to just consolidate the requests yourself prior to invoking the Graph API and adding commands to the batch.  It is possible that using the Path-based variants of the create node and set property commands would also work around this problem if the SNS indices were set correctly on the paths.  I've not tried this approach I think it would be fairly cumbersome and fragile as it would require the caller to track whether there are already any nodes with the same name at the same location and offset SNS indices accordingly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 11:36:46 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 11:36:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-58) Create repository
 configuration and component
In-Reply-To: <10425152.1208876804469.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7316478.1241105806803.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-58.
------------------------------

    Resolution: Done


Marking as resolved.  Another issue (DNA-389) was created to deal with using this configuration mechanism in the examples.

> Create repository configuration and component
> ---------------------------------------------
>
>                 Key: DNA-58
>                 URL: https://jira.jboss.org/jira/browse/DNA-58
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors, Federation, Sequencers
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.4
>
>         Attachments: DNA-58_builder_engine.patch, DNA-58_component_properties.patch
>
>
> There needs to be a configuration object that wraps the sequencing and repository services and makes working with DNA repositories easier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 12:16:19 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 30 Apr 2009 12:16:19 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13006040.1241108179285.JavaMail.jira@cloud.prod.atl2.jboss.com>


    [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12465251#action_12465251 ] 

Randall Hauch commented on DNA-378:
-----------------------------------

Applied the patch, which adds support for multi-valued properties as child elements (intermixed with child elements for nodes).

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-378.patch, DNA-378_redux.patch, DNA-378_round_3.patch
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


From jira-events at lists.jboss.org  Thu Apr 30 10:21:46 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 30 Apr 2009 10:21:46 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-378) XML Graph Importer
 should support importing multi-valued properties
In-Reply-To: <26267936.1240499861049.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32602826.1241101306434.JavaMail.jira@cloud.prod.atl2.jboss.com>


     [ https://jira.jboss.org/jira/browse/DNA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-378:
--------------------------------

    Attachment: DNA-378_round_3.patch


Added a new patch that replaces prior patches and fixes a few regressions that they opened up.

> XML Graph Importer should support importing multi-valued properties 
> --------------------------------------------------------------------
>
>                 Key: DNA-378
>                 URL: https://jira.jboss.org/jira/browse/DNA-378
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>            Reporter: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-378.patch, DNA-378_redux.patch, DNA-378_round_3.patch
>
>
> The XML handler used in the Graph importer (that is, org.jboss.dna.graph.xml.XmlHandler) does not currently support producing multi-valued properties.  This is a fairly substantial limitation.
> The current XML handler simply maps an XML element to a graph node and an XML attribute to a property.  There is no such thing as multi-valued XML attributes, so another mapping has to be used for multi-valued properties.  Since a graph node does not directly hold any values (rather, it holds properties that have the values), and the XML handler currently ignores all XML character content (e.g., <element>this is character content</element>), it is fairly logical to conclude that a child XML element with character content should be mapped to a property.  If there is a "jcr:name" attribute, then this attribute's value would be used to determine the property name (meaning the element's name could be anything); otherwise, the child element's name would be the property name.
> This would also address the shortcoming of XML attribute values not being able to (easily) have any character content, since such property values could be placed in a child element.
> Here's an example:
> <cars>
>   <car jcr:name="Mini">
>     <jcr:description>This is a description that would be stored as a property on the 'Mini' node</jcr:description>
>     <property jcr:name="summary">This is the value of the 'summary' property on the 'Mini' node</property>
>   </car>
> </cars>
> I'm not sure how easy it is to change the XmlHandler to behave this way, since under certain situations it may require postponing the creation of a node since it is unknown when processing a "startElement" method that the element has character content.  However, I believe that it is worth any additional complexity to make the XML more intuitive and natural.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


