From jira-events at lists.jboss.org  Tue Dec  1 09:45:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 09:45:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-562) Upgrade to Lucene 3.0
Message-ID: <1619122568.1259678730050.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Upgrade to Lucene 3.0
---------------------

                 Key: DNA-562
                 URL: https://jira.jboss.org/jira/browse/DNA-562
             Project: DNA
          Issue Type: Thirdparty Change
          Components: JCR, Query, Search
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.7


Lucene 3.0 was just released and includes mostly just removals of the deprecated features and APIs in Lucene 2.9.1 (which is what we were previously using).  We do not have any deprecated warnings, so I'm guessing this should be a pretty easy upgrade for us.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 10:48:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 10:48:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-562) Upgrade to Lucene 3.0
In-Reply-To: <1619122568.1259678730050.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1888806497.1259682509611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-562.
-------------------------------

    Resolution: Done


Upgraded Lucene to the latest release (3.0.0), which was made just last week and contains only removal of deprecated APIs.

> Upgrade to Lucene 3.0
> ---------------------
>
>                 Key: DNA-562
>                 URL: https://jira.jboss.org/jira/browse/DNA-562
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Lucene 3.0 was just released and includes mostly just removals of the deprecated features and APIs in Lucene 2.9.1 (which is what we were previously using).  We do not have any deprecated warnings, so I'm guessing this should be a pretty easy upgrade for us.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 11:32:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 1 Dec 2009 11:32:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <35479650.1259685149950.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-548.
-----------------------------

    Resolution: Done


Session IDs and Changes IDs are matching. Applicable tests are now passing. Marking as resolved.

> The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
> ------------------------------------------------------------------------------------------
>
>                 Key: DNA-548
>                 URL: https://jira.jboss.org/jira/browse/DNA-548
>             Project: DNA
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> There is no way for the ObservationManager to obtain the session from the NetChanges/Changes/ChangeRequest objects. The session identifier is needed to implement the event notification of the ObservationManager. Specifically, listeners are registered with a "noLocal" flag indicating if they want or don't want to receive events from the session that they are registered in.

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

        

From jira-events at lists.jboss.org  Tue Dec  1 11:59:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 1 Dec 2009 11:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
Message-ID: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
---------------------------------------------------------------------------------

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


If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.

See JBoss forum referenced below for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 14:29:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 1 Dec 2009 14:29:29 -0500 (EST)
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: <1162110929.1259695769655.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 ]

Dan Florian updated DNA-456:
----------------------------

    Attachment: DNA-456-dna-graph.patch
                DNA-456-dna-jcr.patch
                DNA-456-dna-repository.patch


DNA-456-dna-graph.patch, DNA-456-dna-jcr.path, and DNA-456-dna-repository should all be attached together into there appropriate project.

> 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
>
>         Attachments: DNA-456-dna-graph.patch, DNA-456-dna-jcr.patch, DNA-456-dna-repository.patch
>
>
> 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  Tue Dec  1 16:17:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:17:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-556) Need a
 graph-specific SequencerOutput class to simplify testing sequencer results.
In-Reply-To: <498100892.1259012856344.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1069196016.1259702250964.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-556:
-----------------------------------

This was committed in 'dna-graph' under 'src/main/java', but if this is used only for testing, then it should probably be moved under 'src/test/java'.

> Need a graph-specific SequencerOutput class to simplify testing sequencer results.
> ----------------------------------------------------------------------------------
>
>                 Key: DNA-556
>                 URL: https://jira.jboss.org/jira/browse/DNA-556
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, Sequencers
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While developing the test for the DdlSequencer, it would be beneficial to create a simplified graph oriented SequencerOutput class that provided 1) simple setProperty() and setReference() methods and performed a batched request.

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

        

From jira-events at lists.jboss.org  Tue Dec  1 16:26:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:26:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-564) Move Eclipse plugin
 code outside of the Maven modules
Message-ID: <255585603.1259702796558.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Move Eclipse plugin code outside of the Maven modules
-----------------------------------------------------

                 Key: DNA-564
                 URL: https://jira.jboss.org/jira/browse/DNA-564
             Project: DNA
          Issue Type: Task
          Components: Tools
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


As it stands now in its current location, the Eclipse plugin projects are not Mavenized and thus cannot be easily integrated into the Maven build.  Plus, the release process is made much more complex in the current form, because the Eclipse plugin would depend on the Maven artifacts (in released form).  Therefore, we should move the Eclipse plugin source code outside of the http://anonsvn.jboss.org/repos/dna/trunk/ area of SVN and into a new http://anonsvn.jboss.org/repos/dna/eclipse/trunk area.  

See also this email discussion thread: http://lists.jboss.org/pipermail/dna-dev/2009-November/000853.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 16:28:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:28:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-329) Create build scripts
 for integration with Hudson and running of continuous tests
In-Reply-To: <23285601.1237397482306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <425886824.1259702910045.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-329.
-------------------------------

    Resolution: Won't Fix


Marking as "Won't Fix" because we do not want to (nor easily can) integrate the Eclipse plugins into the Maven build process.  This issue has been superseded by DNA-564.

> Create build scripts for integration with Hudson and running of continuous tests
> --------------------------------------------------------------------------------
>
>                 Key: DNA-329
>                 URL: https://jira.jboss.org/jira/browse/DNA-329
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Testing, Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 16:30:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-308) Eclipse plug-in
 providing simple publishing capabilities
In-Reply-To: <8122682.1237392526796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2072104908.1259703029743.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-308.
-------------------------------

    Resolution: Done


Marking this uber issue as resolved, since all subtasks have been completed or marked as resolved.  Enhancements and bugs will be tracked as other issues.

Nicely done, Dan!

> Eclipse plug-in providing simple publishing capabilities
> --------------------------------------------------------
>
>                 Key: DNA-308
>                 URL: https://jira.jboss.org/jira/browse/DNA-308
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Views
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Providing an Eclipse plug-in to access DNA would provide applications such as JBoss Tools immediate ability to integrate with DNA by publishing files to a JBoss DNA Web Application with RESTful API.  
> The plug-in should initially provide simple capabilities such as:
> - Managing connections to one or more DNA repositories
> - Publishing files, specifically those in an Eclipse workspace
> - Un-publishing files

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

        

From jira-events at lists.jboss.org  Tue Dec  1 16:30:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-537) Update Reference Guide
 To Include Instructions On Developing/Building/Testing/Releasing The
 Eclipse Plugin
In-Reply-To: <910841711.1254757129152.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <566238627.1259703029938.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-537:
------------------------------

    Component/s: Documentation


> 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: Documentation, 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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-308) Eclipse plug-in
 providing simple publishing capabilities
In-Reply-To: <8122682.1237392526796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1582384379.1259703510224.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-308:
------------------------------

    Component/s: Tools
                     (was: Views)


> Eclipse plug-in providing simple publishing capabilities
> --------------------------------------------------------
>
>                 Key: DNA-308
>                 URL: https://jira.jboss.org/jira/browse/DNA-308
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Providing an Eclipse plug-in to access DNA would provide applications such as JBoss Tools immediate ability to integrate with DNA by publishing files to a JBoss DNA Web Application with RESTful API.  
> The plug-in should initially provide simple capabilities such as:
> - Managing connections to one or more DNA repositories
> - Publishing files, specifically those in an Eclipse workspace
> - Un-publishing files

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

        

From jira-events at lists.jboss.org  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-373) Provide OSGi
 information in archives (via META-INF/MANIFEST.MF files)
In-Reply-To: <5343833.1240324600751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2052507212.1259703510104.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-373:
------------------------------

    Component/s: Tools
                     (was: Development Environment)
                     (was: Documentation)


> Provide OSGi information in archives (via META-INF/MANIFEST.MF files)
> ---------------------------------------------------------------------
>
>                 Key: DNA-373
>                 URL: https://jira.jboss.org/jira/browse/DNA-373
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Tools
>            Reporter: Randall Hauch
>            Priority: Minor
>             Fix For: Future Releases
>
>
> If the JBoss DNA JAR files each included a META-INF/MANIFEST.MF file, our existing JARs could be used as OSGi bundles within an OSGi class loader environment (for example within Eclipse), while they continue to work outside of an OSGI environment.
> Another option is to create a single OSGi bundle containing the top-level archives and OSGi bundles for each of our extensions.

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

        

From jira-events at lists.jboss.org  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-321) Create
	publishing-related actions
In-Reply-To: <5477247.1237395503468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <154741741.1259703510137.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 ]

Randall Hauch updated DNA-321:
------------------------------

    Component/s: Tools
                     (was: Views)


> Create publishing-related actions
> ---------------------------------
>
>                 Key: DNA-321
>                 URL: https://jira.jboss.org/jira/browse/DNA-321
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-327) Create feature
In-Reply-To: <13711834.1237397141278.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1541246994.1259703510199.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 ]

Randall Hauch updated DNA-327:
------------------------------

    Component/s: Tools
                     (was: Views)


> Create feature
> --------------
>
>                 Key: DNA-327
>                 URL: https://jira.jboss.org/jira/browse/DNA-327
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
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: <1503994677.1259703510178.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 ]

Randall Hauch updated DNA-534:
------------------------------

    Component/s: Tools
                     (was: Views)


> Contribute To Eclipse Welcome Page Framework
> --------------------------------------------
>
>                 Key: DNA-534
>                 URL: https://jira.jboss.org/jira/browse/DNA-534
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>            Priority: Minor
>             Fix For: 1.0
>
>
> 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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-537) Update Reference Guide
 To Include Instructions On Developing/Building/Testing/Releasing The
 Eclipse Plugin
In-Reply-To: <910841711.1254757129152.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <767045144.1259703510269.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-537:
------------------------------

    Component/s: Tools
                     (was: Documentation)
                     (was: Views)


> 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: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-328) Create update site
In-Reply-To: <15378134.1237397362425.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <180647476.1259703510245.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 ]

Randall Hauch updated DNA-328:
------------------------------

    Component/s: Tools
                     (was: Views)


> Create update site
> ------------------
>
>                 Key: DNA-328
>                 URL: https://jira.jboss.org/jira/browse/DNA-328
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-326) Create documentation
In-Reply-To: <13759744.1237396882299.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <753484144.1259703510372.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 ]

Randall Hauch updated DNA-326:
------------------------------

    Component/s: Tools
                     (was: Documentation)
                     (was: Views)


> Create documentation
> --------------------
>
>                 Key: DNA-326
>                 URL: https://jira.jboss.org/jira/browse/DNA-326
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-536) Develop Update Site
	Website
In-Reply-To: <717460463.1254756769197.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1951679925.1259703510332.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-536:
------------------------------

    Component/s: Tools
                     (was: Views)


> Develop Update Site Website
> ---------------------------
>
>                 Key: DNA-536
>                 URL: https://jira.jboss.org/jira/browse/DNA-536
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-319) Create plug-in project
	in SVN
In-Reply-To: <26330711.1237394963598.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1303850908.1259703510299.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 ]

Randall Hauch updated DNA-319:
------------------------------

    Component/s: Tools
                     (was: Views)


> 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: Tools
>    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  Tue Dec  1 16:38:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-329) Create build scripts
 for integration with Hudson and running of continuous tests
In-Reply-To: <23285601.1237397482306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1244828462.1259703510399.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-329:
------------------------------

    Component/s: Tools
                     (was: Testing)
                     (was: Views)


> Create build scripts for integration with Hudson and running of continuous tests
> --------------------------------------------------------------------------------
>
>                 Key: DNA-329
>                 URL: https://jira.jboss.org/jira/browse/DNA-329
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Tools
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 16:41:15 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:41:15 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-326) Create documentation
In-Reply-To: <13759744.1237396882299.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1627914943.1259703675477.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 ]

Randall Hauch updated DNA-326:
------------------------------

    Component/s: Documentation


> Create documentation
> --------------------
>
>                 Key: DNA-326
>                 URL: https://jira.jboss.org/jira/browse/DNA-326
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Documentation, Tools
>    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  Tue Dec  1 16:41:15 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:41:15 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-537) Update Reference Guide
 To Include Instructions On Developing/Building/Testing/Releasing The
 Eclipse Plugin
In-Reply-To: <910841711.1254757129152.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1981014774.1259703675451.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-537:
------------------------------

    Component/s: Documentation


> 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: Documentation, Tools
>    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  Tue Dec  1 16:41:15 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:41:15 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-329) Create build scripts
 for integration with Hudson and running of continuous tests
In-Reply-To: <23285601.1237397482306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <710000139.1259703675503.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-329:
------------------------------

    Component/s: Testing


> Create build scripts for integration with Hudson and running of continuous tests
> --------------------------------------------------------------------------------
>
>                 Key: DNA-329
>                 URL: https://jira.jboss.org/jira/browse/DNA-329
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Testing, Tools
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 16:41:15 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 16:41:15 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-373) Provide OSGi
 information in archives (via META-INF/MANIFEST.MF files)
In-Reply-To: <5343833.1240324600751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1563950164.1259703675522.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-373:
------------------------------

    Component/s: Development Environment
                 Documentation


> Provide OSGi information in archives (via META-INF/MANIFEST.MF files)
> ---------------------------------------------------------------------
>
>                 Key: DNA-373
>                 URL: https://jira.jboss.org/jira/browse/DNA-373
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Development Environment, Documentation, Tools
>            Reporter: Randall Hauch
>            Priority: Minor
>             Fix For: Future Releases
>
>
> If the JBoss DNA JAR files each included a META-INF/MANIFEST.MF file, our existing JARs could be used as OSGi bundles within an OSGi class loader environment (for example within Eclipse), while they continue to work outside of an OSGI environment.
> Another option is to create a single OSGi bundle containing the top-level archives and OSGi bundles for each of our extensions.

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

        

From jira-events at lists.jboss.org  Tue Dec  1 18:21:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 1 Dec 2009 18:21:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-565) JCR Implementation
 Should Support Anonymous Access More Easily
Message-ID: <724178255.1259709689795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JCR Implementation Should Support Anonymous Access More Easily
--------------------------------------------------------------

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


The JCR implementation doesn't support anonymous access right now.  One could emulate anonymous access by creating a guest user, but that requires custom code, adding an actual user in the authentication store, managing the password for the user, etc.  It would be nice if DNA just support anonymous users in a configurable fashion and defaulted this anonymous access to disabled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 19:06:29 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 1 Dec 2009 19:06:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-536) Develop Update Site
	Website
In-Reply-To: <717460463.1254756769197.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <901905741.1259712389643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop commented on DNA-536:
------------------------------------------

the url should be http://www.jboss.org/dna/downloads/eclipse-update-sites.html and the site may have a table with versionable plugins (descriptions) and also a HOW TO install and required artifacts or tools (like jdk version, Eclipse IDE, ...)

> Develop Update Site Website
> ---------------------------
>
>                 Key: DNA-536
>                 URL: https://jira.jboss.org/jira/browse/DNA-536
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             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  Tue Dec  1 21:48:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 1 Dec 2009 21:48:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-565) JCR Implementation
 Should Support Anonymous Access More Easily
In-Reply-To: <724178255.1259709689795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1187852878.1259722109622.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-565:
--------------------------------

    Attachment: DNA-565.patch


Attached a patch that adds a JcrRepository.Option for ANONYMOUS_USER_ROLES.  This defaults to null (indicating that an anonymous user will not be granted any roles and will not be able to log in).  It can be set to a comma-delimited list of role names that will be provided to an anonymous user.  A test case has been added at the JCR layer.

The patch also changes the REST server around a bit to accommodate this new access.  If the requesting user is not authenticated, the REST code will now attempt to log in anonymously.  I've tested this locally and it did work for me, but I couldn't figure out a good way to write test cases for it and still test the behavior when it's not enabled (short of creating a whole new subproject which doesn't seem worth it).

I added this line to the configRepository.xml in the dna-web-jcr-rest project to test the anonymous access:
                <anonymousUserRoles jcr:primaryType="dna:option" value="connect,readonly"/>

This gave all unauthenticated users the ability to connect to the REST server and read-only privileges for all workspaces in all repositories.

> JCR Implementation Should Support Anonymous Access More Easily
> --------------------------------------------------------------
>
>                 Key: DNA-565
>                 URL: https://jira.jboss.org/jira/browse/DNA-565
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-565.patch
>
>
> The JCR implementation doesn't support anonymous access right now.  One could emulate anonymous access by creating a guest user, but that requires custom code, adding an actual user in the authentication store, managing the password for the user, etc.  It would be nice if DNA just support anonymous users in a configurable fashion and defaulted this anonymous access to disabled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:11:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 1 Dec 2009 22:11:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-565) JCR Implementation
 Should Support Anonymous Access More Easily
In-Reply-To: <724178255.1259709689795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <771903599.1259723489683.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-565.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Committed patch to resolve defect

> JCR Implementation Should Support Anonymous Access More Easily
> --------------------------------------------------------------
>
>                 Key: DNA-565
>                 URL: https://jira.jboss.org/jira/browse/DNA-565
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-565.patch
>
>
> The JCR implementation doesn't support anonymous access right now.  One could emulate anonymous access by creating a guest user, but that requires custom code, adding an actual user in the authentication store, managing the password for the user, etc.  It would be nice if DNA just support anonymous users in a configurable fashion and defaulted this anonymous access to disabled.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:19:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:19:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-566) Provide a
 short-circuit (for debugging purposes only) that does not use federation in
 JcrRepository
Message-ID: <1301748053.1259723976030.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Provide a short-circuit (for debugging purposes only) that does not use federation in JcrRepository
---------------------------------------------------------------------------------------------------

                 Key: DNA-566
                 URL: https://jira.jboss.org/jira/browse/DNA-566
             Project: DNA
          Issue Type: Feature Request
    Affects Versions: 0.6
            Reporter: Randall Hauch
             Fix For: 0.7


The JcrRepository implementation uses a shared repository source to persist the "/jcr:system" content that is common and shared amongst all workspaces in that repository, and it uses a federated repository to provide a unified view of the normal repository source and the system repository source (whereby the system content is projected into each of the workspace graphs).  This works really well, but it does complicate debugging (since the federated connector using a fork-join multi-threaded mechanism to parallelize the requests to the projected sources).

It would be nice to have a short-circuit that we can use during debugging that would make the JcrRepository _not_ use the federated connector, and instead to just directly use the repository source.  This does have implications, like the "/jcr:system" branch can't always be created in the underlying repository source (like the file system or SVN connectors).  In such cases, the short-circuit means that the JcrRepository.login(...) methods always fail because that method attempts to create the "/jcr:system" branch if it is not there.  Under normal circumstances, the JcrRepository creates the "/jcr:system" branch in the system repository source upon construction, and then upon JcrRepository.login(...) just obtains a connection via the federated connector.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:19:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:19:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-566) Provide a
 short-circuit (for debugging purposes only) that does not use federation in
 JcrRepository
In-Reply-To: <1301748053.1259723976030.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <931429053.1259723976056.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reassigned DNA-566:
---------------------------------

    Assignee: Randall Hauch


> Provide a short-circuit (for debugging purposes only) that does not use federation in JcrRepository
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-566
>                 URL: https://jira.jboss.org/jira/browse/DNA-566
>             Project: DNA
>          Issue Type: Feature Request
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> The JcrRepository implementation uses a shared repository source to persist the "/jcr:system" content that is common and shared amongst all workspaces in that repository, and it uses a federated repository to provide a unified view of the normal repository source and the system repository source (whereby the system content is projected into each of the workspace graphs).  This works really well, but it does complicate debugging (since the federated connector using a fork-join multi-threaded mechanism to parallelize the requests to the projected sources).
> It would be nice to have a short-circuit that we can use during debugging that would make the JcrRepository _not_ use the federated connector, and instead to just directly use the repository source.  This does have implications, like the "/jcr:system" branch can't always be created in the underlying repository source (like the file system or SVN connectors).  In such cases, the short-circuit means that the JcrRepository.login(...) methods always fail because that method attempts to create the "/jcr:system" branch if it is not there.  Under normal circumstances, the JcrRepository creates the "/jcr:system" branch in the system repository source upon construction, and then upon JcrRepository.login(...) just obtains a connection via the federated connector.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:29:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:29:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-566) Provide a
 short-circuit (for debugging purposes only) that does not use federation in
 JcrRepository
In-Reply-To: <1301748053.1259723976030.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1983753564.1259724569656.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-566:
------------------------------

    Component/s: Federation
                 JCR


> Provide a short-circuit (for debugging purposes only) that does not use federation in JcrRepository
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-566
>                 URL: https://jira.jboss.org/jira/browse/DNA-566
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Federation, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> The JcrRepository implementation uses a shared repository source to persist the "/jcr:system" content that is common and shared amongst all workspaces in that repository, and it uses a federated repository to provide a unified view of the normal repository source and the system repository source (whereby the system content is projected into each of the workspace graphs).  This works really well, but it does complicate debugging (since the federated connector using a fork-join multi-threaded mechanism to parallelize the requests to the projected sources).
> It would be nice to have a short-circuit that we can use during debugging that would make the JcrRepository _not_ use the federated connector, and instead to just directly use the repository source.  This does have implications, like the "/jcr:system" branch can't always be created in the underlying repository source (like the file system or SVN connectors).  In such cases, the short-circuit means that the JcrRepository.login(...) methods always fail because that method attempts to create the "/jcr:system" branch if it is not there.  Under normal circumstances, the JcrRepository creates the "/jcr:system" branch in the system repository source upon construction, and then upon JcrRepository.login(...) just obtains a connection via the federated connector.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:29:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:29:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-566) Provide a
 short-circuit (for debugging purposes only) that does not use federation in
 JcrRepository
In-Reply-To: <1301748053.1259723976030.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1835526270.1259724569628.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-566:
-----------------------------------

I created a package-level static final boolean WORKSPACES_SHARE_SYSTEM_BRANCH flag that may be changed to false when debugging so that the federated connector is not used.  As stated above, this has implications for some connectors, and definitely cannot be changed in production without having some potentially serious deviations from JCR spec behavior with respect to the '/jcr:system' branch.  However, it is very useful while debugging certain situations.

I added a new unit test to check that the flag is 'true', and this should always pass (except when debugging).  This helps ensure that the value is not accidentally committed to SVN with a value of 'false'.

> Provide a short-circuit (for debugging purposes only) that does not use federation in JcrRepository
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-566
>                 URL: https://jira.jboss.org/jira/browse/DNA-566
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Federation, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> The JcrRepository implementation uses a shared repository source to persist the "/jcr:system" content that is common and shared amongst all workspaces in that repository, and it uses a federated repository to provide a unified view of the normal repository source and the system repository source (whereby the system content is projected into each of the workspace graphs).  This works really well, but it does complicate debugging (since the federated connector using a fork-join multi-threaded mechanism to parallelize the requests to the projected sources).
> It would be nice to have a short-circuit that we can use during debugging that would make the JcrRepository _not_ use the federated connector, and instead to just directly use the repository source.  This does have implications, like the "/jcr:system" branch can't always be created in the underlying repository source (like the file system or SVN connectors).  In such cases, the short-circuit means that the JcrRepository.login(...) methods always fail because that method attempts to create the "/jcr:system" branch if it is not there.  Under normal circumstances, the JcrRepository creates the "/jcr:system" branch in the system repository source upon construction, and then upon JcrRepository.login(...) just obtains a connection via the federated connector.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:36:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:36:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-566) Provide a
 short-circuit (for debugging purposes only) that does not use federation in
 JcrRepository
In-Reply-To: <1301748053.1259723976030.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <145307358.1259724989670.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-566.
-------------------------------

    Resolution: Done


> Provide a short-circuit (for debugging purposes only) that does not use federation in JcrRepository
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-566
>                 URL: https://jira.jboss.org/jira/browse/DNA-566
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Federation, JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> The JcrRepository implementation uses a shared repository source to persist the "/jcr:system" content that is common and shared amongst all workspaces in that repository, and it uses a federated repository to provide a unified view of the normal repository source and the system repository source (whereby the system content is projected into each of the workspace graphs).  This works really well, but it does complicate debugging (since the federated connector using a fork-join multi-threaded mechanism to parallelize the requests to the projected sources).
> It would be nice to have a short-circuit that we can use during debugging that would make the JcrRepository _not_ use the federated connector, and instead to just directly use the repository source.  This does have implications, like the "/jcr:system" branch can't always be created in the underlying repository source (like the file system or SVN connectors).  In such cases, the short-circuit means that the JcrRepository.login(...) methods always fail because that method attempts to create the "/jcr:system" branch if it is not there.  Under normal circumstances, the JcrRepository creates the "/jcr:system" branch in the system repository source upon construction, and then upon JcrRepository.login(...) just obtains a connection via the federated connector.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  1 22:58:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 1 Dec 2009 22:58:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-536) Develop Update Site
	Website
In-Reply-To: <717460463.1254756769197.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <15308887.1259726309704.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-536:
-----------------------------------

Serge, Is there a reason you suggested http://www.jboss.org/dna/downloads/eclipse-update-sites.html ?

When we changed over to the new project site, the downloads were moved to http://downloads.jboss.org/jbossdna/ (for example http://downloads.jboss.org/jbossdna/0.6/jboss-dna-0.6-gettingstarted-examples.zip).  JBoss.org automatically provides download metrics for artifacts on http://downloads.jboss.org, so it'd be useful to have the actual update site be at http://downloads.jboss.org/jbossdna/updatesite/<versionOrLatest>. Note that the last URL would have a readable HTML page that should point to the installation instructions (something akin to http://www.jboss.org/tools/download/update.html).

This is the same pattern that JBoss Tools uses: a page at http://www.jboss.org/tools/download.html that describes the different update sites that are actually available at URLs like http://download.jboss.org/jbosstools/updates/stable/

> Develop Update Site Website
> ---------------------------
>
>                 Key: DNA-536
>                 URL: https://jira.jboss.org/jira/browse/DNA-536
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             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  Wed Dec  2 09:26:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 2 Dec 2009 09:26:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
In-Reply-To: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1967047550.1259763989755.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-563:
------------------------------

    Priority: Blocker  (was: Major)


Dan summarized what was in the JCR specifications:

The requirements for generating events for children of nodes that have been added/removed/moved/copied seems to be different between JCR 1.0 to JCR 2.0. For JCR 1.0 it seems these events are required. For JCR 2.0 it they are optional.

These 2 TCK observation tests are failing because of this:

NodeRemovedTest.testMultiNodesRemoved
WorkspaceOperationTest.testCopy

Here are the spec details:

1. JSR 170 1.0 (JCR 1.0 11 May 2005)

a. Section 8.3.7.1 Creating a new Node

... as well for each of the automatically created child nodes or properties (either NODE_ADDED or PROPERTY_ADDED, as the case may be).

b. Section 8.3.7.4 Removing a Child Node

... Additionally, an implementation should also generate a NODE_REMOVE or PROPERTY_REMOVE (as appropriate) for each item in the removed subtree.

c. Section 8.3.7.6 Copying a Subtree

... Additionally, an implementation should generate appropriate events for each resulting node and property addition in the copied subtree.

d Section 8.3.7.7 Moving a Subtree

... Additionally, an implementation should generate a NODE_REMOVE or PROPERTY_REMOVE (as appropriate) for each node and property removed from its source path location and a NODE_ADDED or PROPERTY_ADDED (as appropriate) for each node and property added at its destination path location.

e. Section 8.3.7.8 Re-ordering a set of Child Nodes

... Additionally, an implementation should generate appropriate events reflecting the "shifting over" of the node B and any nodes that come after it in the child node ordering. Each such shifted node would also produce a NODE_REMOVED and NODE_ADDED event pair with paths differing at most by a final index.

2. JSR 283 FCS (JCR 2.0 10 Aug 2009)- Section 12.2 Scope of Event Reporting

The scope of event reporting is implementation-dependent. An implementation
should make a best-effort attempt to report all events, but may exclude events if
reporting them would be impractical given implementation or resource limitations.
For example, on an import, move or remove of a subgraph containing a large
number of items, an implementation may choose to report only events associated
with the root node of the affected graph and not those for every subitem in the
structure.


> Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-563
>                 URL: https://jira.jboss.org/jira/browse/DNA-563
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.
> See JBoss forum referenced below for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  2 09:26:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 2 Dec 2009 09:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
In-Reply-To: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <716387229.1259763990006.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-563:
------------------------------

    Comment: was deleted


> Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-563
>                 URL: https://jira.jboss.org/jira/browse/DNA-563
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.
> See JBoss forum referenced below for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  2 10:34:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Wed, 2 Dec 2009 10:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-456) Add JSR-170
 Observation Optional Feature
In-Reply-To: <29781241.1244747516423.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1187394877.1259768069904.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian commented on DNA-456:
---------------------------------

After applying the patches uploaded on 1 Dec 09 to the workspace, there are problems running the JcrTckTest (the version of this file in the patch) unit test. If you modify JcrTckTest to ONLY run the observation tests, all the tests pass. Once you add back either/or both of the LevelOneFeatureTests and LevelTwoFeatureTests some observation tests begin to fail. And it is not always the same tests that fail.

This same type of behavior occurs when running a full mvn build. Tests in JcrObservationManagerTest and JcrTckTest. Again, different tests fail each time a build is run.

Also, SequencingServiceTest.shouldExecuteSequencersUponChangesToRepositoryThatMatchSequencerPathExpressions() is failing. I have annotated this test with @Ignore so it will not execute during the build. 


> 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
>
>         Attachments: DNA-456-dna-graph.patch, DNA-456-dna-jcr.patch, DNA-456-dna-repository.patch
>
>
> 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  Wed Dec  2 15:35:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 2 Dec 2009 15:35:30 -0500 (EST)
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: <470643287.1259786130355.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=12497836#action_12497836 ] 

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

Added a new AccessQueryRequest and support in the RequestProcessor and its implementations.  The Graph API now provides methods for submitting queries (in the form of QueryCommand objects) and full-text searches to the underlying graph and its connector.  The Graph.query(QueryCommand,Schemata) method runs the query through the QueryEngine, which plans, replaces views, optimizes, validates, and executes the query.  The QueryEngine (with the Graph's tailored Processor implementation) generates a single AccessQueryRequest for each of the low-level access queries.  Access queries are usually SELECTs against a single table, after all of the view replacement and optimization has been performed.  These access queries are submitted to the connector in a single batch for each high-level query), ensuring that a query sees only consistent results.


> 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: JCR, Query, Search
>    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  Wed Dec  2 16:13:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 2 Dec 2009 16:13:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <148087972.1259788409669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-546:
--------------------------------

    Attachment: DNA-546_mostly_working.patch


Attached patch (DNA-546_mostly_working.patch) that provides a mostly working implementation of a new model for the JPA connector.  The model passed all of the connector reading and writing tests except for a single test that tracks graph-level references.  This is not surprising as the only outstanding feature on the model is the equivalent of the ReferenceEntity and referentialIntegrityEnforced code in the Basic model.  I have overridden that test for now so that the CI build will work.

This patch also does not include a TCK integration test.  That is because it will not pass the TCK integration test unless the JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH is set to false.  When the flag is set to false, the same L1, L2, and locking TCK tests pass for this connector as pass for (as an example) the InMemoryRepository.  However, this flag manifestly cannot be changed to false in a production environment, so sorting out this issue is a major priority.

> 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
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_mostly_working.patch, DNA-546_simple_model_WIP.patch
>
>
> 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  Wed Dec  2 16:42:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 2 Dec 2009 16:42:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1496883434.1259790149707.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-546:
--------------------------------

    Attachment: DNA-546_tck_test.patch


Attached patch that adds TCK integration tests for new JPA connector model.  I am not committing this patch at this time because these tests pass consistently and in their entirety if and only if JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH is set to false.

> 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
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_mostly_working.patch, DNA-546_simple_model_WIP.patch, DNA-546_tck_test.patch
>
>
> 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  Wed Dec  2 17:35:30 2009
From: jira-events at lists.jboss.org (Tom Ruff (JIRA))
Date: Wed, 2 Dec 2009 17:35:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-567) missing word in
	documentation
Message-ID: <162154950.1259793330507.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

missing word in documentation
-----------------------------

                 Key: DNA-567
                 URL: https://jira.jboss.org/jira/browse/DNA-567
             Project: DNA
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 0.6
            Reporter: Tom Ruff


section 5.3 of DNA reference guide, third paragraph down, last sentence states in part:

"and is an immutable interface patterned after the corresponding interface is JSR-170 and JSR-283. "

There should be a type specified as the second word in the above phrase with a link to its javadoc.  I'm not sure which type.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  3 08:24:17 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 3 Dec 2009 08:24:17 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-567) missing word in
	documentation
In-Reply-To: <162154950.1259793330507.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <389725349.1259846657172.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-567.
---------------------------------

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


I've confirmed that we had already cleaned this up in the trunk, but it is definitely broken in 0.6.

The trunk version of that paragraph reads:

"JBoss DNA properties can hold a wide range of value objects, including normal Java strings, names, paths, URIs, booleans, longs, doubles, decimals, binary content, dates, UUIDs, references to other nodes, or any other serializable object. All but three of these are the standard Java classes: dates are represented by an immutable DateTime class; binary content is represented by an immutable Binary  interface patterned after the proposed interface of the same name in JSR-283; and Reference is an immutable interface patterned after the corresponding interface is JSR-170 and JSR-283."

Thanks for catching this!  Please let us know if you find any other issues.

> missing word in documentation
> -----------------------------
>
>                 Key: DNA-567
>                 URL: https://jira.jboss.org/jira/browse/DNA-567
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Tom Ruff
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>
> section 5.3 of DNA reference guide, third paragraph down, last sentence states in part:
> "and is an immutable interface patterned after the corresponding interface is JSR-170 and JSR-283. "
> There should be a type specified as the second word in the above phrase with a link to its javadoc.  I'm not sure which type.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  3 15:17:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 3 Dec 2009 15:17:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-568)
 Observable.register(Observer) Contract Is Being Violated
Message-ID: <1805108419.1259871450454.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Observable.register(Observer) Contract Is Being Violated
--------------------------------------------------------

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


The Observable.register(Observable) method allows a null observable. When it is null the method should return false. These classes are violating that contract:

org.jboss.dna.repository.RepositoryLibrary
org.jboss.dna.graph.observe.ObservationBus
org.jboss.dna.jcr.JcrRepository#RepositoryObservationManager


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  3 15:47:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 3 Dec 2009 15:47:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <806125481.1259873250530.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-468:
-----------------------------------

Completed the integration and implementation of the JCR interfaces, meaning the implementation of the query functionality in the JCR layers should be complete.

HOWEVER, THE UNDERLYING CONNECTORS DO NOT YET SUPPORT QUERIES OR SEARCHES, SO THE JCR QUERY FUNCTIONALITY DOES NOT YET WORK.

Updated the JcrQueryManager implementation of javax.jcr.query.QueryManager to parse the queries using one of three languages: SQL, XPath, and free-text search.  The SQL language is really that spelled out in JCR 2.0, with enhancements to support UNION, INTERSECT, EXCEPT, IN clauses, additional join types, BETWEEN criteria, and the PATH(...) and DEPTH(...) functions for use on the left-hand side of criteria (e.g., dynamic operands).  The XPath language is that specified by JCR 1.0.  And the free-text search language just allows the client to submit a search expression that complies with the Section 6.7.19 of the JCR 2.0 specification (the same search grammar used in the JCR-JQOM 'FullTextSearch' criteria and the 'CONTAINS(...)' function in JCR-SQL2).

If the submitted query is valid and well-formed, a javax.jcr.query.Query object is created (using either JcrQuery or JcrSearch, depending upon the language).  When executed, the query/search is pushed down to the graph layer via the new Graph API methods.  The Graph then does its thing (like planning, validating, optimizing, and processing) by pushing down to the connector (as a single batch) the one or more AccessQueryRequest objects.  The connector then does its thing by computing the results for each the access query and setting the results on the request.  The graph's query engine uses these results and performs any additional operations (like joins, unions, ordering, or application of additional criteria that couldn't be pushed down) to produce the final results (in the form of the org.jboss.dna.graph.query.QueryResults).  Back in the JCR layer, the graph results are wrapped by a javax.jcr.query.QueryResult implementation (JcrQueryResult), where the client can access the javax.jcr.Node object for each row or the Value objects in each column of each Row.  

There are a couple of things to note about the QueryResult implementation.  First, because of the signature of the NodeIterator (specifically that the methods don't throw RepositoryException), accessing the nodes in the results is done when the NodeIterator is obtained.  In other words, the Nodes are fetched and loaded into the Session immediately when the 'QueryResult.getNodes()' method is called.  However, the RowIterator method signatures do throw RepositoryException, so the values are NOT loaded when 'QueryResult.getRows()' is called but are instead loaded lazily as the iterator is used.

Second, the QueryResult always returns the values cached in the Session, meaning that while transient changes within the Session are not used to evaluate criteria and determine the rows, the actual values of the rows DO come from the Session's transient state.  This behavior is spelled out in the specification.

Submitting the queries to the Graph API require supplying an implementation of the org.jboss.dna.graph.validate.Schemata interface.  This is used by the query engine to a) identify valid tables and columns by their names so that the submitted query can be resolved; b) to identify all selectable columns in a table when SELECT * is used; c) determine the appropriate datatype for each column appearing in the SELECT or WHERE clauses; and d) to obtain the definition of views so that use of views in a query plan can be replaced with the view's definition.

This commit includes an implementation of Schemata that is based upon the node types in the repository.  Each node should appear in all tables represented by its primary type, all supertypes of the primary type, all mixin types, and all supertypes of all mixin types.

Each non-mixin node type is represented as a VIEW defined with a query of the form:
  SELECT <propertyList> FROM __ALLNODES__ 
  WHERE [jcr:primaryType] IN (<nodeTypeName>,<subtypeNameList>)

Similarly, each mixin node type is represented as a VIEW defined with a query of the form:
  SELECT <propertyList> FROM __ALLNODES__ 
  WHERE [jcr:mixinTypes] IN (<nodeTypeName>,<subtypeNameList>)

In these queries, the '<propertyList>' is the comma-separated names of the single-valued, non-residual properties explicitly defined on the node type (and optionally all its supertypes).  Also, '<subtypeNameList>' is the comma-separated names of all node types that have the node type in question as a supertype.

It was pretty easy to create a Schemata implementation of the node types in the RepositoryNodeTypeManager (the master definition of node types for all workspaces in the repository). As NodeTypeSchemata is immutable, it can always be used to provide an immutable, consistent schemata for a query.  Additionally, it can continue to be reused until a node type changes in the RNTM, and the RNTM ensures this is so.  A NodeTypeSchemata is only created when needed by the QueryManager, and will be discarded any time node types are changed in the repository.

One twist, however, is that Schemata uses stringified names, not DNA Name objects.  And that means the Schemata is dependent upon the namespace mappings, and the NodeTypeSchemata is dependent upon the JcrRepository's context.  Each Session might have redefined some namespace mappings, and the queries are to use the session's namespace mappings.  So, NodeTypeSchemata provides a method to obtain a Schemata instance given a JcrSession instance, and this is what is used by QueryManager.  Obtaining a session-specific schemata could be expensive, so this method does a couple of cool tricks to minimize the time required to build the session-specific schemata.  First, if the JcrSession doesn't actually redefine _any_ namespace mappings, or it doesn't redefine any of the namespace mappings for namespaces used in the node types, or if the namespace mappings for those namespaces used in the node types are unchanged, the NodeTypeSchemata can be used as is.  In all other cases, a session-specific Schemata must be created (and must be thown out if any namespace mappings are changed in the session).

But, unlike the NodeTypeSchemata (which creates views for all node types preemptively), the session-specific Schemata implementations are lazy.  The theory is that a single query may not involve that many tables, so it's not worth defining all views.

It should also be noted that the Lucene integration stores properties and paths in a manner that is dependent upon the namespace URI, and not the prefix.  The search engine uses the ExecutionContext in which each query is being performed to transform the Schemata names back into the prefix-independent form, prior to working with the indexed content.

This whole system appears to work very well so far.  Again, work still needs to be done at the connector-level to support FullTextSearchRequest and AccessQueryRequest types.  That's next.


> Add XPath query language support
> --------------------------------
>
>                 Key: DNA-468
>                 URL: https://jira.jboss.org/jira/browse/DNA-468
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Query, Search
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Create an XPath language binding for our graph model, so that we can parse XPath queries and produce query models that can then be executed.
> This can probably be done as a separate project dependent upon dna-graph, perhaps in the extensions folder (since it'd be a query language extension).  Maybe "extensions/dna-query-xpath"?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  3 17:03:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Thu, 3 Dec 2009 17:03:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-556) Need a graph-specific
 SequencerOutput class to simplify testing sequencer results.
In-Reply-To: <498100892.1259012856344.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1623925361.1259877809611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-556:
-----------------------------


moved GraphSequencerOutput.java to src/test/java

> Need a graph-specific SequencerOutput class to simplify testing sequencer results.
> ----------------------------------------------------------------------------------
>
>                 Key: DNA-556
>                 URL: https://jira.jboss.org/jira/browse/DNA-556
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, Sequencers
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While developing the test for the DdlSequencer, it would be beneficial to create a simplified graph oriented SequencerOutput class that provided 1) simple setProperty() and setReference() methods and performed a batched request.

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

        

From jira-events at lists.jboss.org  Thu Dec  3 17:03:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Thu, 3 Dec 2009 17:03:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-556) Need a graph-specific
 SequencerOutput class to simplify testing sequencer results.
In-Reply-To: <498100892.1259012856344.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <792884969.1259877809631.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond resolved DNA-556.
------------------------------

    Resolution: Done


> Need a graph-specific SequencerOutput class to simplify testing sequencer results.
> ----------------------------------------------------------------------------------
>
>                 Key: DNA-556
>                 URL: https://jira.jboss.org/jira/browse/DNA-556
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, Sequencers
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While developing the test for the DdlSequencer, it would be beneficial to create a simplified graph oriented SequencerOutput class that provided 1) simple setProperty() and setReference() methods and performed a batched request.

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

        

From jira-events at lists.jboss.org  Thu Dec  3 17:10:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Thu, 3 Dec 2009 17:10:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-569) Enhance Graph.java's
 Subgraph object toString() method to show recursive node structure and
 properties.
Message-ID: <69290190.1259878230193.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Enhance Graph.java's Subgraph object toString() method to show recursive node structure and properties.
-------------------------------------------------------------------------------------------------------

                 Key: DNA-569
                 URL: https://jira.jboss.org/jira/browse/DNA-569
             Project: DNA
          Issue Type: Bug
          Components: Graph
    Affects Versions: 0.7
            Reporter: Barry LaFond
             Fix For: 0.7


While developing DdlSequencer tests, a need developed obtain a sub-graph of the sequenced DDL file and operate on the resultant nodes and properties. However, the Sub-graph was difficult to debug because viewing child nodes and properties were difficult to see in values view.

By constructing a more descriptive/recursive toString() value for subgraph, it would make debugging and testing much easier.

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

        

From jira-events at lists.jboss.org  Thu Dec  3 17:10:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Thu, 3 Dec 2009 17:10:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-569) Enhance Graph.java's
 Subgraph object toString() method to show recursive node structure and
 properties.
In-Reply-To: <69290190.1259878230193.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <725175663.1259878230217.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond reassigned DNA-569:
--------------------------------

    Assignee: Barry LaFond


> Enhance Graph.java's Subgraph object toString() method to show recursive node structure and properties.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-569
>                 URL: https://jira.jboss.org/jira/browse/DNA-569
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While developing DdlSequencer tests, a need developed obtain a sub-graph of the sequenced DDL file and operate on the resultant nodes and properties. However, the Sub-graph was difficult to debug because viewing child nodes and properties were difficult to see in values view.
> By constructing a more descriptive/recursive toString() value for subgraph, it would make debugging and testing much easier.

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

        

From jira-events at lists.jboss.org  Fri Dec  4 01:45:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 4 Dec 2009 01:45:29 -0500 (EST)
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: <505723440.1259909129644.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:
------------------------------

    Attachment: DNA-456-fix-concurrency-issues.patch


I've attached a patch that fixes all of the problems, so now all of the Observation tests should be passing (except for the still missing deep events upon delete and clone).

The major problem was in how the JcrRepository.RepositoryObservationManager.notify(...) method was behaving.  This Observer is actually listening to the RepositoryLibrary's ObservationBus instance, which is the observer for all of the RepositorySource objects, and the 'notify(...)' method is being called within the same thread as the RepositorySource is processing the requests (and firing the Changes).  The whole purpose of the JcrRepository.RepositoryObservationManager is to quickly enqueue the Changes for processing in another thread, to get off of the thread used by the connector (so the request processing can be completed).  It turns out that the 'notify(...)' method was passing the list of session observers into the Runnable.  BUT THIS LIST CHANGES WHENEVER A NEW JCR LISTENER IS ADDED OR REMOVED. As a result, the changes may get sent to listeners that were registered AFTER the save().  This is the whole reason why the timestamp checking (originally) and ObservedId (more recently) were needed.

The fix was pretty simple.  Rather than pass the list of session observers to the Runnable, the RepositoryObservationManager should grab a snapshot of the list.  This is trivial to do, since the list is a CopyOnWriteArrayList: simply get an Iterator<Observer> from the list and pass THAT to the Runnable.  Thus, the snapshot of the observer list is made within the same thread where the connector is running, which is within the context of the save().  Any listener added after the save completes will not be in the snapshot used to fire off the changes.

In other words, instead of this:

            final List<Observer> observersList = observers;
            Runnable sender = new Runnable() {
                public void run() {
                    for (Observer observer: observersList ) {
                        observer.notify(changes);
                    }
                }
            };
            this.observerService.execute(sender);

the method should be this:

            final Iterator<Observer> observerIterator = observers.iterator();
            Runnable sender = new Runnable() {
                public void run() {
                    while (observerIterator.hasNext()) {
                        Observer observer = observerIterator.next();
                        observer.notify(changes);
                    }
                }
            };
            this.observerService.execute(sender);

Another improvement was added to the 'notify(...)' method.  Since the JcrRepository only cares about one source (usually the federated source), it can safely ignore all Changes objects that are from other sources.  Doing this saves work being added to the worker queue.

After this change was made, there was no more need for the ObservedId, so that (and all uses of it) was removed.

One minor problem was that SetPropertyRequest.setNewProperty(boolean) was always setting the 'is new' property to true, rather than to the supplied value.  This was always resulting in a PROPERTY_ADDED event rather than a PROPERTY_CHANGED when the property is not new.

Another issue was that the Federated Connector was not always firing the events in the correct order.  I don't think this mattered in the results, but this was fixed.

Finally, the tests in the sequencer examples were failing because the SequencingService was processing the NetChange.getModifiedProperties().  Obviously this missed any ADDED property.  Therefore, a 'getAddOrModifiedProperties()' method was added to the NetChange class, and the SequencingService changed to use this method.

These changes were committed, and the recently ignored tests were added back in.

> 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
>
>         Attachments: DNA-456-dna-graph.patch, DNA-456-dna-jcr.patch, DNA-456-dna-repository.patch, DNA-456-fix-concurrency-issues.patch
>
>
> 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 Dec  4 02:04:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 4 Dec 2009 02:04:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
In-Reply-To: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1451948049.1259910269589.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-563:
-----------------------------------

This is a blocker for DNA-456 (Observation feature).  Be sure to uncomment all the remaining observation-related unit and TCK tests.

> Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-563
>                 URL: https://jira.jboss.org/jira/browse/DNA-563
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.
> See JBoss forum referenced below for more information.

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


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

Randall Hauch commented on DNA-456:
-----------------------------------

The build failed again in JcrObservationManagerTest, and so I re-ran the tests about 10x before I got the failure locally.  After some debugging, I noticed that when it failed, all of the missing events appear to be the last event, so I poked around the TestListener.waitForEvents() method, which calls 'await(...)' on a CountDownLatch that is decremented in the 'onEvent(...)' method.  The 'latch.countDown()' method was being called (and potentially the 'waitForEvents()' method returning) immediately after 'itr.nextEvent()' and before the event was added to the TestListener's state.  Of course, whether the 'waitForEvents()' method returns before or after the event info is added depends completely on thread scheduling.  This would explain how it frequently worked on some machines but frequently failed on others.

I put the whole content of the while loop in the 'onEvent(...)' method in a try-finally block, and moved the 'latch.countDown()' method to the finally.  I ran several tests locally with no failures, but I'll commit to see if they pass on the build box.

> 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
>
>         Attachments: DNA-456-dna-graph.patch, DNA-456-dna-jcr.patch, DNA-456-dna-repository.patch, DNA-456-fix-concurrency-issues.patch
>
>
> 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 Dec  4 02:51:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 4 Dec 2009 02:51:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-456) Add JSR-170
 Observation Optional Feature
In-Reply-To: <29781241.1244747516423.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1200457525.1259913089600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-456:
-----------------------------------

Just got a clean build, so I'm hoping this fix actually worked.  Let's hope that we don't see these failures pop up anymore. Meanwhile, this issue still needs a resolution for DNA-563.

> 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
>
>         Attachments: DNA-456-dna-graph.patch, DNA-456-dna-jcr.patch, DNA-456-dna-repository.patch, DNA-456-fix-concurrency-issues.patch
>
>
> 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 Dec  4 07:51:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 4 Dec 2009 07:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-568)
 Observable.register(Observer) Contract Is Being Violated
In-Reply-To: <1805108419.1259871450454.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1717084175.1259931090164.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-568.
-----------------------------

    Resolution: Done


Changed the following classes so that they return false when a null observable is passed in to the register method:

org.jboss.dna.repository.RepositoryLibrary
org.jboss.dna.graph.observe.MockObservable
org.jboss.dna.graph.observe.ObservationBus
org.jboss.dna.jcr.JcrRepository#RepositoryObservationManager 

> Observable.register(Observer) Contract Is Being Violated
> --------------------------------------------------------
>
>                 Key: DNA-568
>                 URL: https://jira.jboss.org/jira/browse/DNA-568
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The Observable.register(Observable) method allows a null observable. When it is null the method should return false. These classes are violating that contract:
> org.jboss.dna.repository.RepositoryLibrary
> org.jboss.dna.graph.observe.ObservationBus
> org.jboss.dna.jcr.JcrRepository#RepositoryObservationManager

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


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

Brian Carothers updated DNA-546:
--------------------------------

    Attachment: concurrency_issue.patch


I am still hitting semi-random failures in the TCK test if awaitAllSubtasks is false in FederatedRepositoryConnector.execute(...) and the JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH flag is set to true.

I have added some logging to the SimpleJpaRequestProcessor to see what's going on, and it looks like requests are getting interleaved.  For example, I get the following SetPropertyRequest and the adjacent read request executing at the same time:

08:55:29,250 [pool-3-thread-1] Executing [CompositeRequest (1)
	set property {}prop1 on </{}testroot/{}node1 && [{http://www.jboss.org/dna/1.0}uuid = 3954dafa-8367-47f0-a421-0a28a529b73f]> in the "default" workspace to [org.jboss.dna.graph.property.basic.InMemoryBinary at 25b64dbinary[0] with hash 2jmj7l5rSw0yVb/vlWAYkK/YBwk=]]
08:55:29,250 [pool-3-thread-3] Executing [CompositeRequest (3)
	read node at / in the "default" workspace
	read node at /{}testroot in the "default" workspace
	read node at /{}testroot/{}node1 in the "default" workspace]
08:55:29,250 [pool-3-thread-3] Executed [CompositeRequest (3)
	read node at / in the "default" workspace
	read node at /{}testroot in the "default" workspace
	read node at /{}testroot/{}node1 in the "default" workspace]
08:55:29,250 [pool-3-thread-3] Closing request processor
08:55:29,250 [pool-3-thread-3] Closed request processor
08:55:29,250 [pool-3-thread-1] Executed [CompositeRequest (1)
	set property {}prop1 on </{}testroot/{}node1 && [{http://www.jboss.org/dna/1.0}uuid = 3954dafa-8367-47f0-a421-0a28a529b73f]> in the "default" workspace to [org.jboss.dna.graph.property.basic.InMemoryBinary at 25b64dbinary[0] with hash 2jmj7l5rSw0yVb/vlWAYkK/YBwk=]]
08:55:29,250 [pool-3-thread-1] Closing request processor
08:55:29,250 [pool-3-thread-1] Closed request processor

Note how the set property request starts to execute on /testroot/node1, then a read request for /testroot/node1 starts and completes before the set property request completes.  Since the read is part of a test to see if the property was set or cleared, the test often fails.

This can be reproduced by running the SimpleJpaRepositoryTckText (added in the attached patch).  It runs the SetValueBinaryTest case, consisting of 4 tests.  Typical runs on my laptop produce 0-4 errors (usually 1-3), although YMMV based on local performance.  Please note that the read and the set are coming from the same thread.

> 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
>             Fix For: 0.7
>
>         Attachments: concurrency_issue.patch, DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_mostly_working.patch, DNA-546_simple_model_WIP.patch, DNA-546_tck_test.patch
>
>
> 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 Dec  4 14:20:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 4 Dec 2009 14:20:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-570)
 JcrObservationManager's Logic For Filtering Events Based On Node Types Is
 Incorrect
Message-ID: <1328220643.1259954429670.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect
-----------------------------------------------------------------------------------

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


The logic was determining if the Event node's primary type or mixins were equal to or derived from one or more given types. This was backwards and was allowing too many events to get through. The logic should check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Changes to JcrNodeManager and JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 14:29:36 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 4 Dec 2009 14:29:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-571)
 JcrObservationManager's Logic For Filtering Events Based On Path Is
 Incorrect For Property Events
Message-ID: <1348896281.1259954976254.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JcrObservationManager's Logic For Filtering Events Based On Path Is Incorrect For Property Events
-------------------------------------------------------------------------------------------------

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


The logic for filtering events based on the event path is incorrect for property events. Instead of using the property's node's parent it needs to use the node path. Changes to JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 15:22:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:22:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-572)
 FederatedRepositoryConnection Can Freeze When Exception Thrown from
 RepositoryConnection.execute(...)
Message-ID: <1681354438.1259958149600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

FederatedRepositoryConnection Can Freeze When Exception Thrown from RepositoryConnection.execute(...)
-----------------------------------------------------------------------------------------------------

                 Key: DNA-572
                 URL: https://jira.jboss.org/jira/browse/DNA-572
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Federation
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Priority: Minor
             Fix For: Future Releases


If a runtime exception is thrown from with a RepositoryConnection.execute method, the FederatedRepositoryConnector can get stuck waiting infinitely for a countdown latch on the FederatedRequest. 
 The stack trace for the blocked main thread follows:

Thread [main] (Suspended)	
	Unsafe.park(boolean, long) line: not available [native method]	
	LockSupport.park(Object) line: 158	
	CountDownLatch$Sync(AbstractQueuedSynchronizer).parkAndCheckInterrupt() line: 747	
	CountDownLatch$Sync(AbstractQueuedSynchronizer).doAcquireSharedInterruptibly(int) line: 905	
	CountDownLatch$Sync(AbstractQueuedSynchronizer).acquireSharedInterruptibly(int) line: 1217	
	CountDownLatch.await() line: 207	
	FederatedRequest.await() line: 97	
	JoinRequestProcessor.process(BlockingQueue<FederatedRequest>) line: 141	
	FederatedRepositoryConnection.execute(ExecutionContext, Request) line: 221	
	Graph.execute(Request) line: 267	
	Graph$Batch.execute() line: 4592	
	GraphSession<Payload,PropertyPayload>.save() line: 813	
	SessionCache.save() line: 374	
	JcrSession.save() line: 876	
	SetPropertyStringTest.testSetNullStringArray() line: 362	
	NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]	
	NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39	
	DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25	
	Method.invoke(Object, Object...) line: 597	
	SetPropertyStringTest(TestCase).runTest() line: 168	
	SetPropertyStringTest(TestCase).runBare() line: 134	
	TestResult$1.protect() line: 110	
	JCRTestResult(TestResult).runProtected(Test, Protectable) line: 128	
	JCRTestResult(TestResult).run(TestCase) line: 113	
	SetPropertyStringTest(TestCase).run(TestResult) line: 124	
	SetPropertyStringTest(AbstractJCRTest).run(TestResult) line: 406	
	TestSuite.runTest(Test, TestResult) line: 232	
	TestSuite.run(TestResult) line: 227	
	TestSuite.runTest(Test, TestResult) line: 232	
	TestSuite.run(TestResult) line: 227	
	AllTests(JUnit38ClassRunner).run(RunNotifier) line: 81	
	JUnit4TestClassReference(JUnit4TestReference).run(TestExecution) line: 46	
	TestExecution.run(ITestReference[]) line: 38	
	RemoteTestRunner.runTests(String[], String, TestExecution) line: 467	
	RemoteTestRunner.runTests(TestExecution) line: 683	
	RemoteTestRunner.run() line: 390	
	RemoteTestRunner.main(String[]) line: 197	

This condition can be reproduced by forcing a NullPointerException in the execute method of a connection (e.g., the SimpleJpaConnection). 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 15:24:35 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:24:35 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-573)
 FederatedRepositoryConnection Can Interleave Successive Requests
Message-ID: <16881569.1259958275144.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

FederatedRepositoryConnection Can Interleave Successive Requests
----------------------------------------------------------------

                 Key: DNA-573
                 URL: https://jira.jboss.org/jira/browse/DNA-573
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Federation
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Randall Hauch
            Priority: Critical


The FederatedRepositoryConnection is returning before all of the federated connections are closed.  This creates the potential for a race condition between adjacent calls to the federated repository.

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

        

From jira-events at lists.jboss.org  Fri Dec  4 15:30:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-573)
 FederatedRepositoryConnection Can Interleave Successive Requests
In-Reply-To: <16881569.1259958275144.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1239405180.1259958629656.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-573:
--------------------------------

    Attachment: DNA-573.patch


Randall came up with the attached patch that forces the FRC to wait for all requests to be fully processed before returning.  This corrects the defect.

> FederatedRepositoryConnection Can Interleave Successive Requests
> ----------------------------------------------------------------
>
>                 Key: DNA-573
>                 URL: https://jira.jboss.org/jira/browse/DNA-573
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Federation
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-573.patch
>
>
> The FederatedRepositoryConnection is returning before all of the federated connections are closed.  This creates the potential for a race condition between adjacent calls to the federated repository.

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

        

From jira-events at lists.jboss.org  Fri Dec  4 15:30:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-573)
 FederatedRepositoryConnection Can Interleave Successive Requests
In-Reply-To: <16881569.1259958275144.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <58725293.1259958629681.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-573.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Committed patch to resolve defect.

> FederatedRepositoryConnection Can Interleave Successive Requests
> ----------------------------------------------------------------
>
>                 Key: DNA-573
>                 URL: https://jira.jboss.org/jira/browse/DNA-573
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Federation
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-573.patch
>
>
> The FederatedRepositoryConnection is returning before all of the federated connections are closed.  This creates the potential for a race condition between adjacent calls to the federated repository.

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

        

From jira-events at lists.jboss.org  Fri Dec  4 15:32:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:32:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-574)
 SetPropertyRequest.toString() Can Throw a NullPointerException
Message-ID: <2114611853.1259958749580.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

SetPropertyRequest.toString() Can Throw a NullPointerException
--------------------------------------------------------------

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


I added an innocuous looking toString "enhancement" for SetPropertyRequest a week or two ago that throws an NPE if one is setting the property to null (i.e., removing the property).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 15:34:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-574)
 SetPropertyRequest.toString() Can Throw a NullPointerException
In-Reply-To: <2114611853.1259958749580.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1934100882.1259958869786.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-574:
--------------------------------

    Attachment: DNA-574.patch


Attached patch that makes SetPropertyRequest.toString null-safe and adds a better toString method for CompositeRequest.

> SetPropertyRequest.toString() Can Throw a NullPointerException
> --------------------------------------------------------------
>
>                 Key: DNA-574
>                 URL: https://jira.jboss.org/jira/browse/DNA-574
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-574.patch
>
>
> I added an innocuous looking toString "enhancement" for SetPropertyRequest a week or two ago that throws an NPE if one is setting the property to null (i.e., removing the property).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 15:34:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-574)
 SetPropertyRequest.toString() Can Throw a NullPointerException
In-Reply-To: <2114611853.1259958749580.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1532850457.1259958869816.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-574.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Committed patch to resolve defect

> SetPropertyRequest.toString() Can Throw a NullPointerException
> --------------------------------------------------------------
>
>                 Key: DNA-574
>                 URL: https://jira.jboss.org/jira/browse/DNA-574
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-574.patch
>
>
> I added an innocuous looking toString "enhancement" for SetPropertyRequest a week or two ago that throws an NPE if one is setting the property to null (i.e., removing the property).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  4 15:38:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:38:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-575) JoinRequestProcessor
 Enters Infinite Loop if VerifyWorkspaceRequest Has Error
In-Reply-To: <1484971586.1259959109830.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <533123223.1259959109919.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-575:
--------------------------------

    Attachment: DNA-575.patch


Attached patch that sets the error on the original request and then returns from the process method instead of continuing infinitely.

> JoinRequestProcessor Enters Infinite Loop if VerifyWorkspaceRequest Has Error
> -----------------------------------------------------------------------------
>
>                 Key: DNA-575
>                 URL: https://jira.jboss.org/jira/browse/DNA-575
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Federation
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-575.patch
>
>
> If any part of a federated VerifyWorkspaceRequest throws an error in the source VerifyNodeExistsRequest, the processor will enter into an infinite loop (it will continue the loop without moving to the next source request).

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

        

From jira-events at lists.jboss.org  Fri Dec  4 15:38:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:38:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-575) JoinRequestProcessor
 Enters Infinite Loop if VerifyWorkspaceRequest Has Error
Message-ID: <1484971586.1259959109830.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JoinRequestProcessor Enters Infinite Loop if VerifyWorkspaceRequest Has Error
-----------------------------------------------------------------------------

                 Key: DNA-575
                 URL: https://jira.jboss.org/jira/browse/DNA-575
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Federation
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
         Attachments: DNA-575.patch

If any part of a federated VerifyWorkspaceRequest throws an error in the source VerifyNodeExistsRequest, the processor will enter into an infinite loop (it will continue the loop without moving to the next source request).

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

        

From jira-events at lists.jboss.org  Fri Dec  4 15:40:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 15:40:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-575) JoinRequestProcessor
 Enters Infinite Loop if VerifyWorkspaceRequest Has Error
In-Reply-To: <1484971586.1259959109830.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <526225793.1259959229587.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-575.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Committed patch to resolve defect.

> JoinRequestProcessor Enters Infinite Loop if VerifyWorkspaceRequest Has Error
> -----------------------------------------------------------------------------
>
>                 Key: DNA-575
>                 URL: https://jira.jboss.org/jira/browse/DNA-575
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Federation
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-575.patch
>
>
> If any part of a federated VerifyWorkspaceRequest throws an error in the source VerifyNodeExistsRequest, the processor will enter into an infinite loop (it will continue the loop without moving to the next source request).

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

        

From jira-events at lists.jboss.org  Fri Dec  4 21:43:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 21:43:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-547) TCK Tests for Locking
 and Moving Nodes Fail for JPA Connector
In-Reply-To: <110540148.1256938805728.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <524909513.1259981009601.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-547.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


As with DNA-546, the root cause for this issue is the Basic JPA model's use of the node UUID as a component of the primary key.  This makes it impossible to have two nodes in the same workspace with the same UUID in the JPA session at the same time, even if one copy is deleted before the other is created.  

The Simple JPA model changes the primary key for the node entity and avoids this issue entirely.  As the Simple model now passes all of the same TCK tests as the other writable connectors, the fix for this defect is to switch from the simple model to the basic model.

> 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
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>
> 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

        

From jira-events at lists.jboss.org  Fri Dec  4 21:50:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 21:50:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-576) SImple JPA Model Does
 Not Support Transparent Referential Integrity
Message-ID: <1391252535.1259981430273.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

SImple JPA Model Does Not Support Transparent Referential Integrity
-------------------------------------------------------------------

                 Key: DNA-576
                 URL: https://jira.jboss.org/jira/browse/DNA-576
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Priority: Optional
             Fix For: Future Releases


One feature in the basic model that has not yet been carried forward into the simple model is the ability to store references from one node to another in a transparent entity external to the node entity.  This allows for database foreign keys to help enforce referential integrity at the graph level.  However, since the primary consumer of DNA graph information at this time is the JCR layer, it may not be necessary to add this feature (and its associated performance cost at this time).

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

        

From jira-events at lists.jboss.org  Fri Dec  4 21:52:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 21:52:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <905552590.1259981549624.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-546:
--------------------------------

    Attachment: DNA-546_final.patch


Attached patch that cleans up the simple JPA model by fixing the last broken test, removing semi-implemented referential integrity checks, adding copyright headers to a number of files, and adding a full TCK integration test.

At this point, the simple model passes all of the TCK tests (including the workspace and session import tests) and the recommended fix/workaround for users who need to import things into a JPA-backed repository is to use the simple model instead of the basic model. 

> 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
>             Fix For: 0.7
>
>         Attachments: concurrency_issue.patch, DNA-546_final.patch, DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_mostly_working.patch, DNA-546_simple_model_WIP.patch, DNA-546_tck_test.patch
>
>
> 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 Dec  4 21:55:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 21:55:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1379482422.1259981729602.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-546.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


With the recent commits, the simple model now allows the JPA connector to provide a fully-functional connector that can support all of the TCK tests.  Most of the settings and capabilities of the basic model have been brought forward into the simple model.  The exception is the ability to enforce referential integrity at the database level.  A separate defect (DNA-576) has been opened to track the implementation of this feature.

> 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
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: concurrency_issue.patch, DNA-546_final.patch, DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_mostly_working.patch, DNA-546_simple_model_WIP.patch, DNA-546_tck_test.patch
>
>
> 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 Dec  4 22:14:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 4 Dec 2009 22:14:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
In-Reply-To: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2067288493.1259982869701.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-563:
-------------------------------------

Is the thinking that each connector should translate the actual events into different events for the change (e.g., one CopyBranchRequest might turn into 100 CreateNodeRequests when passed to the request processor's observer) or that the requests should be augmented to contain all of the information needed to generate the correct JCR events (e.g., CopyBranchRequest might get a new field called targetLocations())?

The LOE is probably pretty close between the two.

> Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-563
>                 URL: https://jira.jboss.org/jira/browse/DNA-563
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.
> See JBoss forum referenced below for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 12:54:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 12:54:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-563) Connectors Are Not
 Generating Events For Children Of Nodes Being Added Or Removed
In-Reply-To: <990910116.1259686770473.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <277176483.1260035669830.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-563:
-----------------------------------

It seems intuitive that the LOE for each approach is about the same, primarily because the largest part of the effort is changing the connectors to determine the correct information.

When considering whether to augment the original ChangeRequest or simply generate additional ChangeRequest objects in the event stream, it may be important to know what information is required. For example, a DeleteBranchRequest could be addressed by either adding a Collection<Location> for all nodes that were deleted, or it could be addressed by generating additional DeleteBranchRequest for each node.  (This latter is a bit odd.)

But for a CopyBranchRequest, the events need to know about the Location of each created node (for the NODE_ADDED event) and that node's property names (for the PROPERTY_ADDED events).  So the augmenting approach could add a LinkedHashMap<Location,Set<Name>>, since that would retain the order of insertion of Location (which should probably be the top-down order of the nodes being created).

Augmenting might actually work out better than generating extra events, especially because I think the existing ChangeRequest types won't fit our need well.  Consider that we don't have a DeleteNodeRequest (because semantically when a node is deleted all nodes below it must also be deleted).  CopyBranchRequest is similar: each connector would need to generate a CreateNodeRequest for each of the new nodes, but the CreateNodeRequest only has a slot for the collection of the Property objects whereas we only need the property names to generate the correct PROPERTY_ADDED events.  We could require the event store the values, but that would increase the size of the Changes and seems unnecessary (especially for Binary objects) considering that we may not need the values on the Observer side (NetChangeObserver certainly does NOT need them) and that it may place an extra burden on the connectors to retrieve the values.

I would tentatively vote for the 'augmenting' approach. It is more straightforward (a connector must simply fill out the information in each request) and thus easier for us to document and connector developers and Observer developers to understand the semantics (one request maps into one event).

Before we go much further, however, I'd like to see a list of every ChangeRequest that is affected by this issue, and how it would be augmented to provide the information that is currently missing.

> Connectors Are Not Generating Events For Children Of Nodes Being Added Or Removed
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-563
>                 URL: https://jira.jboss.org/jira/browse/DNA-563
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> If a node is created (or removed) which causes child nodes to also be created (or removed), events should be generated for those child nodes. See Section 8.3.7 of the JCR 1.0 specification. Copying, moving, and reordering of nodes, under the covers, may also add and remove nodes.
> See JBoss forum referenced below for more information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 12:58:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 12:58:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-577) Change the default
 model of the JPA connector from 'Basic' to 'Simple'
Message-ID: <404548522.1260035909663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Change the default model of the JPA connector from 'Basic' to 'Simple'
----------------------------------------------------------------------

                 Key: DNA-577
                 URL: https://jira.jboss.org/jira/browse/DNA-577
             Project: DNA
          Issue Type: Task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 0.7


A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well.  This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model.

The JPA connector's default model should be changed to 'Simple'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 13:00:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 13:00:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-577) Change the default
 model of the JPA connector from 'Basic' to 'Simple'
In-Reply-To: <404548522.1260035909663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <546369394.1260036029594.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-577:
------------------------------

    Priority: Blocker  (was: Major)


Marking as 'blocker' for 0.7, since IMO we should not release with 'Basic' being the default, since it has issues with core JCR functionality.

> Change the default model of the JPA connector from 'Basic' to 'Simple'
> ----------------------------------------------------------------------
>
>                 Key: DNA-577
>                 URL: https://jira.jboss.org/jira/browse/DNA-577
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well.  This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model.
> The JPA connector's default model should be changed to 'Simple'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 13:04:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 13:04:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-577) Change the default
 model of the JPA connector from 'Basic' to 'Simple'
In-Reply-To: <404548522.1260035909663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <274369887.1260036269608.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-577:
-----------------------------------

I should add that the JPA connector does store in the database which model is being used.  So even after an application with an existing database upgrades from JBoss DNA 0.6 to 0.7, the DNA would continue to use the model that was selected when the database was created.  However, new database would by default use the 'Simple' model.  In other words, existing database would be unaffected by the change in the default model, and would need to be migrated to a new database (via content export and import) to use the 'Simple' model.

> Change the default model of the JPA connector from 'Basic' to 'Simple'
> ----------------------------------------------------------------------
>
>                 Key: DNA-577
>                 URL: https://jira.jboss.org/jira/browse/DNA-577
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well.  This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model.
> The JPA connector's default model should be changed to 'Simple'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 13:07:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 13:07:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-576) SImple JPA Model
 Does Not Support Transparent Referential Integrity
In-Reply-To: <1391252535.1259981430273.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1095596240.1260036449992.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-576:
-----------------------------------

I'm not convinced that this is terribly important feature to have in the connector.  The 'Basic' model's referential integrity feature only works with content stored in the database; federation of multiple sources requires performing referential integrity at a higher level than the connector.  As such, the JCR implementation will likely use the query/search functionality to identify references as part of its referential integrity checks.

> SImple JPA Model Does Not Support Transparent Referential Integrity
> -------------------------------------------------------------------
>
>                 Key: DNA-576
>                 URL: https://jira.jboss.org/jira/browse/DNA-576
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>
> One feature in the basic model that has not yet been carried forward into the simple model is the ability to store references from one node to another in a transparent entity external to the node entity.  This allows for database foreign keys to help enforce referential integrity at the graph level.  However, since the primary consumer of DNA graph information at this time is the JCR layer, it may not be necessary to add this feature (and its associated performance cost at this time).

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

        

From jira-events at lists.jboss.org  Sat Dec  5 13:09:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 13:09:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-576) Simple JPA Model Does
 Not Support Transparent Referential Integrity
In-Reply-To: <1391252535.1259981430273.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1478588478.1260036570007.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-576:
------------------------------

    Summary: Simple JPA Model Does Not Support Transparent Referential Integrity  (was: SImple JPA Model Does Not Support Transparent Referential Integrity)


> Simple JPA Model Does Not Support Transparent Referential Integrity
> -------------------------------------------------------------------
>
>                 Key: DNA-576
>                 URL: https://jira.jboss.org/jira/browse/DNA-576
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>
> One feature in the basic model that has not yet been carried forward into the simple model is the ability to store references from one node to another in a transparent entity external to the node entity.  This allows for database foreign keys to help enforce referential integrity at the graph level.  However, since the primary consumer of DNA graph information at this time is the JCR layer, it may not be necessary to add this feature (and its associated performance cost at this time).

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

        

From jira-events at lists.jboss.org  Sat Dec  5 17:30:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 17:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
Message-ID: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JPA Connector Simple Model Does Not Support "supportsUpdates" Property
----------------------------------------------------------------------

                 Key: DNA-578
                 URL: https://jira.jboss.org/jira/browse/DNA-578
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Priority: Optional
             Fix For: Future Releases


The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.

This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.

If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 18:18:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 18:18:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-577) Change the default
 model of the JPA connector from 'Basic' to 'Simple'
In-Reply-To: <404548522.1260035909663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1644051155.1260055109710.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-577:
--------------------------------

    Attachment: DNA-577.patch


Attached patch that changes the default setting in JpaSource and updates the reference guide.  I changed the sub-sections to be of style <sect1> instead of <sect2> to be compliant with the DTD for the enclosing <chapter> tag.  This cleans up an error in the Eclipse Docbook editor. 

The patch also re-adds a test that was overridden a few months ago when DNA-466 was still open and cleans up some of the existing connector-level tests for the simple model.


> Change the default model of the JPA connector from 'Basic' to 'Simple'
> ----------------------------------------------------------------------
>
>                 Key: DNA-577
>                 URL: https://jira.jboss.org/jira/browse/DNA-577
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-577.patch
>
>
> A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well.  This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model.
> The JPA connector's default model should be changed to 'Simple'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 18:22:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 18:22:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-577) Change the default
 model of the JPA connector from 'Basic' to 'Simple'
In-Reply-To: <404548522.1260035909663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1896418630.1260055349622.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-577.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


Committed patch to resolve issue.

> Change the default model of the JPA connector from 'Basic' to 'Simple'
> ----------------------------------------------------------------------
>
>                 Key: DNA-577
>                 URL: https://jira.jboss.org/jira/browse/DNA-577
>             Project: DNA
>          Issue Type: Task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-577.patch
>
>
> A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well.  This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model.
> The JPA connector's default model should be changed to 'Simple'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 19:46:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 19:46:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation
 Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1466141906.1260060389631.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-541:
--------------------------------

    Attachment: DNA-541_admin_unlock.patch


Attached patch that adds a new permission (granted to anyone with the admin role) that allows them to break any locks.  This will at least give DNA administrators an ability to manually clean up any dangling locks.

> 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
>
>         Attachments: DNA-541_admin_unlock.patch
>
>
> 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  Sat Dec  5 20:20:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 20:20:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
In-Reply-To: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1554204885.1260062429778.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-578:
-----------------------------------

I think the scenario mentioned in the last paragraph of the description is the primary use case: a master-clone relationship.

> JPA Connector Simple Model Does Not Support "supportsUpdates" Property
> ----------------------------------------------------------------------
>
>                 Key: DNA-578
>                 URL: https://jira.jboss.org/jira/browse/DNA-578
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>
> The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.
> This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.
> If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 20:55:36 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 20:55:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-541) Locking
 Implementation Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1594412392.1260064536913.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-541:
-------------------------------------

The final piece is the ability to add a timeout for session-scoped and/or permanent locks.  This would allow the system to clean itself up if sessions get closed without calling logout or a coding error results in lost lock tokens for permanent locks.

Randall and I had an IRC discussion about this months ago where he suggested adding an expiry time to the lock record in /jcr:system/dna:locks and adding a thread that would periodically advance the time into the future for active sessions.  The tricky part is determining which sessions are active.  I was thinking about having each session create a ScheduledFuture task that would advance the expiry time for its own locks (if the session still existed), but I think it would be easier to just put a set of weak references to active sessions into the JcrRepository.  The algorithm would then be something like this:

let M := the repository's set of active sessions
for each lock L under /jcr:system/dna:locks
    if (L.isSessionScoped)
        if (L.lockExpiration < the current time)
            delete L from graph
            delete corresponding lock from WorkspaceLockManager
        else if (M.containsKey(L.sessionId))
            L.expiryTime += some interval

There would probably have to be some balancing in there between the frequency at which this task runs and the amount that the expiry time is advanced to handle things like clock-drift across a cluster or the task running behind on heavily loaded systems.

Any thoughts or feedback on this approach would be appreciated.  My big questions are: 

1.  Is this even worth doing?
2.  If it is worth doing, where should the scheduler (presumably a ScheduledExecutorService) live?  That's the kind of service that the DNA repository has provided to the JcrRepositories in the past, I think.


> 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
>
>         Attachments: DNA-541_admin_unlock.patch
>
>
> 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  Sat Dec  5 20:59:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 5 Dec 2009 20:59:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
In-Reply-To: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <896427662.1260064769615.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-578:
-------------------------------------

Please let me know if you want this done soonish.  I moved it into Future Releases because it didn't seem all that likely to be used (to me, anyway), but it's only an hour or two's worth of work to get it integrated.  Most of the work would be in setting up tests, I think.

> JPA Connector Simple Model Does Not Support "supportsUpdates" Property
> ----------------------------------------------------------------------
>
>                 Key: DNA-578
>                 URL: https://jira.jboss.org/jira/browse/DNA-578
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>
> The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.
> This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.
> If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  5 21:23:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 21:23:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-541) Locking
 Implementation Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1860669266.1260066209748.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-541:
-----------------------------------

I like the weak reference approach, since it's pretty simple.

1) I'm not sure. If you have time, it might be nice to complete this while you're thinking about it.
2) Rather than have the JcrRepository own the scheduler, how about if the JcrRepository exposed a package-level method to perform the cleanup operation.  The JcrEngine could have a single scheduler for all of its JcrRepository instances, configured with the desired interval, and that thread iterates through the JcrRepository instances and calls the cleanupLocks method. This way, the cleanup is performed in a separate thread on a schedule, but there's only one thread in the whole JcrEngine instance configurable through the JcrConfiguration, and yet the JcrRepository instances actually don't have to worry about when this should be called.  The JcrEngine could (eventually) have a public management method to perform the cleanup right then.


> 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
>
>         Attachments: DNA-541_admin_unlock.patch
>
>
> 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  Sat Dec  5 21:25:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 5 Dec 2009 21:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
In-Reply-To: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <575682435.1260066330166.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-578:
-----------------------------------

I don't think it's needed for 0.7, and I'm fine with 'Future Releases'.  (That's why I didn't change the Fix Version.)

> JPA Connector Simple Model Does Not Support "supportsUpdates" Property
> ----------------------------------------------------------------------
>
>                 Key: DNA-578
>                 URL: https://jira.jboss.org/jira/browse/DNA-578
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>
> The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.
> This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.
> If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

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

        

From jira-events at lists.jboss.org  Sun Dec  6 11:01:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 6 Dec 2009 11:01:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation
 Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1424870521.1260115289613.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-541:
--------------------------------

    Attachment: DNA-541_admin_unlock.patch


Those are good calls.

Attached is a patch that implements lock expiration based on the algorithm above modified by Randall's comments.  The patch includes two tests to confirm that the functionality works, but one is @Ignored because it depends on garbage collector behavior to test the results and the other is @Ignored because it has to sleep for 30 seconds to test the timeout.

If the patch looks ok, I will commit it and resolve the defect.

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_admin_unlock.patch
>
>
> 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  Sun Dec  6 11:06:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 6 Dec 2009 11:06:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation
 Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2133669726.1260115589612.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-541:
--------------------------------

    Attachment:     (was: DNA-541_admin_unlock.patch)


> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch
>
>
> 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  Sun Dec  6 11:06:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 6 Dec 2009 11:06:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation
 Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <833519513.1260115589637.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-541:
--------------------------------

    Attachment: DNA-541_lock_timeout.patch


Uploaded last night's patch in previous comment.

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch
>
>
> 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  Mon Dec  7 10:13:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 7 Dec 2009 10:13:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-541) Locking
 Implementation Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1646642921.1260198810590.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-541:
-----------------------------------

Nice job!  The patch looks good, tho I have a few comments:

1) The ScheduledExecutorService should be shutdown when the JcrEngine is shutdown, so JcrEngine needs to override the DnaEngine.shutdown() method.
2) The new JcrRepository.cleanUpLocks() method should make its copy of the JcrSession objects (or their IDs) in a synchronized block.  (Helping identify when the methods/fields can be used w/r/t concurrency is one reason I try to put the JCIP annotations on the methods and fields).
3) The ExecutionContext that was newly added to WorkspaceLockManager doesn't appear to be used (or certainly is not used nearly as much as their session's)

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch
>
>
> 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  Mon Dec  7 11:19:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 7 Dec 2009 11:19:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-541) Locking
 Implementation Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <807382943.1260202769589.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-541:
-------------------------------------

Responding point-by-point to the previous comment:

1.  Good call.  I've also added startup and awaitTermination to clean up the start-stop behavior with the new service.
2.  Good call.  Is it sufficient to wrap the three accesses to the activeSessions map in synchonized (this.activeSessions) { ... }?  If not, I promise to go buy a copy of JCIP and read it over Xmas break.
3.  Yeah, I'll add a comment on that one.  The WLM's execution context is used only when performing actions outside the scope of the session.  In general, I'm still trying to use the relevant session's context in case we ever start leveraging SSO more fully and use the session's JAAS subject and privileges to broker access to underlying repositories (which some incarnation of the jcr:system branch may rely on).  Let me know if you want me to standardize on using one context or the other.

Thanks for the great feedback!

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch
>
>
> 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  Mon Dec  7 15:36:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 7 Dec 2009 15:36:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-570)
 JcrObservationManager's Logic For Filtering Events Based On Node Types Is
 Incorrect
In-Reply-To: <1328220643.1259954429670.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1251652793.1260218189720.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-570.
-----------------------------

    Resolution: Done


Changed logic of JcrNodeTypeManager.isDerivedFrom method to check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Uncommented the appropriate tests in JcrObservationManagerTest and JcrTckTest which now run fine.

> JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect
> -----------------------------------------------------------------------------------
>
>                 Key: DNA-570
>                 URL: https://jira.jboss.org/jira/browse/DNA-570
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The logic was determining if the Event node's primary type or mixins were equal to or derived from one or more given types. This was backwards and was allowing too many events to get through. The logic should check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Changes to JcrNodeManager and JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  7 15:38:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 7 Dec 2009 15:38:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-571)
 JcrObservationManager's Logic For Filtering Events Based On Path Is
 Incorrect For Property Events
In-Reply-To: <1348896281.1259954976254.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2059769752.1260218309699.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-571.
-----------------------------

    Resolution: Done


The event node path is now used for property events. For node events, the event node parent's path is used. Uncommented the appropriate tests in JcrObservationManagerTest and JcrTckTest which now run fine.

> JcrObservationManager's Logic For Filtering Events Based On Path Is Incorrect For Property Events
> -------------------------------------------------------------------------------------------------
>
>                 Key: DNA-571
>                 URL: https://jira.jboss.org/jira/browse/DNA-571
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The logic for filtering events based on the event path is incorrect for property events. Instead of using the property's node's parent it needs to use the node path. Changes to JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  7 15:45:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 7 Dec 2009 15:45:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-549) Creating A New
 Property And Changing An Existing Property Should Have Different
 ChangeRequest Types
In-Reply-To: <1946803342.1257437465795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1557004.1260218729920.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian reopened DNA-549:
-----------------------------



The UpdateValuesRequest also has the same problem. According to the documentation for this class it can be used for a new or an existing property. There is no way to tell using the existing API. This is needed by the ObservationManager implementation. 

> Creating A New Property And Changing An Existing Property Should Have Different ChangeRequest Types
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-549
>                 URL: https://jira.jboss.org/jira/browse/DNA-549
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> There is no way to differentiate between when a new property is created and when an existing property is set. Both are handled using the SetPropertyRequest. The JCR spec clearly states the difference between these two cases as each one has their own event type.
> Work to change to the relevant change requests, update connectors, and update the NetChangeObserver will need to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  7 15:53:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 7 Dec 2009 15:53:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-541) Locking Implementation
 Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <615351365.1260219209657.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-541:
--------------------------------

    Attachment: DNA-541_lock_timeout_updated.patch


Attached an updated version of the previous patch that addresses the feedback.

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch, DNA-541_lock_timeout_updated.patch
>
>
> 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  Mon Dec  7 15:57:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 7 Dec 2009 15:57:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-541) Locking
 Implementation Does Not Support Timeouts
In-Reply-To: <1843297386.1256243405772.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1897912266.1260219449592.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-541.
---------------------------------

    Resolution: Done


Committed patch to resolve defect

> 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
>
>         Attachments: DNA-541_admin_unlock.patch, DNA-541_lock_timeout.patch, DNA-541_lock_timeout_updated.patch
>
>
> 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  Tue Dec  8 09:56:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 8 Dec 2009 09:56:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-579)
 JcrObservationManagerTest Should Check To See If Listeners Receive Too Many
 Events
Message-ID: <1595461178.1260284189729.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JcrObservationManagerTest Should Check To See If Listeners Receive Too Many Events
----------------------------------------------------------------------------------

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


The JcrObservationManagerTest is using a CountDownLatch to determine if the correct number of events are received by a JCR event listener. Once the correct number of events are received the test listener "quits" listening and the test passes (assuming the received events were the correct ones). What the test does not check is if too many events could've been broadcast to a listener (i.e., events that the listener has not been registered to receive).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  8 12:04:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 8 Dec 2009 12:04:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-580) Rebrand project to new
	name
Message-ID: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Rebrand project to new name
---------------------------

                 Key: DNA-580
                 URL: https://jira.jboss.org/jira/browse/DNA-580
             Project: DNA
          Issue Type: Task
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


The project will be rebranded, so we need to change the package names and all references to "JBoss DNA" in the code and documentation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  8 12:04:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 8 Dec 2009 12:04:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-580) Rebrand project to new
	name
In-Reply-To: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <993449099.1260291869750.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-580:
------------------------------

    Component/s: Analysis and Reporting
                 API
                 Common
                 Connectors
                 Development Environment
                 Documentation
                 Examples
                 Federation
                 Graph
                 JCR
                 Maven Classloader
                 Query
                 Search
                 Sequencers
                 Server
                 Testing
                 Tools
                 Views
                 Web Application


> Rebrand project to new name
> ---------------------------
>
>                 Key: DNA-580
>                 URL: https://jira.jboss.org/jira/browse/DNA-580
>             Project: DNA
>          Issue Type: Task
>          Components: Analysis and Reporting, API, Common, Connectors, Development Environment, Documentation, Examples, Federation, Graph, JCR, Maven Classloader, Query, Search, Sequencers, Server, Testing, Tools, Views, Web Application
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 1.0
>
>
> The project will be rebranded, so we need to change the package names and all references to "JBoss DNA" in the code and documentation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  8 13:30:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 8 Dec 2009 13:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-526) IllegalStateException
 calling TokenStream.canConsume(String str) after consuming all tokens via
 canConsume(String[])
In-Reply-To: <2101351563.1253719669245.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <509796214.1260297029684.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond resolved DNA-526.
------------------------------

    Resolution: Done


This patch was applied. Marking Done

> IllegalStateException calling TokenStream.canConsume(String str) after consuming all tokens via canConsume(String[])
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-526
>                 URL: https://jira.jboss.org/jira/browse/DNA-526
>             Project: DNA
>          Issue Type: Bug
>          Components: Common
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>         Attachments: dna-common_DNA_526.patch
>
>
> While parsing, I wished to call canConsume() for multiple "optional" properties.  Some are "multi-string" using canConsume("xxxx", "xxxx", ....)
> If a previous canConsume() had finished parsing the tokens (i.e. currentToken == NULL), then a subsequent canConsume("xxxx") would result in the following exception:
> java.lang.IllegalStateException: The 'start()' method must be called before tokens can be consumed or matched
> 	at org.jboss.dna.common.text.TokenStream.currentToken(TokenStream.java:1160)
> 	at org.jboss.dna.common.text.TokenStream.matches(TokenStream.java:866)
> 	at org.jboss.dna.common.text.TokenStream.canConsume(TokenStream.java:609)
> 	at ....
> It appears that the canConsume( <MULTIPLE> ) methods do NOT call moveToNextToken() which is currently the only method that sets this.completed = TRUE.
> Fix would be to add:  this.completed = this.currentToken == NULL before returning on the canConsume( <MULTIPLE> ) methods.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  8 13:34:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 8 Dec 2009 13:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-569) Enhance Graph.java's
 Subgraph object toString() method to show recursive node structure and
 properties.
In-Reply-To: <69290190.1259878230193.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1122183729.1260297269658.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond resolved DNA-569.
------------------------------

    Resolution: Done


Graph.SubgraphResults.toString() and Graph.SubgraphNodeImpl.toString() methods were enhanced. 

> Enhance Graph.java's Subgraph object toString() method to show recursive node structure and properties.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-569
>                 URL: https://jira.jboss.org/jira/browse/DNA-569
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While developing DdlSequencer tests, a need developed obtain a sub-graph of the sequenced DDL file and operate on the resultant nodes and properties. However, the Sub-graph was difficult to debug because viewing child nodes and properties were difficult to see in values view.
> By constructing a more descriptive/recursive toString() value for subgraph, it would make debugging and testing much easier.

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

        

From jira-events at lists.jboss.org  Tue Dec  8 13:50:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 8 Dec 2009 13:50:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-49) Sequence DDL files
Message-ID: <1256021828.1260298230274.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond commented on DNA-49:
---------------------------------

Finished DdlParsers Test.

Working on adding an integration test to verify DdlSequencer contribution.

> Sequence DDL files
> ------------------
>
>                 Key: DNA-49
>                 URL: https://jira.jboss.org/jira/browse/DNA-49
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> Create a sequencer that parses DDL files and generates the subgraph representing the relational schema.  Multiple dialects should be supported, including those for Oracle, MS SqlServer, PostgreSQL, MySQL, and others.  Ideally this could be done with one sequencer (since most users/admins won't care about which dialect a particular file is; they'll just want it sequenced).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  8 15:55:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 8 Dec 2009 15:55:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-579)
 JcrObservationManagerTest Should Check To See If Listeners Receive Too Many
 Events
In-Reply-To: <1595461178.1260284189729.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1433581171.1260305730061.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-579.
-----------------------------

    Resolution: Done


Changed JcrObservationManagerTest  CountDownLatch to use the expected number of EventIterators (which is usually only one) instead of the expected number of events. Then when the going through the iterator I determine if the correct number of events have been received. An EventIterator is received each time a "transaction" is committed.

> JcrObservationManagerTest Should Check To See If Listeners Receive Too Many Events
> ----------------------------------------------------------------------------------
>
>                 Key: DNA-579
>                 URL: https://jira.jboss.org/jira/browse/DNA-579
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> The JcrObservationManagerTest is using a CountDownLatch to determine if the correct number of events are received by a JCR event listener. Once the correct number of events are received the test listener "quits" listening and the test passes (assuming the received events were the correct ones). What the test does not check is if too many events could've been broadcast to a listener (i.e., events that the listener has not been registered to receive).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 09:49:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 9 Dec 2009 09:49:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-455) Add Sub-Project to
 Execute Official TCK
In-Reply-To: <28501370.1244747216332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <445426937.1260370169621.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-455:
-------------------------------------

I created this bug many moons ago before I understood what the TCK compat test looked like.  It turns out to be a web application that looks up a reference to your repository in the JNDI tree.  You then click a button to start the test.   This would be fairly painful to fully automate and would provide no gain over our current integration tests, which run the exact same test cases and do so against a variety of repository configurations.

Instead of writing a bunch of automated web-scripting code, I propose that we add a class to the dna-jcr layer that allows access to our JCR repositories through JNDI.  This would make running the formal compatibility test require 5 steps:

1.  Install a servlet container like Tomcat locally 
2.  Build DNA and copy the resulting JARs into the Tomcat lib directory
3.  Modify the Tomcat context.xml to add the JNDI entry for DNA
4.  Copy the TCK compatibility web app into the Tomcat deploy directory
5.  Go to the test page and click the button to start the test.

Considering that we really only need to run this once, I think that's not too many steps and it would add a deployment vector for DNA that could be reused.

Any thoughts?

> Add Sub-Project to Execute Official TCK
> ---------------------------------------
>
>                 Key: DNA-455
>                 URL: https://jira.jboss.org/jira/browse/DNA-455
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> JSR-170 compliance is achieved when all tests in the official TCK are passed.  This TCK is distinct from (but related to) the "unofficial" JackRabbit TCK that DNA currently runs each night.  In order to achieve full compliance(and make sure that future changes don't break it), an automated means of executing the official TCK (and passing or failing based on the results) should be added.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 10:01:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 10:01:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-455) Add Sub-Project to
 Execute Official TCK
In-Reply-To: <28501370.1244747216332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1301922833.1260370889780.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-455:
-----------------------------------

It is fine to not automate, because you are correct in that we won't be running this often.  However, it needs to be fully documented with all steps spelled out so that even a dumb monkey (namely me) can run it repeatedly when needed.

> Add Sub-Project to Execute Official TCK
> ---------------------------------------
>
>                 Key: DNA-455
>                 URL: https://jira.jboss.org/jira/browse/DNA-455
>             Project: DNA
>          Issue Type: Sub-task
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> JSR-170 compliance is achieved when all tests in the official TCK are passed.  This TCK is distinct from (but related to) the "unofficial" JackRabbit TCK that DNA currently runs each night.  In order to achieve full compliance(and make sure that future changes don't break it), an automated means of executing the official TCK (and passing or failing based on the results) should be added.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 10:13:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 10:13:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-445) Formally Delineate
	the Public API
In-Reply-To: <3872687.1244382536324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1558190588.1260371616341.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-445:
-----------------------------------

Per TAG-29, we need to provide a set of public API JavaDocs that have only the publicly-accessible classes/interfaces.  This shouldn't be too difficult, as it basically entails a different JavaDoc configuration to limit the packages and visibility.  

Generally, our approach is that every public class in our public API packages should be part of the public API; any classes with other visibility (or classes in other packages) are not considered part of the API.  We really just need to put together the list of public API packages, and that can be done in the JavaDoc configuration (keeping it DRY).

Note that we may want to change the existing JavaDoc assembly into the public API artifact, and (if desired) _add_ another JavaDoc assembly that creates the "developer JavaDoc".


> Formally Delineate the Public API
> ---------------------------------
>
>                 Key: DNA-445
>                 URL: https://jira.jboss.org/jira/browse/DNA-445
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API
>    Affects Versions: 0.4
>            Reporter: Brian Carothers
>             Fix For: 1.1
>
>
> DNA has a fairly large number of classes, not all of which are intended to be stable.  Although some examples and documentation "best practices" for utilizing the API are provided, there is no explicit contract in the API that indicates which portions of the API are expected to remain stable and supported over time.
> A comparable discussion was occurring on the jboss-development mailing list (https://lists.jboss.org/mailman/listinfo/jboss-development)  Vol. 36 Issue 8 et al.  It appears that Eclipse uses annotations to provide this information.  These annotations (http://www.opends.org/promoted-builds/2.0.0-RC1/javadoc/org/opends/server/types/PublicAPI.html and http://www.eclipse.org/pde/pde-api-tools/) were tossed around in the discussion.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 14:30:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 14:30:30 -0500 (EST)
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: <41694541.1260387030285.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=12499114#action_12499114 ] 

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

Restructured the SearchEngine functionality to simplify it, and to change over to have implementations be extensions.  To specialize, an implementation now simply subclasses the SearchEngine, and this is instantiated directly.  

The SearchEngine is also now oriented around a RequestProcessor.  It's possible to obtain a RequestProcessor to issue multiple requests within a single connection, and this will make it significantly easier to reuse within a connector implementation (as well as within the 'dna-repository' module).  Also, the SearchEngine's abstract RequestProcessor implementation provides default implementations for crawling and indexing entire subgraphs to generate the required UpdatePropertiesRequest and CreateNodeRequest stream.  Specializations are responsible for fully-implementing the RequestProcessor to handle all the different kinds of requests, including AccessQueryRequest and FullTextSearchRequest.

Thus, the LuceneSearchEngine can be instantiated directly, as it is now a subclass of SearchEngine.  It also exists in a new 'extensions/dna-search-lucene' project, and continues to use the two-index design that was implemented previously.  This new implementation uses a customized RequestProcessor implementation.  This also should make it easier to process Changes via the request processor's methods.


> 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: JCR, Query, Search
>    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  Wed Dec  9 20:47:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 20:47:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-581) Alter logging to use
 categories and message codes
Message-ID: <1142200420.1260409649586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Alter logging to use categories and message codes 
--------------------------------------------------

                 Key: DNA-581
                 URL: https://jira.jboss.org/jira/browse/DNA-581
             Project: DNA
          Issue Type: Task
          Components: Common
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.1


Our logging facility should use message codes that can be used to cross-reference more information about the message and possible actions to alter the behavior.  The logging should also use categories rather than just using class names.

Ideally this can be done such that the only changes are to the logging class and the I18n library, and that all other code remains untouched.  (Though we'll have to record for each subproject the message codes in a file so they're durable and documented.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 21:39:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 21:39:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-581) Alter logging to use
 categories and message codes
In-Reply-To: <1142200420.1260409649586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1392043428.1260412769699.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-581:
-----------------------------------

One way to do this is to change the I18n class to have, in addition to the localized message, a locale-independent and immutable "event code".  Thus, the I18n framework could not only find in a bundle the localized messages for a given local but also to look up the code in another resource file (one that doesn't change with locale).  Basically, this can have the same property-file format as the localization files, except that the value should be the code.  To match other JBoss.org projects, the code should be of the form "<SYSTEM>-<EVENT_CODE>", where "<SYSTEM>" is a unique name of the system that is at most 6 characters (e.g., "MODES" for ModeShape) and "<EVENT_CODE>" is a 5-digit, leading zero-padded unique number for the message (e.g., "00001").  I would recommend breaking the 100K-1 range of event codes into ranges for each of our subsystems, so "01XXXX" might apply to our graph subproject, "02XXXX" might apply to the JCR implementation, "11XXXX" might apply to a particular connector (and "1XXXXX" would apply to all connectors), etc.

> Alter logging to use categories and message codes 
> --------------------------------------------------
>
>                 Key: DNA-581
>                 URL: https://jira.jboss.org/jira/browse/DNA-581
>             Project: DNA
>          Issue Type: Task
>          Components: Common
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>
> Our logging facility should use message codes that can be used to cross-reference more information about the message and possible actions to alter the behavior.  The logging should also use categories rather than just using class names.
> Ideally this can be done such that the only changes are to the logging class and the I18n library, and that all other code remains untouched.  (Though we'll have to record for each subproject the message codes in a file so they're durable and documented.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec  9 22:06:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 9 Dec 2009 22:06:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-581) Alter logging to use
 categories and message codes
In-Reply-To: <1142200420.1260409649586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2101669697.1260414389610.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-581:
-----------------------------------

One nice thing about having a resource bundle similar to the localization files is that all of these files could easily be processed to generate message code tables for each locale.  In fact, it wouldn't be too hard to generate them automatically (though that's likely beyond scope at the moment).

> Alter logging to use categories and message codes 
> --------------------------------------------------
>
>                 Key: DNA-581
>                 URL: https://jira.jboss.org/jira/browse/DNA-581
>             Project: DNA
>          Issue Type: Task
>          Components: Common
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>
> Our logging facility should use message codes that can be used to cross-reference more information about the message and possible actions to alter the behavior.  The logging should also use categories rather than just using class names.
> Ideally this can be done such that the only changes are to the logging class and the I18n library, and that all other code remains untouched.  (Though we'll have to record for each subproject the message codes in a file so they're durable and documented.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 10 16:42:29 2009
From: jira-events at lists.jboss.org (Nick Boldt (JIRA))
Date: Thu, 10 Dec 2009 16:42:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-564) Move Eclipse plugin
 code outside of the Maven modules
In-Reply-To: <255585603.1259702796558.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1896593753.1260481349884.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Nick Boldt commented on DNA-564:
--------------------------------

Perhaps instead of moving within the dna repo, you should move these into the jbosstools repo? See JBIDE-5318 for further discussion.

> Move Eclipse plugin code outside of the Maven modules
> -----------------------------------------------------
>
>                 Key: DNA-564
>                 URL: https://jira.jboss.org/jira/browse/DNA-564
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> As it stands now in its current location, the Eclipse plugin projects are not Mavenized and thus cannot be easily integrated into the Maven build.  Plus, the release process is made much more complex in the current form, because the Eclipse plugin would depend on the Maven artifacts (in released form).  Therefore, we should move the Eclipse plugin source code outside of the http://anonsvn.jboss.org/repos/dna/trunk/ area of SVN and into a new http://anonsvn.jboss.org/repos/dna/eclipse/trunk area.  
> See also this email discussion thread: http://lists.jboss.org/pipermail/dna-dev/2009-November/000853.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 16:45:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:45:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-582) The
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <1348612834.1260567929990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The connector.execute(...) method is not 'all-or-nothing'
---------------------------------------------------------

                 Key: DNA-582
                 URL: https://jira.jboss.org/jira/browse/DNA-582
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Graph
            Reporter: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


The RepositoryConnector.execute(ExecutionContext,Request) method does not have all-or-nothing behavior.  That is, if the request is a CompositeRequest with multiple requests to change the content, and some of those change requests result in errors, the execution should 'rollback' the changes and return the content to the state before the method was called.  In other words, either all of the requests are fulfilled, or none of them are.  

None of the writable connectors work this way, and they all need to be corrected.  Also, this behavior needs to be documented in the connector API.  Finally, we need to make sure that the JCR session's transient state is unchanged if a save() call results in an error (the connector's state should rollback, but the session's state should remain, per Section 7.1.1.6-7.1.1.7 of JCR 1.0.1).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 16:53:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-583) The In-Memory
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <309725502.1260568410014.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The In-Memory connector.execute(...) method is not 'all-or-nothing'
-------------------------------------------------------------------

                 Key: DNA-583
                 URL: https://jira.jboss.org/jira/browse/DNA-583
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
            Reporter: Randall Hauch
            Priority: Blocker


Maybe the easiest way to correct this is to record the MapNode objects before they are changed, and then if a rollback occurs, to replace the newly-changed MapNode objects with the original.  This is a bit more complicated, since individual MapNode methods are called to change the node.

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

        

From jira-events at lists.jboss.org  Fri Dec 11 16:56:13 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:56:13 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-584) The Infinispan
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <1274674743.1260568573591.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The Infinispan connector.execute(...) method is not 'all-or-nothing'
--------------------------------------------------------------------

                 Key: DNA-584
                 URL: https://jira.jboss.org/jira/browse/DNA-584
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


We should be able to rely upon the transactional semantics of Infinispan.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 16:56:13 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:56:13 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-582) The
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <1348612834.1260567929990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1203122728.1260568573628.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-582:
------------------------------

    Affects Version/s: 0.7


> The connector.execute(...) method is not 'all-or-nothing'
> ---------------------------------------------------------
>
>                 Key: DNA-582
>                 URL: https://jira.jboss.org/jira/browse/DNA-582
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 1.0
>
>
> The RepositoryConnector.execute(ExecutionContext,Request) method does not have all-or-nothing behavior.  That is, if the request is a CompositeRequest with multiple requests to change the content, and some of those change requests result in errors, the execution should 'rollback' the changes and return the content to the state before the method was called.  In other words, either all of the requests are fulfilled, or none of them are.  
> None of the writable connectors work this way, and they all need to be corrected.  Also, this behavior needs to be documented in the connector API.  Finally, we need to make sure that the JCR session's transient state is unchanged if a save() call results in an error (the connector's state should rollback, but the session's state should remain, per Section 7.1.1.6-7.1.1.7 of JCR 1.0.1).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 16:56:13 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:56:13 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-583) The In-Memory
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <309725502.1260568410014.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1485820179.1260568573948.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-583:
------------------------------

        Fix Version/s: 1.0
    Affects Version/s: 0.7


> The In-Memory connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------------
>
>                 Key: DNA-583
>                 URL: https://jira.jboss.org/jira/browse/DNA-583
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 1.0
>
>
> Maybe the easiest way to correct this is to record the MapNode objects before they are changed, and then if a rollback occurs, to replace the newly-changed MapNode objects with the original.  This is a bit more complicated, since individual MapNode methods are called to change the node.

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

        

From jira-events at lists.jboss.org  Fri Dec 11 16:57:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:57:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-586) The JBoss Cache
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <1536968834.1260568649551.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The JBoss Cache connector.execute(...) method is not 'all-or-nothing'
---------------------------------------------------------------------

                 Key: DNA-586
                 URL: https://jira.jboss.org/jira/browse/DNA-586
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


We should be able to rely upon the transactional semantics of JBoss Cache.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 16:57:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:57:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-585) The JPA
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <943254042.1260568649529.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The JPA connector.execute(...) method is not 'all-or-nothing'
-------------------------------------------------------------

                 Key: DNA-585
                 URL: https://jira.jboss.org/jira/browse/DNA-585
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


We should be able to just commit or rollback, but we just need to do this at the appropriate time.

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

        

From jira-events at lists.jboss.org  Fri Dec 11 16:59:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 16:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-587) The FileSystem
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <345275680.1260568770127.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The FileSystem connector.execute(...) method is not 'all-or-nothing'
--------------------------------------------------------------------

                 Key: DNA-587
                 URL: https://jira.jboss.org/jira/browse/DNA-587
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Priority: Blocker
             Fix For: 1.0


Making this happen might be a bit tough.  We might have to copy any changed files and changed/removed directories into a temporary area, and then move them back upon rollback.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 17:09:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 17:09:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-589) The
 JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect
Message-ID: <979009724.1260569369609.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect
-------------------------------------------------------------------

                 Key: DNA-589
                 URL: https://jira.jboss.org/jira/browse/DNA-589
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.0


JcrRepository instances can be configured with the UPDATE_INDEXES_SYNCHRONOUSLY option to specify whether the search indexes should be updated asynchronously or synchronously.  Because of DNA-588, the option value has no effect, and all updates to the search indexes are made asynchronously.  As soon as DNA-588 is fixed, this issue should be fixed with no other changes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 11 17:09:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 11 Dec 2009 17:09:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-588) The connectors should
 release all resources before notifying observer of events
Message-ID: <849646424.1260569369590.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The connectors should release all resources before notifying observer of events
-------------------------------------------------------------------------------

                 Key: DNA-588
                 URL: https://jira.jboss.org/jira/browse/DNA-588
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Graph
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.0


Right now, most connectors are firing off the changes to the Observer before the resources acquired by the connector are released, meaning that the Observer cannot use the source within the same thread.  This prevents writing Observers that operate fully before the 'execute(...)' method returns, and requires that any Observer that might need access to the source needs to do its work asynchronously.

By notifying the Observer _after_ the resources are released but before 'execute(...)' returns, Observers could call back to the source (really through a different connection or at least through a different 'execute(...)' call) to access content.  This means that Observers could be written to work synchronously while still access the (committed) content.

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

        

From jira-events at lists.jboss.org  Sat Dec 12 13:15:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:15:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-590) The FederatedConnector
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <256844001.1260641730732.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The FederatedConnector connector.execute(...) method is not 'all-or-nothing'
----------------------------------------------------------------------------

                 Key: DNA-590
                 URL: https://jira.jboss.org/jira/browse/DNA-590
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors, Federation
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.0


The federation connector needs to ensure that either changes are made to all connectors or changes are made to none.  This is going to be a challenge if multiple sources are involved in a transaction (without resorting to a transaction manager and XA).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 12 13:36:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-582) The
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <1348612834.1260567929990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <36334407.1260642990665.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-582:
-----------------------------------

Changed the semantics of the RequestProcessor.close().  Previously, this method released all resources _and_ notified the observer of all changes.  The resources always have to be released and thus close() must be called, yet this was always notifying the observer even in the case of change failures.

The close() method now no longer notifies the observer, and a new notifyObserverOfChanges() method has been added to do the notification.  This makes it possible to always close the resources yet optionally do the notification depending upon other conditions.

The RequestProcessor.process(CompositeRequest) method behavior has also changed. Now, if there is an error on any of the change requests (any request that returns 'false' for isReadOnly()), the processing stops and the error is recorded.

The abstract MapRepositorySource has been changed to take advantage of this.  A new MapRepositoryTransaction has been created, and the MapRepository now has a method to return a new transaction.  The MapRepositoryConnection.execute(...) method has been changed to take advantage of this to obtain a transaction, perform the processing, check for errors on change requests, close the processor (to release any resources), and then either commit or rollback the transaction based upon whether the requests had errors and involved changes.  Thus, the new MapRepositoryTransaction encapsulates all of the locking and rollback behavior for specializations of the MapRepository.

As part of DNA-585, the simple model in the JPA connector has been changed to use this transaction behavior and to commit or rollback the JPA transaction appropriately.  The basic model in the JPA connector doesn't extend the MapRepository classes, but it does the same thing (using the JPA transaction directly in the connection's execute method).  Therefore, this change should resolve DNA-585.

> The connector.execute(...) method is not 'all-or-nothing'
> ---------------------------------------------------------
>
>                 Key: DNA-582
>                 URL: https://jira.jboss.org/jira/browse/DNA-582
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 1.0
>
>
> The RepositoryConnector.execute(ExecutionContext,Request) method does not have all-or-nothing behavior.  That is, if the request is a CompositeRequest with multiple requests to change the content, and some of those change requests result in errors, the execution should 'rollback' the changes and return the content to the state before the method was called.  In other words, either all of the requests are fulfilled, or none of them are.  
> None of the writable connectors work this way, and they all need to be corrected.  Also, this behavior needs to be documented in the connector API.  Finally, we need to make sure that the JCR session's transient state is unchanged if a save() call results in an error (the connector's state should rollback, but the session's state should remain, per Section 7.1.1.6-7.1.1.7 of JCR 1.0.1).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 12 13:36:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-585) The JPA
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <943254042.1260568649529.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <654334420.1260642990747.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-585.
-------------------------------

    Resolution: Done


> The JPA connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------
>
>                 Key: DNA-585
>                 URL: https://jira.jboss.org/jira/browse/DNA-585
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We should be able to just commit or rollback, but we just need to do this at the appropriate time.

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

        

From jira-events at lists.jboss.org  Sat Dec 12 13:36:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-585) The JPA
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <943254042.1260568649529.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <499710722.1260642990699.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-585:
-----------------------------------

As part of DNA-582, the simple model in the JPA connector has been changed to use this transaction behavior and to commit or rollback the JPA transaction appropriately. The basic model in the JPA connector doesn't extend the MapRepository classes, but it does the same thing (using the JPA transaction directly in the connection's execute method). Therefore, this change should resolve DNA-585.

> The JPA connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------
>
>                 Key: DNA-585
>                 URL: https://jira.jboss.org/jira/browse/DNA-585
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We should be able to just commit or rollback, but we just need to do this at the appropriate time.

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

        

From jira-events at lists.jboss.org  Sat Dec 12 13:36:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-585) The JPA
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <943254042.1260568649529.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <190143693.1260642990725.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-585:
------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
         Assignee: Randall Hauch


> The JPA connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------
>
>                 Key: DNA-585
>                 URL: https://jira.jboss.org/jira/browse/DNA-585
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We should be able to just commit or rollback, but we just need to do this at the appropriate time.

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

        

From jira-events at lists.jboss.org  Sat Dec 12 13:43:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-588) The connectors should
 release all resources before notifying observer of events
In-Reply-To: <849646424.1260569369590.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2116091441.1260643410716.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-588.
-------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
       Resolution: Done
         Assignee: Randall Hauch


This was changed as part of the fix for DNA-582.

> The connectors should release all resources before notifying observer of events
> -------------------------------------------------------------------------------
>
>                 Key: DNA-588
>                 URL: https://jira.jboss.org/jira/browse/DNA-588
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Right now, most connectors are firing off the changes to the Observer before the resources acquired by the connector are released, meaning that the Observer cannot use the source within the same thread.  This prevents writing Observers that operate fully before the 'execute(...)' method returns, and requires that any Observer that might need access to the source needs to do its work asynchronously.
> By notifying the Observer _after_ the resources are released but before 'execute(...)' returns, Observers could call back to the source (really through a different connection or at least through a different 'execute(...)' call) to access content.  This means that Observers could be written to work synchronously while still access the (committed) content.

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

        

From jira-events at lists.jboss.org  Sat Dec 12 13:43:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 13:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-582) The
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <1348612834.1260567929990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1813100177.1260643410680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-582.
-------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
       Resolution: Done
         Assignee: Randall Hauch


Marking this super-task as resolved, since all unit and integration tests pass with the changes to the RequestProcessor and connector frameworks.  However, each connector needs to be addressed to make sure they properly implement the semantics, and these are addressed separately as part of the appropriate subtask.

> The connector.execute(...) method is not 'all-or-nothing'
> ---------------------------------------------------------
>
>                 Key: DNA-582
>                 URL: https://jira.jboss.org/jira/browse/DNA-582
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The RepositoryConnector.execute(ExecutionContext,Request) method does not have all-or-nothing behavior.  That is, if the request is a CompositeRequest with multiple requests to change the content, and some of those change requests result in errors, the execution should 'rollback' the changes and return the content to the state before the method was called.  In other words, either all of the requests are fulfilled, or none of them are.  
> None of the writable connectors work this way, and they all need to be corrected.  Also, this behavior needs to be documented in the connector API.  Finally, we need to make sure that the JCR session's transient state is unchanged if a save() call results in an error (the connector's state should rollback, but the session's state should remain, per Section 7.1.1.6-7.1.1.7 of JCR 1.0.1).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 12 16:42:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 16:42:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-583) The In-Memory
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <309725502.1260568410014.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <668663748.1260654150714.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-583:
-----------------------------------

Added a mechanism by which the InMemory connector maintains the original state of nodes the first time they are changed, so that the original state can be restored should the changes be rolled back.  This does add a little extra overhead as nodes are changed, but there's almost no extra overhead to committing the changes (since the original states are thrown out).  When a rollback does occur, there is (obviously) some extra work restoring the state of the changed nodes.

There is also a new TransactionalConnectorTest abstract class in the 'org.jboss.dna.graph.connector.test' package that can be subclassed to create a connector-specific test to verify that a rollback results in no changes to the state.  A new InMemoryConnectorTransactionalTest concrete class was created to test the InMemory connector.

This design was a tradeoff that achieves simplicity and straightforwardness (and encapsulation within the InMemoryRepositorySource code) while adding only modest overhead to the changes.  It is possible that the design could be improved to lower the overhead of each change, but this change does only add less than 1-2% overhead the 'dna-jcr' unit tests (<0.9sec increase on 59 sec tests, which is actually within the variation common between runs).

> The In-Memory connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------------
>
>                 Key: DNA-583
>                 URL: https://jira.jboss.org/jira/browse/DNA-583
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 1.0
>
>
> Maybe the easiest way to correct this is to record the MapNode objects before they are changed, and then if a rollback occurs, to replace the newly-changed MapNode objects with the original.  This is a bit more complicated, since individual MapNode methods are called to change the 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  Sat Dec 12 16:42:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 16:42:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-582) The
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <1348612834.1260567929990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <256669414.1260654150762.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-582:
-----------------------------------

Added a new TransactionalConnectorTest abstract class in the 'org.jboss.dna.graph.connector.test' package that can be subclassed to create a connector-specific test to verify that a rollback results in no changes to the state.  Then used this for DNA-583 by adding a new InMemoryConnectorTransactionalTest concrete class to test the InMemory connector.

> The connector.execute(...) method is not 'all-or-nothing'
> ---------------------------------------------------------
>
>                 Key: DNA-582
>                 URL: https://jira.jboss.org/jira/browse/DNA-582
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The RepositoryConnector.execute(ExecutionContext,Request) method does not have all-or-nothing behavior.  That is, if the request is a CompositeRequest with multiple requests to change the content, and some of those change requests result in errors, the execution should 'rollback' the changes and return the content to the state before the method was called.  In other words, either all of the requests are fulfilled, or none of them are.  
> None of the writable connectors work this way, and they all need to be corrected.  Also, this behavior needs to be documented in the connector API.  Finally, we need to make sure that the JCR session's transient state is unchanged if a save() call results in an error (the connector's state should rollback, but the session's state should remain, per Section 7.1.1.6-7.1.1.7 of JCR 1.0.1).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 12 16:44:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 16:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-583) The In-Memory
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <309725502.1260568410014.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <281987831.1260654270676.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-583.
-------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
       Resolution: Done
         Assignee: Randall Hauch


Marking this as completed.

> The In-Memory connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------------
>
>                 Key: DNA-583
>                 URL: https://jira.jboss.org/jira/browse/DNA-583
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Maybe the easiest way to correct this is to record the MapNode objects before they are changed, and then if a rollback occurs, to replace the newly-changed MapNode objects with the original.  This is a bit more complicated, since individual MapNode methods are called to change the 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  Sat Dec 12 16:44:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 16:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-564) Move Eclipse plugin
 code outside of the Maven modules
In-Reply-To: <255585603.1259702796558.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <615362241.1260654270709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reassigned DNA-564:
---------------------------------

    Assignee: Dan Florian  (was: Randall Hauch)


Dan is working on this.

> Move Eclipse plugin code outside of the Maven modules
> -----------------------------------------------------
>
>                 Key: DNA-564
>                 URL: https://jira.jboss.org/jira/browse/DNA-564
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> As it stands now in its current location, the Eclipse plugin projects are not Mavenized and thus cannot be easily integrated into the Maven build.  Plus, the release process is made much more complex in the current form, because the Eclipse plugin would depend on the Maven artifacts (in released form).  Therefore, we should move the Eclipse plugin source code outside of the http://anonsvn.jboss.org/repos/dna/trunk/ area of SVN and into a new http://anonsvn.jboss.org/repos/dna/eclipse/trunk area.  
> See also this email discussion thread: http://lists.jboss.org/pipermail/dna-dev/2009-November/000853.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 12 16:52:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 12 Dec 2009 16:52:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-589) The
 JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect
In-Reply-To: <979009724.1260569369609.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1066897393.1260654750597.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-589.
-------------------------------

    Fix Version/s: 0.7
                       (was: 1.0)
       Resolution: Done
         Assignee: Randall Hauch


DNA-588 is fixed, so this shouldn't be an issue anymore.

> The JcrRepository.Option.UPDATE_INDEXES_SYNCHRONOUSLY has no effect
> -------------------------------------------------------------------
>
>                 Key: DNA-589
>                 URL: https://jira.jboss.org/jira/browse/DNA-589
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> JcrRepository instances can be configured with the UPDATE_INDEXES_SYNCHRONOUSLY option to specify whether the search indexes should be updated asynchronously or synchronously.  Because of DNA-588, the option value has no effect, and all updates to the search indexes are made asynchronously.  As soon as DNA-588 is fixed, this issue should be fixed with no other changes.

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

        

From jira-events at lists.jboss.org  Sun Dec 13 20:50:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 13 Dec 2009 20:50:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <982138466.1260755430752.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-468:
-----------------------------------

Added more implementation to the LuceneSearchEngine to properly process the changes it observes from its source. Some of the individual requests can be processed by merging them (into the CreateNodeRequest or UpdatePropertiesRequests), while other kinds of requests require crawling the content (either the properties of a node or a whole subgraph), while still other kinds of events cause the wholesale re-indexing of the entire content.  (We may be able to improve the logic so that we don't have to re-index in all of the latter cases.)

Changed how the SearchEngineIndexer works so that it can perform multiple indexing operations using a single source connection and index session.  This made it possible to use this in the LuceneSearchEngine.index(ExecutionContext,Iterable<ChangeRequest>) method as described in the previous paragraph.

Added some test cases to verify that the LuceneSearchEngine is observing and updating correctly.  Tried a number of simple scenarios, and verified (with searches AND queries) that the indexes are getting updated correctly (given the kinds of changes in the tests).  Discovered that the Lucene indexes always need to be optimized prior to committing, so adjusted to '1' the number of changes allowed before optimization is done (in LuceneSearchWorkspace.CHANGES_BEFORE_OPTIMIZATION).

While doing the above, I discovered it was possible to check the right-hand-side values used in property value constraints against the numeric index rule's minimum and maximum values.  Consider a constraint 'year < 1800' and an index rule for the 'year' property.  If the rule has a minimum value of  '1900', then the constraint will never satisfy any values (the values will never be smaller than the minimum value of 1900), so we can use a 'MatchNoneQuery' query object for the constraint.  Similarly, if the constraint uses a '!=' operator, then we can return a 'MatchAllDocsQuery' query object if the right-hand-side value is outside the range of values.  This optimization is more important for numeric values, since Lucene's NumericRangeQuery can be expensive.

Incidentally, one of the tests I added does some very simplistic baseline measurements of the additional time it takes to update the indexes to reflect the changes, and the times seem to be vary wildly (the set of changes and content size are still fairly small).

> Add XPath query language support
> --------------------------------
>
>                 Key: DNA-468
>                 URL: https://jira.jboss.org/jira/browse/DNA-468
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Query, Search
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Create an XPath language binding for our graph model, so that we can parse XPath queries and produce query models that can then be executed.
> This can probably be done as a separate project dependent upon dna-graph, perhaps in the extensions folder (since it'd be a query language extension).  Maybe "extensions/dna-query-xpath"?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 08:43:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 08:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
Message-ID: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
-----------------------------------------------------------------------------

                 Key: DNA-591
                 URL: https://jira.jboss.org/jira/browse/DNA-591
             Project: DNA
          Issue Type: Bug
    Affects Versions: 0.7
            Reporter: Barry LaFond
         Attachments: test_cnd.cnd

Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')

java.lang.NullPointerException
	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)

 My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.

//------------------------------------------------------------------------------
// N A M E S P A C E S
//------------------------------------------------------------------------------
<jcr='http://www.jcp.org/jcr/1.0'>
<nt='http://www.jcp.org/jcr/nt/1.0'>
<mix='http://www.jcp.org/jcr/mix/1.0'>
<ddl='http://jboss.org/dna/ddl/1.0'>

[ddl:statement] mixin abstract
  - ddl:expression (string) mandatory
  + * (ddl:ddlProblem) = ddl:ddlProblem multiple

[ddl:schemaDefinition] > ddl:statement  mixin
  - ddl:defaultCharacterSetName (STRING)
  + * (ddl:ddlStatement) = ddl:ddlStatement multiple
  
[ddl:ddlProblem] mixin
  - ddl:problemLevel (LONG) mandatory
  - ddl:message (STRING) mandatory

The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]

Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 08:43:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 08:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1502072864.1260884610881.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-591:
-----------------------------

    Attachment: test_cnd.cnd


Breaking CND file

> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 08:45:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 08:45:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1193274352.1260884730830.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-591:
-----------------------------

    Comment: was deleted


> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 09:04:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 09:04:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1223780585.1260885870895.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-591:
-----------------------------

    Attachment: DNA_591_Test.java


Attached Test case to replicate NPE.  Place test case in dna-integration-tests  org.jboss.dna.test.integration package and the test_cnd.cnd file in the corresponding resource package

> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 09:26:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 15 Dec 2009 09:26:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <140104167.1260887191071.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-591:
-----------------------------------

If if it turns out that this is particular case has an incorrect CND, we need to figure out is why we're not identifying errors/warnings in the CND importer, and why those errors are not being reported when the JcrRepository loads them into the node type manager.

> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 09:55:31 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 09:55:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1473064988.1260888931066.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-591:
-----------------------------

    Attachment: test_cnd.cnd


> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 09:55:31 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 09:55:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1280328199.1260888931045.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-591:
-----------------------------

    Attachment:     (was: test_cnd.cnd)


> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 09:59:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 15 Dec 2009 09:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-564) Move Eclipse plugin
 code outside of the Maven modules
In-Reply-To: <255585603.1259702796558.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <602998276.1260889170603.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-564.
-----------------------------

    Resolution: Done


The DNA REST Eclipse projects/plugins have been moved from dna/trunk to dna/eclipse/trunk. This maybe a temporary new home as they could be moving soon to JBossTools prior to releasing them along with DNA 1.0.

> Move Eclipse plugin code outside of the Maven modules
> -----------------------------------------------------
>
>                 Key: DNA-564
>                 URL: https://jira.jboss.org/jira/browse/DNA-564
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> As it stands now in its current location, the Eclipse plugin projects are not Mavenized and thus cannot be easily integrated into the Maven build.  Plus, the release process is made much more complex in the current form, because the Eclipse plugin would depend on the Maven artifacts (in released form).  Therefore, we should move the Eclipse plugin source code outside of the http://anonsvn.jboss.org/repos/dna/trunk/ area of SVN and into a new http://anonsvn.jboss.org/repos/dna/eclipse/trunk area.  
> See also this email discussion thread: http://lists.jboss.org/pipermail/dna-dev/2009-November/000853.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 10:31:31 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Tue, 15 Dec 2009 10:31:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-592) The DNA REST Server
 Registry Should Be Moved From The DNA REST Client Maven Project To The
 Eclipse Plugin
Message-ID: <109903738.1260891091098.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The DNA REST Server Registry Should Be Moved From The DNA REST Client Maven Project To The Eclipse Plugin
---------------------------------------------------------------------------------------------------------

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


The REST client Maven project currently maintains and persists a server registry. This project only uses this registry to verify a DNA server (a host running the DNA REST web service) is registered before allowing a publishing or unpublishing operation to take place. A short circuit if you will. But a better design would be for this project to not impose having a server registry at all. The server registry should be moved to the DNA REST Eclipse UI plugin.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 15 10:09:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 15 Dec 2009 10:09:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <820055106.1260889770643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond commented on DNA-591:
----------------------------------

Note:  If I change the following:

[ddl:schemaDefinition] > ddl:statement  mixin
  - ddl:defaultCharacterSetName (STRING)
  + * (ddl:statement) = ddl:statement multiple

to specifically name the child statements instead of the wildcard '*', the NPE does NOT occur

[ddl:schemaDefinition] > ddl:statement  mixin
  - ddl:defaultCharacterSetName (STRING)
  + ddl:childStatements (ddl:statement) = ddl:statement multiple

> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 11:23:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 16 Dec 2009 11:23:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-593) File system connector
 documentation is missing the 'updatesAllowed' property
Message-ID: <2125880841.1260980610643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

File system connector documentation is missing the 'updatesAllowed' property
----------------------------------------------------------------------------

                 Key: DNA-593
                 URL: https://jira.jboss.org/jira/browse/DNA-593
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Documentation
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Brian Carothers
            Priority: Critical
             Fix For: 0.7


The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-connector.html) is missing the 'updatesAllowed' property.

Marking as 'critical' just so it gets done.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 11:25:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 16 Dec 2009 11:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-594) The JDBC Metadata
 Connector documentation in Reference Guide is missing
Message-ID: <357149707.1260980730586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The JDBC Metadata Connector documentation in Reference Guide is missing
-----------------------------------------------------------------------

                 Key: DNA-594
                 URL: https://jira.jboss.org/jira/browse/DNA-594
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Documentation
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Brian Carothers
            Priority: Critical
             Fix For: 0.7


The Reference Guide lists in the TOC the chapter on the JDBC Metadata Connector and has a link for it, but the chapter doesn't exist.  Since 0.7 won't have include the connector, we should remove it from the TOC, and add it back in when we have something.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 11:27:34 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 16 Dec 2009 11:27:34 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-594) The JDBC Metadata
 Connector documentation in Reference Guide is missing
In-Reply-To: <357149707.1260980730586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1542888139.1260980854575.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-594:
-----------------------------------

Brian, I assigned this to you in case you make some progress on the connector and it makes it into 0.7 (even if the connector is 'technology preview').  If that's the case, we'll need to _add_ the chapter on the connector.  If the updated connector is not ready, then we can just remove the chapter from the TOC.

> The JDBC Metadata Connector documentation in Reference Guide is missing
> -----------------------------------------------------------------------
>
>                 Key: DNA-594
>                 URL: https://jira.jboss.org/jira/browse/DNA-594
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>
> The Reference Guide lists in the TOC the chapter on the JDBC Metadata Connector and has a link for it, but the chapter doesn't exist.  Since 0.7 won't have include the connector, we should remove it from the TOC, and add it back in when we have something.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 11:42:32 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 16 Dec 2009 11:42:32 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-595) Connector chapters in
 the Reference Guide should should examples of configuring in Java code and
 XML configuration
Message-ID: <1203983171.1260981752191.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Connector chapters in the Reference Guide should should examples of configuring in Java code and XML configuration
------------------------------------------------------------------------------------------------------------------

                 Key: DNA-595
                 URL: https://jira.jboss.org/jira/browse/DNA-595
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Documentation
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.0


The Reference Guide has a chapter describing each connector, and those chapters usually describe the various settings and talk about how to use.  All of these chapters should document how to configure programmatically using JcrConfiguration AND how to configure using the XML format.  Most only show one approach.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 13:53:31 2009
From: jira-events at lists.jboss.org (Jason Dobies (JIRA))
Date: Wed, 16 Dec 2009 13:53:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-596) Relax security by
 default to be more accessible to new users
Message-ID: <1795356049.1260989611394.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Relax security by default to be more accessible to new users
------------------------------------------------------------

                 Key: DNA-596
                 URL: https://jira.jboss.org/jira/browse/DNA-596
             Project: DNA
          Issue Type: Feature Request
          Components: Documentation, Examples
    Affects Versions: 0.6
            Reporter: Jason Dobies


While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues:

- I wasn't able to simply login using Repository.login(). I had to configure and use JAAS.
- I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update"

The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true.

After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired).

On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 15:33:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Wed, 16 Dec 2009 15:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-597) Namespace
 inconsistencies in example and sequencer CND files
Message-ID: <2108722294.1260995610668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Namespace inconsistencies in example and sequencer CND files
------------------------------------------------------------

                 Key: DNA-597
                 URL: https://jira.jboss.org/jira/browse/DNA-597
             Project: DNA
          Issue Type: Bug
    Affects Versions: 0.6
            Reporter: Barry LaFond
             Fix For: 0.7


While debugging the new DDL Sequencer Integration test, noticed that some of the CND files for other sequencers were using inconsistent namespace definitions.

Namely, some use "http://jboss.org/xxx/1.0/" and others use "http://www.jboss.org//xxxx/1.0/"

Let's be consistent and use the "www" form.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 15:35:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Wed, 16 Dec 2009 15:35:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-597) Namespace
 inconsistencies in example and sequencer CND files
In-Reply-To: <2108722294.1260995610668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <512017823.1260995730647.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond reassigned DNA-597:
--------------------------------

    Assignee: Barry LaFond


> Namespace inconsistencies in example and sequencer CND files
> ------------------------------------------------------------
>
>                 Key: DNA-597
>                 URL: https://jira.jboss.org/jira/browse/DNA-597
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While debugging the new DDL Sequencer Integration test, noticed that some of the CND files for other sequencers were using inconsistent namespace definitions.
> Namely, some use "http://jboss.org/xxx/1.0/" and others use "http://www.jboss.org//xxxx/1.0/"
> Let's be consistent and use the "www" form.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 16 15:50:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Wed, 16 Dec 2009 15:50:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-597) Namespace
 inconsistencies in example and sequencer CND files
In-Reply-To: <2108722294.1260995610668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <901055800.1260996630804.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-597:
-----------------------------

    Component/s: Sequencers
    Description: 
While debugging the new DDL Sequencer Integration test, noticed that some of the CND files for other sequencers were using inconsistent namespace definitions.

Namely, some use "http://jboss.org/xxx/1.0/" and others use "http://www.jboss.org/xxxx/1.0/"

Let's be consistent and use the "www" form.

  was:
While debugging the new DDL Sequencer Integration test, noticed that some of the CND files for other sequencers were using inconsistent namespace definitions.

Namely, some use "http://jboss.org/xxx/1.0/" and others use "http://www.jboss.org//xxxx/1.0/"

Let's be consistent and use the "www" form.



> Namespace inconsistencies in example and sequencer CND files
> ------------------------------------------------------------
>
>                 Key: DNA-597
>                 URL: https://jira.jboss.org/jira/browse/DNA-597
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>
> While debugging the new DDL Sequencer Integration test, noticed that some of the CND files for other sequencers were using inconsistent namespace definitions.
> Namely, some use "http://jboss.org/xxx/1.0/" and others use "http://www.jboss.org/xxxx/1.0/"
> Let's be consistent and use the "www" form.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 17 15:26:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 15:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
Message-ID: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
-----------------------------------------------------------------------------------------------------------

                 Key: DNA-598
                 URL: https://jira.jboss.org/jira/browse/DNA-598
             Project: DNA
          Issue Type: Bug
          Components: JCR
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.7


A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 17 15:37:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 15:37:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
In-Reply-To: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1915020885.1261082250629.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-598:
-----------------------------------

Fixed the problem with the shutdown leaving idle threads and blocking termination of the VM.  After debugging (and using a new NameThreadFactory that creates threads with names beginning with a specified prefix), it's clear now that these extra threads were owned by the Executor used in the FederatedRepositorySource, and this executor was not being shutdown in the FederatedRepositorySource.close() method.  The Executor was creating the threads with a timeout of 60sec, which makes sense.  Fixing this now properly shuts down the Executor, and this fixes the problem.

> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-598
>                 URL: https://jira.jboss.org/jira/browse/DNA-598
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 17 15:37:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 15:37:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
In-Reply-To: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1240280406.1261082250659.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-598.
-------------------------------

    Resolution: Done


> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-598
>                 URL: https://jira.jboss.org/jira/browse/DNA-598
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 17 20:53:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 20:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <943351088.1261101210763.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-468:
-----------------------------------

Completed more of the integration, including the addition of the mandatory 'jcr:path' and 'jcr:score' so-called 'pseudo-columns' to the results for XPath queries.  However, there still are issues with the TCK query-related tests, so they are not enabled at the moment.

> Add XPath query language support
> --------------------------------
>
>                 Key: DNA-468
>                 URL: https://jira.jboss.org/jira/browse/DNA-468
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Query, Search
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Create an XPath language binding for our graph model, so that we can parse XPath queries and produce query models that can then be executed.
> This can probably be done as a separate project dependent upon dna-graph, perhaps in the extensions folder (since it'd be a query language extension).  Maybe "extensions/dna-query-xpath"?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 17 20:53:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 20:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <260817719.1261101210913.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-37:
-----------------------------

    Attachment: DNA-37_jdbc_meta_connector.patch


> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Sergiy Litsenko
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Thu Dec 17 20:53:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 20:53:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <1156744657.1261101211089.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-37:
-----------------------------

    Attachment: DNA-37_graph_changes.patch


> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Sergiy Litsenko
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Thu Dec 17 20:53:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 20:53:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <1003030181.1261101211197.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-37:
-----------------------------

    Attachment: DNA-37_deletes_and_project_pom.patch


> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Sergiy Litsenko
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Thu Dec 17 21:03:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 21:03:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-37) Federate schema
 information from relational sources
Message-ID: <34840775.1261101810647.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-37:
----------------------------------

Updated three patch files created by BCar (who is currently having login issues) that restructure this connector.  From Brian:

- DNA-37_deletes_and_project_pom.patch - Deletes the existing dna-common-jdbc project and substantially all of the existing files in the dna-connector-metadata project.  At the very bottom, it also makes changes to the master project pom, removing the reference to the dna-common-jdbc module and making all of the JDBC driver JARs be test-scoped so that we don't end up with a compile time dependency in all of our projects (we currently do, I checked).  I also accidentally commented out the dna-sequencer-java module.  That's unintentional, but it seems safer to let you not patch that one line than to try to redo the whole patch file.
- DNA-37_graph_changes.patch - Adds a new read-only path-based repository framework.  This is intended to complement the map repository framework, although it does not yet support writes.  The patch also corrects a minor error that I caught in the name of one of the messages.
- DNA-37_jdbc_meta_connector.patch - Adds the JDBC metadata connector itself along with its associated tests.  The patch is surprisingly lengthy (due mostly to the large number of configurable properties on the source), but its conceptually very simple.  The JdbcMetadataSource is patterned after the JpaSource, but it creates a PathRepositoryConnection instead of a MapRepositoryConnection.  The JdbcPathRepository is persistent across connections (like the InfinispanRepository, JBossCacheRepository, InMemoryRepository, and InMemoryRepository, but unlike the SimpleJpaRepository), and provides an internal class that implements the PathWorkspace interface to do the bulk of the connector-specific work.  This class has 1 method each for creating the 8 different node types (root node, catalog node, schema node, tables node, table node, column node, procedures node, procedure node).

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Sergiy Litsenko
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Thu Dec 17 22:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 17 Dec 2009 22:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <112743876.1261105230686.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-37:
-----------------------------

    Assignee: Brian Carothers  (was: Sergiy Litsenko)


Committed Brian's patches (with only minor modification). This is a great to have this connector working and in the release.  Nice job, Brian!

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Fri Dec 18 08:49:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 18 Dec 2009 08:49:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-599) Upgrade to SVNKit
	1.3.2-1
Message-ID: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Upgrade to SVNKit 1.3.2-1
-------------------------

                 Key: DNA-599
                 URL: https://jira.jboss.org/jira/browse/DNA-599
             Project: DNA
          Issue Type: Thirdparty Change
          Components: Connectors
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 10:19:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 18 Dec 2009 10:19:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-599) Upgrade to SVNKit
	1.3.2-1
In-Reply-To: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1907415911.1261149570730.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-599.
-------------------------------

    Resolution: Won't Fix


> Upgrade to SVNKit 1.3.2-1
> -------------------------
>
>                 Key: DNA-599
>                 URL: https://jira.jboss.org/jira/browse/DNA-599
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 10:19:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 18 Dec 2009 10:19:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-599) Upgrade to SVNKit
	1.3.2-1
In-Reply-To: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1163965025.1261149570694.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-599:
-----------------------------------

SVNKit version 1.3.1 and later now have a dependency on SQLJet, which is open source under the GPL.  This is not acceptable to us, since our connector would then fall under GPL.  I've afraid we cannot do this.  It may be possible to upgrade to 1.3.0, since it doesn't use SVNKit.  However, the 3 versions since (1.3.1, 1.3.2, 1.3.2-1) all have bug fixes.

Serge, feel free to test with 1.3.0 to see if we want to upgrade.  If so, please re-open this issue and I'll upload the artifacts to the JBoss Maven repository.  Otherwise, for the moment I'll mark as 'will not fix'.

> Upgrade to SVNKit 1.3.2-1
> -------------------------
>
>                 Key: DNA-599
>                 URL: https://jira.jboss.org/jira/browse/DNA-599
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 10:31:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 18 Dec 2009 10:31:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-596) Relax security by
 default to be more accessible to new users
In-Reply-To: <1795356049.1260989611394.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <813151729.1261150296003.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-596:
------------------------------

    Fix Version/s: 0.7
         Assignee: Brian Carothers


> Relax security by default to be more accessible to new users
> ------------------------------------------------------------
>
>                 Key: DNA-596
>                 URL: https://jira.jboss.org/jira/browse/DNA-596
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Documentation, Examples
>    Affects Versions: 0.6
>            Reporter: Jason Dobies
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>
> While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues:
> - I wasn't able to simply login using Repository.login(). I had to configure and use JAAS.
> - I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update"
> The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true.
> After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired).
> On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 11:33:31 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 18 Dec 2009 11:33:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-599) Upgrade to SVNKit
	1.3.2-1
In-Reply-To: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1325162891.1261154011247.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop reopened DNA-599:
--------------------------------------



upload the svnkit with version 1.3.0 and we will upgrade dna svn connector to that version

> Upgrade to SVNKit 1.3.2-1
> -------------------------
>
>                 Key: DNA-599
>                 URL: https://jira.jboss.org/jira/browse/DNA-599
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 12:05:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 18 Dec 2009 12:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
In-Reply-To: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <517672789.1261155930664.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian reopened DNA-598:
-----------------------------

      Assignee: Dan Florian  (was: Randall Hauch)


Found another ExecutorService that needs to be shutdown. The JcrRepository's RepositoryObservationManager inner class has a service that isn't being shutdown.

> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-598
>                 URL: https://jira.jboss.org/jira/browse/DNA-598
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 14:12:30 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 18 Dec 2009 14:12:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-600) mvn eclipse:clean
 eclipse:eclipse doesn't work on dna-connector-store-jpa
Message-ID: <1511559070.1261163550660.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa
-------------------------------------------------------------------------

                 Key: DNA-600
                 URL: https://jira.jboss.org/jira/browse/DNA-600
             Project: DNA
          Issue Type: Bug
          Components: Development Environment
    Affects Versions: 0.7, 1.0, 1.1, Future Releases
         Environment: MAC OS X 10.6.2, java version "1.6.0_17", Apache Maven 2.2.0 
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
            Priority: Critical
             Fix For: 0.7


During building the DNA modules with mvn clean install eclipse:clean eclipse:eclipse I got this error:

------ Start Error Trace
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
        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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true

------ End Error Trace

Because this is a bug in the maven eclipse plugin version 2.7, this link "http://stackoverflow.com/questions/1397903/setting-project-for-eclipse-using-maven" gives more information about

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 15:01:31 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 18 Dec 2009 15:01:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
In-Reply-To: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2115258228.1261166491167.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian updated DNA-598:
----------------------------

    Attachment: DNA598_dna-jcr.patch


Code to shutdown the JcrRepository#RepositoryObservationManager's ExecutorService. 

> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-598
>                 URL: https://jira.jboss.org/jira/browse/DNA-598
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>         Attachments: DNA598_dna-jcr.patch
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 15:59:30 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 18 Dec 2009 15:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-598) Shutting down
 JcrEngine returns,
 but leaves idle threads running (preventing shutdown of VM) for 60 seconds
In-Reply-To: <884606670.1261081590709.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1100552595.1261169970688.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-598.
-----------------------------

    Resolution: Done


The ExecutorService in JcrRepository#RepositoryObservationManager is now being shutdown when the repository is closed.

> Shutting down JcrEngine returns, but leaves idle threads running (preventing shutdown of VM) for 60 seconds
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-598
>                 URL: https://jira.jboss.org/jira/browse/DNA-598
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>         Attachments: DNA598_dna-jcr.patch
>
>
> A simple program that configures, starts, uses, and then (properly) shuts down a JcrEngine will work correctly, but the VM will not exit for roughly 60 seconds after the engine is shutdown.  A stack dump shows that there are several running (but idle) worker threads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 18 22:24:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 18 Dec 2009 22:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <1091528795.1261193070669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-37:
-------------------------------

    Attachment: DNA-37_mysql_postgresql.patch


Thanks!  

However, as soon as I started testing against other drivers, I found a few one-off issues.  The attached patch gets the connector to a state where it will work with HSQLDB, MySql5, or PostgreSQL8.  The Oracle, MS, Sybase, and DB2 JDBC drivers don't seem to be in the JBoss maven repository anymore, so I haven't tested against those yet.

The patch adds the support for MySQL and PostgreSQL and fixes two minor problems with the previous patches that Randall had caught, switching JdbcMetadataException to be an unchecked exception and using the more efficient Path.getSegmentsList() instead of Path.getSegmentsAsArray() in JdbcMetadataRepository.getNode(Path).

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Sat Dec 19 09:06:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 09:06:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-593) File system connector
 documentation is missing the 'updatesAllowed' property
In-Reply-To: <2125880841.1260980610643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <771368965.1261231590633.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-593:
--------------------------------

    Attachment: DNA-593.patch


Updated the documentation to reflect that the connector is no longer read-only (incl. adding the updatesAllowed property to the docs) and renamed the getSupportsUpdates method to be consistent with the setUpdatesAllowed mutator.

Added references to the custom properties factory, but didn't complete the sub-section describing the behavior yet.  I'm going to leave this defect open until that gets addressed better.

> File system connector documentation is missing the 'updatesAllowed' property
> ----------------------------------------------------------------------------
>
>                 Key: DNA-593
>                 URL: https://jira.jboss.org/jira/browse/DNA-593
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-593.patch
>
>
> The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-connector.html) is missing the 'updatesAllowed' property.
> Marking as 'critical' just so it gets done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 19 11:23:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 11:23:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-594) The JDBC Metadata
 Connector documentation in Reference Guide is missing
In-Reply-To: <357149707.1260980730586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <364757236.1261239810924.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-594:
--------------------------------

    Attachment: DNA-594.patch


Attached patch that fixes the link to the JDBC metadata connector page and brings it up to the same standard as the other connector pages in the reference guide.  Also corrects a few typos in the JPA connector page.

The patch doesn't explicitly list the connector as "experimental" or "technology preview" yet because I'm pretty confident that I'll at least be able to test it against MSSQL and Oracle prior to the 0.7 release.  The page does list the drivers that the connector has been tested against.

> The JDBC Metadata Connector documentation in Reference Guide is missing
> -----------------------------------------------------------------------
>
>                 Key: DNA-594
>                 URL: https://jira.jboss.org/jira/browse/DNA-594
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-594.patch
>
>
> The Reference Guide lists in the TOC the chapter on the JDBC Metadata Connector and has a link for it, but the chapter doesn't exist.  Since 0.7 won't have include the connector, we should remove it from the TOC, and add it back in when we have something.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 19 11:25:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 11:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-594) The JDBC Metadata
 Connector documentation in Reference Guide is missing
In-Reply-To: <357149707.1260980730586.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <574996747.1261239930809.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-594.
---------------------------------

    Resolution: Done


Applied patch to resolve defect.  The reference guide is now up-to-date with the connector.  As the solution to DNA-37 evolves, the documentation can be updated accordingly as part of that defect.

> The JDBC Metadata Connector documentation in Reference Guide is missing
> -----------------------------------------------------------------------
>
>                 Key: DNA-594
>                 URL: https://jira.jboss.org/jira/browse/DNA-594
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-594.patch
>
>
> The Reference Guide lists in the TOC the chapter on the JDBC Metadata Connector and has a link for it, but the chapter doesn't exist.  Since 0.7 won't have include the connector, we should remove it from the TOC, and add it back in when we have something.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 19 12:24:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 12:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-596) Relax security by
 default to be more accessible to new users
In-Reply-To: <1795356049.1260989611394.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1048422957.1261243470885.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-596:
--------------------------------

    Attachment: DNA-596.patch


Per discussion with Jason and Randall, the attached patch makes the following changes:

1.  Makes the default anonymous (guest) user access "admin"
2.  Makes the FileSystem error message for attempts to update a source that does not allow updates more specific:
        The source "{0}" does not allow updates.  Set the "updatesAllowed" property to "true" on the repository source (connector) to enable updates. 
3.  Modifies the Getting Started Guide to highlight the default settings and provide examples for how to modify the setting through XML or programmatic or XML configuration.
4.  Modifies the Reference Guide to describe the impact of the ANONYMOUS_USER_ROLES setting and provide a reference to the examples in the Getting Started Guide

> Relax security by default to be more accessible to new users
> ------------------------------------------------------------
>
>                 Key: DNA-596
>                 URL: https://jira.jboss.org/jira/browse/DNA-596
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Documentation, Examples
>    Affects Versions: 0.6
>            Reporter: Jason Dobies
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-596.patch
>
>
> While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues:
> - I wasn't able to simply login using Repository.login(). I had to configure and use JAAS.
> - I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update"
> The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true.
> After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired).
> On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 19 12:27:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 12:27:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-596) Relax security by
 default to be more accessible to new users
In-Reply-To: <1795356049.1260989611394.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1609125410.1261243650644.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-596.
---------------------------------

    Resolution: Done


Committed patch to resolve issue.  I think that should cover it, but if anyone sees anything I missed, please feel free to re-open this.

> Relax security by default to be more accessible to new users
> ------------------------------------------------------------
>
>                 Key: DNA-596
>                 URL: https://jira.jboss.org/jira/browse/DNA-596
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Documentation, Examples
>    Affects Versions: 0.6
>            Reporter: Jason Dobies
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-596.patch
>
>
> While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues:
> - I wasn't able to simply login using Repository.login(). I had to configure and use JAAS.
> - I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update"
> The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true.
> After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired).
> On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 19 12:29:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 19 Dec 2009 12:29:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Work started: (DNA-593) File system
 connector documentation is missing the 'updatesAllowed' property
In-Reply-To: <2125880841.1260980610643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <318758094.1261243770606.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Work on DNA-593 started by Brian Carothers.

> File system connector documentation is missing the 'updatesAllowed' property
> ----------------------------------------------------------------------------
>
>                 Key: DNA-593
>                 URL: https://jira.jboss.org/jira/browse/DNA-593
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-593.patch
>
>
> The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-connector.html) is missing the 'updatesAllowed' property.
> Marking as 'critical' just so it gets done.

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

        

From jira-events at lists.jboss.org  Sun Dec 20 20:20:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 20 Dec 2009 20:20:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <1743558623.1261358430680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-37:
-------------------------------

    Attachment: DNA-37_other_databases.patch


Attached patch that adds DDL and code corrections for other databases (Oracle 10g/11g, MS SQL 2008, IBM DB2 v9, Sybase ASE 15).

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Mon Dec 21 09:21:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 09:21:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-37) Federate schema
 information from relational sources
Message-ID: <2110033771.1261405290706.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-37:
-------------------------------

    Attachment: DNA-37_jcr_works.patch


Attached patch that adds custom node types, a JCR integration test for the connector, a provision to the integration test framework to allow for the importing of a custom node types file, and a minor fix to getProperties().

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jcr_works.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Mon Dec 21 09:25:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 09:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-37) Federate schema
 information from relational sources
Message-ID: <1580237537.1261405530595.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-37.
--------------------------------

    Fix Version/s: 0.7
                       (was: 1.1)
       Resolution: Done


Committed patch to complete integration with JCR layer.  At this point, the connector functions like any other read-only connector, so I am going to mark this defect as resolved.  If any new feature requests or bugs come up, they can be opened and addressed separately.

> Federate schema information from relational sources
> ---------------------------------------------------
>
>                 Key: DNA-37
>                 URL: https://jira.jboss.org/jira/browse/DNA-37
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-37_deletes_and_project_pom.patch, DNA-37_graph_changes.patch, DNA-37_jcr_works.patch, DNA-37_jdbc_meta_connector.patch, DNA-37_mysql_postgresql.patch, DNA-37_other_databases.patch
>
>
> Create a connector for the federation engine that contributes and exposes the database schema information for a relational database (via JDBC) into the federated repository.  This would make it possible to have a repository provide information about the databases in an organization.  One choice would be whether to import (and copy) the schema structure, or to provide access to it in real time.

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

        

From jira-events at lists.jboss.org  Mon Dec 21 15:33:31 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 15:33:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-105) Sequence content from
 delimited text files
In-Reply-To: <25062773.1212612560463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1072865831.1261427611095.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-105:
--------------------------------

    Attachment: DNA-105_preview.patch


Attached patch that adds a new project with two new sequencers, one for parsing sequencing files and one for sequencing fixed width files.  Both sequencers are row-based and assume that the file is allocated at one row per line with the EOL character being recognizable by BufferedReader.readLine().  Both sequencers support basic functionality like being able to specify a comment character and custom factory for creating the record associated with each row.

The DelimitedTextSequencer allows users to specify a particular regular expression that is used to split each line into columns.  This value defaults to ",", presumably allowing this solution to address DNA-229 as well.  Since any valid regular expression can be used, this also allows for the use of multiple delimiters.

The FixedWidthTextSequencer allows users to specify the column index at which each column starts either as an array of ints or as a single, comma-delimited string.  As an example, a user could specify { 3, 6 } as this index to sequence this line: 

 onetwothree

into this array of columns: 

one, two, three

The attached patch is about as undocumented as possible, but it's exceedingly straightforward.  In fact, there's only about 100 lines of actual code.  The rest is just test cases and test data.  I'm going to leave this out for a day or two in case anyone has comments.  If no major concerns are expressed, I'm going to add documentation, commit this, and then treat any future bugs or feature requests as separate issues.





> Sequence content from delimited text files
> ------------------------------------------
>
>                 Key: DNA-105
>                 URL: https://jira.jboss.org/jira/browse/DNA-105
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Greg Haber
>            Priority: Minor
>             Fix For: Future Releases
>
>         Attachments: DNA-105_preview.patch
>
>
> It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file.  A sequencer to capture this metadata could be useful,and should be straightforward to implement.

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

        

From jira-events at lists.jboss.org  Mon Dec 21 15:33:31 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 15:33:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-105) Sequence content from
 delimited text files
In-Reply-To: <25062773.1212612560463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <848192669.1261427611115.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reassigned DNA-105:
-----------------------------------

    Assignee: Brian Carothers


> Sequence content from delimited text files
> ------------------------------------------
>
>                 Key: DNA-105
>                 URL: https://jira.jboss.org/jira/browse/DNA-105
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Greg Haber
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: Future Releases
>
>         Attachments: DNA-105_preview.patch
>
>
> It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file.  A sequencer to capture this metadata could be useful,and should be straightforward to implement.

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

        

From jira-events at lists.jboss.org  Mon Dec 21 15:56:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 15:56:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-595) Connector chapters in
 the Reference Guide should should examples of configuring in Java code and
 XML configuration
In-Reply-To: <1203983171.1260981752191.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <938163642.1261428990744.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reassigned DNA-595:
-----------------------------------

    Assignee: Brian Carothers


> Connector chapters in the Reference Guide should should examples of configuring in Java code and XML configuration
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-595
>                 URL: https://jira.jboss.org/jira/browse/DNA-595
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.0
>
>
> The Reference Guide has a chapter describing each connector, and those chapters usually describe the various settings and talk about how to use.  All of these chapters should document how to configure programmatically using JcrConfiguration AND how to configure using the XML format.  Most only show one approach.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 21 18:47:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 18:47:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-593) File system connector
 documentation is missing the 'updatesAllowed' property
In-Reply-To: <2125880841.1260980610643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1794583006.1261439250872.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-593:
--------------------------------

    Attachment: DNA-593_final.patch


Attached patch that cleans up the file system connector page.  It does not expound on the CustomPropertiesFactory since the Javadoc for that class is pretty descriptive.

> File system connector documentation is missing the 'updatesAllowed' property
> ----------------------------------------------------------------------------
>
>                 Key: DNA-593
>                 URL: https://jira.jboss.org/jira/browse/DNA-593
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-593.patch, DNA-593_final.patch
>
>
> The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-connector.html) is missing the 'updatesAllowed' property.
> Marking as 'critical' just so it gets done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 21 18:49:36 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 21 Dec 2009 18:49:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-593) File system connector
 documentation is missing the 'updatesAllowed' property
In-Reply-To: <2125880841.1260980610643.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <253824853.1261439376170.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-593.
---------------------------------

    Resolution: Done


Committed patch to resolve issue.  The original issue with the updatesAllowed property is addressed.  If more documentation needs to be added for the CustomPropertiesFactory, that can be done under a separate issue.

> File system connector documentation is missing the 'updatesAllowed' property
> ----------------------------------------------------------------------------
>
>                 Key: DNA-593
>                 URL: https://jira.jboss.org/jira/browse/DNA-593
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-593.patch, DNA-593_final.patch
>
>
> The Reference Guide chapter on the File System connector (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/file-system-connector.html) is missing the 'updatesAllowed' property.
> Marking as 'critical' just so it gets done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 22 08:33:30 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 22 Dec 2009 08:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-600) mvn eclipse:clean
 eclipse:eclipse doesn't work on dna-connector-store-jpa
In-Reply-To: <1511559070.1261163550660.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <386096037.1261488810990.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop resolved DNA-600.
--------------------------------------

    Fix Version/s: 1.0
                   1.1
                   Future Releases
       Resolution: Done


Bug is only existent in the version 2.7 of Maven Eclipse Plugin

> mvn eclipse:clean eclipse:eclipse doesn't work on dna-connector-store-jpa
> -------------------------------------------------------------------------
>
>                 Key: DNA-600
>                 URL: https://jira.jboss.org/jira/browse/DNA-600
>             Project: DNA
>          Issue Type: Bug
>          Components: Development Environment
>    Affects Versions: 0.7, 1.0, 1.1, Future Releases
>         Environment: MAC OS X 10.6.2, java version "1.6.0_17", Apache Maven 2.2.0 
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>            Priority: Critical
>             Fix For: 0.7, 1.0, 1.1, Future Releases
>
>
> During building the DNA modules with mvn clean install eclipse:clean eclipse:eclipse I got this error:
> ------ Start Error Trace
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>         at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>         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 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Request to merge when 'filtering' is not identical. Original=resource src/test/resources: output=target/test-classes, include=[*|**/*], exclude=[database.properties|**/*.java], test=true, filtering=false, merging with=resource src/test/resources: output=target/test-classes, include=[database.properties], exclude=[**/*.java], test=true, filtering=true
> ------ End Error Trace
> Because this is a bug in the maven eclipse plugin version 2.7, this link "http://stackoverflow.com/questions/1397903/setting-project-for-eclipse-using-maven" gives more information about

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 22 16:31:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 16:31:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-105) Sequence content from
 delimited text files
In-Reply-To: <25062773.1212612560463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1903946698.1261517490615.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-105:
--------------------------------

    Attachment: DNA-105_final.patch


Attached more refined version of the previous patch.  This version includes documentation (incl. the obligatory Reference Guide chapter), integration with the gettingstarted sequencers example, and a maximumLinesToRead property that allows the sequencers to be configured to not sequencer an entire file.

The patch also modifes StreamSequencerAdapter.setConfiguration to allow for properties to be set on StreamSequencers through DnaConfiguration.

> Sequence content from delimited text files
> ------------------------------------------
>
>                 Key: DNA-105
>                 URL: https://jira.jboss.org/jira/browse/DNA-105
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Greg Haber
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: Future Releases
>
>         Attachments: DNA-105_final.patch, DNA-105_preview.patch
>
>
> It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file.  A sequencer to capture this metadata could be useful,and should be straightforward to implement.

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

        

From jira-events at lists.jboss.org  Tue Dec 22 16:36:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 16:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-601) POM Version of HSQLDB
 No Longer Exists in Maven Repository
Message-ID: <1223411731.1261517790788.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

POM Version of HSQLDB No Longer Exists in Maven Repository
----------------------------------------------------------

                 Key: DNA-601
                 URL: https://jira.jboss.org/jira/browse/DNA-601
             Project: DNA
          Issue Type: Bug
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
            Priority: Blocker


The HSQLDB version 1.8.0.7 no longer exists in the project Maven repository.  Current versions that we can choose from are 1.7.2, 1.8.0.2, 1.8.0.8-brew, 1.8.0.8patch01-brew, and 1.8.0.8patch02-brew.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 22 16:40:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 16:40:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-601) POM Version of HSQLDB
 No Longer Exists in Maven Repository
In-Reply-To: <1223411731.1261517790788.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <80816604.1261518030693.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-601:
--------------------------------

    Attachment: DNA-601.patch


Attached patch that centralizes the version of the HSQLDB JAR in the project POM and sets it to 1.8.0.2 (where it already was for the JPA connector but not the JDBC metadata connector)

> POM Version of HSQLDB No Longer Exists in Maven Repository
> ----------------------------------------------------------
>
>                 Key: DNA-601
>                 URL: https://jira.jboss.org/jira/browse/DNA-601
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-601.patch
>
>
> The HSQLDB version 1.8.0.7 no longer exists in the project Maven repository.  Current versions that we can choose from are 1.7.2, 1.8.0.2, 1.8.0.8-brew, 1.8.0.8patch01-brew, and 1.8.0.8patch02-brew.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 22 16:40:31 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 16:40:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-601) POM Version of HSQLDB
 No Longer Exists in Maven Repository
In-Reply-To: <1223411731.1261517790788.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1384531849.1261518031514.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-601.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Committed patch to resolve issue

> POM Version of HSQLDB No Longer Exists in Maven Repository
> ----------------------------------------------------------
>
>                 Key: DNA-601
>                 URL: https://jira.jboss.org/jira/browse/DNA-601
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-601.patch
>
>
> The HSQLDB version 1.8.0.7 no longer exists in the project Maven repository.  Current versions that we can choose from are 1.7.2, 1.8.0.2, 1.8.0.8-brew, 1.8.0.8patch01-brew, and 1.8.0.8patch02-brew.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 22 16:42:31 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 16:42:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-105) Sequence content from
 delimited text files
In-Reply-To: <25062773.1212612560463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7693175.1261518151096.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-105.
---------------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Done


Committing patch to resolve defect.  

> Sequence content from delimited text files
> ------------------------------------------
>
>                 Key: DNA-105
>                 URL: https://jira.jboss.org/jira/browse/DNA-105
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Greg Haber
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-105_final.patch, DNA-105_preview.patch
>
>
> It is a somewhat common practice for delimited text files such as comma-separated (CSV) or tab delimited files to contain a list of column names in the first line of the file.  A sequencer to capture this metadata could be useful,and should be straightforward to implement.

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

        

From jira-events at lists.jboss.org  Tue Dec 22 21:08:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 22 Dec 2009 21:08:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-591) NullPointerException
 in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded()
In-Reply-To: <1320558796.1260884610724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1605517772.1261534110656.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-591:
--------------------------------

    Attachment: DNA-591.patch


Here's a first-cut patch that provides a meaningful error message when this situation occurs.  The error occurs because the 3rd type in the .cnd file (ddl:schemaDefinition) declares a residual child node and extends another type in the file (ddl:statement) that also declares a residual child node.  This is legal in the current type system if the child node definition in the subclass is "narrower" than the child node definition in the superclass.  That is, the subclass's residual child node must be defined such that any node that matches the subclass definition must always match the superclass's definition as well.

This all means that the RNTM must check that (among other things) the required primary types for the subclass are the same as the required primary types for the superclass (or that they are even more restrictive).  To do this, the RTNM must load the required primary types of the superclass and subclass and compare the two.  But the required primary type of the residual child node definition in the superclass (ddl:statement) is ddl:problem, which is the last type declared in the file.  Since ddl:problem hasn't been loaded yet, the attempt to load the required primary types for the residual child node of ddl:statement fails and you get an NPE (or a semi-useful error message if you apply this patch).

Now, the immediate issue can be fixed by moving the definition for ddl:problem to be first in the list.  Then you get this slightly more helpful error message:

org.jboss.dna.jcr.nodetype.InvalidNodeTypeDefinitionException: Cannot redefine child node '{}*' with required type 'ddl:ddlProblem' with new child node that does not required that type or a subtype of that type.

To my way of thinking, this is a correct message.  ddl:schemaDefinition is attempting to redefine the required priamry type of its residual node from ddl:problem (in the supertype ddl:statement) to ddl:otherStatement.  If ddl:otherStatement extended ddl:problem, this would be ok with me.

Having said that, not everyone agrees with me on this and the point is still being debated.  I'm not going to try to commit this patch unless/until a consensus is reached on the issue of overriding child node definitions.

> NullPointerException in JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded() 
> -----------------------------------------------------------------------------
>
>                 Key: DNA-591
>                 URL: https://jira.jboss.org/jira/browse/DNA-591
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Barry LaFond
>         Attachments: DNA-591.patch, DNA_591_Test.java, test_cnd.cnd
>
>
> Using the attached CND file, the repository set-up fails with an NPE when attempting to resolve node types. (ala config.repository(xxxxxx).addNodeTypes('test_cnd.cnd')
> java.lang.NullPointerException
> 	at org.jboss.dna.jcr.JcrNodeDefinition.ensureRequiredPrimaryTypesLoaded(JcrNodeDefinition.java:113)
> 	at org.jboss.dna.jcr.JcrNodeDefinition.getRequiredPrimaryTypes(JcrNodeDefinition.java:161)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1938)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.validate(RepositoryNodeTypeManager.java:1861)
> 	at org.jboss.dna.jcr.RepositoryNodeTypeManager.registerNodeTypes(RepositoryNodeTypeManager.java:1513)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:246)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:161)
>  My original DDL seqencer cnd is much more complex, but by paring it down to the following, the error still occured.
> //------------------------------------------------------------------------------
> // N A M E S P A C E S
> //------------------------------------------------------------------------------
> <jcr='http://www.jcp.org/jcr/1.0'>
> <nt='http://www.jcp.org/jcr/nt/1.0'>
> <mix='http://www.jcp.org/jcr/mix/1.0'>
> <ddl='http://jboss.org/dna/ddl/1.0'>
> [ddl:statement] mixin abstract
>   - ddl:expression (string) mandatory
>   + * (ddl:ddlProblem) = ddl:ddlProblem multiple
> [ddl:schemaDefinition] > ddl:statement  mixin
>   - ddl:defaultCharacterSetName (STRING)
>   + * (ddl:ddlStatement) = ddl:ddlStatement multiple
>   
> [ddl:ddlProblem] mixin
>   - ddl:problemLevel (LONG) mandatory
>   - ddl:message (STRING) mandatory
> The [ddl:schemaDefinition]  mixin is the ONLY mixin that both extends a mixin and allows children of the same mixin type (i.e. [ddl:statement]) however the NPE is occuring when attempting to find the primary node type for [ddl:ddlProblem]
> Note that the NPE does not occur when the [ddl:schemaDefinition] type is removed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 23 20:54:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 23 Dec 2009 20:54:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-519) SVN Connector
 integration test runs in a very long time
In-Reply-To: <1669549818.1252597104126.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <444059671.1261619670692.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-519:
--------------------------------

    Attachment: DNA-519.patch


Here's an initial patch that gets rid of some extra checks in the SVNRepositoryConnection constructor.  Mostly it just optimizes the read-only tests to only copy the repository once per test class instead of once per test.  I may be an anomaly, but this reduces the overall build time for the SVN connector by about 80% and the build time whole project by about 20%.

> SVN Connector integration test runs in a very long time
> -------------------------------------------------------
>
>                 Key: DNA-519
>                 URL: https://jira.jboss.org/jira/browse/DNA-519
>             Project: DNA
>          Issue Type: Patch
>          Components: Connectors
>    Affects Versions: 0.6
>         Environment: Mac OS X 10.6 JDK 1.5 
>            Reporter: Luiz Fernando Teston
>            Priority: Critical
>             Fix For: 1.1
>
>         Attachments: DNA-519.patch
>
>
> During the tests on issue DNA-505 a test called SvnAndJcrIntegrationTest was created inside the project dna-integration-tests. The problem related to the issue DNA-505 was solved successfully but it takes a very long time to run. On my environment it takes more than 270 seconds to run the tests method on SvnAndJcrIntegrationTest. This tests appears to do not load so much nodes. When loading more nodes (for example, changing the Option.READ_DEPTH to a bigger value) the test takes a very long time to run and it could make the use of DNA SVN Connector very difficult in a situation where is needed to load all the repository. I don't know if there's a way to do this load in a faster way, but if it is possible, it should be really useful to my needs.
> Thanks a lot for the help!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 24 17:30:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 24 Dec 2009 17:30:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-62) Sequence Java class
 files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1219955095.1261693830719.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reassigned DNA-62:
----------------------------------

    Assignee: Brian Carothers


> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 19:55:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 19:55:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-602) Can't Set Multi-Valued
 Property from Object[] through StreamSequencerAdapter
Message-ID: <71363633.1261875330783.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Can't Set Multi-Valued Property from Object[] through StreamSequencerAdapter
----------------------------------------------------------------------------

                 Key: DNA-602
                 URL: https://jira.jboss.org/jira/browse/DNA-602
             Project: DNA
          Issue Type: Bug
          Components: Sequencers
    Affects Versions: 0.6
            Reporter: Brian Carothers


I may just be missing something, but when I try to call like this in my sequencer:

Path path =...;
Name propertyName = ...;
SequencerOutput output = ...;
List<String> list = ...;
output.setProperty(path, propertyName, list.toArray());

StreamSequencerAdapter.saveOutput creates a single-valued property with an Object[] as the value instead of the multi-valued property that I would like it to create.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 19:57:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 19:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-602) Can't Set Multi-Valued
 Property from Object[] through StreamSequencerAdapter
In-Reply-To: <71363633.1261875330783.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <39076462.1261875450608.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-602:
--------------------------------

    Attachment: DNA-602.patch


Attached patch that checks for Object[] and forces the correct cast in StreamSequencerAdapter.  I'm not committing this until I hear from Randall that I'm not doing something else wrong that would obviate the need for the patch.

> Can't Set Multi-Valued Property from Object[] through StreamSequencerAdapter
> ----------------------------------------------------------------------------
>
>                 Key: DNA-602
>                 URL: https://jira.jboss.org/jira/browse/DNA-602
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>         Attachments: DNA-602.patch
>
>
> I may just be missing something, but when I try to call like this in my sequencer:
> Path path =...;
> Name propertyName = ...;
> SequencerOutput output = ...;
> List<String> list = ...;
> output.setProperty(path, propertyName, list.toArray());
> StreamSequencerAdapter.saveOutput creates a single-valued property with an Object[] as the value instead of the multi-valued property that I would like it to create.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 20:09:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 20:09:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-62) Sequence Java class
 files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <324886858.1261876170722.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-62:
-------------------------------

    Attachment: DNA-62_draft.patch


Added first (working) version of this sequencer.  The sequencer calls a Reader implementation (a la the MS Office sequencer) that parses a class file into a metadata object.  The metadata object is then passed to a (customizable) recorder object that creates the relevant graph entries.  The patch integrates the sequencer with the getting started sequencers example to help verify that it works.

The current version has extensive testing of the class file reader implementation, but very little testing of the default recorder (the object that converts the metadata into a series of graph nodes and properties).

For the defect to be resolved properly, I think these things would need to happen (in no particular order):

1.  Align the default output for the class sequencer and the Java sequencer so that they are as identical as possible.  This will be very helpful for future analyzer writers.  
2.  Align the metadata objects between the class sequencer and the Java source sequencer.  Both are parsing into objects with the same name.  It seems like they could probably be moved to share a common interface and then reuse recorder implementations (solving issue 1).
3.  Move the sequencer into the same package and namespace as the java sequencer.  This is a nice to have, but the two sequencers are so tightly related that it makes a lot of sense (to me, anyway)
4.  Clean up/add Javadoc, add more testing for the default recorder implementation, and update the reference guide for the new sequencer

As always, any feedback is appreciated.

> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-62_draft.patch
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 20:14:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 20:14:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-603) File System Repository
 Should Be Ported To Use Path Repository
Message-ID: <625613943.1261876470669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

File System Repository Should Be Ported To Use Path Repository
--------------------------------------------------------------

                 Key: DNA-603
                 URL: https://jira.jboss.org/jira/browse/DNA-603
             Project: DNA
          Issue Type: Feature Request
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
            Priority: Minor


Unifying the file system repository and the path repository would reduce the amount of code to be maintained and help establish write support in the path repository framework.  This, in turn, would benefit future path-based repositories (like a CVS repository, a Maven repository, a JDBC storage repository (DNA-199))

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 22:14:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 22:14:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
In-Reply-To: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2102262492.1261883670743.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-578:
--------------------------------

    Attachment: DNA-578.patch


Attached patch that requires support for "allowsUpdates" property in MapRepositorySource implementations and adds a default implementation in MapRequestProcessor.  The patch also adds the property to the Infinispan and JBoss Cache connectors and the simple model in the JPA connector.  Finally, the patch updates the documentation accordingly.

> JPA Connector Simple Model Does Not Support "supportsUpdates" Property
> ----------------------------------------------------------------------
>
>                 Key: DNA-578
>                 URL: https://jira.jboss.org/jira/browse/DNA-578
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Optional
>             Fix For: Future Releases
>
>         Attachments: DNA-578.patch
>
>
> The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.
> This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.
> If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 26 22:20:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 26 Dec 2009 22:20:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-578) JPA Connector Simple
 Model Does Not Support "supportsUpdates" Property
In-Reply-To: <696746748.1260052229596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1229196100.1261884030703.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-578.
---------------------------------

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


Applied patch to resolve defect

> JPA Connector Simple Model Does Not Support "supportsUpdates" Property
> ----------------------------------------------------------------------
>
>                 Key: DNA-578
>                 URL: https://jira.jboss.org/jira/browse/DNA-578
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Optional
>             Fix For: 0.7
>
>         Attachments: DNA-578.patch
>
>
> The JPA Basic Model supported a read-only mode by setting the "supportsUpdates" property to false on the JpaSource.  This feature was unintentionally omitted from the Simple Model.
> This could be added to the MapRequestProcessor and MapRepository classes pretty easily (which would enable it for the Simple Model, the JBoss Cache repository, Infinispan repository, and the InMemoryRepository (where it would be worse than useless).  However, I'm struggling to see where this would be used, especially since the database for the JPA connector is not intended to be shared.
> If anyone needs to set up a master-clone configuration for DNA where the master DNA server has read-write access to the database and the clone has read-only access, we could add this pretty quickly.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 12:14:49 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 27 Dec 2009 12:14:49 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-602) Can't Set
 Multi-Valued Property from Object[] through StreamSequencerAdapter
In-Reply-To: <71363633.1261875330783.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <986872508.1261934089492.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-602:
-----------------------------------

Good catch.  I'm not sure why we've not noticed this before ... must be something we either didn't test or didn't use.  Patch looks good to me.

> Can't Set Multi-Valued Property from Object[] through StreamSequencerAdapter
> ----------------------------------------------------------------------------
>
>                 Key: DNA-602
>                 URL: https://jira.jboss.org/jira/browse/DNA-602
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>         Attachments: DNA-602.patch
>
>
> I may just be missing something, but when I try to call like this in my sequencer:
> Path path =...;
> Name propertyName = ...;
> SequencerOutput output = ...;
> List<String> list = ...;
> output.setProperty(path, propertyName, list.toArray());
> StreamSequencerAdapter.saveOutput creates a single-valued property with an Object[] as the value instead of the multi-valued property that I would like it to create.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 12:21:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 27 Dec 2009 12:21:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-62) Sequence Java class
 files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <865069059.1261934490644.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-62:
----------------------------------

Nice work.  

On first blush, it could sense to put both the classfile and source sequencers in the same project.  However, that would mean that if you just wanted a Java classfile sequencer, you'd have to depend on the Eclipse Java parser (which has more than a few dependencies).  It's not horrible, and I wonder how many people would use one sequencer and not the other.

Another option is to have the Java source sequencer depend on the Java classfile sequencer, since the former has a lot more (transitive) dependencies, and since the latter only has a few.  

A third option is to move the general reader code to a separate module, and to have both sequencer depend on it.  This is my least favorite.

> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-62_draft.patch
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 12:32:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 27 Dec 2009 12:32:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Issue Comment Edited: (DNA-62) Sequence
 Java class files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1946921365.1261935150661.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch edited comment on DNA-62 at 12/27/09 12:31 PM:
-------------------------------------------------------------

It'd be interesting to demonstrate how having multiple sequencers allows us to chain things together.  For example, the ZIP file sequencer should create the nodes representing the contents of a ZIP (and JAR) file, which means we'd create nt:file nodes representing each .class file in the JAR file (or .java source file if a source JAR).  The act of creating those file nodes should activate the Java classfile sequencer for .class files or the Java source sequencer for .java files.

This way, we don't actually have to wire together the ZIP/JAR sequencer to invoke the Java source or classfile sequencer.

      was (Author: rhauch):
    It'd be interesting to demonstrate how having multiple sequencers allows us to chain things together.  For example, the ZIP file sequencer should create the nodes representing the contents of a ZIP (and JAR) file, which means we'd create nt:file nodes representing each .class file in the JAR file (or .java source file if a source JAR).  The act of creating those file nodes should activate the Java classfile sequencer for .class files or the Java source sequencer for .java files.
  
> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-62_draft.patch
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 15:46:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 27 Dec 2009 15:46:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-602) Can't Set
 Multi-Valued Property from Object[] through StreamSequencerAdapter
In-Reply-To: <71363633.1261875330783.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <246750133.1261946790700.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-602.
---------------------------------

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


Committed patch to resolve defect

> Can't Set Multi-Valued Property from Object[] through StreamSequencerAdapter
> ----------------------------------------------------------------------------
>
>                 Key: DNA-602
>                 URL: https://jira.jboss.org/jira/browse/DNA-602
>             Project: DNA
>          Issue Type: Bug
>          Components: Sequencers
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-602.patch
>
>
> I may just be missing something, but when I try to call like this in my sequencer:
> Path path =...;
> Name propertyName = ...;
> SequencerOutput output = ...;
> List<String> list = ...;
> output.setProperty(path, propertyName, list.toArray());
> StreamSequencerAdapter.saveOutput creates a single-valued property with an Object[] as the value instead of the multi-valued property that I would like it to create.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 15:46:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 27 Dec 2009 15:46:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-62) Sequence Java class
 files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1851223033.1261946790677.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-62:
------------------------------------

The patch does make the sequencers getting started example demonstrate sequencer chaining, so I think we've got this going.  

The sequencer configuration for SequencingClientTest is slightly different than for the UI-driven sequencing example.  The test case only looks for JcrRepository.clazz (name mangled to avoid an eclipse feature) and the UI-driven example looks for *.class.  I have to admit that I didn't try sequencing through the UI, but I did make sure that the chaining worked in one-off testing through the test cases.

Thanks for the feedback!  I'd like to get Serge's thoughts on this as well, but I know he's focusing on SVN right now.

> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-62_draft.patch
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

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

        

From jira-events at lists.jboss.org  Sun Dec 27 16:25:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 27 Dec 2009 16:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-603) File System Repository
 Should Be Ported To Use Path Repository
In-Reply-To: <625613943.1261876470669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <508920614.1261949130691.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-603:
--------------------------------

    Component/s: Connectors


> File System Repository Should Be Ported To Use Path Repository
> --------------------------------------------------------------
>
>                 Key: DNA-603
>                 URL: https://jira.jboss.org/jira/browse/DNA-603
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>
> Unifying the file system repository and the path repository would reduce the amount of code to be maintained and help establish write support in the path repository framework.  This, in turn, would benefit future path-based repositories (like a CVS repository, a Maven repository, a JDBC storage repository (DNA-199))

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

        

From jira-events at lists.jboss.org  Sun Dec 27 17:29:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 27 Dec 2009 17:29:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-603) File System
 Repository Should Be Ported To Use Path Repository
In-Reply-To: <625613943.1261876470669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1170220784.1261952970607.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-603:
-----------------------------------

I think this would be a great way to shrink the connector code, have more consistent behaviors, and share much more code.

> File System Repository Should Be Ported To Use Path Repository
> --------------------------------------------------------------
>
>                 Key: DNA-603
>                 URL: https://jira.jboss.org/jira/browse/DNA-603
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>
> Unifying the file system repository and the path repository would reduce the amount of code to be maintained and help establish write support in the path repository framework.  This, in turn, would benefit future path-based repositories (like a CVS repository, a Maven repository, a JDBC storage repository (DNA-199))

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 28 16:06:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 28 Dec 2009 16:06:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-18) Sequencer service
 should use rules to determine which sequencer(s) should run
Message-ID: <1365343966.1262034390774.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-18.
------------------------------

    Fix Version/s: 0.5
                       (was: Future Releases)
       Resolution: Done
         Assignee: Randall Hauch


This was addressed in 0.5 by removing the dependency on Drools (which was overkill for what we're doing).

> Sequencer service should use rules to determine which sequencer(s) should run
> -----------------------------------------------------------------------------
>
>                 Key: DNA-18
>                 URL: https://jira.jboss.org/jira/browse/DNA-18
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.5
>
>
> The sequencer system should use rules to determine which sequencer implementation should be selected to process nodes with changed content.

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

        

From jira-events at lists.jboss.org  Mon Dec 28 17:57:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 28 Dec 2009 17:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-460)
	NodeTypeManager.unregisterType
In-Reply-To: <11755013.1244762396313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1209581299.1262041050947.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reassigned DNA-460:
-----------------------------------

    Assignee: Brian Carothers


> NodeTypeManager.unregisterType
> ------------------------------
>
>                 Key: DNA-460
>                 URL: https://jira.jboss.org/jira/browse/DNA-460
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-460.patch
>
>
> The JSR-170 specification doesn't require (or really even mention) registering and unregistering custom node types.  But since DNA supports registering node types, it seems like its pretty important to support unregistering node types as well.  A swapTypes method to atomically port from one set of types to another may also be useful.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 28 23:05:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 28 Dec 2009 23:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-603) File System Repository
 Should Be Ported To Use Path Repository
In-Reply-To: <625613943.1261876470669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <547066898.1262059530669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-603:
--------------------------------

    Attachment: DNA-603.patch


Attached patch that augments the path repository framework to support writes and moves the file system repository over onto the framework.  All tests pass.

> File System Repository Should Be Ported To Use Path Repository
> --------------------------------------------------------------
>
>                 Key: DNA-603
>                 URL: https://jira.jboss.org/jira/browse/DNA-603
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-603.patch
>
>
> Unifying the file system repository and the path repository would reduce the amount of code to be maintained and help establish write support in the path repository framework.  This, in turn, would benefit future path-based repositories (like a CVS repository, a Maven repository, a JDBC storage repository (DNA-199))

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 28 23:26:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 28 Dec 2009 23:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-603) File System
 Repository Should Be Ported To Use Path Repository
In-Reply-To: <625613943.1261876470669.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1317439632.1262060790883.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-603.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Applied patch to resolve defect

> File System Repository Should Be Ported To Use Path Repository
> --------------------------------------------------------------
>
>                 Key: DNA-603
>                 URL: https://jira.jboss.org/jira/browse/DNA-603
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-603.patch
>
>
> Unifying the file system repository and the path repository would reduce the amount of code to be maintained and help establish write support in the path repository framework.  This, in turn, would benefit future path-based repositories (like a CVS repository, a Maven repository, a JDBC storage repository (DNA-199))

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 11:26:35 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 29 Dec 2009 11:26:35 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-595) Connector chapters in
 the Reference Guide should should examples of configuring in Java code and
 XML configuration
In-Reply-To: <1203983171.1260981752191.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1308957074.1262103995833.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-595:
--------------------------------

    Attachment: DNA-595.patch


Attached patch that adds the XML examples as per the defect.  The patch also updates the JCR section and cleans up a few places where a programlisting was overflowing horizontally.

> Connector chapters in the Reference Guide should should examples of configuring in Java code and XML configuration
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-595
>                 URL: https://jira.jboss.org/jira/browse/DNA-595
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.0
>
>         Attachments: DNA-595.patch
>
>
> The Reference Guide has a chapter describing each connector, and those chapters usually describe the various settings and talk about how to use.  All of these chapters should document how to configure programmatically using JcrConfiguration AND how to configure using the XML format.  Most only show one approach.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 11:28:31 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 29 Dec 2009 11:28:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-595) Connector chapters in
 the Reference Guide should should examples of configuring in Java code and
 XML configuration
In-Reply-To: <1203983171.1260981752191.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <105927930.1262104111242.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-595.
---------------------------------

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


Applied patch to resolve defect

> Connector chapters in the Reference Guide should should examples of configuring in Java code and XML configuration
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-595
>                 URL: https://jira.jboss.org/jira/browse/DNA-595
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Documentation
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-595.patch
>
>
> The Reference Guide has a chapter describing each connector, and those chapters usually describe the various settings and talk about how to use.  All of these chapters should document how to configure programmatically using JcrConfiguration AND how to configure using the XML format.  Most only show one approach.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 15:05:05 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 29 Dec 2009 15:05:05 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-229) dna-sequencer-csv
 (sequence csv files)
In-Reply-To: <5894630.1221819082487.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <398976914.1262117105392.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop closed DNA-229.
------------------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Done


Brian wrotes this feature request JBoss DNA Sequencer that processes fixed width and delimited text files

> dna-sequencer-csv (sequence csv files)
> --------------------------------------
>
>                 Key: DNA-229
>                 URL: https://jira.jboss.org/jira/browse/DNA-229
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>    Affects Versions: Future Releases
>         Environment: sequencer
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>
> create a sequencer to data from csv content and meta data description, we will use the csv4j(http://csv4j.sourceforge.net/) project

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 18:15:31 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 29 Dec 2009 18:15:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-604) Support for create or
 write new Folders/Nodes and File with content / Item into the SVN repos
Message-ID: <773751523.1262128531220.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Support for create or write new  Folders/Nodes and File with content / Item into the SVN repos
----------------------------------------------------------------------------------------------

                 Key: DNA-604
                 URL: https://jira.jboss.org/jira/browse/DNA-604
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 18:22:30 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 29 Dec 2009 18:22:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-605) svn connector to
 support for copying folder with file or file with content to a new folder
 or to a new file
Message-ID: <1875411072.1262128950837.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

svn connector to support for copying folder with file or file with content to a new folder or to a new file
-----------------------------------------------------------------------------------------------------------

                 Key: DNA-605
                 URL: https://jira.jboss.org/jira/browse/DNA-605
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.7, 1.0, 1.1, Future Releases
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7, 1.0, 1.1, Future Releases




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 18:24:36 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Tue, 29 Dec 2009 18:24:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-605) svn connector to
 support for copying folder with file or file with content to a new folder
 or to a new file
In-Reply-To: <1875411072.1262128950837.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1257899589.1262129076946.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop updated DNA-605:
-------------------------------------

        Fix Version/s:     (was: Future Releases)
                           (was: 1.0)
                           (was: 1.1)
    Affects Version/s:     (was: Future Releases)
                           (was: 1.0)
                           (was: 1.1)


> svn connector to support for copying folder with file or file with content to a new folder or to a new file
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-605
>                 URL: https://jira.jboss.org/jira/browse/DNA-605
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 29 20:15:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 29 Dec 2009 20:15:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-464) Add use of file system
 connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <860502112.1262135730758.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-464:
--------------------------------

    Attachment: DNA-464.patch


Attached a patch that adds a file system connector (for UFOs, which are so strange that they can't be placed in a normal in-memory repository!) and updates the tests and documentation accordingly*  The patch also removes the need to manually log in to each repository, something I found seriously annoying and impossible to use without reading either the manual or the source code.  I can replace the old code if anyone disagrees with this change.

* - I do not have "graffle" installed, so I did not update any of the images in the Repositories Example chapter of the Getting Started Guide

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>         Attachments: DNA-464.patch
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 11:33:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 30 Dec 2009 11:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-464) Add use of file
 system connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <548812943.1262190810668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-464:
-----------------------------------

The removal of the authentication challenge is fine.  As Brian points out, this isn't really the appropriate place to be showing off that we do indeed use JAAS, and it's not possible to run the example and get beyond this challenge without reading the manual first.

Patch looks good.  Go ahead and apply the patch, but leave this issue open and I'll update the images.

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>         Attachments: DNA-464.patch
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 15:36:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 30 Dec 2009 15:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-606)
 RepositoryConnectionPool Returns Invalid Connections to the Available Pool
Message-ID: <2124810792.1262205390740.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

RepositoryConnectionPool Returns Invalid Connections to the Available Pool
--------------------------------------------------------------------------

                 Key: DNA-606
                 URL: https://jira.jboss.org/jira/browse/DNA-606
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Graph
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
             Fix For: 0.7


if the RepositoryConnectionPool.validateConnectionBeforeUse property is set to "true", connection validation does occur, but invalid connections are simply returned to the pool where they will be used again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 15:38:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 30 Dec 2009 15:38:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-606)
 RepositoryConnectionPool Returns Invalid Connections to the Available Pool
In-Reply-To: <2124810792.1262205390740.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1201757774.1262205510638.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-606:
--------------------------------

    Attachment: DNA-606.patch


Attached patch that turns on connection validation and modifies the validateConnection(...) method to remove invalid connections from the in-use pool rather than returning them to the available pool.

> RepositoryConnectionPool Returns Invalid Connections to the Available Pool
> --------------------------------------------------------------------------
>
>                 Key: DNA-606
>                 URL: https://jira.jboss.org/jira/browse/DNA-606
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-606.patch
>
>
> if the RepositoryConnectionPool.validateConnectionBeforeUse property is set to "true", connection validation does occur, but invalid connections are simply returned to the pool where they will be used again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 15:40:38 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 30 Dec 2009 15:40:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-606)
 RepositoryConnectionPool Returns Invalid Connections to the Available Pool
In-Reply-To: <2124810792.1262205390740.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1377399959.1262205638534.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-606.
---------------------------------

    Resolution: Done


Committed patch to resolve issue

> RepositoryConnectionPool Returns Invalid Connections to the Available Pool
> --------------------------------------------------------------------------
>
>                 Key: DNA-606
>                 URL: https://jira.jboss.org/jira/browse/DNA-606
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-606.patch
>
>
> if the RepositoryConnectionPool.validateConnectionBeforeUse property is set to "true", connection validation does occur, but invalid connections are simply returned to the pool where they will be used again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 15:42:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 30 Dec 2009 15:42:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-464) Add use of file
 system connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1327615741.1262205750609.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-464:
-----------------------------------

Updated the example-repositories.png and example-federated-repository.png diagrams with the new UFOs source (using the File System connector) and changing the Aircraft source to use the JPA connector.

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>         Attachments: DNA-464.patch
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 17:08:37 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 30 Dec 2009 17:08:37 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-464) Add use of file system
 connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <413696539.1262210917776.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-464:
--------------------------------

    Attachment: DNA-464_jpa.patch


Attached patch that also adds a JPA repository to the example to demonstrate that connector.

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>         Attachments: DNA-464.patch, DNA-464_jpa.patch
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 30 17:10:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 30 Dec 2009 17:10:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-464) Add use of file
 system connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <852111052.1262211030597.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-464.
---------------------------------

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


Added a the JPA example and double-checked the images (they look great, thanks!).  Marked defect as resolved

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-464.patch, DNA-464_jpa.patch
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 07:51:30 2009
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Thu, 31 Dec 2009 07:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-607) Delete node/folder or
 rather item/file from the svn repository through dna svn connector
Message-ID: <1615591246.1262263890770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Delete node/folder or rather item/file from the svn repository through dna svn connector
----------------------------------------------------------------------------------------

                 Key: DNA-607
                 URL: https://jira.jboss.org/jira/browse/DNA-607
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 08:08:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 08:08:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
Message-ID: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
---------------------------------------------------------------------------------

                 Key: DNA-608
                 URL: https://jira.jboss.org/jira/browse/DNA-608
             Project: DNA
          Issue Type: Bug
          Components: Connectors, Graph
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
             Fix For: 0.7


The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 08:56:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 08:56:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1933770721.1262267790734.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-608:
--------------------------------

    Attachment: DNA-608.patch


Attached a patch that changes the ConnectionWrapper close behavior to not attempt to close the underlying connection.  This allowed a graph message to be retired and forced compensating changes in SimpleJpaConnector.

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 09:09:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 09:09:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1162730659.1262268570713.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-608.
---------------------------------

    Resolution: Done


Applied patch to resolve defect

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 09:11:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 09:11:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-609) DnaEngine
 RepositoryConnectionFactory Returns Unpooled Connections
Message-ID: <761060176.1262268690666.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

DnaEngine RepositoryConnectionFactory Returns Unpooled Connections
------------------------------------------------------------------

                 Key: DNA-609
                 URL: https://jira.jboss.org/jira/browse/DNA-609
             Project: DNA
          Issue Type: Bug
          Components: Graph
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
            Priority: Minor


DnaEngine.getRepositoryConnectionFactory() returns an inner class that returns unwrapped connections from the RepositorySource.  However, DnaEngine.getRepositoryService().getRepositoryLibrary() implements RepositoryConnectionFactory as well but returns connections from a RepositoryConnectionPool.  DnaEngine.getGraph uses the RepositoryLibrary as the connection factory for the graph.

In short, there are currently two reasonable ways to get get a RepositoryConnectionFactory from the DnaEngine but they both behave slightly differently.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 09:14:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 09:14:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-609) DnaEngine
 RepositoryConnectionFactory Returns Unpooled Connections
In-Reply-To: <761060176.1262268690666.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1509591909.1262268870610.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-609:
--------------------------------

    Attachment: DNA-609.patch


Attached path that removes DnaEngine's internal connection factory and replaces it with getRepositoryService().getRepositoryLibrary().  This will return connections that have been wrapped/pooled by a RepositoryConnectionPool.

> DnaEngine RepositoryConnectionFactory Returns Unpooled Connections
> ------------------------------------------------------------------
>
>                 Key: DNA-609
>                 URL: https://jira.jboss.org/jira/browse/DNA-609
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>         Attachments: DNA-609.patch
>
>
> DnaEngine.getRepositoryConnectionFactory() returns an inner class that returns unwrapped connections from the RepositorySource.  However, DnaEngine.getRepositoryService().getRepositoryLibrary() implements RepositoryConnectionFactory as well but returns connections from a RepositoryConnectionPool.  DnaEngine.getGraph uses the RepositoryLibrary as the connection factory for the graph.
> In short, there are currently two reasonable ways to get get a RepositoryConnectionFactory from the DnaEngine but they both behave slightly differently.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 09:16:38 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 09:16:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-609) DnaEngine
 RepositoryConnectionFactory Returns Unpooled Connections
In-Reply-To: <761060176.1262268690666.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1117063072.1262268998782.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-609.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Applied patch to resolve defect

> DnaEngine RepositoryConnectionFactory Returns Unpooled Connections
> ------------------------------------------------------------------
>
>                 Key: DNA-609
>                 URL: https://jira.jboss.org/jira/browse/DNA-609
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-609.patch
>
>
> DnaEngine.getRepositoryConnectionFactory() returns an inner class that returns unwrapped connections from the RepositorySource.  However, DnaEngine.getRepositoryService().getRepositoryLibrary() implements RepositoryConnectionFactory as well but returns connections from a RepositoryConnectionPool.  DnaEngine.getGraph uses the RepositoryLibrary as the connection factory for the graph.
> In short, there are currently two reasonable ways to get get a RepositoryConnectionFactory from the DnaEngine but they both behave slightly differently.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 09:29:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 09:29:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1239187986.1262269770663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reopened DNA-608:
-------------------------------



I'm not sure I agree with one of the changes in the patch.  The ConnectionWrapper class formerly kept state that tracked whether it was closed and could no longer be used.  This meant that a component using the connection pool could not close the (wrapped) connection yet continue to use the connection.  With the current changes, it is possible for this to happen and for a connection to not have the correct close semantics.

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 11:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 11:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-467) Add search/query
 support to the graph API
In-Reply-To: <27219418.1245358316391.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1701540922.1262275230703.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 resolved DNA-467.
-------------------------------

    Resolution: Done


I'm going to resolve this issue, since query and search appear to be working fine from the graph layer.  There still are some issues with XPath queries at the JCR level, but those are being addressed as part of DNA-468.

> 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: JCR, Query, Search
>    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  Thu Dec 31 11:05:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 11:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-537) Update Reference
 Guide To Include Instructions On Developing/Building/Testing/Releasing The
 Eclipse Plugin
In-Reply-To: <910841711.1254757129152.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1379838019.1262275530680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-537.
-------------------------------

    Resolution: Won't Fix


Since we're moving the Eclipse plugin into the JBoss Tools repository, it probably doesn't make sense to document how to build it here.  Rather, it probably needs to be documented elsewhere (wiki, or README, or even a new docbook dedicated to the Eclipse plugin).  Therefore, marking as 'wont fix'.

> 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: Documentation, Tools
>    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  Thu Dec 31 12:24:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 12:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1135819860.1262280270716.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-608:
--------------------------------

    Attachment: DNA-608_Take_2.patch


Sorry.  I completely missed the !this.availableConnections.offer(new ConnectionWrapper(wrapper.getOriginal()) part in returnConnection.

Attached a new patch that returns the closed flag and the related checks to the ConnectionWrapper class.  Please let me know if this one is better.

Thanks!

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch, DNA-608_Take_2.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 13:11:30 2009
From: jira-events at lists.jboss.org (John Ament (JIRA))
Date: Thu, 31 Dec 2009 13:11:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-610) Allow JPA Connector to
 be generic (not require hibernate)
Message-ID: <2067165663.1262283090668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Allow JPA Connector to be generic (not require hibernate)
---------------------------------------------------------

                 Key: DNA-610
                 URL: https://jira.jboss.org/jira/browse/DNA-610
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.6
            Reporter: John Ament
            Priority: Minor


Allowing the use of any JPA provider (not just hibernate) would make it easier to use the JPA connector on other app servers - e.g. glassfish, weblogic, etc.  There is no direct dependency on hibernate's features in the jpa connector, other than using their Ejb3Configurator.  It looks like the config settings could be done in such a way that the persistence.xml could be provided by the bundling application.  Design of it should probably be discussed a bit more thoroughly, and hopefully come up with a way that it can be automatically bootstrapped by the container, instead of the way configuration is done now.

I'm willing to provide the implementation of this if you'd like.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 13:52:03 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 13:52:03 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <868164817.1262285523241.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-608:
-----------------------------------

The patch looks great; commit away.  Thanks again for humoring me by putting the closed state back into the ConnectionWrapper.

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch, DNA-608_Take_2.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 13:55:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 13:55:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <651863592.1262285730607.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-468:
-----------------------------------

Simplified the design of the Lucene search indexes, which improves the performance signifantly (the TCK unit tests run approximately 10% or more faster). The performance improvement should be even higher when there's a lot of content and the queries have more criteria.

> Add XPath query language support
> --------------------------------
>
>                 Key: DNA-468
>                 URL: https://jira.jboss.org/jira/browse/DNA-468
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Query, Search
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Create an XPath language binding for our graph model, so that we can parse XPath queries and produce query models that can then be executed.
> This can probably be done as a separate project dependent upon dna-graph, perhaps in the extensions folder (since it'd be a query language extension).  Maybe "extensions/dna-query-xpath"?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 14:04:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 14:04:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-611) Add JCR 1.0 optional
 versioning feature
Message-ID: <739858627.1262286270635.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add JCR 1.0 optional versioning feature
---------------------------------------

                 Key: DNA-611
                 URL: https://jira.jboss.org/jira/browse/DNA-611
             Project: DNA
          Issue Type: Feature Request
          Components: JCR
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.1


Many JCR clients use the optional versioning feature, so it would be great to add support for this.  See the <a href="http://www.day.com/specs/jcr/1.0/8.2_Versioning.html">Section 8.2 of the JCR 1.0 spec</a>, or <a href="http://www.day.com/specs/jcr/2.0/15_Versioning.html">Section 15 of the JCR 2.0 spec</a>. There is also some <a href="http://wiki.apache.org/jackrabbit/ExamplesPage#Versioning_Basics">example code</a> showing the basics of how to use versioning.

This task should also include adding a small section to the Reference Guide to describe how versioning can be used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 14:06:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 14:06:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-611) Add JCR 1.0 optional
 versioning feature
In-Reply-To: <739858627.1262286270635.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1187048874.1262286390679.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-611:
------------------------------

    Description: 
Many JCR clients use the optional versioning feature, so it would be great to add support for this.  See the Section 8.2 of the JCR 1.0 spec [1], or Section 15 of the JCR 2.0 spec [2]. There is also some example code showing the basics of how to use versioning [3].

This task should also include adding a small section to the Reference Guide to describe how versioning can be used.

[1] http://www.day.com/specs/jcr/1.0/8.2_Versioning.html
[2] http://www.day.com/specs/jcr/2.0/15_Versioning.html
[3] http://wiki.apache.org/jackrabbit/ExamplesPage#Versioning_Basics

  was:
Many JCR clients use the optional versioning feature, so it would be great to add support for this.  See the <a href="http://www.day.com/specs/jcr/1.0/8.2_Versioning.html">Section 8.2 of the JCR 1.0 spec</a>, or <a href="http://www.day.com/specs/jcr/2.0/15_Versioning.html">Section 15 of the JCR 2.0 spec</a>. There is also some <a href="http://wiki.apache.org/jackrabbit/ExamplesPage#Versioning_Basics">example code</a> showing the basics of how to use versioning.

This task should also include adding a small section to the Reference Guide to describe how versioning can be used.



> Add JCR 1.0 optional versioning feature
> ---------------------------------------
>
>                 Key: DNA-611
>                 URL: https://jira.jboss.org/jira/browse/DNA-611
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 1.1
>
>
> Many JCR clients use the optional versioning feature, so it would be great to add support for this.  See the Section 8.2 of the JCR 1.0 spec [1], or Section 15 of the JCR 2.0 spec [2]. There is also some example code showing the basics of how to use versioning [3].
> This task should also include adding a small section to the Reference Guide to describe how versioning can be used.
> [1] http://www.day.com/specs/jcr/1.0/8.2_Versioning.html
> [2] http://www.day.com/specs/jcr/2.0/15_Versioning.html
> [3] http://wiki.apache.org/jackrabbit/ExamplesPage#Versioning_Basics

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 16:33:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 16:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-612) XPath position() and
 last() functions are not supported
Message-ID: <1766345663.1262295210646.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

XPath position() and last() functions are not supported
-------------------------------------------------------

                 Key: DNA-612
                 URL: https://jira.jboss.org/jira/browse/DNA-612
             Project: DNA
          Issue Type: Bug
          Components: JCR, Query
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


An XPath expression that uses the 'position()' or 'last()' functions will not work.  This doesn't appear to be required by the JCR 1.0 specification [1], but is required by several TCK unit tests.

[1] Section 6.6.6.3 mentions "Required function support ([42] and [60] above) is limited to the functions described in 6.6.5 XPath Extensions", but 6.6.5 does not mention position() or last()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 16:33:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 16:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-613) XPath order-by clause
 is not working
Message-ID: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

XPath order-by clause is not working
------------------------------------

                 Key: DNA-613
                 URL: https://jira.jboss.org/jira/browse/DNA-613
             Project: DNA
          Issue Type: Bug
          Components: JCR, Query
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


The JCR extension to XPath that adds support for 'order by' is not working.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 16:35:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 16:35:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <376187282.1262295330604.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-468.
-------------------------------

    Resolution: Done


This commit includes several fixes for the XPath query functionality, some fixes for several tests, and some new unit tests.  At this point there are still some outstanding issues with certain XPath tests, but these are being tracked under DNA-612 and DNA-613.

> Add XPath query language support
> --------------------------------
>
>                 Key: DNA-468
>                 URL: https://jira.jboss.org/jira/browse/DNA-468
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR, Query, Search
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Create an XPath language binding for our graph model, so that we can parse XPath queries and produce query models that can then be executed.
> This can probably be done as a separate project dependent upon dna-graph, perhaps in the extensions folder (since it'd be a query language extension).  Maybe "extensions/dna-query-xpath"?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 16:39:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 16:39:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-285) Pass all Level 1 TCK
	unit tests
In-Reply-To: <18642947.1235148944956.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1334996207.1262295570749.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-285.
-------------------------------

    Resolution: Done


Marking this as complete, since the only outstanding issues are being tracked by specific defects (DNA-612 and DNA-613).

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

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

        

From jira-events at lists.jboss.org  Thu Dec 31 16:45:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 16:45:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-599) Upgrade to SVNKit 1.3.0
In-Reply-To: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1548329090.1262295931299.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-599:
------------------------------

    Summary: Upgrade to SVNKit 1.3.0  (was: Upgrade to SVNKit 1.3.2-1)


Changed the title to reflect that we'll upgrade to 1.3.0, but versions after this have a dependency on GPL code, which we cannot use.

> Upgrade to SVNKit 1.3.0
> -----------------------
>
>                 Key: DNA-599
>                 URL: https://jira.jboss.org/jira/browse/DNA-599
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 17:33:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 17:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-612) XPath position() and
 last() functions are not supported
In-Reply-To: <1766345663.1262295210646.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1652284518.1262298810765.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-612:
-----------------------------------

See http://issues.apache.org/jira/browse/JCR-591 for a similar issue with the JCR reference implementation.  The issue nicely points out that the position() function applies to the SNS index value, not to the index of the child amongst all children (as it would in XML).

> XPath position() and last() functions are not supported
> -------------------------------------------------------
>
>                 Key: DNA-612
>                 URL: https://jira.jboss.org/jira/browse/DNA-612
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> An XPath expression that uses the 'position()' or 'last()' functions will not work.  This doesn't appear to be required by the JCR 1.0 specification [1], but is required by several TCK unit tests.
> [1] Section 6.6.6.3 mentions "Required function support ([42] and [60] above) is limited to the functions described in 6.6.5 XPath Extensions", but 6.6.5 does not mention position() or last()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 17:44:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 17:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-608)
 RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying
 Connection
In-Reply-To: <7884042.1262264910649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <821775503.1262299470662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-608.
---------------------------------

    Resolution: Done


No, you were right; that was my bad.  I missed the line that offered back a new ConnectionWrapper instead of the old one in returnConnection.  Knowing that, taking out the close flag was the wrong thing to do.  Thanks for catching that!

Committed patch to resolve defect.

> RepositoryConnectionPool.ConnectionWrapper.close Closes the Underlying Connection
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-608
>                 URL: https://jira.jboss.org/jira/browse/DNA-608
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-608.patch, DNA-608_Take_2.patch
>
>
> The RepositoryConnectionPool.ConnectionWrapper.close method is calling close on the underlying connection and then returning it to the available pool.  However, after being closed, the underlying connection is no longer valid and cannot be used.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 18:16:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 31 Dec 2009 18:16:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-599) Upgrade to SVNKit
	1.3.0
In-Reply-To: <1559912740.1261144170632.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <223017330.1262301390783.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-599.
-------------------------------

    Resolution: Done


Uploaded the svnkit and com.trilead libraries to the JBoss repository.  (I had to manually fix the sha1 and md5 files; not sure why, but the ones uploaded by 'mvn deploy:deploy-file didn't match those in other Maven repositories nor the values computed locally with openssl.)

> Upgrade to SVNKit 1.3.0
> -----------------------
>
>                 Key: DNA-599
>                 URL: https://jira.jboss.org/jira/browse/DNA-599
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Upgrade to the latest version of SVNKit.  Version 1.3.2-1 was released just a few weeks ago, and includes a number of bug fixes that we want to incorporate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 20:57:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 20:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-549) Creating A New
 Property And Changing An Existing Property Should Have Different
 ChangeRequest Types
In-Reply-To: <1946803342.1257437465795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1891103095.1262311050694.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-549:
--------------------------------

    Attachment: DNA-549.patch


Attached patch that adds a boolean method (isNewProperty())  that indicates whether a property was created as a result of processing this request.  It's a parallel to the same method in SetPropertyRequest.

> Creating A New Property And Changing An Existing Property Should Have Different ChangeRequest Types
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DNA-549
>                 URL: https://jira.jboss.org/jira/browse/DNA-549
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-549.patch
>
>
> There is no way to differentiate between when a new property is created and when an existing property is set. Both are handled using the SetPropertyRequest. The JCR spec clearly states the difference between these two cases as each one has their own event type.
> Work to change to the relevant change requests, update connectors, and update the NetChangeObserver will need to be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Dec 31 22:31:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 31 Dec 2009 22:31:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-62) Sequence Java class
 files to extract the class structure with annotations
In-Reply-To: <31837504.1209483069549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2132447632.1262316690883.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-62:
-------------------------------

    Attachment: DNA-62_ref_guide.patch


Attached a reference guide page for this sequencer.  The page specifically lists the sequencer as a technology preview and nodes that the default output and associated CNDs are subject to change in future versions to better align with the Java sequencer.  

If no one objects, I'll check in all of the -62 changes to get them into SVN while Serge and I work out the details of the alignment.  Any feedback is appreciated.

> Sequence Java class files to extract the class structure with annotations
> -------------------------------------------------------------------------
>
>                 Key: DNA-62
>                 URL: https://jira.jboss.org/jira/browse/DNA-62
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Sequencers
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 1.1
>
>         Attachments: DNA-62_draft.patch, DNA-62_ref_guide.patch
>
>
> This use case comes from a discussion about starting up the Microcontainer, and the desire to have a single processor of the JAR files to extract into a centralized repository the runtime annotations.  Right now the annotations are scanned by each component/service that needs them.  This feature would obviate the scanning being done by each component/service.
> Consider using http://scannotation.sourceforge.net/ for doing the actual scanning.

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

        

