From jira-events at lists.jboss.org  Fri Jan  1 12:19:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 1 Jan 2010 12:19: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: <2040937886.1262366370731.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_path_repo_initial.patch


Attached patch that reworks the path repository interfaces slightly to enhance their flexibility and make path repository easier to integrate with the SVN connector.

> 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, DNA-519_path_repo_initial.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  Fri Jan  1 12:24:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 1 Jan 2010 12:24:38 -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: <714662704.1262366678600.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_svn_port_WIP.patch


WIP for the SVN connector port to the path repository framework.  This version passes the connector readable test, but doesn't support writes.  It also has some minor rough spots (SVNRepository isn't pooled, missing exception messages) that can get cleaned up later.

> 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, DNA-519_path_repo_initial.patch, DNA-519_svn_port_WIP.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  Fri Jan  1 12:35:35 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 1 Jan 2010 12:35:35 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-614) REST client osgi
 bundle for the Eclipse plugin
Message-ID: <206867925.1262367335949.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

REST client osgi bundle for the Eclipse plugin
----------------------------------------------

                 Key: DNA-614
                 URL: https://jira.jboss.org/jira/browse/DNA-614
             Project: DNA
          Issue Type: Task
          Components: Tools
    Affects Versions: 0.7
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7


create REST client osgi bundle for the Eclipse plugin to avoid to build them manually every 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 Jan  1 12:35:35 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 1 Jan 2010 12:35:35 -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: <542646596.1262367335998.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=12501865#action_12501865 ] 

Brian Carothers commented on DNA-62:
------------------------------------

Committed previous two patches as a tech preview.  I am going to leave the defect open though, as the node type definitions still need to be finalized and unified with the Java source file sequencer.

> 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

        

From jira-events at lists.jboss.org  Fri Jan  1 20:37:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 1 Jan 2010 20:37: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: <349126150.1262396250755.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_svn_port_WIP_2.patch


Updated WIP patch for review.  All write operations are now supported, but it still lacks pooling, caching, and transactions.  The last 40% of the patch is test cases - the source isn't all that big.

> 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, DNA-519_path_repo_initial.patch, DNA-519_svn_port_WIP.patch, DNA-519_svn_port_WIP_2.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  Sat Jan  2 08:19:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 2 Jan 2010 08:19:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-615) PathRepository Should
 Provide Support for Caching
Message-ID: <292815203.1262438370770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

PathRepository Should Provide Support for Caching
-------------------------------------------------

                 Key: DNA-615
                 URL: https://jira.jboss.org/jira/browse/DNA-615
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors, Graph
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
             Fix For: 0.7


The path repository framework should be able to provide OOTB caching support (tied into the source's default cache policy).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  2 11:06:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 2 Jan 2010 11:06:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
Message-ID: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JPA connector pooling doesn't appear to shutdown
------------------------------------------------

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


Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).

02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11,  , sameNameSiblingIndex=1, indexInParent=1, nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
02:16:42,310 DEBUG more......
02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
02:16:42,310 DEBUG 
    delete 
    from
        DNA_SUBGRAPH_NODES 
    where
        QUERY_ID=?
02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)

and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  3 22:04:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 3 Jan 2010 22:04:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-615) PathRepository Should
 Provide Support for Caching
In-Reply-To: <292815203.1262438370770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1247916483.1262574270711.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-615:
--------------------------------

    Attachment: DNA-615.patch


Attached a patch that provides a default caching implementation for path-based repositories.  The patch has the following salient features:

1.  It adds a new base class (AbstractPathRepositorySource) for path repository sources that encapuslates some of the common required properties that have been cut-and-pasted a few times and manages the path repository cache for the source.
2.  It adds PathRepositoryCache (a map of workspace names to WorkspaceCaches) and WorkspaceCache (a per-workspace Path to PathNode map).
3.  It adds a beefed-up version of CachePolicy (called PathCachePolicy) that is used by the PathRepositoryCache to determine which implementation of WorkspaceCache to use.  It is also used by the WorkspaceCache implementation to determine if a particular node should be cached, allowing for custom exclusion policies based on node size, node volatility, etc.
4.  It integrates these changes with the FileSystemSource and JDBC Metadata source to demonstrate their efficacy.

It's fairly vanilla stuff, but it's built to be rather customizable.  Also, changing the cache policy on the source at run-time is supported, so you're not limited to configuring the cache for a repo at startup.

Any feedback/thoughts would be appreciated, as ever.  Thanks!

> PathRepository Should Provide Support for Caching
> -------------------------------------------------
>
>                 Key: DNA-615
>                 URL: https://jira.jboss.org/jira/browse/DNA-615
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-615.patch
>
>
> The path repository framework should be able to provide OOTB caching support (tied into the source's default cache policy).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  3 22:08:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 3 Jan 2010 22:08:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-610) Allow JPA Connector
 to be generic (not require hibernate)
In-Reply-To: <2067165663.1262283090668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1561233419.1262574510599.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-610:
-------------------------------------

I think you bring up a good point here.  I'd love to not have a compile-time dependency on Hibernate for all of the reasons that you just mentioned.  If you could provide an implementation, that would be better still.

Thanks!


> 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  Sun Jan  3 22:57:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 3 Jan 2010 22:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-572)
 FederatedRepositoryConnection Can Freeze When Exception Thrown from
 RepositoryConnection.execute(...)
In-Reply-To: <1681354438.1259958149600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1071837922.1262577450613.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-572:
--------------------------------

    Attachment: DNA-572.patch


The attached patch corrects one possible source of freezes in the federated connector by ensuring that a FederatedRequest is still submitted if the projection fails.

> 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
>
>         Attachments: DNA-572.patch
>
>
> 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  Mon Jan  4 09:58:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 09:58:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-615) PathRepository
 Should Provide Support for Caching
In-Reply-To: <292815203.1262438370770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <865189032.1262617111023.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-615:
-----------------------------------

Very nicely done!  I vote to commit.

> PathRepository Should Provide Support for Caching
> -------------------------------------------------
>
>                 Key: DNA-615
>                 URL: https://jira.jboss.org/jira/browse/DNA-615
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-615.patch
>
>
> The path repository framework should be able to provide OOTB caching support (tied into the source's default cache policy).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  4 10:04:38 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 10:04:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (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: <984631792.1262617478788.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-549:
-----------------------------------

Looks good.  Exactly what I was thinking of. I vote to commit.

> 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  Mon Jan  4 10:04:39 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 10:04:39 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-572)
 FederatedRepositoryConnection Can Freeze When Exception Thrown from
 RepositoryConnection.execute(...)
In-Reply-To: <1681354438.1259958149600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1471318381.1262617479342.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-572:
-----------------------------------

Looks great.  I vote to commit.

> 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
>
>         Attachments: DNA-572.patch
>
>
> 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  Mon Jan  4 10:27:32 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 4 Jan 2010 10:27:32 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (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: <1562396865.1262618852101.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 resolved DNA-549.
---------------------------------

    Resolution: Done


Committed patch to resolve defect

> 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  Mon Jan  4 10:33:32 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Mon, 4 Jan 2010 10:33:32 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-615) PathRepository Should
 Provide Support for Caching
In-Reply-To: <292815203.1262438370770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <726793503.1262619212254.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-615.
---------------------------------

    Resolution: Done


Applied patch to resolve defect

> PathRepository Should Provide Support for Caching
> -------------------------------------------------
>
>                 Key: DNA-615
>                 URL: https://jira.jboss.org/jira/browse/DNA-615
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-615.patch
>
>
> The path repository framework should be able to provide OOTB caching support (tied into the source's default cache policy).  

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


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

Brian Carothers resolved DNA-572.
---------------------------------

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


Marking this issue as resolved.  If it reappears, we can either re-open this issue or create a new issue as appropriate.

> 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
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-572.patch
>
>
> 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  Mon Jan  4 10:49:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 10:49:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-617) NPE while updating
 indexes (during integration tests)
Message-ID: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

NPE while updating indexes (during integration tests)
-----------------------------------------------------

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


This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:

java.lang.IllegalStateException: Failed to initialize the repository with text content.
	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
	at junit.framework.TestCase.runBare(TestCase.java:132)
	at junit.framework.TestResult$1.protect(TestResult.java:110)
	at junit.framework.TestResult.runProtected(TestResult.java:128)
	at junit.framework.TestResult.run(TestResult.java:113)
	at junit.framework.TestCase.run(TestCase.java:124)
	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
	at junit.framework.TestSuite.runTest(TestSuite.java:232)
	at junit.framework.TestSuite.run(TestSuite.java:227)
	at junit.framework.TestSuite.runTest(TestSuite.java:232)
	at junit.framework.TestSuite.run(TestSuite.java:227)
	at junit.framework.TestSuite.runTest(TestSuite.java:232)
	at junit.framework.TestSuite.run(TestSuite.java:227)
	at junit.framework.TestSuite.runTest(TestSuite.java:232)
	at junit.framework.TestSuite.run(TestSuite.java:227)
	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
	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:585)
	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Caused by: java.lang.NullPointerException
	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
	at junit.framework.TestCase.runBare(TestCase.java:132)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  4 10:49:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 10:49:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <974780686.1262620171782.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-617:
------------------------------

    Component/s: JCR
                 Query
                 Search


> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  4 10:53:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 4 Jan 2010 10:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-618) SVN connector
 integration tests are failing with '404 Not Found'
Message-ID: <848461723.1262620410717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

SVN connector integration tests are failing with '404 Not Found'
----------------------------------------------------------------

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


This failure happened during one of the nightly integration tests.  Note the '!' character in the path - is that right??

org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
	at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380)
	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265)
	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
	at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	...
Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
	at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275)
	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351)
	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285)
	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
	at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174)
	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  4 13:52:30 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 4 Jan 2010 13:52:30 -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: <188762311.1262631150634.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:
-----------------------------

      Assignee: Dan Florian  (was: Randall Hauch)


The RequestProcessor needs to set the actual Property on the UpdatePropertiesRequest as the property is needed during observation event handling. Currently the request only contains the property name.

> 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: Dan Florian
>            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  Mon Jan  4 15:15:30 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 4 Jan 2010 15:15:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (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: <296594837.1262636130763.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 resolved DNA-549.
-----------------------------

    Resolution: Done


The RequestProcessor now sets the actual Property on the UpdatePropertiesRequest. This property is used by the NetChangeObserver during observation event handling.

> 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: Dan Florian
>            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  Mon Jan  4 15:25:32 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 4 Jan 2010 15:25:32 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-619) Remove Eclipse IDE
 Comments That Denote A String Need Not Be Externalized
Message-ID: <2124466869.1262636732263.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Remove Eclipse IDE Comments That Denote A String Need Not Be Externalized
-------------------------------------------------------------------------

                 Key: DNA-619
                 URL: https://jira.jboss.org/jira/browse/DNA-619
             Project: DNA
          Issue Type: Task
          Components: Common, Sequencers, Web Application
    Affects Versions: 0.7
            Reporter: Dan Florian
            Assignee: Dan Florian
             Fix For: 0.7


Eclipse's //$NON-NLS-x$ comments are meaningless to a developer who is not using Eclipse. And DNA developers are not required to use the Eclipse IDE. All these comments should be removed. Looks like there is 129 occurrences in our code base.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  4 16:05:30 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Mon, 4 Jan 2010 16:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-619) Remove Eclipse IDE
 Comments That Denote A String Need Not Be Externalized
In-Reply-To: <2124466869.1262636732263.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1127151598.1262639130676.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-619.
-----------------------------

    Resolution: Done


All //NON-NLS-x$ comments have been removed from the codebase.

> Remove Eclipse IDE Comments That Denote A String Need Not Be Externalized
> -------------------------------------------------------------------------
>
>                 Key: DNA-619
>                 URL: https://jira.jboss.org/jira/browse/DNA-619
>             Project: DNA
>          Issue Type: Task
>          Components: Common, Sequencers, Web Application
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Eclipse's //$NON-NLS-x$ comments are meaningless to a developer who is not using Eclipse. And DNA developers are not required to use the Eclipse IDE. All these comments should be removed. Looks like there is 129 occurrences in our code base.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 06:13:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 06:13:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-460)
	NodeTypeManager.unregisterType
In-Reply-To: <11755013.1244762396313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2089758800.1262690010702.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 updated DNA-460:
--------------------------------

    Attachment: DNA-460_query.patch


Attached patch that completes the unregistration functionality by using the query engine to make sure that a type is not in use before it is unregistered.

Using the query manager outside of the context of a particular session required some the extraction of an abstract class that provides a small subset of the total functionality of the JcrWorkspace class.  An abstract class was used instead of an interface to preserve the package visibility of most of the methods in the class.

> 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, DNA-460_query.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  Tue Jan  5 07:42:36 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 07:42:36 -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: <69909736.1262695356291.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_svn_port_final.patch


Attached updated patch that has passed Serge's review.  This will be committed in two parts to work around case sensitivity issues on Windows.  In the first part, this patch will be applied and all files will move into an svn2 package with the class name case corrected from SVN* to Svn*.  A subsequent patch will move the classes back into the svn package.

> 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, DNA-519_path_repo_initial.patch, DNA-519_svn_port_final.patch, DNA-519_svn_port_WIP.patch, DNA-519_svn_port_WIP_2.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  Tue Jan  5 07:49:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 07:49: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: <957626193.1262695770657.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_repackage_svn.patch


Attached patch (DNA-519_repackage_svn.patch) that moves everything back into the svn package.  At this point, the SVN connector has now been fully converted to the path repository framework and can start to leverage the caching support provided therein.  The next step is to write a CachePolicy and WorkspaceCache implementation for the SVN connector to improve read performance.  After that, connection pooling can be considered.  

There is also a need to implement all-or-nothing transaction support.  That will be covered in a separate defect.

> 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, DNA-519_path_repo_initial.patch, DNA-519_repackage_svn.patch, DNA-519_svn_port_final.patch, DNA-519_svn_port_WIP.patch, DNA-519_svn_port_WIP_2.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  Tue Jan  5 08:10:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 08:10:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-620) The SVN
 connector.execute(...) method is not 'all-or-nothing'
Message-ID: <443442789.1262697030727.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

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

                 Key: DNA-620
                 URL: https://jira.jboss.org/jira/browse/DNA-620
             Project: DNA
          Issue Type: Sub-task
          Components: Connectors
    Affects Versions: 0.7
            Reporter: Brian Carothers
            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  Tue Jan  5 08:12:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 08:12:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-620) The SVN
 connector.execute(...) method is not 'all-or-nothing'
In-Reply-To: <443442789.1262697030727.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <200914588.1262697151108.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-620:
--------------------------------

    Description: The connector is already using Action classes to manage updates, these just need to be aggregated and run through the same ISVNEditor when the transaction commits.  (was: We should be able to rely upon the transactional semantics of Infinispan.)


> The SVN connector.execute(...) method is not 'all-or-nothing'
> -------------------------------------------------------------
>
>                 Key: DNA-620
>                 URL: https://jira.jboss.org/jira/browse/DNA-620
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Brian Carothers
>            Priority: Blocker
>             Fix For: 1.0
>
>
> The connector is already using Action classes to manage updates, these just need to be aggregated and run through the same ISVNEditor when the transaction commits.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 08:37:39 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 08:37:39 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-618) SVN connector
 integration tests are failing with '404 Not Found'
In-Reply-To: <848461723.1262620410717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <325251785.1262698659997.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-618:
-------------------------------------

I temporarily worked around this by disabling query execution (through the JcrRepository options) for this test case to make sure that the SVN connector would still pass the integration tests,  The issue hasn't been fixed yet.

> SVN connector integration tests are failing with '404 Not Found'
> ----------------------------------------------------------------
>
>                 Key: DNA-618
>                 URL: https://jira.jboss.org/jira/browse/DNA-618
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> This failure happened during one of the nightly integration tests.  Note the '!' character in the path - is that right??
> org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	...
> Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
> 	at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174)
> 	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 11:07:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 5 Jan 2010 11:07:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-621) Document search/query
 languages in the Reference Guide
Message-ID: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Document search/query languages in the Reference Guide
------------------------------------------------------

                 Key: DNA-621
                 URL: https://jira.jboss.org/jira/browse/DNA-621
             Project: DNA
          Issue Type: Task
          Components: Documentation, Query, Search
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 0.7


We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 12:54:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 5 Jan 2010 12:54:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-622) Remove from SVN the
 'dna-search' project, which contains only empty directories
Message-ID: <822317816.1262714070870.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Remove from SVN the 'dna-search' project, which contains only empty directories
-------------------------------------------------------------------------------

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


Simple task: remove the 'dna-search' project, which contains only empty directories and is no longer needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 12:58:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 5 Jan 2010 12:58:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (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: <946847379.1262714311156.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-373:
-----------------------------------

One way to do this is (supposedly) as simple as:

<plugins>
  <plugin>
    <artifactId>maven-jar-plugin</artifactId>
    <configuration>
      <archive>
         <manifestFile>
${project.build.outputDirectory}/META-INF/MANIFEST.MF
         </manifestFile>
      </archive>
    </configuration>
   </plugin>
   <plugin>
     <groupId>org.apache.felix</groupId>
      <artifactId>maven-bundle-plugin</artifactId>
      <version>2.0.1</version>
      <executions>
        <execution>
          <id>bundle-manifest</id>
          <phase>process-classes</phase>
          <goals>
            <goal>manifest</goal>
          </goals>
        </execution>
      </executions>
      </plugin>
    </plugins>


> 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 Jan  5 14:17:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 14:17:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-622) Remove from SVN the
 'dna-search' project, which contains only empty directories
In-Reply-To: <822317816.1262714070870.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <149159144.1262719050607.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-622.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


Removed the directories from SVN to resolve this issue

> Remove from SVN the 'dna-search' project, which contains only empty directories
> -------------------------------------------------------------------------------
>
>                 Key: DNA-622
>                 URL: https://jira.jboss.org/jira/browse/DNA-622
>             Project: DNA
>          Issue Type: Task
>          Components: Development Environment
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Simple task: remove the 'dna-search' project, which contains only empty directories and is no longer needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 14:25:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 14:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-604) Support for create or
 write new Folders/Nodes and File with content / Item into the SVN repos
In-Reply-To: <773751523.1262128531220.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <964284604.1262719530666.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-604.
---------------------------------

    Resolution: Done


Previous commits from Serge added this functionality.  o.j.d.connector.svn.SvnRepositoryConnectorWritableTest has methods to demonstrate that this works.

> 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 Jan  5 14:27:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 14:27:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (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: <23145785.1262719650847.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 ]

Brian Carothers resolved DNA-605.
---------------------------------

    Resolution: Done


Previous commits from Serge added this functionality.  o.j.d.connector.svn.SvnRepositoryConnectorWritableTest has methods to demonstrate that this works.

> 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 Jan  5 14:27:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 14:27:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-607) Delete node/folder or
 rather item/file from the svn repository through dna svn connector
In-Reply-To: <1615591246.1262263890770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1015603571.1262719651486.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-607.
---------------------------------

    Resolution: Done


Previous commits from Serge added this functionality.  o.j.d.connector.svn.SvnRepositoryConnectorWritableTest has methods to demonstrate that this works.

> 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  Tue Jan  5 16:02:31 2010
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 5 Jan 2010 16:02:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (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: <138307256.1262725351609.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 resolved DNA-597.
------------------------------

    Resolution: Done


Changed all CND & related example xml files to use "www" prefixed URL's.

> 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  Tue Jan  5 16:04:30 2010
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 5 Jan 2010 16:04:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-49) Sequence DDL files
Message-ID: <1706147292.1262725470836.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond resolved DNA-49.
-----------------------------

    Resolution: Done


Added DdlSequencerTest as well as integration tests for Standard, Oracle, Postgres and Derby ddl's.

> 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 Jan  5 16:52:38 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 5 Jan 2010 16:52:38 -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: <452220058.1262728358203.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:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Pushing to 1.0, since the Eclipse plugin is being moved and rebranded prior to its release, and will only be available after 1.0.

> 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: 1.0
>
>
> 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 Jan  5 17:06:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 17:06:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-499) Wrap system access,
 context class loader access, and reflection with doPrivileged
In-Reply-To: <1931841278.1249401689050.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <762905769.1262729191421.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-499:
-------------------------------------

It appears that JBoss may have a pattern (formal or informal) for isolating privileged actions on a per package level:

http://www.google.com/search?hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=gHx&q=jboss+javadoc+securityactions&aq=f&oq=&aqi=

We probably need to research whether this is a true pattern (as opposed to the way that one developer solved the same problem in different places) and, if so, comply with it.

> Wrap system access, context class loader access, and reflection with doPrivileged
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-499
>                 URL: https://jira.jboss.org/jira/browse/DNA-499
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Common, Connectors, Examples, Federation, Graph, JCR, Maven Classloader, Sequencers
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Vijay Kiran Duvvuri
>             Fix For: 0.7
>
>         Attachments: DNA-499.1.patch
>
>
> Several activities should make use of the Java SecurityManager to ensure the caller has the appropriate privileges to perform the activity.  These activities should be wrapped in a block such as the following:
> String lineSeparator = java.security.AccessController.doPrivileged(
>     new java.security.PrivilegedAction<String>() {
>         public String run() {
>             return System.getProperty("line.separator");
>         }
>     }
>  );
> obviously with the correct generic type for whatever is being returned from the run.  (Nice and concise, huh? Ugh.)
> We need to go through all of the (non-test) code and add this checking (if it is not already there) when the following types of activities are performed:
> - System.getProperty
> - System.setProperty
> - Thread.currentThread().getContextClassLoader()
> - All code executed via reflection

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 17:08:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 5 Jan 2010 17:08:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-499) Wrap system access,
 context class loader access, and reflection with doPrivileged
In-Reply-To: <1931841278.1249401689050.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <762260983.1262729310644.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-499:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Pushing to 1.0, since this just hasn't been our priority for 0.7.

> Wrap system access, context class loader access, and reflection with doPrivileged
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-499
>                 URL: https://jira.jboss.org/jira/browse/DNA-499
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Common, Connectors, Examples, Federation, Graph, JCR, Maven Classloader, Sequencers
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Vijay Kiran Duvvuri
>             Fix For: 1.0
>
>         Attachments: DNA-499.1.patch
>
>
> Several activities should make use of the Java SecurityManager to ensure the caller has the appropriate privileges to perform the activity.  These activities should be wrapped in a block such as the following:
> String lineSeparator = java.security.AccessController.doPrivileged(
>     new java.security.PrivilegedAction<String>() {
>         public String run() {
>             return System.getProperty("line.separator");
>         }
>     }
>  );
> obviously with the correct generic type for whatever is being returned from the run.  (Nice and concise, huh? Ugh.)
> We need to go through all of the (non-test) code and add this checking (if it is not already there) when the following types of activities are performed:
> - System.getProperty
> - System.setProperty
> - Thread.currentThread().getContextClassLoader()
> - All code executed via reflection

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 17:24:30 2010
From: jira-events at lists.jboss.org (Vijay Kiran Duvvuri (JIRA))
Date: Tue, 5 Jan 2010 17:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-499) Wrap system access,
 context class loader access, and reflection with doPrivileged
In-Reply-To: <1931841278.1249401689050.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1820134578.1262730270663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Vijay Kiran Duvvuri commented on DNA-499:
-----------------------------------------

There was a discussion on this issue if we can create a Utility class with static methods, which can be used to reduce code clutter. But it seems to introduce a security hole according to http://java.sun.com/j2se/1.5.0/docs/guide/security/doprivileged.html 

So all the code need to be wrapped with AccessControl individually.

> Wrap system access, context class loader access, and reflection with doPrivileged
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-499
>                 URL: https://jira.jboss.org/jira/browse/DNA-499
>             Project: DNA
>          Issue Type: Bug
>          Components: API, Common, Connectors, Examples, Federation, Graph, JCR, Maven Classloader, Sequencers
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Vijay Kiran Duvvuri
>             Fix For: 1.0
>
>         Attachments: DNA-499.1.patch
>
>
> Several activities should make use of the Java SecurityManager to ensure the caller has the appropriate privileges to perform the activity.  These activities should be wrapped in a block such as the following:
> String lineSeparator = java.security.AccessController.doPrivileged(
>     new java.security.PrivilegedAction<String>() {
>         public String run() {
>             return System.getProperty("line.separator");
>         }
>     }
>  );
> obviously with the correct generic type for whatever is being returned from the run.  (Nice and concise, huh? Ugh.)
> We need to go through all of the (non-test) code and add this checking (if it is not already there) when the following types of activities are performed:
> - System.getProperty
> - System.setProperty
> - Thread.currentThread().getContextClassLoader()
> - All code executed via reflection

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


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

Dan Florian resolved DNA-592.
-----------------------------

    Resolution: Done


The REST server registry is now the responsibility of the Eclipse-based project.

> 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 Jan  5 18:24:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 18:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-460)
	NodeTypeManager.unregisterType
In-Reply-To: <11755013.1244762396313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <48164414.1262733870778.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 updated DNA-460:
--------------------------------

    Attachment: DNA-460_query_2.patch


Attached a new version of the patch that doesn't have the QueryWorkspace weirdness.  It refactors RepositoryQueryManager a bit to make search and query take workspace names instead of JcrWorkspace objects.  The patch does not truly implement a "repository search" because such a thing would not be useful for RTNM, which just needs to know if a node is used in at least one place in any workspace.



> 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, DNA-460_query.patch, DNA-460_query_2.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  Tue Jan  5 19:30:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 19:30:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-623) JDBC Metadata TCK Test
 Failing in Nightly Integration Build
Message-ID: <2121862460.1262737830596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JDBC Metadata TCK Test Failing in Nightly Integration Build
-----------------------------------------------------------

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


The JDBC Metadata TCK test has one failure in the NI build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 19:34:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 19:34:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-623) JDBC Metadata TCK Test
 Failing in Nightly Integration Build
In-Reply-To: <2121862460.1262737830596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <315302654.1262738070764.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-623:
--------------------------------

    Attachment: DNA-623.patch


Now that the query tests are enabled, the TCK test is running XPathPosIndexTest against all of the connectors.  This test has a written prerequisite (in Javadoc) that the root node have at least 3 child nodes named the same as the value of the "nodeName1" property.  However, the test checks for a different precondition (more than three child nodes in total).

Since the JDBC Metadata connector doesn't support same-name siblings, it cannot meet the written prerequisite, but the configured root node did have more than 3 child nodes.  So the test tried to execute, but the query (which ended in [2]) couldn't possibly return values from this connector.

The attached patch moves the root for the test cases to a node that only has two children, effectively bypassing this test[1].  This is actually better for most other tests since it moves the test root closer to the actual root of the repository and exposes more nodes to TCK testing.  I tried to do this originally when I added the connector, but the performance was too slow.  

[1] - This is why the FileSystemRepositoryTCKTest didn't also break.  Although it doesn't support SNS either, the root node happened to only have two children so this test was effectively bypassed for that connector as well.

> JDBC Metadata TCK Test Failing in Nightly Integration Build
> -----------------------------------------------------------
>
>                 Key: DNA-623
>                 URL: https://jira.jboss.org/jira/browse/DNA-623
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-623.patch
>
>
> The JDBC Metadata TCK test has one failure in the NI build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 19:39:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 19:39:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <4096355.1262738371259.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-617:
-------------------------------------

This is only happening on the BasicJPA integration test.  IIRC, that test doesn't run during the CI build.

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 19:39:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 19:39:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-623) JDBC Metadata TCK
 Test Failing in Nightly Integration Build
In-Reply-To: <2121862460.1262737830596.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1795345326.1262738371287.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-623.
---------------------------------

    Resolution: Done


Applied patch to resolve defect

> JDBC Metadata TCK Test Failing in Nightly Integration Build
> -----------------------------------------------------------
>
>                 Key: DNA-623
>                 URL: https://jira.jboss.org/jira/browse/DNA-623
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-623.patch
>
>
> The JDBC Metadata TCK test has one failure in the NI build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 20:18:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 20:18:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1924335648.1262740710712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers reassigned DNA-617:
-----------------------------------

    Assignee: Brian Carothers  (was: Randall Hauch)


> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  5 20:20:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Tue, 5 Jan 2010 20:20:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <272016912.1262740830597.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-617:
-------------------------------------

I think I can take care of this one.  Please feel free to assign it back to yourself if you want it and/or get to it first.

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 11:42:34 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 6 Jan 2010 11:42:34 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-613) XPath order-by
 clause is not working
In-Reply-To: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1779009221.1262796154750.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-613:
-----------------------------------

One problem was when there was an ORDER BY SCORE(selectorName) when the selector was a view that joined multiple tables. In this case, the score function would need to be resolved against the scores from multiple source tables. The existing FullTextSearchScore subclass of DynamicOperand required a single selector name, so it was not possible to represent a single DynamicOperand that represented the score from multiple tables.

One option considered was the creation of a FullTextSearchCompositeScore that would accept multiple selector names.  Unfortunately, DynamicOperand makes the assumption that it only applies to a single selector, and thus has a 'getSelectorName()' method.  This could be changed to no longer make this assumption (as well as adjust all places that use this method), but the composite score DynamicOperand seems to be a bit of a hack.

Instead, I decided that it was better to support a DynamicOperand that represented an arithmetic operation between two other DynamicOperands, and thus there is a new ArithmeticOperand class that contains a left DynamicOperand, an arithmetic operator, and a right DynamicOperand.  And of course, ArithmeticOperands can be nested inside each other to create relatively complex operations.  Because an ArithmeticOperand applies to two DynamicOperands, those DynamicOperands might apply to different selectors.  Thus, this approach also required changing DynamicOperand.getSelectorName():SelectorName to getSelectorNames():Set<SelectorName>.  Also, it was critical for this set to maintain the order of insertion of the set, so a LinkedHashSet was used.

This addition required changes to the SQL parser, the planner, and the optimizer (along with the corresponding tests).  The change to multiple selector names for DynamicOperand also required changes to all other DynamicOperand subclasses, and the code that used these methods.

Another change was made to the PlanHints so that a string representation of the query plan could be requested and placed in the results. In the JCR layer, this was leveraged by always requesting the plan and then making the string representation of the plan publicly available on the JcrQueryResult class.

Finally, there were changes made to the way the XPath-to-SQL translator works (along with the test cases).

> 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  Wed Jan  6 13:34:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 13:34:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-624) Canonicalize Property
 Names/Behavior in SVN Connector
Message-ID: <1904168938.1262802870638.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Canonicalize Property Names/Behavior in SVN Connector
-----------------------------------------------------

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


The SVN connector assigns the same semantics to setDirectoryOfDefaultWorkspace that other connectors assign to setDefaultWorkspaceName.  It also requires a full URL for each workspace name (equivalent to the original method of naming workspaces in the FS connector, but unlike the other connectors and the new method of naming workspaces in the FS connector).  For consistency, it would be nice if these methods used the canonical names and behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 13:44:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 13:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-624) Canonicalize Property
 Names/Behavior in SVN Connector
In-Reply-To: <1904168938.1262802870638.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <322923206.1262803470724.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-624:
--------------------------------

    Attachment: DNA-624.patch


Attached patch that changes the name of setDirectoryOfDefaultWorkspace to setDefaultWorkspaceName and changes the behavior of the workspace names as described in the issue description.

> Canonicalize Property Names/Behavior in SVN Connector
> -----------------------------------------------------
>
>                 Key: DNA-624
>                 URL: https://jira.jboss.org/jira/browse/DNA-624
>             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-624.patch
>
>
> The SVN connector assigns the same semantics to setDirectoryOfDefaultWorkspace that other connectors assign to setDefaultWorkspaceName.  It also requires a full URL for each workspace name (equivalent to the original method of naming workspaces in the FS connector, but unlike the other connectors and the new method of naming workspaces in the FS connector).  For consistency, it would be nice if these methods used the canonical names and behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 13:44:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 13:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-624) Canonicalize Property
 Names/Behavior in SVN Connector
In-Reply-To: <1904168938.1262802870638.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1594229940.1262803470919.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-624.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Applied patch to resolve issue

> Canonicalize Property Names/Behavior in SVN Connector
> -----------------------------------------------------
>
>                 Key: DNA-624
>                 URL: https://jira.jboss.org/jira/browse/DNA-624
>             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-624.patch
>
>
> The SVN connector assigns the same semantics to setDirectoryOfDefaultWorkspace that other connectors assign to setDefaultWorkspaceName.  It also requires a full URL for each workspace name (equivalent to the original method of naming workspaces in the FS connector, but unlike the other connectors and the new method of naming workspaces in the FS connector).  For consistency, it would be nice if these methods used the canonical names and behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 19:05:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 6 Jan 2010 19:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <335278324.1262822730628.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-617:
------------------------------

    Attachment: DNA-617_FixForNPE.patch


I've attached a very simple patch to fix the NPE in the search indexer (in the case when there isn't even a root in the source), but once I apply this I'm getting other errors in the basic JPA connector (see stack trace that follows).  I'm not sure why this might be happening, but I haven't had time to investigate. I did want to post the fix for the NPE, though.

java.lang.IllegalArgumentException: The actual location of </{}testroot/{}node1[2] && [{http://www.jboss.org/dna/1.0}uuid = 656a90cd-1703-440d-b4f2-19280cf20c57]> is not equal to the current location of </{}testroot/{}node1[3] && [{http://www.jboss.org/dna/1.0}uuid = 656a90cd-1703-440d-b4f2-19280cf20c57]>
	at org.jboss.dna.graph.request.ReadNodeRequest.setActualLocationOfNode(ReadNodeRequest.java:263)
	at org.jboss.dna.connector.store.jpa.model.basic.BasicRequestProcessor.process(BasicRequestProcessor.java:519)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:243)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
	at org.jboss.dna.connector.store.jpa.model.basic.BasicJpaConnection.execute(BasicJpaConnection.java:154)
	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:183)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:637)



> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_FixForNPE.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 19:14:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 6 Jan 2010 19:14:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1630093074.1262823270657.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-617:
-----------------------------------

The fix for the NPE seems to work fine, with all unit tests passing.  Therefore, I'm committing this one-line change.

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_FixForNPE.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 19:16:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 6 Jan 2010 19:16:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Issue Comment Edited: (DNA-617) NPE while
 updating indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1740878931.1262823390695.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch edited comment on DNA-617 at 1/6/10 7:15 PM:
-----------------------------------------------------------

The one-line change fixes the NPE in the SearchIndexer class, but it does not resolve the other issue.  Therefore, I'm committing the one-line change and leaving issue open.

      was (Author: rhauch):
    The fix for the NPE seems to work fine, with all unit tests passing.  Therefore, I'm committing this one-line change.
  
> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_FixForNPE.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 19:57:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 19:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-618) SVN connector
 integration tests are failing with '404 Not Found'
In-Reply-To: <848461723.1262620410717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1988988014.1262825850729.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-618:
--------------------------------

    Attachment: DNA-618.patch


The attached patch shrinks the size of the repo, making it run dramatically more quickly from sites outside of the jboss.org network.  Prior to the search code, there was no particular penalty for having a huge repo as long as you didn't try to read every node.  But the search code has to read the whole repo to build the search index.  In this case, that required reading several thousand files, each requiring two network calls (one for the file and one for its contents).

To echo something Randall said earlier on IRC, we probably need to start adding our own internal tests of the connectors on large repositories, but I think that will be separate from the TCK tests.

> SVN connector integration tests are failing with '404 Not Found'
> ----------------------------------------------------------------
>
>                 Key: DNA-618
>                 URL: https://jira.jboss.org/jira/browse/DNA-618
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-618.patch
>
>
> This failure happened during one of the nightly integration tests.  Note the '!' character in the path - is that right??
> org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	...
> Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
> 	at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174)
> 	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 21:07:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 21:07:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-625)
 JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
Message-ID: <739645558.1262830058275.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
----------------------------------------------------------------

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

The JdbcMetadataRepositoryTckTest is failing with an OOM exception when "mvn clean install" was run from the command line in dna-integration-tests with less than 1G of heap size.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 21:07:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 21:07:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-625)
 JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
In-Reply-To: <739645558.1262830058275.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <757069306.1262830058321.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-625.
---------------------------------

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


Committed patch to resolve defect

> JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
> ----------------------------------------------------------------
>
>                 Key: DNA-625
>                 URL: https://jira.jboss.org/jira/browse/DNA-625
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-625.patch
>
>
> The JdbcMetadataRepositoryTckTest is failing with an OOM exception when "mvn clean install" was run from the command line in dna-integration-tests with less than 1G of heap size.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 21:07:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 21:07:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-625)
 JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
In-Reply-To: <739645558.1262830058275.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1182976493.1262830058297.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-625:
--------------------------------

    Attachment: DNA-625.patch


Attached patch that shrinks the size of the repository for the test back down.

> JdbcMetadataRepositoryTckTest Failing When Run From Command-Line
> ----------------------------------------------------------------
>
>                 Key: DNA-625
>                 URL: https://jira.jboss.org/jira/browse/DNA-625
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-625.patch
>
>
> The JdbcMetadataRepositoryTckTest is failing with an OOM exception when "mvn clean install" was run from the command line in dna-integration-tests with less than 1G of heap size.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  6 23:04:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 6 Jan 2010 23:04:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1780777798.1262837070613.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-617:
--------------------------------

    Attachment: DNA-617_connector.patch


The attached patch corrects an issue in the connector that caused it calculate an SNS index of 2 for all nodes whose SNS index was not supposed to be 1.  The expanded TCK test data exposed this.

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_connector.patch, DNA-617_FixForNPE.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 00:48:38 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 00:48:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
In-Reply-To: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <757654376.1262843318578.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reassigned DNA-616:
---------------------------------

    Assignee: Randall Hauch  (was: Brian Carothers)


> JPA connector pooling doesn't appear to shutdown
> ------------------------------------------------
>
>                 Key: DNA-616
>                 URL: https://jira.jboss.org/jira/browse/DNA-616
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).
> 02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11,  , sameNameSiblingIndex=1, indexInParent=1, nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
> 02:16:42,310 DEBUG more......
> 02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> 02:16:42,310 DEBUG 
>     delete 
>     from
>         DNA_SUBGRAPH_NODES 
>     where
>         QUERY_ID=?
> 02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
> 02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
> 02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
> 02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 01:32:38 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 01:32:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
In-Reply-To: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1193136290.1262845958031.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-616:
------------------------------

    Attachment: DNA-616_fix.patch


The problem has to do with the fact that this example uses a FederatedRepositorySource as a source for a JpaRepository (which creates a FederatedRepositorySource on top of the supplied source).  Thus, there is a FederatedRepositorySource that uses another FederatedRepositorySource, and this is the condition that causes the deadlock.

When the JcrRepository is created, it uses a SearchIndexer to crawl the content and create the requisite indexes for query/search.  The SearchIndexer is create a CompositeRequestChannel (which it uses to submit to the designated repository source a CompositeRequest that remains open, allowing the SearchIndexer to supply requests and then use those requests to build other requests that are submitted within the same execution/transaction), and is submitting a ReadBranchRequest to the source that happens to be the lower FederatedRepositorySource. The FederatedRepositorySource returns a connection that has an execute(...) method that implements the work by using the fork-join algorithm to process the request, which in this case is the  CompositeRequest (owned by the CompositeRequestChannel created by the SearchIndexer).

Now, the ForkRequestProcessor works on all the incoming request, which again is the CompositeRequest.  The FRP's process(CompositeRequest) is actually inherited from RequestProcessor, and simply uses an iterator to get all of the requests within the CompositeRequest.  The iterator promptly returns the first ReadBranchRequest, so the ForkRequestProcessor handles this via it's process(ReadBranchRequest), and like all of the ForkRequestProcessor.process(...) methods, forks the request into appropriate requests to submit to the underlying (federated) sources, and then it enqueues the forked requests into a queue.  

Note that the ForkRequestProcessor does NOT mark the requests it processes as being completed.  After all, this is the job of the JoinRequestProcessor.

Meanwhile, the ForkRequestProcessor.process(ReadBranchRequest) completes and returns, and the iterator in the ForkRequestProcessor.process(CompositeRequest) then attempts to get the next request.

But the SearchIndexer has only added one ReadBranchRequest and is waiting/blocking until that request is completed before it continues.  But the FederatedRepositoryConnection is waiting/blocking until the next request is added to the CompositeRequest.  Thus the deadlock.

The only way to break this deadlock is for the ReadRequestBranch to be completed.  But, because of the way that FederatedRepositoryConnection.execute(...) is implemented, the ForkRequestProcessor.process(request) must complete before the JoinRequestProcessor is started.  So we need to create and start the JoinRequestProcessor without waiting for the ForkRequestProcessor.process(request) to complete. 

The solution is actually coded in the FederatedRepositoryConnection.execute(...) - there is a 'shouldProcessSynchronously(Request)' method that returns whether the ForkRequestProcessor should be processed synchronously or asynchronously, and is implemented to always return 'true' (synchronous).  The solution to this problem requires that the method return 'false' for CompositeRequests that contain more than one (or an unknown number) of requests.  (In other cases, there is just one request, so the forking can be done synchronously, saving the work of pushing the fork processing into the executor service.)

Thus, the 'shouldProcessSynchronously(Request)' was implemented to do this, and the test completed ... with an error.  This error is caused by a bug in the JoinRequestProcessor.process(ReadBranchRequest) that failed to properly calculate the projected actual Locations for the ProxyNodes from the source requests.  (Apparently the SearchIndexer reads a branch that is deeper than was previously tested.) 

Fixing the JoinRequestProcessor.process(ReadBranchRequest) allows the repository example test cases to complete successfully.

See the attached patch, which was committed and verified with a full integration build (all unit and integration tests pass).  The patch also changes the log level of the repository example back to 'ERROR' (what it was previously), and also re-enables the 'docs/examples/gettingstarted/repository' project in the 'docs/examples/gettingstarted/pom.xml'.

> JPA connector pooling doesn't appear to shutdown
> ------------------------------------------------
>
>                 Key: DNA-616
>                 URL: https://jira.jboss.org/jira/browse/DNA-616
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-616_fix.patch
>
>
> Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).
> 02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11,  , sameNameSiblingIndex=1, indexInParent=1, nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
> 02:16:42,310 DEBUG more......
> 02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> 02:16:42,310 DEBUG 
>     delete 
>     from
>         DNA_SUBGRAPH_NODES 
>     where
>         QUERY_ID=?
> 02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
> 02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
> 02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
> 02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 01:44:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 01:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
In-Reply-To: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <394821201.1262846670664.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-616:
------------------------------

    Workaround Description: Added line breaks to the description to prevent the page from layout out uber-wide.
               Description: 
Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).

02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11, data=2c6d8085f7848080808af480a7fbe8f4f4f0baafaff7f7f7aeeae3f0aeeff2e7afeae3f2afb1aeb0fdf0f2e9ede1f2f9d4f9f0e5f
7868080808180cef480b8fbe8f4f4f0baafaff7f7f7aeeae2eff3f3aeeff2e7afe4eee1afe5f8e1edf0ece5f3afe1e9f2e3f2e1e6f4afb
1aeb0fdc1e9f2e3f2e1e6f4f4808ae9eef4f2efe4f5e3e5e4f7868080808180d3f48084b1b9b9b5f48084e3f2e5f7f7868080808
180d3f48081b2f48085ede1ebe5f2f7868080808180d3f48087cce5e1f2eae5f4f48085edefe4e5ecf7868080808180d3f4808
4cccab4b5f4808be3f2f5e9f3e5d3f0e5e5e4f7868080808180d3f48085b4b5b7ebf4f48083f5f2ecf7868080808180d3f480a7
e8f4f4f0baafafe5eeaef7e9ebe9f0e5e4e9e1aeeff2e7aff7e9ebe9afcce5e1f2eae5f4dfb4b5f48085f2e1eee7e5f7868080808
180d3f48086b2b1b2b0eeedf4808beef5ede2e5f2c2f5e9ecf4f7868080808180d3f48084b2b6b4abf4808be5edf0f4f9d7e5
e9e7e8f4f7868080808180d3f48087b1b3b6b9b5ece2, sameNameSiblingIndex=1, indexInParent=1, 
nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
02:16:42,310 DEBUG more......
02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
02:16:42,310 DEBUG 
    delete 
    from
        DNA_SUBGRAPH_NODES 
    where
        QUERY_ID=?
02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)

and so on.

  was:
Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).

02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11,  , sameNameSiblingIndex=1, indexInParent=1, nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
02:16:42,310 DEBUG more......
02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
02:16:42,310 DEBUG 
    delete 
    from
        DNA_SUBGRAPH_NODES 
    where
        QUERY_ID=?
02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)

and so on.



> JPA connector pooling doesn't appear to shutdown
> ------------------------------------------------
>
>                 Key: DNA-616
>                 URL: https://jira.jboss.org/jira/browse/DNA-616
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-616_fix.patch
>
>
> Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).
> 02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11, data=2c6d8085f7848080808af480a7fbe8f4f4f0baafaff7f7f7aeeae3f0aeeff2e7afeae3f2afb1aeb0fdf0f2e9ede1f2f9d4f9f0e5f
> 7868080808180cef480b8fbe8f4f4f0baafaff7f7f7aeeae2eff3f3aeeff2e7afe4eee1afe5f8e1edf0ece5f3afe1e9f2e3f2e1e6f4afb
> 1aeb0fdc1e9f2e3f2e1e6f4f4808ae9eef4f2efe4f5e3e5e4f7868080808180d3f48084b1b9b9b5f48084e3f2e5f7f7868080808
> 180d3f48081b2f48085ede1ebe5f2f7868080808180d3f48087cce5e1f2eae5f4f48085edefe4e5ecf7868080808180d3f4808
> 4cccab4b5f4808be3f2f5e9f3e5d3f0e5e5e4f7868080808180d3f48085b4b5b7ebf4f48083f5f2ecf7868080808180d3f480a7
> e8f4f4f0baafafe5eeaef7e9ebe9f0e5e4e9e1aeeff2e7aff7e9ebe9afcce5e1f2eae5f4dfb4b5f48085f2e1eee7e5f7868080808
> 180d3f48086b2b1b2b0eeedf4808beef5ede2e5f2c2f5e9ecf4f7868080808180d3f48084b2b6b4abf4808be5edf0f4f9d7e5
> e9e7e8f4f7868080808180d3f48087b1b3b6b9b5ece2, sameNameSiblingIndex=1, indexInParent=1, 
> nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
> 02:16:42,310 DEBUG more......
> 02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> 02:16:42,310 DEBUG 
>     delete 
>     from
>         DNA_SUBGRAPH_NODES 
>     where
>         QUERY_ID=?
> 02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
> 02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
> 02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
> 02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 02:23:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:23:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
In-Reply-To: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1904058042.1262849010610.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-616:
------------------------------

    Workaround Description:   (was: Added line breaks to the description to prevent the page from layout out uber-wide.)


Added line breaks to the description to prevent the page from layout out uber-wide.

> JPA connector pooling doesn't appear to shutdown
> ------------------------------------------------
>
>                 Key: DNA-616
>                 URL: https://jira.jboss.org/jira/browse/DNA-616
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-616_fix.patch
>
>
> Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).
> 02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11, data=2c6d8085f7848080808af480a7fbe8f4f4f0baafaff7f7f7aeeae3f0aeeff2e7afeae3f2afb1aeb0fdf0f2e9ede1f2f9d4f9f0e5f
> 7868080808180cef480b8fbe8f4f4f0baafaff7f7f7aeeae2eff3f3aeeff2e7afe4eee1afe5f8e1edf0ece5f3afe1e9f2e3f2e1e6f4afb
> 1aeb0fdc1e9f2e3f2e1e6f4f4808ae9eef4f2efe4f5e3e5e4f7868080808180d3f48084b1b9b9b5f48084e3f2e5f7f7868080808
> 180d3f48081b2f48085ede1ebe5f2f7868080808180d3f48087cce5e1f2eae5f4f48085edefe4e5ecf7868080808180d3f4808
> 4cccab4b5f4808be3f2f5e9f3e5d3f0e5e5e4f7868080808180d3f48085b4b5b7ebf4f48083f5f2ecf7868080808180d3f480a7
> e8f4f4f0baafafe5eeaef7e9ebe9f0e5e4e9e1aeeff2e7aff7e9ebe9afcce5e1f2eae5f4dfb4b5f48085f2e1eee7e5f7868080808
> 180d3f48086b2b1b2b0eeedf4808beef5ede2e5f2c2f5e9ecf4f7868080808180d3f48084b2b6b4abf4808be5edf0f4f9d7e5
> e9e7e8f4f7868080808180d3f48087b1b3b6b9b5ece2, sameNameSiblingIndex=1, indexInParent=1, 
> nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
> 02:16:42,310 DEBUG more......
> 02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> 02:16:42,310 DEBUG 
>     delete 
>     from
>         DNA_SUBGRAPH_NODES 
>     where
>         QUERY_ID=?
> 02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
> 02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
> 02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
> 02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 02:26:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-616) JPA connector pooling
 doesn't appear to shutdown
In-Reply-To: <1070825282.1262448390662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1919234143.1262849190641.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-616.
-------------------------------

    Resolution: Done


I'm going to mark this as resolved, since the repositories example unit tests are running successfully again, and because the fix worked in all test and integration tests (except for the BasicJpaRepositoryTckTest, which is currently failing per DNA-617, but produces the same results before and after this patch).

> JPA connector pooling doesn't appear to shutdown
> ------------------------------------------------
>
>                 Key: DNA-616
>                 URL: https://jira.jboss.org/jira/browse/DNA-616
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-616_fix.patch
>
>
> Our integration tests now appear to be running forever in what appears to be an infinite loop.  The unit tests in 'docs/examples/gettingstarted/repositories' module appear to run forever, with the log ending with the snippet below (which goes on forever).  Note that the example is running with DEBUG (which also needs to be changed).
> 02:16:42,310 DEBUG org.jboss.dna.connector.store.jpa.model.simple.NodeEntity{referentialIntegrityEnforced=false, childName=Learjet 45, childNamespace=org.jboss.dna.connector.store.jpa.model.common.NamespaceEntity#1, compressed=null, id=5, allowsSameNameChildren=false, largeValues=<uninitialized>, propertyCount=11, data=2c6d8085f7848080808af480a7fbe8f4f4f0baafaff7f7f7aeeae3f0aeeff2e7afeae3f2afb1aeb0fdf0f2e9ede1f2f9d4f9f0e5f
> 7868080808180cef480b8fbe8f4f4f0baafaff7f7f7aeeae2eff3f3aeeff2e7afe4eee1afe5f8e1edf0ece5f3afe1e9f2e3f2e1e6f4afb
> 1aeb0fdc1e9f2e3f2e1e6f4f4808ae9eef4f2efe4f5e3e5e4f7868080808180d3f48084b1b9b9b5f48084e3f2e5f7f7868080808
> 180d3f48081b2f48085ede1ebe5f2f7868080808180d3f48087cce5e1f2eae5f4f48085edefe4e5ecf7868080808180d3f4808
> 4cccab4b5f4808be3f2f5e9f3e5d3f0e5e5e4f7868080808180d3f48085b4b5b7ebf4f48083f5f2ecf7868080808180d3f480a7
> e8f4f4f0baafafe5eeaef7e9ebe9f0e5e4e9e1aeeff2e7aff7e9ebe9afcce5e1f2eae5f4dfb4b5f48085f2e1eee7e5f7868080808
> 180d3f48086b2b1b2b0eeedf4808beef5ede2e5f2c2f5e9ecf4f7868080808180d3f48084b2b6b4abf4808be5edf0f4f9d7e5
> e9e7e8f4f7868080808180d3f48087b1b3b6b9b5ece2, sameNameSiblingIndex=1, indexInParent=1, 
> nodeUuidString=6ae6cf0c-88b8-4cb9-af63-195a6a351378, children=<uninitialized>, parent=org.jboss.dna.connector.store.jpa.model.simple.NodeEntity#3, workspaceId=1}
> 02:16:42,310 DEBUG more......
> 02:16:42,310 DEBUG about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
> 02:16:42,310 DEBUG 
>     delete 
>     from
>         DNA_SUBGRAPH_NODES 
>     where
>         QUERY_ID=?
> 02:16:42,311 DEBUG cxnStmtMgr.statementSet( org.hsqldb.jdbc.jdbcConnection at 588a137c ).size(): 15
> 02:16:42,311 DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 1; num connections: 1; num keys: 15
> 02:16:42,311 DEBUG about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 02:16:42,312 DEBUG checkinStatement(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 15; checked out: 0; num connections: 1; num keys: 15
> 02:19:41,831 DEBUG Checking for expired resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG Refurbishing idle resources - Fri Jan 01 02:19:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:19:41,831 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:20:26,832 DEBUG Checking for expired resources - Fri Jan 01 02:20:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:20:26,832 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG Checking for expired resources - Fri Jan 01 02:21:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:11,835 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG Checking for expired resources - Fri Jan 01 02:21:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:21:56,837 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG Refurbishing idle resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,834 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> 02:22:41,838 DEBUG Checking for expired resources - Fri Jan 01 02:22:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:22:41,838 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG Checking for expired resources - Fri Jan 01 02:23:26 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:23:26,840 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG Checking for expired resources - Fri Jan 01 02:24:11 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:11,843 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG Checking for expired resources - Fri Jan 01 02:24:56 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG BEGIN check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:24:56,845 DEBUG FINISHED check for expired resources.  [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG Refurbishing idle resources - Fri Jan 01 02:25:41 EST 2010 [com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea]
> 02:25:41,837 DEBUG trace com.mchange.v2.resourcepool.BasicResourcePool at 427a39ea [managed: 1, unused: 0, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection at 2ac6fb1)
> and so on.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 02:30:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:30:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-618) SVN connector
 integration tests are failing with '404 Not Found'
In-Reply-To: <848461723.1262620410717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1643218890.1262849430662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-618:
-----------------------------------

The SVN connector unit and integration tests were all successful in tonight's integration build.  Unless something was disabled in the tests, this looks like the issue could be resolved.

> SVN connector integration tests are failing with '404 Not Found'
> ----------------------------------------------------------------
>
>                 Key: DNA-618
>                 URL: https://jira.jboss.org/jira/browse/DNA-618
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-618.patch
>
>
> This failure happened during one of the nightly integration tests.  Note the '!' character in the path - is that right??
> org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	...
> Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
> 	at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174)
> 	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)

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


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

Randall Hauch updated DNA-455:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
           Labels: known_issue  (was: )


I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release.  Therefore, retargeting to the 1.0 release.

> 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: 1.0
>
>
> 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  Thu Jan  7 02:33:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:33:31 -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: <1273172607.1262849611343.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:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release.  Therefore, retargeting to the 1.0 release.

> 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: 1.0
>
>
> 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  Thu Jan  7 02:33:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:33:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-46) DNA should provide a
 JCR 1.0 API (JSR-170) implementation
Message-ID: <2118271275.1262849611305.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-46:
-----------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
           Labels: known_issue  (was: )


I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release.  Therefore, retargeting to the 1.0 release.

> DNA should provide a JCR 1.0 API (JSR-170) implementation
> ---------------------------------------------------------
>
>                 Key: DNA-46
>                 URL: https://jira.jboss.org/jira/browse/DNA-46
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, JCR
>    Affects Versions: 0.2
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Critical
>             Fix For: 1.0
>
>
> DNA should provide a JCR 1.0 API (JSR-170) implementation.

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

        

From jira-events at lists.jboss.org  Thu Jan  7 02:33:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:33:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (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: <834584456.1262849611404.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-612:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
           Labels: known_issue  (was: )


I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release.  Therefore, retargeting to the 1.0 release.

> 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: 1.0
>
>
> 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 Jan  7 02:33:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:33:31 -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: <285440266.1262849611379.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

    Fix Version/s: 1.0
                       (was: 0.7)
           Labels: known_issue  (was: )


I don't think it's critical that this issue is fixed in 0.7, but it should be fixed before the 1.0 release.  Therefore, retargeting to the 1.0 release.

> 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: 1.0
>
>         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  Thu Jan  7 02:36:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-610) Allow JPA Connector to
 be generic (not require hibernate)
In-Reply-To: <2067165663.1262283090668.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1707328065.1262849790791.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-610:
------------------------------

    Fix Version/s: Future Releases


Targeting to 'Future Releases' (rather than leaving un-targeted) for now. This can be targeted to any release when desired.

> 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
>             Fix For: Future Releases
>
>
> 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 Jan  7 02:40:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:40: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: <101963194.1262850030662.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 ]

Randall Hauch updated DNA-591:
------------------------------

    Workaround Description: See comments.
             Fix Version/s: 1.0
                Workaround: [Workaround Exists]


Targeting to 1.0. We should at least fix the NPE and provide a more useful error message.  However, we may also decide that we want to support this kind of inheritance.

> 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
>             Fix For: 1.0
>
>         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  Thu Jan  7 02:57:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 02:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1297908279.1262851050822.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-617:
-----------------------------------

There still were a lot of failures in last night's integration [1].  I'm wondering whether the Basic model is just not going to cut it anymore.  Thoughts?

[1] http://hudson.jboss.org/hudson/job/DNA%20nightly%20integration%20on%20JDK1.5/638/ (link will eventually not work when job 638 is pushed out of history)

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_connector.patch, DNA-617_FixForNPE.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 03:02:44 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 03:02:44 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Assigned: (DNA-621) Document search/query
 languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2028011727.1262851364149.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reassigned DNA-621:
---------------------------------

    Assignee: Randall Hauch


> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 03:17:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 03:17:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-613) XPath order-by
 clause is not working
In-Reply-To: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1372934175.1262852250646.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-613:
-----------------------------------

The latest status is that the TCK tests that use ORDER BY are still not working because of a failure to resolve the dynamic operands in the ORDER BY clauses to the proper columns in the results (or the selectors for SCORE). I think this is simply because the queries get translated into SQL that uses aliases.

I think there is a straightforward fix, though I need to write some additional tests. So I'm leaving the target to 0.7 for now.  However, if this consumes too much time, it is okay to push to 1.0 since this issue only affects XPath queries with ORDER BY clauses.  (DNA-612 is already pushed.)

> 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 Jan  7 03:19:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 03:19:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-621) Document search/query
 languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <220072012.1262852370630.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-621:
------------------------------

    Priority: Blocker  (was: Major)


I think I can put together the documentation for the languages pretty quickly, but it is pretty important to have document the query/search functionality (considering it is the primary feature of this release). So I'm leaving the target as 0.7 but raising the priority to 'Blocker'.

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 06:03:49 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 06:03:49 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-618) SVN connector
 integration tests are failing with '404 Not Found'
In-Reply-To: <848461723.1262620410717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1124566698.1262862229357.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-618.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


I concur.  Applying the patch resolved the defect locally and in the NI build.

> SVN connector integration tests are failing with '404 Not Found'
> ----------------------------------------------------------------
>
>                 Key: DNA-618
>                 URL: https://jira.jboss.org/jira/browse/DNA-618
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-618.patch
>
>
> This failure happened during one of the nightly integration tests.  Note the '!' character in the path - is that right??
> org.jboss.dna.graph.connector.RepositorySourceException: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.checkRequestForErrors(SearchEngineIndexer.java:380)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:265)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.test.integration.svn.SvnAndJcrIntegrationTest.beforeEach(SvnAndJcrIntegrationTest.java:72)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	...
> Caused by: org.tmatesoft.svn.core.SVNException: svn: '/repos/dna/!svn/bc/1517/trunk/ddl_sequencer/pom.xml' path not found: 404 Not Found (http://anonsvn.jboss.org)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> 	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:71)
> 	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getFile(DAVRepository.java:275)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.getData(SVNRepositoryRequestProcessor.java:1351)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.readNode(SVNRepositoryRequestProcessor.java:285)
> 	at org.jboss.dna.connector.svn.SVNRepositoryRequestProcessor.process(SVNRepositoryRequestProcessor.java:308)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:608)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:241)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:314)
> 	at org.jboss.dna.graph.request.processor.RequestProcessor.process(RequestProcessor.java:223)
> 	at org.jboss.dna.connector.svn.SVNRepositoryConnection.execute(SVNRepositoryConnection.java:174)
> 	at org.jboss.dna.graph.connector.RepositoryConnectionPool$ConnectionWrapper.execute(RepositoryConnectionPool.java:996)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:193)
> 	at org.jboss.dna.graph.request.CompositeRequestChannel$2.call(CompositeRequestChannel.java:189)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 09:38:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 09:38: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: <2098829565.1262875110574.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_clean.patch


Attached patch that cleanly (i.e., with proper internationalization) corrects the NPE and provides a reasonably useful error message instead.

> 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
>             Fix For: 1.0
>
>         Attachments: DNA-591.patch, DNA-591_clean.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  Thu Jan  7 09:43:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 09:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
Message-ID: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Change Default Path Repository Cache Behavior to Not Cache
----------------------------------------------------------

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


The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 09:49:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 09:49:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
In-Reply-To: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <208350943.1262875770854.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-626:
--------------------------------

    Attachment: DNA-626.patch


Attached patch that reverts the default caching behavior for the path repository implementations to not cache.  It is still possible to override the cache policy for any path repository by calling setCachePolicy(PathCachePolicy)  on the repository source.

> Change Default Path Repository Cache Behavior to Not Cache
> ----------------------------------------------------------
>
>                 Key: DNA-626
>                 URL: https://jira.jboss.org/jira/browse/DNA-626
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-626.patch
>
>
> The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 10:48:31 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 10:48:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-627) Improve Support for
 Node Type Inheritance
Message-ID: <905958517.1262879311014.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Improve Support for Node Type Inheritance
-----------------------------------------

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


DNA is currently fairly conservative in when it allows node type inheritance.  As just one example, the following definitions are not allowed (because type A and B both declare a child node with the same name:

[nodeA]
+ child (nt:unstructured)

[nodeB]
+ child (nt:unstructured)

[nodeC] > nodeA, nodeB

Opening this defect as a placeholder for discussion/patches around whether the inheritance rules should be relaxed and how.

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

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


Applied patch to resolve issue.

> 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
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-591.patch, DNA-591_clean.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  Thu Jan  7 11:12:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 11:12:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
In-Reply-To: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1872019181.1262880751013.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-626:
-----------------------------------

Is there a way to set the cache policy on the source via DnaConfiguration (or JcrConfiguration) and its configuration files?

> Change Default Path Repository Cache Behavior to Not Cache
> ----------------------------------------------------------
>
>                 Key: DNA-626
>                 URL: https://jira.jboss.org/jira/browse/DNA-626
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-626.patch
>
>
> The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 11:22:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 11:22:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-368) Referenced Nodes Can
	Be Deleted
In-Reply-To: <27124321.1240252162271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <423560816.1262881350736.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-368:
-----------------------------------

Right now its not really very easy to write a single query that finds all references to this type, since we don't know which properties to search/query.  We may need to add something to the index so that this is easier. Keep this targeted to 0.7 for the moment (though we may want to create another issue for the index change, keep only that in 0.7, and move this to 1.0).

> Referenced Nodes Can Be Deleted
> -------------------------------
>
>                 Key: DNA-368
>                 URL: https://jira.jboss.org/jira/browse/DNA-368
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> There is not currently a check in AbstractJcrNode.remove() to see if the node (or any of its child nodes) are targets of references.  Per section 7.1.6 of the 1.0.1 specification, this should cause a ReferentialIntegrityException to be thrown.

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

        

From jira-events at lists.jboss.org  Thu Jan  7 11:48:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 11:48:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-460)
	NodeTypeManager.unregisterType
In-Reply-To: <11755013.1244762396313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1891587345.1262882918626.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 updated DNA-460:
--------------------------------

    Attachment: DNA-460_sql.patch


Attached patch that changes the query language from XPath to SQL to allow the use of the LIMIT keyword.  The patch also corrects a minor problem with limit/offset parsing.

> 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, DNA-460_query.patch, DNA-460_query_2.patch, DNA-460_sql.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  Thu Jan  7 12:11:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 12:11:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
In-Reply-To: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2101709506.1262884290894.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-626:
-------------------------------------

Not yet.  There needs to be though.

> Change Default Path Repository Cache Behavior to Not Cache
> ----------------------------------------------------------
>
>                 Key: DNA-626
>                 URL: https://jira.jboss.org/jira/browse/DNA-626
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-626.patch
>
>
> The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 13:13:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 13:13:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
In-Reply-To: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1445522195.1262888010787.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-626:
------------------------------

    Component/s: Connectors
                 Graph


> Change Default Path Repository Cache Behavior to Not Cache
> ----------------------------------------------------------
>
>                 Key: DNA-626
>                 URL: https://jira.jboss.org/jira/browse/DNA-626
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-626.patch
>
>
> The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 13:24:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 13:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-460)
	NodeTypeManager.unregisterType
In-Reply-To: <11755013.1244762396313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1821542588.1262888670603.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 resolved DNA-460.
---------------------------------

    Fix Version/s: 0.7
                       (was: 1.1)
       Resolution: Done


Applied patch to resolve defect.

> 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: 0.7
>
>         Attachments: DNA-460.patch, DNA-460_query.patch, DNA-460_query_2.patch, DNA-460_sql.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  Thu Jan  7 13:35:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 13:35:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-628) Allow CachePolicy
 Configuration through Graph and Configuration Files
Message-ID: <651183981.1262889330705.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Allow CachePolicy Configuration through Graph and Configuration Files
---------------------------------------------------------------------

                 Key: DNA-628
                 URL: https://jira.jboss.org/jira/browse/DNA-628
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors, Graph
    Affects Versions: 0.6
            Reporter: Brian Carothers
            Assignee: Brian Carothers
             Fix For: 1.0


The AbstractPathRepositorySource (which is used by all three of our path repository implementations) allows cache policies to be set programmatically.  There needs to be a corresponding way to set the cache policy through the configuration graph (and, hence, the configuration file).

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

        

From jira-events at lists.jboss.org  Thu Jan  7 13:53:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 7 Jan 2010 13:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-626) Change Default Path
 Repository Cache Behavior to Not Cache
In-Reply-To: <1481390595.1262875410696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <532858207.1262890410693.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-626.
---------------------------------

    Resolution: Done


Applied patch to resolve issue.

> Change Default Path Repository Cache Behavior to Not Cache
> ----------------------------------------------------------
>
>                 Key: DNA-626
>                 URL: https://jira.jboss.org/jira/browse/DNA-626
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, Graph
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: DNA-626.patch
>
>
> The path repositories currently have a default cache policy that caches nodes for 30 seconds.  In previous releases, nothing was cached.  The default cache policy should be to not cache anything both for backwards compatibility and to avoid confusing evaluators who won't understand why there's a 30 second delay between them directly adding a file or folder to an FS repository source and the corresponding node showing up in the JCR 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  Thu Jan  7 14:16:30 2010
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Thu, 7 Jan 2010 14:16:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-49) Sequence DDL files
Message-ID: <266363657.1262891790914.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=12502806#action_12502806 ] 

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

Re-factored integration test into dialect-specific tests.

Added initial parsing methods for StandardDdlParser ..... CREATE:  DOMAIN, COLLATION, TRANSLATION & CHARACTER SET. (i.e. type and "name" only).

Couple of fixes for bugs found while creating more integration test cases.

Added Oracle parsing methods for CREATE PROCEDURE, FUNCTION & MATERIALIZED VIEW

> 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  Thu Jan  7 17:23:30 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 7 Jan 2010 17:23:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-629) Document The REST
 Client API In The Reference Guide
Message-ID: <1966304968.1262903010600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Document The REST Client API In The Reference Guide
---------------------------------------------------

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


Add a section to Chapter 10 "The JBoss DNA RESTful Web Service" describing and demonstrating the REST client API.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 17:25:30 2010
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 7 Jan 2010 17:25:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-629) Document The REST
 Client API In The Reference Guide
In-Reply-To: <1966304968.1262903010600.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1537590276.1262903130610.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Dan Florian resolved DNA-629.
-----------------------------

    Resolution: Done


Modified introduction.xml and rest_service.xml to document the REST client API.

> Document The REST Client API In The Reference Guide
> ---------------------------------------------------
>
>                 Key: DNA-629
>                 URL: https://jira.jboss.org/jira/browse/DNA-629
>             Project: DNA
>          Issue Type: Task
>          Components: Web Application
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> Add a section to Chapter 10 "The JBoss DNA RESTful Web Service" describing and demonstrating the REST client API.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 22:53:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 22:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-630) Executing a query
 resulted in a "read past EOF" error
Message-ID: <2039162797.1262922810695.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Executing a query resulted in a "read past EOF" error
-----------------------------------------------------

                 Key: DNA-630
                 URL: https://jira.jboss.org/jira/browse/DNA-630
             Project: DNA
          Issue Type: Bug
          Components: Query, Search
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


When executing a query against the LuceneSearchEngine, the query came back with an error (in the problems), which stated "read past EOF".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 23:03:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 23:03:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-630) Executing a query
 resulted in a "read past EOF" error
In-Reply-To: <2039162797.1262922810695.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1988171260.1262923410753.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-630:
-----------------------------------

This was found while trying to fix DNA-613.

I logged this because this was so tricky.  LuceneSearchEngine works by building up a (complex) Lucene Query object and executing that, then collecting the tuples from the Lucene documents that are returned in the results. 

In this case, the AQM query included a constraint (among others) that LuceneSearchEngine converted into a custom HasValueQuery class (which extends Query).  HasValueQuery creates a custom ExistsScorer class (which subclasses org.apache.lucene.search.Scorer), and the problem was that the 'nextDoc()' method was implemented incorrectly.  It uses an internal counter to walk through the documents (handed to it in the constructor), and was not (correctly) checking whether the docId was less than the maxDoc, which is obtained from the IndexReader.maxDoc().

Essentially, the ExistsScorer was iterating through more documents than in the reader, and thus the "read past EOF".  (The IndexReader uses a random-access mechanism to seek to the desired document, but if the document ID is too big, the seek goes beyond the EOF.)

I checked the other Query subclasses in org.jboss.dna.search.lucene.query, and found a few other classes that were also implemented incorrectly.  These were fixed as well, and all tests pass.

> Executing a query resulted in a "read past EOF" error
> -----------------------------------------------------
>
>                 Key: DNA-630
>                 URL: https://jira.jboss.org/jira/browse/DNA-630
>             Project: DNA
>          Issue Type: Bug
>          Components: Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> When executing a query against the LuceneSearchEngine, the query came back with an error (in the problems), which stated "read past EOF".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  7 23:22:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 23:22:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-613) XPath order-by
 clause is not working
In-Reply-To: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1139499212.1262924550612.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-613:
-----------------------------------

Found several minor issues that all conspired to make this functionality not work.  
1) The XPathToQueryTranslator was incorrectly translating queries that used wildcards in the path.
2) Queries that used aliases in columns, criteria, or order-by clauses were not always being resolved correctly, resulting in the inability to locate the correct column (when constraints or order-by clauses had to be evaluated after the fact.
3) The optimizer was not always pushing SELECT nodes (e.g., criteria) down below ACCESS nodes. The rule to do this was not included by default and was instead added to the rule stack only when criteria were encountered. This was changed to simply always add the rule to the stack.
4) Columns used in constraints or order-by clauses were not always being included in the PROJECT columns. Thus it was possible that the evaluation of the criteria or order-by required data that was not in the tuples, causing an error.  Note that these PROJECT columns dictate which values are included in the tuples during processing, and all of these are not necessarily included in the result columns.
5) The LuceneSearchEngine was incorrectly mapping paths into criteria values that could be applied to Lucene. If the user specified a criteria such as 
            PATH(table) LIKE '/Cars/Hybrid/%'
the "/Cars/Hybrid/%" value was used directly as the LIKE expression. But paths are stored in the indexes so that the SNS index is always included, and thus the LIKE expressions never evaluated to return any documents. Since the SNS index in the path might include the wildcard characters (e.g., '[%]' or '[_]'), we couldn't use the standard PathFactory to convert the LIKE expression value into a Path.  The solution was to just use String manipulation to insert a '[1]' at the end of each segment that didn't already include a SNS index.
6) Lucene 'read past EOF' errors; see DNA-630.

> 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 Jan  7 23:24:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 7 Jan 2010 23:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-613) XPath order-by
 clause is not working
In-Reply-To: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <928776303.1262924670728.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-613:
-----------------------------------

The TCK unit tests that use 'order by' in XPath queries now pass and as such are included in all runs.

> 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  Fri Jan  8 00:21:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 00:21:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-631) Provide a way to set
 the JcrRepository descriptors from the JcrConfiguration and JcrEngine
Message-ID: <636247246.1262928090606.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Provide a way to set the JcrRepository descriptors from the JcrConfiguration and JcrEngine
------------------------------------------------------------------------------------------

                 Key: DNA-631
                 URL: https://jira.jboss.org/jira/browse/DNA-631
             Project: DNA
          Issue Type: Feature Request
          Components: JCR
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Priority: Minor
             Fix For: 1.0


The JcrRepository constructor takes a Map for the descriptors, and a few of these are checked by the TCK tests. It would be nice to control the Repository.QUERY_XPATH_DOC_ORDER and Repository.QUERY_XPATH_POS_INDEX descriptors via JcrConfiguration and the configuration file to directly control certain XPath tests.

To date we've gotten around it by limiting the number of nodes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 00:44:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 00:44:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-630) Executing a query
 resulted in a "read past EOF" error
In-Reply-To: <2039162797.1262922810695.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1339906322.1262929470734.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-630.
-------------------------------

    Resolution: Done


> Executing a query resulted in a "read past EOF" error
> -----------------------------------------------------
>
>                 Key: DNA-630
>                 URL: https://jira.jboss.org/jira/browse/DNA-630
>             Project: DNA
>          Issue Type: Bug
>          Components: Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> When executing a query against the LuceneSearchEngine, the query came back with an error (in the problems), which stated "read past EOF".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 00:46:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 00:46:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-613) XPath order-by clause
 is not working
In-Reply-To: <767430117.1262295210678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1904359555.1262929590674.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-613.
-------------------------------

    Resolution: Done


> 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  Fri Jan  8 00:48:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 00:48:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-632) The JDBC Metadata
 Connector is failing 3 XPath TCK tests
Message-ID: <758152584.1262929710801.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The JDBC Metadata Connector is failing 3 XPath TCK tests
--------------------------------------------------------

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


Because DNA-613 was just fixed, we now have several XPath-related TCK unit tests now included in the TCK runs.  

The solution may be to just fix DNA-631, and then set the XPath descriptors so that these tests are not executed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 06:51:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 8 Jan 2010 06:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-632) The JDBC Metadata
 Connector is failing 3 XPath TCK tests
In-Reply-To: <758152584.1262929710801.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1409308335.1262951490989.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-632:
--------------------------------

    Attachment: DNA-632.patch


Attached patch that sets javax.jcr.tck.propertyname1 to something meaningful for this connector.  All tests pass.

> The JDBC Metadata Connector is failing 3 XPath TCK tests
> --------------------------------------------------------
>
>                 Key: DNA-632
>                 URL: https://jira.jboss.org/jira/browse/DNA-632
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Query
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 0.7
>
>         Attachments: DNA-632.patch
>
>
> Because DNA-613 was just fixed, we now have several XPath-related TCK unit tests now included in the TCK runs.  
> The solution may be to just fix DNA-631, and then set the XPath descriptors so that these tests are not executed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 06:53:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 8 Jan 2010 06:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-632) The JDBC Metadata
 Connector is failing 3 XPath TCK tests
In-Reply-To: <758152584.1262929710801.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2111565735.1262951610812.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-632.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


Committed patch to resolve defect

> The JDBC Metadata Connector is failing 3 XPath TCK tests
> --------------------------------------------------------
>
>                 Key: DNA-632
>                 URL: https://jira.jboss.org/jira/browse/DNA-632
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Query
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-632.patch
>
>
> Because DNA-613 was just fixed, we now have several XPath-related TCK unit tests now included in the TCK runs.  
> The solution may be to just fix DNA-631, and then set the XPath descriptors so that these tests are not executed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 11:24:30 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 8 Jan 2010 11:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-614) REST client osgi
 bundle for the Eclipse plugin
In-Reply-To: <206867925.1262367335949.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <531100335.1262967870680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop updated DNA-614:
-------------------------------------

    Attachment: DNA_614_WEB_REST_CLIENT_01_JAR_OSGI_COMPLIANT.patch


The maven bundle plugin changes the metadata without change the extension.
This bundle needs 9 osgi compliant dependencies to be register into a felix or equinox container:
- dna-common (uses patch to change the metadata)
- jettison
- httpclient-osgi
- httpcore-osgi
- org.apache.commons
- net.jcip.annotations
- org.slf4j.log4j12
- org.slf4j.api
- org.apache.log4j

I used Pax-Construct "http://www.ops4j.org/projects/pax/construct/help/wrap-jar.html" to wrap some dependencies or got some others from the SpringSource Enterprise Bundle Repository.


> REST client osgi bundle for the Eclipse plugin
> ----------------------------------------------
>
>                 Key: DNA-614
>                 URL: https://jira.jboss.org/jira/browse/DNA-614
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>         Attachments: DNA_614_WEB_REST_CLIENT_01_JAR_OSGI_COMPLIANT.patch
>
>
> create REST client osgi bundle for the Eclipse plugin to avoid to build them manually every 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 Jan  8 11:26:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 11:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Work started: (DNA-621) Document
 search/query languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1070376692.1262967990980.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Work on DNA-621 started by Randall Hauch.

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 11:28:30 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 8 Jan 2010 11:28:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-614) REST client osgi
 bundle for the Eclipse plugin
In-Reply-To: <206867925.1262367335949.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <65875282.1262968110693.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop updated DNA-614:
-------------------------------------

    Attachment: DNA_614_COMMON_01_JAR_OSGI_COMPLIANT.patch


> REST client osgi bundle for the Eclipse plugin
> ----------------------------------------------
>
>                 Key: DNA-614
>                 URL: https://jira.jboss.org/jira/browse/DNA-614
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>         Attachments: DNA_614_COMMON_01_JAR_OSGI_COMPLIANT.patch, DNA_614_WEB_REST_CLIENT_01_JAR_OSGI_COMPLIANT.patch
>
>
> create REST client osgi bundle for the Eclipse plugin to avoid to build them manually every 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 Jan  8 12:09:30 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 8 Jan 2010 12:09:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-633) Paragraphs that
 explains how to use the pax-construct utils to make a bundle of
 dependencies
Message-ID: <1945423499.1262970570741.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Paragraphs that explains how to use the pax-construct utils to make a bundle of dependencies
--------------------------------------------------------------------------------------------

                 Key: DNA-633
                 URL: https://jira.jboss.org/jira/browse/DNA-633
             Project: DNA
          Issue Type: Task
          Components: Documentation
    Affects Versions: 0.7
            Reporter: Serge Emmanuel Pagop
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7


Because we are thereby to get some core dna modules osgi compliant and not the dependencies of each module. However we also have to reference some utils, that can be used to wrap dependencies to osgi bundle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 12:13:30 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 8 Jan 2010 12:13:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-633) Paragraphs that
 explains how to use the pax-construct utils to make a bundle of
 dependencies
In-Reply-To: <1945423499.1262970570741.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <289182945.1262970810800.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

I used Pax-Construct "http://www.ops4j.org/projects/pax/construct/help/wrap-jar.html" to wrap some dependencies and it works.

> Paragraphs that explains how to use the pax-construct utils to make a bundle of dependencies
> --------------------------------------------------------------------------------------------
>
>                 Key: DNA-633
>                 URL: https://jira.jboss.org/jira/browse/DNA-633
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>
> Because we are thereby to get some core dna modules osgi compliant and not the dependencies of each module. However we also have to reference some utils, that can be used to wrap dependencies to osgi bundle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 12:28:30 2010
From: jira-events at lists.jboss.org (Serge Emmanuel Pagop (JIRA))
Date: Fri, 8 Jan 2010 12:28:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-614) REST client osgi bundle
 for the Eclipse plugin
In-Reply-To: <206867925.1262367335949.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1554597589.1262971710642.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Serge Emmanuel Pagop closed DNA-614.
------------------------------------

    Resolution: Done


> REST client osgi bundle for the Eclipse plugin
> ----------------------------------------------
>
>                 Key: DNA-614
>                 URL: https://jira.jboss.org/jira/browse/DNA-614
>             Project: DNA
>          Issue Type: Task
>          Components: Tools
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>         Attachments: DNA_614_COMMON_01_JAR_OSGI_COMPLIANT.patch, DNA_614_WEB_REST_CLIENT_01_JAR_OSGI_COMPLIANT.patch
>
>
> create REST client osgi bundle for the Eclipse plugin to avoid to build them manually every 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 Jan  8 13:59:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 13:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-634) Add write support to
 the SVN connector
Message-ID: <1663536630.1262977170598.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add write support to the SVN connector
--------------------------------------

                 Key: DNA-634
                 URL: https://jira.jboss.org/jira/browse/DNA-634
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Serge Emmanuel Pagop
             Fix For: 0.7


The SVN connector is read-only as of 0.6, but it should support updates so that it can be used to update files stored in SVN.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 14:03:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 14:03:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-634) Add write support to
 the SVN connector
In-Reply-To: <1663536630.1262977170598.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <910913103.1262977410680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-634.
-------------------------------

    Resolution: Done


This work was originally done under DNA-519, DNA-604, and DNA-607.

> Add write support to the SVN connector
> --------------------------------------
>
>                 Key: DNA-634
>                 URL: https://jira.jboss.org/jira/browse/DNA-634
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>
> The SVN connector is read-only as of 0.6, but it should support updates so that it can be used to update files stored in SVN.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 14:12:37 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 14:12:37 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-635) DnaConfiguration and
 JcrConfiguration should provide methods to write the configuration to a
 file
Message-ID: <209190399.1262977957389.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

DnaConfiguration and JcrConfiguration should provide methods to write the configuration to a file
-------------------------------------------------------------------------------------------------

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


The DnaConfiguration/JcrConfiguration classes are able to load content from a configuration file, and then can be used to make changes to the configuration.  However, it would be nice to have methods to write out the configuration content to a file.

The DnaConfiguration and JcrConfiguration classes can be created on top of a RepositorySource, and if this is done, the save() will write the configuration to the source.  If this is not done, a transient in-memory repository source is used, and save() does write to that.  But the load(...) methods can be called multiple times, and there should be corresponding 'write(...)' 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  Fri Jan  8 14:36:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 14:36:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-636) JcrConfiguration files
 should be able to specify node types by referencing one or more CND files
Message-ID: <1838414604.1262979391198.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JcrConfiguration files should be able to specify node types by referencing one or more CND files
------------------------------------------------------------------------------------------------

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


Right now it is not possible to load an entire configuration (including node types) from a file, unless the file contains the graph representation of the node types.  It should be possible to specify in the configuration file the relative path (or URL) of one or more CND files, and then the JcrConfiguration should automatically load those CND files after it loads the configuration file.

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

        

From jira-events at lists.jboss.org  Fri Jan  8 15:10:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 15:10:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-637) Write JOPR plugin to
 manage and monitor a JCR engine/cluster
Message-ID: <652861897.1262981430739.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Write JOPR plugin to manage and monitor a JCR engine/cluster
------------------------------------------------------------

                 Key: DNA-637
                 URL: https://jira.jboss.org/jira/browse/DNA-637
             Project: DNA
          Issue Type: Feature Request
          Components: Connectors, Federation, JCR, Tools
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: Future Releases


Write a JOPR plugin that allows a user to manage and monitor a ModeShape engine or cluster.  There are a number of things that can be monitored, but we'd want to come up with a good list of useful things.  For example:
- nodes in cluster
- # of sessions for each repository
- sources and their activity
- events and journaling
- search engine and it's use/update activity
- sequencers and their activity
- analyzers and their activity
- executor services ?
- other??

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  8 18:50:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 18:50:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-159) Federate/cache content
 from a remote JCR (and DNA) repository
In-Reply-To: <31597339.1213713291723.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29863805.1262994630759.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-159:
------------------------------

    Fix Version/s: 1.0
                       (was: Future Releases)


Targeting to 1.0, since it would be a great feature to be able to access existing JCR repositories hosted by other JCR implementations.

> Federate/cache content from a remote JCR (and DNA) repository
> -------------------------------------------------------------
>
>                 Key: DNA-159
>                 URL: https://jira.jboss.org/jira/browse/DNA-159
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>            Reporter: Randall Hauch
>            Priority: Minor
>             Fix For: 1.0
>
>
> The primary use case for this feature is to allow an application to have a local DNA repository that is configured to be a local, cached copy of a single remote JCR repository.  So, rather than having multiple sources, this use case would have a single source (using a connector to a remote JCR repository), and it would be configured to probably have a cache policy with a relatively short TTL.  (Of course the TTL could be extended if the connector could listen to the remote repository to receive events, which would be propagated up to the local "federated" repository and would cause those particular changed instances to be purged from the cache.
> Ideally this could be made to be very lightweight and very easy to configure, maybe even using just an in-memory "integrated repository" (aka, cache).
> This use case is far superior to an implementation that uses remote calls for every operation.

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

        

From jira-events at lists.jboss.org  Fri Jan  8 21:12:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 21:12:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-638) Delete the
 'dna-jcr-tck' project, as it is no longer used
Message-ID: <1178574982.1263003151321.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Delete the 'dna-jcr-tck' project, as it is no longer used
---------------------------------------------------------

                 Key: DNA-638
                 URL: https://jira.jboss.org/jira/browse/DNA-638
             Project: DNA
          Issue Type: Task
          Components: JCR
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Priority: Critical
             Fix For: 0.7


The 'dna-jcr-tck' project used to contain a subset of the JR TCK unit tests.  It is no longer used, and should be 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  Fri Jan  8 22:11:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 8 Jan 2010 22:11:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-638) Delete the
 'dna-jcr-tck' project, as it is no longer used
In-Reply-To: <1178574982.1263003151321.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1374111755.1263006690647.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-638.
-----------------------------

    Resolution: Rejected


We are in fact still using this to run a nightly run of the full suite of TCK tests.  Rejecting.

> Delete the 'dna-jcr-tck' project, as it is no longer used
> ---------------------------------------------------------
>
>                 Key: DNA-638
>                 URL: https://jira.jboss.org/jira/browse/DNA-638
>             Project: DNA
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Priority: Critical
>             Fix For: 0.7
>
>
> The 'dna-jcr-tck' project used to contain a subset of the JR TCK unit tests.  It is no longer used, and should be 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  Sat Jan  9 06:55:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 06:55:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-639) JcrTckTest Missing Two
	Test Cases
Message-ID: <1445824891.1263038130678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JcrTckTest Missing Two Test Cases
---------------------------------

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


The JcrTckTest in dna-jcr is missing two test cases that are part of the JCR 1.0 TCK test suite (and in the dna-jcr-tck module): ElementTest and XPathLevelTwoTest.  Additionally, the dna-jcr-tck tests has some SQL tests misclassified as Level 1 compliance tests.

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

        

From jira-events at lists.jboss.org  Sat Jan  9 06:57:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 06:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-639) JcrTckTest Missing Two
	Test Cases
In-Reply-To: <1445824891.1263038130678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <866517630.1263038250604.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-639:
--------------------------------

    Attachment: DNA-639.patch


Attached patch that updates the tests in JcrTckTest (and comments them out as they don't pass yet) and cleans up dna-jcr-tck, which had some misclassified test cases and some out-of-date dependencies,

> JcrTckTest Missing Two Test Cases
> ---------------------------------
>
>                 Key: DNA-639
>                 URL: https://jira.jboss.org/jira/browse/DNA-639
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-639.patch
>
>
> The JcrTckTest in dna-jcr is missing two test cases that are part of the JCR 1.0 TCK test suite (and in the dna-jcr-tck module): ElementTest and XPathLevelTwoTest.  Additionally, the dna-jcr-tck tests has some SQL tests misclassified as Level 1 compliance tests.

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

        

From jira-events at lists.jboss.org  Sat Jan  9 06:59:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 06:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-639) JcrTckTest Missing
	Two Test Cases
In-Reply-To: <1445824891.1263038130678.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <856361307.1263038370594.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-639.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Applied patch to resolve issue

> JcrTckTest Missing Two Test Cases
> ---------------------------------
>
>                 Key: DNA-639
>                 URL: https://jira.jboss.org/jira/browse/DNA-639
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-639.patch
>
>
> The JcrTckTest in dna-jcr is missing two test cases that are part of the JCR 1.0 TCK test suite (and in the dna-jcr-tck module): ElementTest and XPathLevelTwoTest.  Additionally, the dna-jcr-tck tests has some SQL tests misclassified as Level 1 compliance tests.

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

        

From jira-events at lists.jboss.org  Sat Jan  9 08:32:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 08:32:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-640) JNDI-Based Deployment
Message-ID: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

JNDI-Based Deployment
---------------------

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


DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 08:36:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 08:36:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <323747396.1263044190802.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-640:
--------------------------------

    Attachment: DNA-640.patch


Attached patch adds a standalone JNDI factory for the JcrEngine class that exposes JCR repositories.  Multiple JCR repositories can be exposed by the same engine by creating successive JNDI references.  On.ly one JcrEngine will be started/loaded.

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:43:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 10:43:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1266057168.1263051810642.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-640:
-----------------------------------

We probably should document this in the Reference Guide. Perhaps a new section in Chapter 8 (http://docs.jboss.org/jbossdna/latest/manuals/reference/html/configuration.html)?

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:49:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 10:49:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <621078244.1263052170649.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-640:
--------------------------------

    Attachment:     (was: DNA-640.patch)


> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:51:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 10:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <149535345.1263052290690.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-640:
-----------------------------------

BTW, the patch looks pretty good.  One very minor nit: maybe change the example in the JavaDoc so that the configuration file name denotes a configuration for multiple repositories, and that it doesn't use the 'tck' in the config file path.

I will attempt to write the section for the Reference Guide, but would appreciate feedback when I commit it.  I'm currently working on updating the Reference Guide for 0.7 (DNA-621), but I hope to be committing some changes very soon. I will also put a similar subsection in Section 3.2 of the Getting Started guide (http://docs.jboss.org/jbossdna/0.6/manuals/gettingstarted/html/using_dna.html#jcr_configuration).

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:51:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 10:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Issue Comment Edited: (DNA-640)
	JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1967150376.1263052290712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch edited comment on DNA-640 at 1/9/10 10:50 AM:
------------------------------------------------------------

We probably should document this in the Reference Guide. Perhaps a new section in Chapter 8 (http://docs.jboss.org/jbossdna/0.6/manuals/reference/html/configuration.html)?

      was (Author: rhauch):
    We probably should document this in the Reference Guide. Perhaps a new section in Chapter 8 (http://docs.jboss.org/jbossdna/latest/manuals/reference/html/configuration.html)?
  
> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:51:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 10:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1766713708.1263052290749.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-640:
--------------------------------

    Attachment: DNA-640.patch


Uploaded a better version of the patch that will at least try to shutdown the repository if the JNDI implementation supports events.


> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:57:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 10:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <825842622.1263052650614.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-640:
-----------------------------------

Do you think the factory should be logging AND throwing an exception? Seems to me that if it propagates the exception, it should not log it.  This is usually a best practice, but this may need to be different because of the way it's part of JNDI and initialization.  Thoughts?

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch, HOWTO-access-DNA-JNDI.txt
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:57:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 10:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <441425865.1263052650718.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-640:
--------------------------------

    Attachment: HOWTO-access-DNA-JNDI.txt


I agree wholeheartedly with the earlier comment about needing to document this in the Ref. Guide.  However, the process isn't wholly smooth yet, as you can see from step 1 in the attached HOWTO.  It does work in Tomcat though.

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch, HOWTO-access-DNA-JNDI.txt
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 10:59:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 10:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Issue Comment Edited: (DNA-640)
	JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1774401664.1263052770645.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch edited comment on DNA-640 at 1/9/10 10:58 AM:
------------------------------------------------------------

Do you think the factory should be logging AND throwing the exceptions? Seems to me that if it propagates an exception, it should not log it.  This is usually a best practice, but this may need to be different because the engine may have multiple problems and because of the way it's part of JNDI and initialization.  Thoughts?

      was (Author: rhauch):
    Do you think the factory should be logging AND throwing an exception? Seems to me that if it propagates the exception, it should not log it.  This is usually a best practice, but this may need to be different because of the way it's part of JNDI and initialization.  Thoughts?
  
> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>         Attachments: DNA-640.patch, HOWTO-access-DNA-JNDI.txt
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 14:47:37 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 14:47:37 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-641) The DDL sequencer
 should allow specifying the dialect type in DDL comments
Message-ID: <1142828809.1263066457009.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The DDL sequencer should allow specifying the dialect type in DDL comments
--------------------------------------------------------------------------

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


At the moment, the DdlParsers class looks for a leading "PARSER_ID = <DialectName>" at the beginning of the DDL stream.  If this is not found, then the class attempts to automatically discover the dialect by performing a best fit.  Unfortunately, the "PARSER_ID = <DialectName>" is not valid DDL, and thus can never be included in a real DDL file.

Rather than look for this kind of leading statement, the DdlParsers should look for the first comment block and simply attempt to find the dialect names in the comment text. This should be done in a case-insensitive way, and would ideally count the number of occurrences of each dialect name (thus handling the case where an Oracle DDL file contained both "oracle" and "postgres" in the comment; hopefully the "oracle" term would appear more than others).  This of course is very imprecise, but it is perhaps only 'better than' the use of non-DDL statements.

It is also desirable that the DdlParsers class should be tolerant of incorrectly typing the DDL stream.  For example, lets say a DDL file contains a comment containing "oracle" and no other dialect name, but this DDL file is actually for PostgreSQL and merely contains the word "oracle" because it was converted from another Oracle DDL file.  In this case, if parsing with the PostgreSQL parser results in an error, the DdlParsers should start over, behaving as though the dialect typing was incorrect, and should perform a "best fit".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 14:56:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 14:56:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-642) DDL sequencer should
 accept optional configuration property listing possible dialects
Message-ID: <30406389.1263066990840.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

DDL sequencer should accept optional configuration property listing possible dialects
-------------------------------------------------------------------------------------

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


The DDL sequencer (which implements StreamSequencer) currently does not look at the properties in the StreamSequencerContext to look for the dialects that should be used. By supporting such an optional property, the DDL sequencer could be configured to only run certain dialects (perhaps even just one). And if the list were ordered, the DDL sequencer could use that order to determine the proper dialect should multiple parsers result in the same score.  This certainly is imprecise, but it does offer the user a bit more control should they need it.

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

        

From jira-events at lists.jboss.org  Sat Jan  9 15:26:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 15:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-643) Provide a JAR (or OSGi
 bundle) that contains all of the JCR implementation, all extensions,
 and all dependencies
Message-ID: <457642340.1263068790705.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Provide a JAR (or OSGi bundle) that contains all of the JCR implementation, all extensions, and all dependencies
----------------------------------------------------------------------------------------------------------------

                 Key: DNA-643
                 URL: https://jira.jboss.org/jira/browse/DNA-643
             Project: DNA
          Issue Type: Feature Request
          Components: Development Environment, JCR, Web Application
    Affects Versions: 0.7
            Reporter: Randall Hauch
             Fix For: 1.0


Web applications and other non-Maven applications often require manual deployment of JARs. This can be very difficult with JBoss DNA, considering the number of artifacts and the number of dependencies. We should include as part of our release one (or several) "convenience" JARs that can be used in different situations.

One might be a JAR that contains the JCR implementation, all extensions, and all third-party dependencies (without the logging JARs?).  This would be useful when deploying our JCR implementation to a web server via JNDI.

Another might contain our JCR implementation and all extensions, but no third-party dependencies.

Ideally we can identify the real-world scenarios so that produce only those artifacts that are 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  Sat Jan  9 15:51:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sat, 9 Jan 2010 15:51:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-643) Provide a JAR (or OSGi
 bundle) that contains all of the JCR implementation, all extensions,
 and all dependencies
In-Reply-To: <457642340.1263068790705.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <826332598.1263070290653.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-643:
------------------------------

    JBoss Forum Reference: http://community.jboss.org/thread/146589?tstart=0


Added link to forum thread asking for more input on this feature.

> Provide a JAR (or OSGi bundle) that contains all of the JCR implementation, all extensions, and all dependencies
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-643
>                 URL: https://jira.jboss.org/jira/browse/DNA-643
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Development Environment, JCR, Web Application
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 1.0
>
>
> Web applications and other non-Maven applications often require manual deployment of JARs. This can be very difficult with JBoss DNA, considering the number of artifacts and the number of dependencies. We should include as part of our release one (or several) "convenience" JARs that can be used in different situations.
> One might be a JAR that contains the JCR implementation, all extensions, and all third-party dependencies (without the logging JARs?).  This would be useful when deploying our JCR implementation to a web server via JNDI.
> Another might contain our JCR implementation and all extensions, but no third-party dependencies.
> Ideally we can identify the real-world scenarios so that produce only those artifacts that are 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  Sat Jan  9 16:33:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 16:33:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1274039741.1263072810670.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-617:
--------------------------------

    Attachment: DNA-617_test.patch


Added a test case that succinctly demonstrates the problem.  The test case will fail if the model is "Basic" and JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH = true.  If the model is simple and JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH = true, the tests will both pass.  If the model is "Basic" and JcrRepository.WORKSPACES_SHARE_SYSTEM_BRANCH = false, the tests will both pass.  

I tried playing with synchronousStep1 and awaitAllSubtasks in the FRC, but to no avail.

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_connector.patch, DNA-617_FixForNPE.patch, DNA-617_test.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan  9 19:39:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sat, 9 Jan 2010 19:39:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1353402684.1263083970658.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-617:
--------------------------------

    Attachment: DNA-617_BJC.patch


Attach patch that corrects the behavior of the BasicJpaConnector with regard to EntityManager lifetime.

Prior to the patch, the BJC obtained an EntityManager in its constructor and released the EntityManager in its close method.  The typical lifecycle for a connection is a call to the constructor followed by a single call to execute(...) followed by a call to close().  With this lifecycle, the EntityManager is only used for one call to execute(...) and the transaction is committed or rolled back after the call as appropriate.

Now that the RepositoryConnectionPool is being used (and was fixed to reuse connections), the typical lifecycle is one call to the constructor followed by multiple calls to execute(...) within different transactions followed by (eventually) a call to close().  Since the same EntityManager was being held for the entire life of the BJC object, the EntityManager would be used for multiple transactions without any attempt being made to clear out its cache.  We're using Hibernate as our JPA implementation, so the Hibernate session cache was gradually accumulating copies of the data in the database _that were gradually falling out of sync with the database_.

In other words, BJC1 would be used to create a node and set a property leaving the ChildEntity and the PropertiesEntity for the node in the Hibernate session cache for BJC1's EntityManager.  BJC2 would then be used to read the same node and update its property.  Since the entities for the node weren't yet in in the session cache for BJC2's EntityManager, BJC2 would execute select statements to load the necessary data and would perform the updates.  THEN in a subsequent call, BJC1 would be reused to read from the same node.  Since BJC already had the ChildEntity and PropertiesEntity for the node in its session cache, it would reuse the cached (and now stale) versions instead of trying to hit the database.  Hilarity ensued.

The patch makes BJC obtain an EntityManager at the beginning of the execute(...) call and release the EntityManager at the end of the execute(...) call.  Since "released" EntityManager objects are really closed by the EntityManagers factory object, this will cure the session cache issue.


> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_BJC.patch, DNA-617_connector.patch, DNA-617_FixForNPE.patch, DNA-617_test.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 02:28:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 02:28:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-621) Document
 search/query languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <487714983.1263108511382.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-621:
-----------------------------------

Updated the Getting Started guide to reflect the state of 0.7, including updating the repositories example with some minor improvements and adding a new section on deploying DNA via JNDI.

Updated the Reference Guide section that talks about the levels of JCR support to reflect the current state. Completed the initial version of the chapter on query and search functionality, and removed text that pointed to the Reference Guide from within the Reference Guide.

The docs should be close to finished, though another round of proof-reading is desired.

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 08:21:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 08:21:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-621) Document search/query
 languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <210668663.1263129690828.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-621:
--------------------------------

    Attachment: DNA-621_gs_review_bc.patch


Attached my feedback from proofing the Getting Started Guide.  A bit of minor grammatical clean-up and some refactoring of code examples to avoid horizontal scrollbars.  Overall, it looked great.  Nice job!

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-621_gs_review_bc.patch
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 11:00:31 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 11:00:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-621) Document
 search/query languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <212944672.1263139231492.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-621:
-----------------------------------

Applied Brian's patch of edits and improvements. Also described how to implement connectors by reusing the MapRepository and PathRepository frameworks (section 6.3 in the Reference Guide).

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-621_gs_review_bc.patch
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 13:57:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 13:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-367)
 AbstractJcrNode.getReferences() Is Incorrect
In-Reply-To: <21712574.1240252042628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1559335789.1263149850637.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-367:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
         Priority: Critical  (was: Major)


Pushing to 1.0.

> AbstractJcrNode.getReferences() Is Incorrect
> --------------------------------------------
>
>                 Key: DNA-367
>                 URL: https://jira.jboss.org/jira/browse/DNA-367
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Critical
>             Fix For: 1.0
>
>
> AbstractJcrNode.getReferences currently returns all of the reference properties in that node.  According to section 6.2.3 of the 1.0.1 specification, it is supposed to return all _other_ nodes that refer to it.

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

        

From jira-events at lists.jboss.org  Sun Jan 10 13:57:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 13:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-368) Referenced Nodes Can
	Be Deleted
In-Reply-To: <27124321.1240252162271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <769017099.1263149850681.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-368:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)
         Priority: Critical  (was: Major)


Pushing to 1.0.

> Referenced Nodes Can Be Deleted
> -------------------------------
>
>                 Key: DNA-368
>                 URL: https://jira.jboss.org/jira/browse/DNA-368
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Priority: Critical
>             Fix For: 1.0
>
>
> There is not currently a check in AbstractJcrNode.remove() to see if the node (or any of its child nodes) are targets of references.  Per section 7.1.6 of the 1.0.1 specification, this should cause a ReferentialIntegrityException to be thrown.

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

        

From jira-events at lists.jboss.org  Sun Jan 10 13:59:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 13:59:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-617) NPE while updating
 indexes (during integration tests)
In-Reply-To: <1675203895.1262620171181.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <333281552.1263149970684.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-617.
-------------------------------

    Resolution: Done


These patches fixed the issue, so I'm resolving. Nice job!

> NPE while updating indexes (during integration tests)
> -----------------------------------------------------
>
>                 Key: DNA-617
>                 URL: https://jira.jboss.org/jira/browse/DNA-617
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-617_BJC.patch, DNA-617_connector.patch, DNA-617_FixForNPE.patch, DNA-617_test.patch
>
>
> This happened on the nightly integration tests, but did not happen during the continuous integration tests.  So while I'm not sure how repeatable it is, there is at least a stack trace:
> java.lang.IllegalStateException: Failed to initialize the repository with text content.
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:140)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)
> 	at junit.framework.TestResult$1.protect(TestResult.java:110)
> 	at junit.framework.TestResult.runProtected(TestResult.java:128)
> 	at junit.framework.TestResult.run(TestResult.java:113)
> 	at junit.framework.TestCase.run(TestCase.java:124)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:406)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:232)
> 	at junit.framework.TestSuite.run(TestSuite.java:227)
> 	at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
> 	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
> 	at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
> 	at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
> 	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:585)
> 	at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
> 	at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
> Caused by: java.lang.NullPointerException
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.indexSubgraph(SearchEngineIndexer.java:294)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:227)
> 	at org.jboss.dna.graph.search.SearchEngineIndexer.index(SearchEngineIndexer.java:135)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.reindexContent(RepositoryQueryManager.java:334)
> 	at org.jboss.dna.jcr.RepositoryQueryManager$SelfContained.<init>(RepositoryQueryManager.java:292)
> 	at org.jboss.dna.jcr.JcrRepository.<init>(JcrRepository.java:593)
> 	at org.jboss.dna.jcr.JcrEngine.doCreateJcrRepository(JcrEngine.java:257)
> 	at org.jboss.dna.jcr.JcrEngine.getRepository(JcrEngine.java:175)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.configureRepository(DnaRepositoryStub.java:120)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:157)
> 	at org.jboss.dna.jcr.DnaRepositoryStub.getRepository(DnaRepositoryStub.java:41)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getRepository(RepositoryHelper.java:68)
> 	at org.apache.jackrabbit.test.RepositoryHelper.getProperty(RepositoryHelper.java:150)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.getProperty(AbstractJCRTest.java:442)
> 	at org.apache.jackrabbit.test.AbstractJCRTest.setUp(AbstractJCRTest.java:264)
> 	at org.apache.jackrabbit.test.api.RootNodeTest.setUp(RootNodeTest.java:47)
> 	at junit.framework.TestCase.runBare(TestCase.java:132)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 14:01:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 14:01:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-644)
 BasicJpaRepositoryTckTest has failures related to XPath queries
Message-ID: <601438178.1263150090593.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

BasicJpaRepositoryTckTest has failures related to XPath queries
---------------------------------------------------------------

                 Key: DNA-644
                 URL: https://jira.jboss.org/jira/browse/DNA-644
             Project: DNA
          Issue Type: Bug
          Components: Connectors, JCR, Query
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


Pending the correction for DNA-617, there are now 5 failures with the TCK tests running against the JPA connector with the "basic" model.  All 5 tests have to do with XPath tests, and all failures report no results found.  These need to get fixed to have a clean integration build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 14:05:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 14:05:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-633) Paragraphs that
 explains how to use the pax-construct utils to make a bundle of
 dependencies
In-Reply-To: <1945423499.1262970570741.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <741057442.1263150330694.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-633.
-------------------------------

    Resolution: Done


Thanks for the info!

> Paragraphs that explains how to use the pax-construct utils to make a bundle of dependencies
> --------------------------------------------------------------------------------------------
>
>                 Key: DNA-633
>                 URL: https://jira.jboss.org/jira/browse/DNA-633
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 0.7
>            Reporter: Serge Emmanuel Pagop
>            Assignee: Serge Emmanuel Pagop
>             Fix For: 0.7
>
>
> Because we are thereby to get some core dna modules osgi compliant and not the dependencies of each module. However we also have to reference some utils, that can be used to wrap dependencies to osgi bundle.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 16:11:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 16:11:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-621) Document search/query
 languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1448391260.1263157890653.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-621:
--------------------------------

    Attachment: DNA-621_rg_review_bc.patch


Attached all feedback from Reference Guide.  Again, nice job on that one!

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-621_gs_review_bc.patch, DNA-621_rg_review_bc.patch
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 17:24:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 17:24:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-640) JNDI-Based Deployment
In-Reply-To: <864405000.1263043950712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1640252211.1263162270645.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-640.
---------------------------------

    Fix Version/s: 0.7
       Resolution: Done


Randall wrote up some really nice documentation in the Ref. Guide - the last missing piece.

> JNDI-Based Deployment
> ---------------------
>
>                 Key: DNA-640
>                 URL: https://jira.jboss.org/jira/browse/DNA-640
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-640.patch, HOWTO-access-DNA-JNDI.txt
>
>
> DNA should support a shared deployment model through JNDI, allowing a single DNA Engine to be shared among multiple deployments in different WARs or JARs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 17:27:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 17:27:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-645) SVN Connector Should
 Support Native Lock/Unlock
Message-ID: <1960535818.1263162450585.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

SVN Connector Should Support Native Lock/Unlock
-----------------------------------------------

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


Subversion provides the ability to lock and unlock files or directories, but the SVN connector does not integrate this capability with incoming LockBranchRequests and UnlockBranchRequests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 18:17:38 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 18:17:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-256) Packaging and
	deployment
In-Reply-To: <20111111.1227230196448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1945805885.1263165458032.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-256.
---------------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Done


The specific deployment models (WAR-based, standalone, JCA-based) discussed in this bug have been split out into separate (linked) issues, some of which have already been completed.  Resolving this defect and tracking progress on the specific topics in the associated specific issues.

> Packaging and deployment
> ------------------------
>
>                 Key: DNA-256
>                 URL: https://jira.jboss.org/jira/browse/DNA-256
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Server, Web Application
>         Environment: Java EE 5 certified environment
> Java SE 5 certified environment
>            Reporter: Sergiy Litsenko
>             Fix For: 0.7
>
>
> Define flexible packaging and deployment scenarios that satisfy both Embedded/Standalone and Enterprise deployments.
> Maven plugins can package the project as different deployment artifacts:
> http://maven.apache.org/plugins/maven-ear-plugin/      JEE Enterprise Archive (EAR) file format
> http://maven.apache.org/plugins/maven-rar-plugin/       JEE Enterprise  JCA Resource adaptor Archive (RAR) file format 
> http://maven.apache.org/plugins/maven-ejb-plugin/      JEE Enterprise Javabean (EJB) file format
> http://maven.apache.org/plugins/maven-war-plugin/     JEE Enterprise Web Archive  (WAR) file format
> http://maven.apache.org/plugins/maven-assembly-plugin/        Custom packaging
> http://maven.apache.org/plugins/maven-dependency-plugin/    Custom packaging
> Examples of deployment scenarios/packaging:
> http://jackrabbit.apache.org/deployment-models.html 
> Apache Jackrabbit deployment models - including embedded, Shared J2EE Resource, and Repository Server accessble through RMI over JRMP or IIOP or WebDAV.
> http://docs.jboss.org/seam/2.1.0.GA/reference/en-US/html/configuration.html
> JBoss Seam framework packaging scenarios:
> 29.3. Configuring Seam in Java EE 5
> 29.5. Configuring Seam in Java SE, without JBoss Embedded
> 29.6. Configuring Seam in Java SE, with JBoss Embedded

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 18:19:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 18:19:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-643) Provide a JAR (or
 OSGi bundle) that contains all of the JCR implementation, all extensions,
 and all dependencies
In-Reply-To: <457642340.1263068790705.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1033489918.1263165570607.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers commented on DNA-643:
-------------------------------------

DNA-256 has some concrete suggestions and links for packaging.

> Provide a JAR (or OSGi bundle) that contains all of the JCR implementation, all extensions, and all dependencies
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-643
>                 URL: https://jira.jboss.org/jira/browse/DNA-643
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Development Environment, JCR, Web Application
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>             Fix For: 1.0
>
>
> Web applications and other non-Maven applications often require manual deployment of JARs. This can be very difficult with JBoss DNA, considering the number of artifacts and the number of dependencies. We should include as part of our release one (or several) "convenience" JARs that can be used in different situations.
> One might be a JAR that contains the JCR implementation, all extensions, and all third-party dependencies (without the logging JARs?).  This would be useful when deploying our JCR implementation to a web server via JNDI.
> Another might contain our JCR implementation and all extensions, but no third-party dependencies.
> Ideally we can identify the real-world scenarios so that produce only those artifacts that are 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  Sun Jan 10 18:34:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Sun, 10 Jan 2010 18:34:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-621) Document search/query
 languages in the Reference Guide
In-Reply-To: <734559266.1262707650785.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1619604712.1263166470661.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-621.
-------------------------------

    Resolution: Done


Applied Brian's patch (with one or two very minor modifications) for the Reference Guide. Excellent edits, with some really good catches and corrections!

> Document search/query languages in the Reference Guide
> ------------------------------------------------------
>
>                 Key: DNA-621
>                 URL: https://jira.jboss.org/jira/browse/DNA-621
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Query, Search
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-621_gs_review_bc.patch, DNA-621_rg_review_bc.patch
>
>
> We probably want to have a section/chapter in the Reference Guide that presents the different languages.  We probably just need to have a bit of intro (list the different languages, maybe show how to use them via JCR API), and then describe the different languages in detail.  The SQL language and full-text search parsers have pretty good JavaDoc, and we can probably just lift it and reformat it for DocBook.  And for XPath, we should be able to just reference the appropriate sections in the JCR 1.0 specification (perhaps linking to the online versions hosted by Day).  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 19:27:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 19:27: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: <1372824649.1263169650812.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_sequenced_date.patch


Added a sequenced date to the output

> 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, DNA-62_sequenced_date.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 Jan 10 20:20:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 20:20:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-644)
 BasicJpaRepositoryTckTest has failures related to XPath queries
In-Reply-To: <601438178.1263150090593.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1285190702.1263172830610.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-644:
--------------------------------

    Attachment: DNA-644.patch


Attached patch that makes BasicRequestProcessor.process(CreateNodeRequest) call recordChange(request) after successful node additions.  If recordChange(...) isn't called, the SearchEngineIndexer is never made aware of the change and the node will not be added to the indexes or returned as a search result.  Adding this line makes all 5 failing tests pass.  I reviewed the rest of the class, but could not find any other places where this call was missing.

> BasicJpaRepositoryTckTest has failures related to XPath queries
> ---------------------------------------------------------------
>
>                 Key: DNA-644
>                 URL: https://jira.jboss.org/jira/browse/DNA-644
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Query
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-644.patch
>
>
> Pending the correction for DNA-617, there are now 5 failures with the TCK tests running against the JPA connector with the "basic" model.  All 5 tests have to do with XPath tests, and all failures report no results found.  These need to get fixed to have a clean integration build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 10 20:48:30 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Sun, 10 Jan 2010 20:48:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-644)
 BasicJpaRepositoryTckTest has failures related to XPath queries
In-Reply-To: <601438178.1263150090593.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <602569737.1263174510613.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-644.
---------------------------------

    Resolution: Done


All tests (including integration tests of course) pass on a clean build.  Resolved issue by applying patch.

> BasicJpaRepositoryTckTest has failures related to XPath queries
> ---------------------------------------------------------------
>
>                 Key: DNA-644
>                 URL: https://jira.jboss.org/jira/browse/DNA-644
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR, Query
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-644.patch
>
>
> Pending the correction for DNA-617, there are now 5 failures with the TCK tests running against the JPA connector with the "basic" model.  All 5 tests have to do with XPath tests, and all failures report no results found.  These need to get fixed to have a clean integration build.

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


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

Randall Hauch commented on DNA-580:
-----------------------------------

We already have acquired all the resources for the new name:
- we have a Magnolia project for the ModeShape JBoss.org site (http://www.jboss.org/modeshape), though it's not yet active as I haven't published it yet
- we own the 'modeshape.org' domain is ours, and http://www.modeshape.org will soon redirect to http://www.jboss.org/modeshape, and we'll be able to use 'org.modeshape' for our package names.
- we have a new JIRA, and I will be moving all of the DNA issues into the ModeShape JIRA.  Our issues will be of the form "MODE-XYZ"
plus a new SVN repository, new mailing lists, new blog site, new Twitter account, and new Ohloh project.
- we have a new logo design and should soon have the images we need

Here are the first steps:

1) The JBoss DNA SVN has already been locked down, and no more changes can be made to it.  DONE!
2) All of the history from the DNA SVN has already been loaded into the ModeShape SVN.  Basically, it looks exactly like the DNA repository did right after the 0.7 release. But at the moment, it is locked down as well, pending the next step.  DONE!
3) I will move all DNA JIRAs (all of them, including those that are complete or incomplete) to the ModeShape JIRA. Any links to DNA issues will automatically redirect to the corresponding issue in the ModeShape JIRA. The numbers won't match, but JIRA has it's own way of doing things.
4) I've started renaming the projects, packages and classes.  The projects will go from 'dna-...' to 'modeshape-...", and our package structure will go from "org.jboss.dna..." to "org.modeshape...".  And any class that has "DNA" in the name will be renamed. I will then commit these changes to the ModeShape SVN.  I will also move all of the JIRA issues from DNA to 
5) I will then open up the ModeShape SVN, and you could switch your development environments over to use https://svn.jboss.org/repos/modeshape/trunk . But at this point, we still only want to change JavaDoc, comments, and the documents.

After this is done, we'll release ModeShape 1.0.0.Beta1, which will essentially be the same thing as DNA 0.7 except with the new brand, new module names, and updated documentation.  We'll publish the http://jboss.org/modeshape project, and we'll start publicizing everywhere we can. And, the code in SVN will be changed to be 1.0.0.GA-SNAPSHOT, and we can continue fixing issues, completing any part of the rebranding, and working towards 100% TCK runs and 1.0.0.GA!

What can you do now?  
- Sign up for the new mailing lists at https://lists.jboss.org/mailman/listinfo/.  As usual, we have modeshape-announce at ..., modeshape-commits at ..., modeshape-dev at ..., modeshape-issues at ..., and modeshape-users at ....
- If you're on Twitter, follow @modeshape and retweet when the time comes
- If you use an RSS reader, add our new blog at http://modeshape.wordpress.com/.  No need to do anything if you're already subscribed to the JBoss Feed. 
- If you have any local changes, create some patches and edit them so that they'll work with the new project names and package structure
- Go to the new IRC room, #modeshape on freenode.net
- Relax for a few days while I do my magic with JIRA and SVN


> 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 Jan 12 16:35:30 2010
From: jira-events at lists.jboss.org (Vijay Kiran Duvvuri (JIRA))
Date: Tue, 12 Jan 2010 16:35:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-580) Rebrand project to
	new name
In-Reply-To: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <239437937.1263332130611.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Vijay Kiran Duvvuri commented on DNA-580:
-----------------------------------------

I'm taking up the documentation update for rebranding. 

> 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  Wed Jan 13 12:32:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 13 Jan 2010 12:32:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-646) Generated JavaDoc is
 missing recently-added public packages
Message-ID: <197296357.1263403950680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Generated JavaDoc is missing recently-added public packages
-----------------------------------------------------------

                 Key: DNA-646
                 URL: https://jira.jboss.org/jira/browse/DNA-646
             Project: DNA
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 0.7
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Critical
             Fix For: 1.0


The JavaDoc generation is configured to only show 'public API' packages by listing them, but some of the packages added during the 0.7 release did not make it into the list, and thus are missing from the JavaDoc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Jan 13 16:59:31 2010
From: jira-events at lists.jboss.org (Vijay Kiran Duvvuri (JIRA))
Date: Wed, 13 Jan 2010 16:59:31 -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: <26294869.1263419971097.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 ]

Vijay Kiran Duvvuri updated DNA-580:
------------------------------------

    Attachment: refguide-rebranding.patch


Patch for the reference guide that fixes the following for rebranding:
JBoss DNA -> ModeShape
DNA -> ModeShape
org.jboss.dna -> org.modeshape
dna-xyz  -> modeshape-xyz (maven artifact references)


> 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
>
>         Attachments: refguide-rebranding.patch
>
>
> 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  Wed Jan 13 22:19:06 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 13 Jan 2010 22:19:06 -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: <1834742455.1263439146476.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:
------------------------------

    Attachment: rebrand-dna.sh


Attached is the script I used to do most of the work, and it does the following:
1) replaces in all files of various extensions (e.g., *.java, *.cnd, *.xml, etc.) various combinations of "JBoss DNA", "DNA", "org.jboss.dna", "org.jboss.examples.dna", "http://www.jboss.org/dna", "http://labs.jboss.org/dna", "org/jboss/dna", and such with the corresponding ModeShape construct.
2) renames various directories, including "org/jboss/dna" -> "org/modeshape", "org/jboss/example/dna" -> "org/modeshape/example", etc.
3) performs various changes to the POM files for artifactIds, groupIds, constants, variables values, etc.
4) handles a number of kinds of files is specific ways that were not addressed globally in #1
5) renames java class (e.g, "DnaConfiguration" -> "ModeShapeConfiguration", etc.) and references to them
6) updates the .gitignore file, which performs a similar function to the numerous svn:ignore properties
7) renames the various modules

The script is done in terms of a git repository (because it handles renames and moves more effectively than SVN, which really just does deletes followed by adds), but this can pretty easily be changed if needed.

As I developed the script, I was able to throw away local changes to revert back to the last version of DNA (but in the ModeShape SVN) and re-run the script.  Toward the end, there were a dozen-or-so minor changes and corrections that needed to be made throughout the code and test cases, so these were done by hand.  (Scripting them would have been too time consuming.)

So while this script doesn't do ALL of the rebranding, it does the majority of it and what it does is be repeatable (if that is every needed).

I will not upload a patch of the changes, because large number of directory renames would result in far too many + and - lines in the patch.  Therefore, I will just commit what I have.

Note, following this commit there are a number of open issues that need to be resolved before we release the rebranded.

> 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
>
>         Attachments: rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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  Thu Jan 14 04:26:00 2010
From: jira-events at lists.jboss.org (Vijay Kiran Duvvuri (JIRA))
Date: Thu, 14 Jan 2010 04:26:00 -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: <822414043.1263461160266.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 ]

Vijay Kiran Duvvuri updated DNA-580:
------------------------------------

    Attachment: gettingstarted-rebranding.patch


Getting started Rebranding

Images and Links still need to be checked. Version is also updated to 1.0.0.Beta1

> 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
>
>         Attachments: gettingstarted-rebranding.patch, rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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  Thu Jan 14 15:48:38 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 14 Jan 2010 15:48:38 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-580) Rebrand project to
	new name
In-Reply-To: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1240740001.1263502118968.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-580:
-----------------------------------

Rebranded all of the codebase, changing from 'JBoss DNA' to 'ModeShape', per the procedure described above. The rebranding is not yet complete with this commit, but at this point all modules have been renamed, all package names have been adjusted, all references to 'DNA' (in the various forms) have been changed, and all of the unit tests and integration tests do pass. The remaining work involves fixing a small number of issues (one TCK failure that has been commented out that apparently was uncovered by the node type names and prefixes were changes) that still have to be fixed.  

Also, applied Vijay's two patches for the Getting Started and Reference Guide changes (with some modifications), and updated the images. The document versions say '1.0.0.Beta1' at the moment., and at this point they look pretty good.

Added svn:ignore properties to ignore 'target' directories, and removed the (now empty) directories for the modules named 'dna-*', as the content has already been moved into 'modeshape-*' modules.

This commit also sets the version in trunk to be 1.0.0-SNAPSHOT.

> 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
>
>         Attachments: gettingstarted-rebranding.patch, rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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  Thu Jan 14 15:54:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 14 Jan 2010 15:54:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-580) Rebrand project to
	new name
In-Reply-To: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <393417097.1263502470837.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-580:
-----------------------------------

So, of the 5 rebranding steps I listed earlier, these are DONE:

1) The JBoss DNA SVN has already been locked down, and no more changes can be made to it.
2) All of the history from the DNA SVN has already been loaded into the ModeShape SVN. Basically, it looks exactly like the DNA repository did right after the 0.7 release. But at the moment, it is locked down as well, pending the next step.
4) The projects/modules have been renamed, the packages and classes changed, and the documentation changed and figures updated.

Still to do:
3) Migrate all of the JIRA issues from DNA to MODE
5) Open up SVN

I actually would like to wait on #5 until we release ModeShape 1.0.0.Beta1 (in a day or two, actually). I think it is critical that the behavior of ModeShape 1.0.0.Beta1 be the same as JBoss DNA 0.7, so it is much easier for people to convert/migrate. Therefore, any changes to the codebase should be put into a patch and attached to this issue, and I will apply.


> 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
>
>         Attachments: gettingstarted-rebranding.patch, rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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  Thu Jan 14 15:54:30 2010
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 14 Jan 2010 15:54:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Work started: (DNA-580) Rebrand project
	to new name
In-Reply-To: <1705168978.1260291869717.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <470366112.1263502470922.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 ]

Work on DNA-580 started by Randall Hauch.

> 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
>
>         Attachments: gettingstarted-rebranding.patch, rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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  Thu Jan 14 23:01:35 2010
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Thu, 14 Jan 2010 23:01:35 -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: <2063999674.1263528095393.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 ]

Brian Carothers updated DNA-580:
--------------------------------

    Attachment: DNA-580_namespaces.patch


Attached patch that corrects namespaces from dna: and dnatest: to mode: and mode:test.  Also changes a few test classes from Dna* to ModeShape* and changes the default JAAS realm from dna-jcr to modeshape-jcr.

All integration tests pass from the command line, although the JDBC metadata connector test is no longer loading its custom node types when I run it from Eclipse.

> 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
>
>         Attachments: DNA-580_namespaces.patch, gettingstarted-rebranding.patch, rebrand-dna.sh, refguide-rebranding.patch
>
>
> 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

        

