From jira-events at lists.jboss.org  Fri Oct  2 08:24:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:24:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-322) Create context menu
 and menu bar items tied to publishing actions
In-Reply-To: <24871012.1237395622388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <395945786.1254486289160.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-322.
-----------------------------

    Resolution: Done


A "DNA" context menu appears in the context menu for all IResources. The context menu includes items to publish, unpublish, and view published locations of the selected resources.

> Create context menu and menu bar items tied to publishing actions
> -----------------------------------------------------------------
>
>                 Key: DNA-322
>                 URL: https://jira.jboss.org/jira/browse/DNA-322
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The context menu items would at a minimum appear in context menus for views representing content in a workspace

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 08:28:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:28:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-321) Create
	publishing-related actions
In-Reply-To: <5477247.1237395503468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1809934724.1254486529153.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-321.
-----------------------------

    Resolution: Done


The publish and unpublish actions use Eclipse's Job framework so they can be run in the background. There is also an action that shows the DNA repositories the selected file has been published to.

> Create publishing-related actions
> ---------------------------------
>
>                 Key: DNA-321
>                 URL: https://jira.jboss.org/jira/browse/DNA-321
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Minimally to publish (tied to HTTP PUT action) and un-publish (tied to HTTP DELETE) files or folders.  Should also action for retrieving what has been published to repository, but to be complete this will require an additional task that provides a view for browsing the results.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 08:36:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:36:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-320) Create connection
	management view
In-Reply-To: <16194240.1237395160384.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <212953021.1254487009284.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-320.
-----------------------------

    Resolution: Done


The "DNA Servers" view contains a tree that has DNA Servers as it's roots. Under a server, the existing repositories for that server are listed. And under each repository the workspaces are listed. A user can add, delete, and edit this server registry. If a connection to a server cannot be established that server tree node is decorated with an error overlay image. There is a also a "Reconnect" action that will refresh the selected server's children. The server registry is persisted from session to session. The dialog that allows users to create and edit a server includes URL, user, password, save password flag, and a way to test the connection.

> Create connection management view
> ---------------------------------
>
>                 Key: DNA-320
>                 URL: https://jira.jboss.org/jira/browse/DNA-320
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> To create and maintain connections to one or more repositories deployed in a container

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 08:42:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:42:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-319) Create plug-in
	project in SVN
In-Reply-To: <26330711.1237394963598.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1304734169.1254487369212.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-319.
-----------------------------

    Resolution: Done


Two projects were created: (1) an Eclipse plugin project for the UI and (2) a Maven business logic project. These projects have been moved from the "eclipse" branch to "trunk." The Eclipse plugin includes Eclipse extensions for the views, the preference page, the help documentation, the context menu, the actions, and the decorator. The Maven business logic project includes the JCR-related objects, the server registry and management, and the JSON-related objects that communicate with the DNA REST server.

> Create plug-in project in SVN
> -----------------------------
>
>                 Key: DNA-319
>                 URL: https://jira.jboss.org/jira/browse/DNA-319
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Unlike other DNA projects, this project will be built using an Eclipse IDE or Ant tasks, and not using Maven, unless we can figure out some way to maintain the Eclipse manifest, build.properties, plugin.xml, etc. in the Maven world.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 08:50:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:50:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-327) Create feature
In-Reply-To: <13711834.1237397141278.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <612794663.1254487849227.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-327.
-----------------------------

    Resolution: Done


The Eclipse feature plugin has been created and now resides on trunk. The only plugin required by this feature is the DNA Eclipse plugin.

> Create feature
> --------------
>
>                 Key: DNA-327
>                 URL: https://jira.jboss.org/jira/browse/DNA-327
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> including about dialog icons and settings, 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  Fri Oct  2 08:54:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 08:54:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-328) Create update site
In-Reply-To: <15378134.1237397362425.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2009589084.1254488089194.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-328.
-----------------------------

    Resolution: Done


The Eclipse update site plugin has been created and is now on trunk. One or more additional Jiras will be written to address building the update site web page, uploading the update site archive, and instructions on how to build the archive.

> Create update site
> ------------------
>
>                 Key: DNA-328
>                 URL: https://jira.jboss.org/jira/browse/DNA-328
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Include update site URL on project site

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 09:04:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 09:04:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-326) Create documentation
In-Reply-To: <13759744.1237396882299.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <714889285.1254488689194.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-326.
-----------------------------

    Resolution: Done


Help documentation is done. There are help pages for the DNA Servers view, DNA Message Console, all the dialogs and wizard pages, the preference page, and the IResource context menu. The Welcome page contributions are still to be done and will be written up in a new Jira.

> Create documentation
> --------------------
>
>                 Key: DNA-326
>                 URL: https://jira.jboss.org/jira/browse/DNA-326
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Documentation, Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.7
>
>
> - Feature welcome page
> - Links from Eclipse welcome page
> - Normal User's guide/Help docs
> - Links from dialog "question mark" icon
> - Links from dialog "light-bulbs" (optional)
> - Cheatsheets (optional)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 09:39:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 09:39:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-531) Servers View Should
 Provide Global Action Handlers
Message-ID: <1361211738.1254490789527.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Servers View Should Provide Global Action Handlers
--------------------------------------------------

                 Key: DNA-531
                 URL: https://jira.jboss.org/jira/browse/DNA-531
             Project: DNA
          Issue Type: Bug
          Components: Views
    Affects Versions: 0.6
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


DNA Servers View needs to set action handlers for the global actions of cut, copy, paste, and delete. Currently when this view is in focus and the main menu cut, copy, and paste items are selected an exception is thrown. Selected the delete menu item does not throw an exception but doesn't do anything. The delete key should run the delete server action and the cut, copy, and paste actions should never be enabled (or at the very least do nothing). The Delete Key should also run the delete server action.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 10:04:50 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 10:04:50 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-532) Delete IHttpConnection
 Interface Since There Is Only One Implementation That Works Correctly
Message-ID: <1096240278.1254492290004.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Delete IHttpConnection Interface Since There Is Only One Implementation That Works Correctly
--------------------------------------------------------------------------------------------

                 Key: DNA-532
                 URL: https://jira.jboss.org/jira/browse/DNA-532
             Project: DNA
          Issue Type: Task
          Components: Views
    Affects Versions: 0.6
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


There are 2 implementations of IHttpConnection: (1) Apache's HttpClient and (2) java.net.Authenticator. There are problems with the java.net.Authenticator version as other Eclipse plugins could also use this framework and overwrite our Authenticator. This is because the java.net framework only allows one, static Authenticator. Get rid of the interface and the java.net 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  Fri Oct  2 10:23:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 10:23:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-533) Decorator Does Not
 Add/Remove Overaly Image Immediately After The Publishing Operation
Message-ID: <1756051350.1254493429127.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Decorator Does Not Add/Remove Overaly Image Immediately After The Publishing Operation
--------------------------------------------------------------------------------------

                 Key: DNA-533
                 URL: https://jira.jboss.org/jira/browse/DNA-533
             Project: DNA
          Issue Type: Bug
          Components: Views
    Affects Versions: 0.6
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


After publishing a file that file's icon should have an overlay image signifying it was published. After unpublishing that file that overlay should be removed. In order to make this happen you must refresh the file or a parent folder after the publishing operation. This should occur right after the publishing operation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 10:41:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 10:41:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-534) Contribute To Eclipse
 Welcome Page Framework
Message-ID: <1947928757.1254494509341.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Contribute To Eclipse Welcome Page Framework
--------------------------------------------

                 Key: DNA-534
                 URL: https://jira.jboss.org/jira/browse/DNA-534
             Project: DNA
          Issue Type: Task
          Components: Views
    Affects Versions: 0.6
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


The Eclipse Welcome Page framework includes extension points for overview, tutorials, what's new, samples, and maybe a few others. At a minimum we need to contribute to the overview.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 11:04:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 11:04:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-535) A Synchronize Action
 Is Needed To Make Sure Workspace Resource Publishing State Agrees With The
 DNA Repositories
Message-ID: <676958315.1254495889266.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

A Synchronize Action Is Needed To Make Sure Workspace Resource Publishing State Agrees With The DNA Repositories
----------------------------------------------------------------------------------------------------------------

                 Key: DNA-535
                 URL: https://jira.jboss.org/jira/browse/DNA-535
             Project: DNA
          Issue Type: Task
          Components: Views
    Affects Versions: 0.6
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


A synchronize action should be added to the context menu. For each file in the workspace, this action will make sure the resource's "publishedLocations" property is set to the right value based on the registered and connected servers. This property value is a list of DNA servers that this resource has been published to.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 13:24:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 13:24:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-531) Servers View Should
 Provide Global Action Handlers
In-Reply-To: <1361211738.1254490789527.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1992038999.1254504289226.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-531.
-----------------------------

    Resolution: Done


Hooked up the global cut, copy, and paste actions to always be disabled when the DNA Servers view is in focus. Hooked the global delete action to run the delete server action. The delete key now also runs the delete server action.

> Servers View Should Provide Global Action Handlers
> --------------------------------------------------
>
>                 Key: DNA-531
>                 URL: https://jira.jboss.org/jira/browse/DNA-531
>             Project: DNA
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> DNA Servers View needs to set action handlers for the global actions of cut, copy, paste, and delete. Currently when this view is in focus and the main menu cut, copy, and paste items are selected an exception is thrown. Selected the delete menu item does not throw an exception but doesn't do anything. The delete key should run the delete server action and the cut, copy, and paste actions should never be enabled (or at the very least do nothing). The Delete Key should also run the delete server action.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 13:28:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 13:28:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-532) Delete
 IHttpConnection Interface Since There Is Only One Implementation That Works
 Correctly
In-Reply-To: <1096240278.1254492290004.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1625625807.1254504529797.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-532.
-----------------------------

    Resolution: Done


Deleted IHttpConnection interface and the HttpUrlConnection (the java.net.Authenticator implementation. The Apache HttpClient is the one and only way we do HTTP authentication now.

> Delete IHttpConnection Interface Since There Is Only One Implementation That Works Correctly
> --------------------------------------------------------------------------------------------
>
>                 Key: DNA-532
>                 URL: https://jira.jboss.org/jira/browse/DNA-532
>             Project: DNA
>          Issue Type: Task
>          Components: Views
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> There are 2 implementations of IHttpConnection: (1) Apache's HttpClient and (2) java.net.Authenticator. There are problems with the java.net.Authenticator version as other Eclipse plugins could also use this framework and overwrite our Authenticator. This is because the java.net framework only allows one, static Authenticator. Get rid of the interface and the java.net 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  Fri Oct  2 16:02:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 16:02:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-324) Create
 publishing-related decorators that can be attached to workspace-related
 views
In-Reply-To: <19751728.1237396222571.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1666639379.1254513769161.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-324.
-----------------------------

    Resolution: Done
      Assignee: Dan Florian


There is now a decoration that is used to decorate a file that has been published. When a file is no longer published to any server the decoration goes away.

Another decoration for a server when a connection to it can't be established.

> Create publishing-related decorators that can be attached to workspace-related views
> ------------------------------------------------------------------------------------
>
>                 Key: DNA-324
>                 URL: https://jira.jboss.org/jira/browse/DNA-324
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> We may want to model our approach after SCM repository plug-ins, while making sure we don't conflict with those plug-ins or "over-decorate".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  2 16:24:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 16:24:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-325) Create preference
 page for working with DNA
In-Reply-To: <9917150.1237396702286.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <813437884.1254515089329.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-325.
-----------------------------

    Resolution: Done
      Assignee: Dan Florian


A preference page has been created. Currently there are 2 preferences: (1) a list of file extensions that determine which files will be filtered out of publishing operations, and (2) a list of folder names whose contents will be filtered out of publishing operations.

As additional preferences are need they should be written up in their own issue.

> Create preference page for working with DNA
> -------------------------------------------
>
>                 Key: DNA-325
>                 URL: https://jira.jboss.org/jira/browse/DNA-325
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Page would include ability to modify decorators, logging levels, 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  Fri Oct  2 16:41:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 2 Oct 2009 16:41:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-323) Create view of
 artifacts published in repositories
In-Reply-To: <31794775.1237395982713.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <831737112.1254516109242.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian updated DNA-323:
----------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
      Description: 
View should allow for multiple repositories, be activated via context menu and menu bar items that reside next to publishing-related actions, and should show mapping to associated workspace items.

For each registered DNA server, the DNA Servers View shows the repositories found on that server. For each repository the view shows workspaces. The view should also show folders and files that have been published to each workspace. Also the view could allow unpublishing of files via a context menu.

  was:View should allow for multiple repositories, be activated via context menu and menu bar items that reside next to publishing-related actions, and should show mapping to associated workspace items.

         Assignee: Dan Florian


> Create view of artifacts published in repositories
> --------------------------------------------------
>
>                 Key: DNA-323
>                 URL: https://jira.jboss.org/jira/browse/DNA-323
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 1.0
>
>
> View should allow for multiple repositories, be activated via context menu and menu bar items that reside next to publishing-related actions, and should show mapping to associated workspace items.
> For each registered DNA server, the DNA Servers View shows the repositories found on that server. For each repository the view shows workspaces. The view should also show folders and files that have been published to each workspace. Also the view could allow unpublishing of files via a context menu.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  3 00:08:01 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 3 Oct 2009 00:08:01 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-467) Add search/query
 support to the graph API
In-Reply-To: <27219418.1245358316391.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1057396011.1254542881149.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-467:
-----------------------------------

Added a lot more implementation and unit tests behind the XPath parser, the XPath AST objects, and the translator that converts an XPath AST into a SQL query model. Found and fixed a number of issues in several of the 'dna-graph' classes, including some tweaks to the SQL query odel, the SQL parser, minor improvements to the JodaDateTime class, and some changes to the exception handling in the 'dna-graph' query model and builder.

At this point, the XPath support is pretty good, though still not complete.  It may be good enough to use for a while - until we have more examples.  The unit tests are verifying not only that the XPath expressions can be parsed, but that they're also converted correctly to an expected SQL representation.

The XPath functionality has not yet been integrated into the JCR implementation, since that requires hooking up the LuceneQueryEngine (which still needs some work).  However, I plan to start putting more of the pieces together and focusing on wrapping up the LuceneQueryEngine (which isn't as finished as I thought).

> Add search/query support to the graph API
> -----------------------------------------
>
>                 Key: DNA-467
>                 URL: https://jira.jboss.org/jira/browse/DNA-467
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Connectors, Graph
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The graph system needs to be able to push a search/query down to a connector, and we need to develop a query model (in the form of concrete classes, probably immutable).  Connectors can optionally support queries, and if they do they will process the query and return the results.
> Particular language bindings would be put on top of this query model.  For example, JCR 1.0 defines an XPath language.  Support for each language would parse a query in that language and produce a query model.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  3 00:09:49 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 3 Oct 2009 00:09:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-467) Add search/query
 support to the graph API
In-Reply-To: <27219418.1245358316391.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1786672272.1254542989135.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-467:
------------------------------

    Complexity: High  (was: Medium)


> Add search/query support to the graph API
> -----------------------------------------
>
>                 Key: DNA-467
>                 URL: https://jira.jboss.org/jira/browse/DNA-467
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Connectors, Graph
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The graph system needs to be able to push a search/query down to a connector, and we need to develop a query model (in the form of concrete classes, probably immutable).  Connectors can optionally support queries, and if they do they will process the query and return the results.
> Particular language bindings would be put on top of this query model.  For example, JCR 1.0 defines an XPath language.  Support for each language would parse a query in that language and produce a query model.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  5 11:24:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 5 Oct 2009 11:24:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-535) A Synchronize Action
 Is Needed To Make Sure Workspace Resource Publishing State Agrees With The
 DNA Repositories
In-Reply-To: <676958315.1254495889266.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1343762640.1254756289165.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian updated DNA-535:
----------------------------

    Priority: Minor  (was: Major)


Lowering priority as this is not a required to be in the next release but would be nice if it could get in.

> A Synchronize Action Is Needed To Make Sure Workspace Resource Publishing State Agrees With The DNA Repositories
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-535
>                 URL: https://jira.jboss.org/jira/browse/DNA-535
>             Project: DNA
>          Issue Type: Task
>          Components: Views
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>            Priority: Minor
>             Fix For: 0.7
>
>
> A synchronize action should be added to the context menu. For each file in the workspace, this action will make sure the resource's "publishedLocations" property is set to the right value based on the registered and connected servers. This property value is a list of DNA servers that this resource has been published to.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  5 11:24:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 5 Oct 2009 11:24:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-534) Contribute To Eclipse
 Welcome Page Framework
In-Reply-To: <1947928757.1254494509341.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <535885921.1254756289277.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian updated DNA-534:
----------------------------

    Priority: Minor  (was: Major)


Lowering priority as this is not a required to be in the next release but would be nice if it could get in.

> Contribute To Eclipse Welcome Page Framework
> --------------------------------------------
>
>                 Key: DNA-534
>                 URL: https://jira.jboss.org/jira/browse/DNA-534
>             Project: DNA
>          Issue Type: Task
>          Components: Views
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>            Priority: Minor
>             Fix For: 0.7
>
>
> The Eclipse Welcome Page framework includes extension points for overview, tutorials, what's new, samples, and maybe a few others. At a minimum we need to contribute to the overview.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  5 11:32:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 5 Oct 2009 11:32:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-536) Develop Update Site
	Website
Message-ID: <717460463.1254756769197.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Develop Update Site Website
---------------------------

                 Key: DNA-536
                 URL: https://jira.jboss.org/jira/browse/DNA-536
             Project: DNA
          Issue Type: Task
          Components: Views
    Affects Versions: 0.7
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


Develop web page where the update site archive can be downloaded from. Include instructions on how to use Eclipse's Update Manager to install the archive. Also include brief  instructions on how to use the feature. Might be nice to include instructions on (1) how to get JBoss running with the DNA REST server. Also might be nice to include instructions on how to build the archive using a development environment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  5 11:38:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 5 Oct 2009 11:38:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-537) Update Reference Guide
 To Include Instructions On Developing/Building/Testing/Releasing The
 Eclipse Plugin
Message-ID: <910841711.1254757129152.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Update Reference Guide To Include Instructions On Developing/Building/Testing/Releasing The Eclipse Plugin
----------------------------------------------------------------------------------------------------------

                 Key: DNA-537
                 URL: https://jira.jboss.org/jira/browse/DNA-537
             Project: DNA
          Issue Type: Task
          Components: Views
    Affects Versions: 0.7
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


Reference Guide needs to be updated to include instructions on developing, testing, building, using, and releasing the Eclipse DNA publishing feature.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  5 11:43:49 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 5 Oct 2009 11:43:49 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-538) Duplicate Error
 Messages Generated When A Connection To A Server Cannot Be Established
Message-ID: <494878869.1254757429357.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Duplicate Error Messages Generated When A Connection To A Server Cannot Be Established
--------------------------------------------------------------------------------------

                 Key: DNA-538
                 URL: https://jira.jboss.org/jira/browse/DNA-538
             Project: DNA
          Issue Type: Bug
          Components: Views
    Affects Versions: 0.7
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


Duplicate error messages are being generated by the SWT Tree widget used by the DNA Servers View when a Server is offline or who has invalid connection properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  7 12:56:06 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Wed, 7 Oct 2009 12:56:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-533) Decorator Does Not
 Add/Remove Overaly Image Immediately After The Publishing Operation
In-Reply-To: <1756051350.1254493429127.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1899590007.1254934566371.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-533.
-----------------------------

    Resolution: Done


The problem was there were some unimplemented interface methods that were not deleted when a super class was chosen for DnaContentProvider. Now the listeners of the label change event get registered and notified of the event and the decorator is getting called.

> Decorator Does Not Add/Remove Overaly Image Immediately After The Publishing Operation
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-533
>                 URL: https://jira.jboss.org/jira/browse/DNA-533
>             Project: DNA
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> After publishing a file that file's icon should have an overlay image signifying it was published. After unpublishing that file that overlay should be removed. In order to make this happen you must refresh the file or a parent folder after the publishing operation. This should occur right after the publishing operation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  7 13:00:06 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Wed, 7 Oct 2009 13:00:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-538) Duplicate Error
 Messages Generated When A Connection To A Server Cannot Be Established
In-Reply-To: <494878869.1254757429357.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1860939192.1254934806105.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-538.
-----------------------------

    Resolution: Done


The DnaContentProvider was changed to not try and connect to a server if it had recently (within 10 seconds)  tried to connect to the same server and failed. The decorator and content provider of this class both are doing this now.

> Duplicate Error Messages Generated When A Connection To A Server Cannot Be Established
> --------------------------------------------------------------------------------------
>
>                 Key: DNA-538
>                 URL: https://jira.jboss.org/jira/browse/DNA-538
>             Project: DNA
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Duplicate error messages are being generated by the SWT Tree widget used by the DNA Servers View when a Server is offline or who has invalid connection properties.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct  9 13:37:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 9 Oct 2009 13:37:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-539)
 AbstractJcrNode.location.getUuid() Returns Null for Referenceable Nodes
Message-ID: <30695825.1255109825911.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

AbstractJcrNode.location.getUuid() Returns Null for Referenceable Nodes
-----------------------------------------------------------------------

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


For non-referenceable nodes, AbstractJcrNode.location.getUuid() returns the node's UUID if the node has a UUID (which is really a function of which connector the node maps to).  For referenceable nodes, AbstractJcrNode.location.getUuid() returns null but AbstractJcrNode.location.getIdProperty(JcrLexicon.UUID) returns a non-null value.

Put another way:
AbstractJcrNode.location has dna:uuid but not jcr:uuid if the node is not referenceable.
AbstractJcrNode.location has jcr:uuid but not dna:uuid if the node is referenceable

This means that the only safe way to get the corresponding UUID for a node (if one exists) is to run a code snippet like this:

        if (location.getUuid() != null) return location.getUuid();

        org.jboss.dna.graph.property.Property uuidProp = location.getIdProperty(JcrLexicon.UUID);
        if (uuidProp == null) return null;

        return this.cache.factories().getUuidFactory().create(uuidProp.getFirstValue());

It would be nice if referenceable nodes still have dna:uuid set in their location field.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 13 16:03:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 13 Oct 2009 16:03:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <803794811.1255464185958.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-457:
--------------------------------

    Attachment: DNA-457_for_review.patch


Updated version of previous patch for review.  Same shortcomings, but works with the new SessionCache.  All feedback is welcome.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 13 17:13:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 13 Oct 2009 17:13:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <743762856.1255468385632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-457:
-----------------------------------

For the most part, this is a great first step!  I do have a few questions, though.

The general approach of persisting the lock information in /jcr:system/dna:locks seems like a good approach - it provides master persisted lock information accessible to all distributed processes.  The organization seems pretty good - /jcr:system/dna:locks/<lock_for_node_given_node_uuid>, where the lock node contains the information about the node being locked as well as the information about the owner of the lock.  And the restriction to mix:referenceable nodes is obvious, since the nodes' UUIDs are used in the name of the DNA lock.

Considering that this approach doesn't work with nodes that are not mix:referenceable, would it work to use the UUID for the lock (rather than the UUID of the locked node) as the node name?  The UUID and/or path could then be kept in the lock info node (and because this node is locked, only the session with the lock token can modify the node and possibly move the node, and in that case the session could update the path in the lock info).  This would make it more difficult to quickly look up a lock given a node, but isn't that the point of the in-memory map?  The in-memory map could be changed to be keyed by Location, which would work by path and/or UUID and/or by other ID properties.  I'm not sure whether this would even work, because I might be missing some aspects of the current design or failing to recognize all of the issues with this alternative.  Thoughts?

Back to the current patch.  Here are a few comments:

In WorkspaceLockManager:
1) As the patch defines the code, the DnaLock.isLive() method is getting backdoor access to the map outside of a lock scope, and this seems like an error.
2) I'm not sure whether the read-write lock is guarding only the in-memory map or also the persisted content.  If it's the latter, then what about other sessions created in other processes?  If the read-write lock is to guard only the in-memory map, then the map probably can be changed to be a concurrent map and the read-write lock removed entirely, which could very well have a significant performance impact since this method is called once for each node in the path of a node that is being modified.  Also, is the map just providing an in-memory cache of the content in the repository?
3) The lock tokens appear to just be the string form of the locked node UUID.  This is pretty easily forged, correct?  Not sure that this is a bad thing, but it does give users a bit more rope to hang themselves.
4) The lockFor(UUID) method could be changed to accept an AbstractJcrNode, and thus would encapsulate a bit more of the WorkspaceLockManager internals. Of course, the lockFor(String token) would need to be changed a bit to reflect how the lockFor(UUID) worked.

The rest of my comments are _very_ minor nits.  

In AbstractJcrNode:
1) lock() will be called a lot (for every modification method on any node or property) ... seems like it'd be useful to cache some of the references. Also (minor nit) seems like the code could be cleaned up to reduce duplication by using a do-while loop.

In JcrRepository:
1) JcrRepository.login(...) calls JcrRepository.getLockManager() and passes the WorkspaceLockManager reference into the JcrWorkspace constructor.  This additional constructor parameter really isn't necessary, since the JcrWorkspace constructor could get it's own WorkspaceLockManager from the JcrRepository that is passed as a parameter to the constructor.
2) Some of the use of the concurrent lockManagers map is not really correct. Basically, one should never do multiple checks within a single method, since the map can change from one map method to the next.  So, for example:

    WorkspaceLockManager getLockManager( String workspaceName ) {
        WorkspaceLockManager lockManager = lockManagers.get(workspaceName);
        if (lockManager != null) return lockManager;
        lockManagers.putIfAbsent(workspaceName, new WorkspaceLockManager(executionContext, this, workspaceName, locksPath));
        return lockManagers.get(workspaceName);
    }

should really be:

    WorkspaceLockManager getLockManager( String workspaceName ) {
        // Check for an existing lock manager ...
        WorkspaceLockManager lockManager = lockManagers.get(workspaceName);
        if (lockManager != null) return lockManager;
        // Need to create one if one hasn't just been created ...
        lockManager = new WorkspaceLockManager(executionContext, this, workspaceName, locksPath);
        WorkspaceLockManager newLockManager = lockManagers.putIfAbsent(workspaceName, lockManager);
        if ( newLockManager != null ) {
            // Some other thread just added this lock manager since our 'get' above ...
            lockManager = newLockManager;
        }
        return lockManager;
    }

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 13 21:03:06 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 13 Oct 2009 21:03:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <598341364.1255482186271.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-457:
-------------------------------------

Thanks for the great feedback!  I'll try to re-work the patch accordingly and put it back up in a few days.  

I like the idea of giving the lock its own UUID rather than reusing the node's UUID.  That would give us a somewhat shorter path to supporting locking of non-referenceable nodes, although there would still be a whole lot of work to do if we wanted to go that route.


> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 16 15:29:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 16 Oct 2009 15:29:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1327149871.1255721345728.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-457:
--------------------------------

    Attachment: DNA-457_for_review_2.patch


Attached new patch (DNA-457_for_review_2.patch)

In WorkspaceLockManager:
1) As the patch defines the code, the DnaLock.isLive() method is getting backdoor access to the map outside of a lock scope, and this seems like an error.
FIXED - switched to use of ConcurrentHashMap and removed the lock

2) I'm not sure whether the read-write lock is guarding only the in-memory map or also the persisted content. If it's the latter, then what about other sessions created in other processes? If the read-write lock is to guard only the in-memory map, then the map probably can be changed to be a concurrent map and the read-write lock removed entirely, which could very well have a significant performance impact since this method is called once for each node in the path of a node that is being modified. Also, is the map just providing an in-memory cache of the content in the repository?
FIXED - Switched DnaLock to ThreadSafe (since it has no mutable internal state but does rely on the thread-safe workspace locks map), moved workspaceLocks to be a ConcurrentHashMap and deleted the manual locking

3) The lock tokens appear to just be the string form of the locked node UUID. This is pretty easily forged, correct? Not sure that this is a bad thing, but it does give users a bit more rope to hang themselves.
FIXED - The lock tokens are now UUIDs themselves that are independent of the underlying node's UUID.

4) The lockFor(UUID) method could be changed to accept an AbstractJcrNode, and thus would encapsulate a bit more of the WorkspaceLockManager internals. Of course, the lockFor(String token) would need to be changed a bit to reflect how the lockFor(UUID) worked.
NOT FIXED - There's a place where I need to walk up the graph from the current node to the root to make sure that none of the parents have a deep lock.  I can get the underlying o.j.d.g.Node easier than the AbstractJcrNode.  If I changed to using AbstractJcrNode as the argument, I'd have to do more materialization (albeit with the same number of data retrieves).  I'm still open to changing this, but it doesn't seem worth the materialization penalty to me off the cuff.

The rest of my comments are _very_ minor nits.

In AbstractJcrNode:
1) lock() will be called a lot (for every modification method on any node or property) ... seems like it'd be useful to cache some of the references. Also (minor nit) seems like the code could be cleaned up to reduce duplication by using a do-while loop.
NOT FIXED - I don't think that you can do any non-trivial lock caching (i.e., cache the results of lockFor(nodeUuid)) since that could be changed outside of the current session.  I did cache the workspace().session().lockManager() calls.  I think I see what you're saying about refactoring into a do-while, but the lock handling is different for a lock on the current node vs. one of its parents if lockIsDeep is false.  I think it's slightly more efficient as is, but I may be missing something.

In JcrRepository:
1) JcrRepository.login(...) calls JcrRepository.getLockManager() and passes the WorkspaceLockManager reference into the JcrWorkspace constructor. This additional constructor parameter really isn't necessary, since the JcrWorkspace constructor could get it's own WorkspaceLockManager from the JcrRepository that is passed as a parameter to the constructor.
FIXED - Good point.  The redundant constructor arg is no more.

2) Some of the use of the concurrent lockManagers map is not really correct. Basically, one should never do multiple checks within a single method, since the map can change from one map method to the next. So, for example:

    WorkspaceLockManager getLockManager( String workspaceName ) {
        WorkspaceLockManager lockManager = lockManagers.get(workspaceName);
        if (lockManager != null) return lockManager;
        lockManagers.putIfAbsent(workspaceName, new WorkspaceLockManager(executionContext, this, workspaceName, locksPath));
        return lockManagers.get(workspaceName);
    }

should really be:

    WorkspaceLockManager getLockManager( String workspaceName ) {
        // Check for an existing lock manager ...
        WorkspaceLockManager lockManager = lockManagers.get(workspaceName);
        if (lockManager != null) return lockManager;
        // Need to create one if one hasn't just been created ...
        lockManager = new WorkspaceLockManager(executionContext, this, workspaceName, locksPath);
        WorkspaceLockManager newLockManager = lockManagers.putIfAbsent(workspaceName, lockManager);
        if ( newLockManager != null ) {
            // Some other thread just added this lock manager since our 'get' above ...
            lockManager = newLockManager;
        }
        return lockManager;
    }

FIXED - Nice catch, thanks!


> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 16 15:41:06 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 16 Oct 2009 15:41:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <823815798.1255722066020.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-457:
-----------------------------------

I just had a cursory look so far, but thanks for addressing my questions/suggestions.  A couple clarifications:

"4) The lockFor(UUID) method could be changed to accept an AbstractJcrNode, and thus would encapsulate a bit more of the WorkspaceLockManager internals. Of course, the lockFor(String token) would need to be changed a bit to reflect how the lockFor(UUID) worked. 
NOT FIXED - There's a place where I need to walk up the graph from the current node to the root to make sure that none of the parents have a deep lock. I can get the underlying o.j.d.g.Node easier than the AbstractJcrNode. If I changed to using AbstractJcrNode as the argument, I'd have to do more materialization (albeit with the same number of data retrieves). I'm still open to changing this, but it doesn't seem worth the materialization penalty to me off the cuff. "

Ooops.  I didn't look closely enough at the code.  Using o.j.d.g.Node would have a better suggestion, but I do see your very good point re materialization.

"In AbstractJcrNode: 
1) lock() will be called a lot (for every modification method on any node or property) ... seems like it'd be useful to cache some of the references. Also (minor nit) seems like the code could be cleaned up to reduce duplication by using a do-while loop. 
NOT FIXED - I don't think that you can do any non-trivial lock caching (i.e., cache the results of lockFor(nodeUuid)) since that could be changed outside of the current session. I did cache the workspace().session().lockManager() calls. I think I see what you're saying about refactoring into a do-while, but the lock handling is different for a lock on the current node vs. one of its parents if lockIsDeep is false. I think it's slightly more efficient as is, but I may be missing something. "

Wow - another bad comment on my part.  Sorry.  All I meant by "cache some of the references" is that there were several places that "session().workspace().lockManager()" was being called within a loop, and that using a local variable would be more efficient.  The new patch uses local references.

I'll keep looking

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 16 16:39:19 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 16 Oct 2009 16:39:19 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <982585012.1255725559535.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-457:
-----------------------------------

Okay, I got through the rest of the patch, and it looks good.  Per an IRC conversation with Brian, we agreed that WorkspaceLockManager should expose Location rather than UUID.  This would make it more likely that changes to support non-referenceable nodes might be encapsulated (mostly) in WorkspaceLockManager.  Other than this, the patch looks great.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 19 15:55:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 19 Oct 2009 15:55:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1687309393.1255982105769.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-457:
-------------------------------------

Committed patch that provides a locking implementation based on tracking the UUIDs of locked nodes.  This implies that any lockable node must also be referenceable.  The patch allows all of the TCK locking tests to pass as well as a few L2 tests which assumed a locking implementation for the repository.  However, the locking approach does not yet provide any way of integrating the lock/unlock capabilities with the underlying repository.  I will leave the defect open until that need can be addressed as well.

Thanks much for the reviews and suggestions!


> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 20 10:55:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 20 Oct 2009 10:55:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <797616722.1256050505819.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-457:
--------------------------------

    Attachment: DNA-457_graph_locking_support.patch


Attached patch that adds graph layer support for locking for review.  The current approach adds two new request, LockBranchRequest and UnlockBranchRequest to communicate lock and unlock requests to the connector.  The LockBranchRequest has the concept of a "scope" (currently indicates whether the lock should affect only the node or also the branch rooted at the node) and a "timeout" (the maximum TTL for the lock, 0 indicates use some default value from the connector).

Any feedback would be appreciated!

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 20 11:31:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 20 Oct 2009 11:31:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7151433.1256052665628.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-457:
-----------------------------------

I definitely like the changes to the graph layer, including the changes to the fluent graph API as well as the requests.

It may be good to elaborate a bit in the JavaDoc for the connector capabilities and what 'supports locking' actually means.  I think it's intuitive that if a connector "supports locking", it basically allows locks to be used on (at least some of) its content, and will either confirm or veto a lock requests.  But it may be a bit more ambiguous as to what it means to not support locking.  I'd guess this means that the connector is saying that locks will not be permitted on any of its content, and that if any lock requests do come down, they will be vetoed/rejected.  Is this correct?

And what will the behavior of our existing connectors be?  IMO, the JPA, in-memory, JBoss Cache, and Infinispan connectors should certainly support locking, but since they are really "storage" connectors (meaning that the underlying systems are 'owned' by DNA and are being accessed by DNA) they have no need to do anything special with the lock requests, other than approve them.  On the other hand, the file system connector should _not_ support locking (perhaps this can change when Java 7 enables interaction with native FS locks).  And the SVN connector is read-only right now and thus should also not support locks, though when the connector is changed to support writes, the connector could also be changed to support locking by integrating with native SVN locks.

Does this sound right?

Probably should update the Reference Guide, too.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 20 11:42:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 20 Oct 2009 11:42:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-539)
 AbstractJcrNode.location.getUuid() Returns Null for Referenceable Nodes
In-Reply-To: <30695825.1255109825911.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1640489351.1256053325651.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-539.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Won't Fix
         Assignee: Brian Carothers


The original design that needed this was refactored and the resulting code ended up being pushed outside of AbstractJcrNode anyway (into WorkspaceLockManager.uuidFor(AbstractJcrNode), for the curious).  Unless/until some other code needs this, I'm withdrawing my defect.

> AbstractJcrNode.location.getUuid() Returns Null for Referenceable Nodes
> -----------------------------------------------------------------------
>
>                 Key: DNA-539
>                 URL: https://jira.jboss.org/jira/browse/DNA-539
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Trivial
>             Fix For: 0.7
>
>
> For non-referenceable nodes, AbstractJcrNode.location.getUuid() returns the node's UUID if the node has a UUID (which is really a function of which connector the node maps to).  For referenceable nodes, AbstractJcrNode.location.getUuid() returns null but AbstractJcrNode.location.getIdProperty(JcrLexicon.UUID) returns a non-null value.
> Put another way:
> AbstractJcrNode.location has dna:uuid but not jcr:uuid if the node is not referenceable.
> AbstractJcrNode.location has jcr:uuid but not dna:uuid if the node is referenceable
> This means that the only safe way to get the corresponding UUID for a node (if one exists) is to run a code snippet like this:
>         if (location.getUuid() != null) return location.getUuid();
>         org.jboss.dna.graph.property.Property uuidProp = location.getIdProperty(JcrLexicon.UUID);
>         if (uuidProp == null) return null;
>         return this.cache.factories().getUuidFactory().create(uuidProp.getFirstValue());
> It would be nice if referenceable nodes still have dna:uuid set in their location field.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 20 12:14:06 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 20 Oct 2009 12:14:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-523) Spelling and grammar
 errors in on-line JBoss DNA Reference Guide
In-Reply-To: <538188676.1253128583648.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1911600969.1256055246624.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-523:
--------------------------------

    Attachment: DNA-523.patch


Attached patch that corrects all of the noted issues.

> Spelling and grammar errors in on-line JBoss DNA Reference Guide
> ----------------------------------------------------------------
>
>                 Key: DNA-523
>                 URL: https://jira.jboss.org/jira/browse/DNA-523
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Priority: Minor
>         Attachments: DNA-523.patch, DNA_Doc_edits.txt
>
>
> Found several grammar errors and typos in Chapter 5 of on-line document.  Attached text file of fixes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 20 12:16:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 20 Oct 2009 12:16:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-523) Spelling and grammar
 errors in on-line JBoss DNA Reference Guide
In-Reply-To: <538188676.1253128583648.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <748399730.1256055365731.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-523.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done
         Assignee: Brian Carothers


Applied attached patch.  Thanks for noting these errors!

> Spelling and grammar errors in on-line JBoss DNA Reference Guide
> ----------------------------------------------------------------
>
>                 Key: DNA-523
>                 URL: https://jira.jboss.org/jira/browse/DNA-523
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-523.patch, DNA_Doc_edits.txt
>
>
> Found several grammar errors and typos in Chapter 5 of on-line document.  Attached text file of fixes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 21 18:11:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 21 Oct 2009 18:11:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <591900382.1256163065631.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-457:
--------------------------------

    Attachment: DNA-457_repo_locks.patch


Attached patch (DNA-457_repo_locks.patch) that adds comments to address the previous feedback and provides a graph-layer API for locking nodes in repositories that provide their own locking mechanism (e.g., SVN).  The patch also modifies the JCR locking code to propagate JCR locks to the graph layer.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_repo_locks.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 22 16:26:19 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 22 Oct 2009 16:26:19 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-540) Locking Implementation
 Needs To Be Clusterable
Message-ID: <1719777867.1256243179710.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Locking Implementation Needs To Be Clusterable
----------------------------------------------

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


The current locking implementation caches a map of active locks in o.d.j.WorkspaceLockManager, but does not provide a means of coordinating changes to that map across nodes.  This could lead to lock contention in a clustered DNA environment.  It's worth noting that a backing store that implemented locking internally (e.g., SVN) would prevent this contention.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 22 16:30:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 22 Oct 2009 16:30:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-541) Locking Implementation
 Does Not Support Timeouts
Message-ID: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Locking Implementation Does Not Support Timeouts
------------------------------------------------

                 Key: DNA-541
                 URL: https://jira.jboss.org/jira/browse/DNA-541
             Project: DNA
          Issue Type: Bug
          Components: JCR
            Reporter: Brian Carothers
            Assignee: Brian Carothers
             Fix For: 0.7


The locking implementation does not provide a means of expiring stale or old locks (other than having the original owner unlock 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 Oct 22 16:34:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 22 Oct 2009 16:34:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <920044245.1256243645700.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-457.
---------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
       Resolution: Done
         Assignee: Brian Carothers


Marking this defect as resolved the base functionality required by the JSR-170 spec is committed and passing tests.  Added defects DNA-540 and DNA-541 to reflect the need for clustered support and lock timeouts, respectively.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_repo_locks.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 22 20:43:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 22 Oct 2009 20:43:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-542) jcr:uuid Property in
 dna:lock Custom Type Needs To Be Renamed
Message-ID: <914862714.1256258585622.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

jcr:uuid Property in dna:lock Custom Type Needs To Be Renamed
-------------------------------------------------------------

                 Key: DNA-542
                 URL: https://jira.jboss.org/jira/browse/DNA-542
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
            Priority: Critical
             Fix For: 0.7


The dna:lock custom node type (used to store information about an active lock) reuses the jcr:uuid and jcr:lockOwner properties.  However, using the jcr:uuid property in this manner means that the dna:lock node type can never be made referenceable later.  It also violates an assumption in the JpaConnector that a node's jcr:uuid refers to the UUID for that node and not some other 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  Thu Oct 22 20:54:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 22 Oct 2009 20:54:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-518) JPA connector fails to
 properly clone or update from another workspace
In-Reply-To: <1941388502.1252594583611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <779805688.1256259245653.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-518:
--------------------------------

    Attachment: DNA-518.patch


Attached patch that pushes the desiredSegment down into the copyNode call (if the desiredSegment is specified).  Previously, copyNode was silently converting the desiredSegment field into a desiredName.

> JPA connector fails to properly clone or update from another workspace
> ----------------------------------------------------------------------
>
>                 Key: DNA-518
>                 URL: https://jira.jboss.org/jira/browse/DNA-518
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Testing
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-518.patch
>
>
> The JPA connector's implementation of CloneBranchRequest is not correct when cloning from another workspace.  This is used in the JCR API in the 'Node.update(String workspaceName)' method as well as the 'Workspace.clone( String srcWorkspace, String srcAbsPath, String destAbsPath, boolean removeExisting )'.
> The problem appears to be that the removeExisting behavior only works by comparing exact UUIDs, whereas the removeExisting behavior (for clone) really should apply only to the specified path.  Yes, any existing nodes with the same UUIDs should be removed, but certainly if 'removeExisting' is true any existing node at the desired location for the clone should be removed as well.
> This was discovered because the TCK tests are failing when they're run against a repository using the JPA connector (both against HSQLDB and PostgreSQL):
> JpaRepositoryTckTest
> Tests for jpa(read-write)
> org.apache.jackrabbit.test.api.NodeTest
> testUpdate(org.apache.jackrabbit.test.api.NodeTest)
> java.lang.IllegalArgumentException: The last segment of the actual location of </{}testroot/{}node1[2] && [{http://www.jboss.org/dna/1.0}uuid = c3863875-6422-46ee-b47f-5a12547e27d8]> does not have the requested child segment {}node1
> 	at org.jboss.dna.graph.request.CloneBranchRequest.setActualLocations(CloneBranchRequest.java:199)
> 	at org.jboss.dna.connector.store.jpa.model.basic.BasicRequestProcessor.process(BasicRequestProcessor.java:1672)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:261)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
> 	at org.jboss.dna.connector.store.jpa.JpaConnection.execute(JpaConnection.java:150)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:308)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:637)
> org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest
> testCloneNodesRemoveExistingTrue(org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest)
> junit.framework.AssertionFailedError: null
> 	at junit.framework.Assert.fail(Assert.java:47)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertFalse(Assert.java:34)
> 	at junit.framework.Assert.assertFalse(Assert.java:41)
> 	at org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest.testCloneNodesRemoveExistingTrue(WorkspaceCloneReferenceableTest.java:81)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at junit.framework.TestCase.runTest(TestCase.java:168)
> 	at junit.framework.TestCase.runBare(TestCase.java:134)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 24 10:16:18 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:16:18 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-543) Add support for
	JCR-SQL2
Message-ID: <1043686697.1256393778397.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add support for JCR-SQL2
------------------------

                 Key: DNA-543
                 URL: https://jira.jboss.org/jira/browse/DNA-543
             Project: DNA
          Issue Type: Feature Request
          Components: Graph, JCR
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.7


Add support for querying graphs using the JCR-SQL2 query language defined by the JCR 2.0 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 Oct 24 10:28:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:28:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-543) Add support for
	JCR-SQL2
In-Reply-To: <1043686697.1256393778397.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1630509707.1256394485664.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-543.
-------------------------------

    Resolution: Done


The full support of the language was added, with several improvements.  

The "IN" clause is supported as an additional DynamicOperand in the WHERE criteria, making it easier to specify a set of possible/allowed values for a property than ORing a Comparison for each of the criteria. For example, a query may use "... WHERE ... [foo:bar] IN ('value 1','value2','value3') ...", which is far easier than "... WHERE ... (([foo:bar] = 'value 1') OR ([foo:bar] = 'value 2') OR ([foo:bar] = 'value 2')) ...".

Two additional DynamicOperand functions are also added.  The "DEPTH(<selectorName>)" function can be used to easily obtain the depth of a particular node, and makes it easy to constraint the query to return nodes within a depth range.  The "PATH(<selectorName>)" function similarly obtains the path of the node, making it easy to constrain the query to return paths matching patterns.

> Add support for JCR-SQL2
> ------------------------
>
>                 Key: DNA-543
>                 URL: https://jira.jboss.org/jira/browse/DNA-543
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Add support for querying graphs using the JCR-SQL2 query language defined by the JCR 2.0 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 Oct 24 10:28:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:28:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-544) Add support for JCR
 1.0 variant of XPath
In-Reply-To: <468182882.1256394485696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1922986430.1256394485729.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-544:
------------------------------

          Component/s: Graph
                       JCR
        Fix Version/s: 0.7
    Affects Version/s: 0.6


> Add support for JCR 1.0 variant of XPath
> ----------------------------------------
>
>                 Key: DNA-544
>                 URL: https://jira.jboss.org/jira/browse/DNA-544
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Add support for querying graphs using the JCR 1.0 variant of XPath, which is a subset plus minor extension of the standard XPath 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 Oct 24 10:28:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:28:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-544) Add support for JCR
 1.0 variant of XPath
Message-ID: <468182882.1256394485696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add support for JCR 1.0 variant of XPath
----------------------------------------

                 Key: DNA-544
                 URL: https://jira.jboss.org/jira/browse/DNA-544
             Project: DNA
          Issue Type: Feature Request
            Reporter: Randall Hauch
            Assignee: Randall Hauch


Add support for querying graphs using the JCR 1.0 variant of XPath, which is a subset plus minor extension of the standard XPath 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 Oct 24 10:31:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:31:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-544) Add support for JCR
 1.0 variant of XPath
In-Reply-To: <468182882.1256394485696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <499071852.1256394665642.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-544:
-----------------------------------

The full support for the JCR 1.0 flavor of XPath was added.  Quite a few unit tests were added, but this is such a flexible query language that it is difficult to test all possible combinations.  I've also grabbed a number of real-world XPath queries for JCR (from various places) and used them in unit tests.

However, we're likely to find some incorrect behavior with more complicated queries, so we'll just have to open additional JIRA issues and treat them as bugs.

> Add support for JCR 1.0 variant of XPath
> ----------------------------------------
>
>                 Key: DNA-544
>                 URL: https://jira.jboss.org/jira/browse/DNA-544
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Add support for querying graphs using the JCR 1.0 variant of XPath, which is a subset plus minor extension of the standard XPath 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 Oct 24 10:31:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:31:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-544) Add support for JCR
 1.0 variant of XPath
In-Reply-To: <468182882.1256394485696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1590840467.1256394665677.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-544.
-------------------------------

    Resolution: Done


> Add support for JCR 1.0 variant of XPath
> ----------------------------------------
>
>                 Key: DNA-544
>                 URL: https://jira.jboss.org/jira/browse/DNA-544
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Add support for querying graphs using the JCR 1.0 variant of XPath, which is a subset plus minor extension of the standard XPath 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 Oct 24 10:33:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 24 Oct 2009 10:33:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-545) Add support for GQL
Message-ID: <1009110997.1256394785619.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add support for GQL
-------------------

                 Key: DNA-545
                 URL: https://jira.jboss.org/jira/browse/DNA-545
             Project: DNA
          Issue Type: Feature Request
          Components: Graph
    Affects Versions: 0.6
            Reporter: Randall Hauch
             Fix For: Future Releases


The GQL language is a SQL-like query language used in the Google App Engine (http://code.google.com/appengine/docs/python/datastore/gqlreference.html).  It's looks like it is just a small subset of the JCR-SQL2 query language (see DNA-543), but with a small extension.  Therefore, we probably do not want to reuse the JCR-SQL2 parser, but rather should implement a new parser (in case there are other diversions between the two).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 27 16:03:06 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 27 Oct 2009 16:03:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <628072226.1256673786094.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reopened DNA-457:
---------------------------------



The default RequestProcessor implementation isn't correctly populating the actual location.  Additionally, the RepositorySourceCapability for supports locking seems to be redundant.



> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-457_fixed_RequestProcessor.patch, DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_repo_locks.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 27 16:03:06 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 27 Oct 2009 16:03:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <274909166.1256673786145.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-457:
--------------------------------

    Attachment: DNA-457_fixed_RequestProcessor.patch


The attached patch (DNA-457_fixed_RequestProcessor.patch) corrects the default RequestProcessor implementation to populate the actual location on the request, looking up the path for the node if necessary.

> Add JSR-170 Locking Optional Feature
> ------------------------------------
>
>                 Key: DNA-457
>                 URL: https://jira.jboss.org/jira/browse/DNA-457
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-457_fixed_RequestProcessor.patch, DNA-457_for_review.patch, DNA-457_for_review_2.patch, DNA-457_graph_locking_support.patch, DNA-457_repo_locks.patch, DNA-457_WIP.patch
>
>
> JSR-170 defines several optional features.  The locking feature allows users to lock nodes (and, optionally, their descendants) until the session terminates or until they are programatically unlocked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 28 10:41:06 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 28 Oct 2009 10:41:06 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-456) Add JSR-170
 Observation Optional Feature
In-Reply-To: <29781241.1244747516423.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1751056017.1256740866021.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-456:
------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
         Assignee: Dan Florian


> Add JSR-170 Observation Optional Feature
> ----------------------------------------
>
>                 Key: DNA-456
>                 URL: https://jira.jboss.org/jira/browse/DNA-456
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> JSR-170 defines several optional features.  The observation feature would provide notification of node and property changes to registered 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  Fri Oct 30 17:35:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 30 Oct 2009 17:35:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-518) JPA connector fails to
 properly clone or update from another workspace
In-Reply-To: <1941388502.1252594583611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <25261196.1256938505704.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-518:
--------------------------------

    Attachment: DNA-518_2.patch


The previous patch fixed the originally declared issue, but exposed a few regressions.  The attached patch fixes most of those regressions and corrects a significant design flaw in the original locking implementation (using jcr:uuid to refer to another nodes uuid).

However, this patch does not correct two key defects.  JCR imports (session and workspace) that include collisions with existing nodes that share a UUID will fail if the removeExisting flag is set to true.  There is also a minor defect with moving locked nodes on this connector.

Since the original defect is addressed, this defect can be resolved and two new defects can be opened for the other regressions.

> JPA connector fails to properly clone or update from another workspace
> ----------------------------------------------------------------------
>
>                 Key: DNA-518
>                 URL: https://jira.jboss.org/jira/browse/DNA-518
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Testing
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-518.patch, DNA-518_2.patch
>
>
> The JPA connector's implementation of CloneBranchRequest is not correct when cloning from another workspace.  This is used in the JCR API in the 'Node.update(String workspaceName)' method as well as the 'Workspace.clone( String srcWorkspace, String srcAbsPath, String destAbsPath, boolean removeExisting )'.
> The problem appears to be that the removeExisting behavior only works by comparing exact UUIDs, whereas the removeExisting behavior (for clone) really should apply only to the specified path.  Yes, any existing nodes with the same UUIDs should be removed, but certainly if 'removeExisting' is true any existing node at the desired location for the clone should be removed as well.
> This was discovered because the TCK tests are failing when they're run against a repository using the JPA connector (both against HSQLDB and PostgreSQL):
> JpaRepositoryTckTest
> Tests for jpa(read-write)
> org.apache.jackrabbit.test.api.NodeTest
> testUpdate(org.apache.jackrabbit.test.api.NodeTest)
> java.lang.IllegalArgumentException: The last segment of the actual location of </{}testroot/{}node1[2] && [{http://www.jboss.org/dna/1.0}uuid = c3863875-6422-46ee-b47f-5a12547e27d8]> does not have the requested child segment {}node1
> 	at org.jboss.dna.graph.request.CloneBranchRequest.setActualLocations(CloneBranchRequest.java:199)
> 	at org.jboss.dna.connector.store.jpa.model.basic.BasicRequestProcessor.process(BasicRequestProcessor.java:1672)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:261)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
> 	at org.jboss.dna.connector.store.jpa.JpaConnection.execute(JpaConnection.java:150)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:308)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:637)
> org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest
> testCloneNodesRemoveExistingTrue(org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest)
> junit.framework.AssertionFailedError: null
> 	at junit.framework.Assert.fail(Assert.java:47)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertFalse(Assert.java:34)
> 	at junit.framework.Assert.assertFalse(Assert.java:41)
> 	at org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest.testCloneNodesRemoveExistingTrue(WorkspaceCloneReferenceableTest.java:81)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at junit.framework.TestCase.runTest(TestCase.java:168)
> 	at junit.framework.TestCase.runBare(TestCase.java:134)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 30 17:35:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 30 Oct 2009 17:35:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-518) JPA connector fails
 to properly clone or update from another workspace
In-Reply-To: <1941388502.1252594583611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1675933874.1256938505770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-518.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers  (was: Randall Hauch)


Previous patch fixes original issue for this defect.  Additional defects will be opened to describe other regressions.

> JPA connector fails to properly clone or update from another workspace
> ----------------------------------------------------------------------
>
>                 Key: DNA-518
>                 URL: https://jira.jboss.org/jira/browse/DNA-518
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Testing
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-518.patch, DNA-518_2.patch
>
>
> The JPA connector's implementation of CloneBranchRequest is not correct when cloning from another workspace.  This is used in the JCR API in the 'Node.update(String workspaceName)' method as well as the 'Workspace.clone( String srcWorkspace, String srcAbsPath, String destAbsPath, boolean removeExisting )'.
> The problem appears to be that the removeExisting behavior only works by comparing exact UUIDs, whereas the removeExisting behavior (for clone) really should apply only to the specified path.  Yes, any existing nodes with the same UUIDs should be removed, but certainly if 'removeExisting' is true any existing node at the desired location for the clone should be removed as well.
> This was discovered because the TCK tests are failing when they're run against a repository using the JPA connector (both against HSQLDB and PostgreSQL):
> JpaRepositoryTckTest
> Tests for jpa(read-write)
> org.apache.jackrabbit.test.api.NodeTest
> testUpdate(org.apache.jackrabbit.test.api.NodeTest)
> java.lang.IllegalArgumentException: The last segment of the actual location of </{}testroot/{}node1[2] && [{http://www.jboss.org/dna/1.0}uuid = c3863875-6422-46ee-b47f-5a12547e27d8]> does not have the requested child segment {}node1
> 	at org.jboss.dna.graph.request.CloneBranchRequest.setActualLocations(CloneBranchRequest.java:199)
> 	at org.jboss.dna.connector.store.jpa.model.basic.BasicRequestProcessor.process(BasicRequestProcessor.java:1672)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:261)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:298)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:219)
> 	at org.jboss.dna.connector.store.jpa.JpaConnection.execute(JpaConnection.java:150)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:318)
> 	at org.jboss.dna.graph.connector.federation.ForkRequestProcessor$Channel$3.call(ForkRequestProcessor.java:308)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:637)
> org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest
> testCloneNodesRemoveExistingTrue(org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest)
> junit.framework.AssertionFailedError: null
> 	at junit.framework.Assert.fail(Assert.java:47)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertFalse(Assert.java:34)
> 	at junit.framework.Assert.assertFalse(Assert.java:41)
> 	at org.apache.jackrabbit.test.api.WorkspaceCloneReferenceableTest.testCloneNodesRemoveExistingTrue(WorkspaceCloneReferenceableTest.java:81)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at junit.framework.TestCase.runTest(TestCase.java:168)
> 	at junit.framework.TestCase.runBare(TestCase.java:134)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 30 17:38:17 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 30 Oct 2009 17:38:17 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
Message-ID: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JCR Workspace and Session Imports Can Fail on JPA Connector
-----------------------------------------------------------

                 Key: DNA-546
                 URL: https://jira.jboss.org/jira/browse/DNA-546
             Project: DNA
          Issue Type: Bug
          Components: Connectors, JCR
    Affects Versions: 0.6
            Reporter: Brian Carothers


Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.

The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Oct 30 17:40:05 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 30 Oct 2009 17:40:05 -0400 (EDT)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-547) TCK Tests for Locking
 and Moving Nodes Fail for JPA Connector
Message-ID: <110540148.1256938805728.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

TCK Tests for Locking and Moving Nodes Fail for JPA Connector
-------------------------------------------------------------

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


Two of the TCK tests for the optional locking feature fail on the JPA connector.  As a result, the TCK tests for the locking feature have been removed from the JPA TCK integration test.

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

        

