From jira-events at lists.jboss.org  Thu Nov  5 10:36:06 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 5 Nov 2009 10:36:06 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-456) Add JSR-170
 Observation Optional Feature
In-Reply-To: <29781241.1244747516423.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <69026838.1257435366835.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

Below are the TCK tests that are failing using my (not currently checked-in) implementation of the ObservationManager and why I think they are failing.

One design note: I had to implement a check that makes sure Changes with a timestamp before the time a listener was registered do not get delivered to that listener. This was a problem because the events were created and the listener was being registered in one thread and the event notification was being handled in a different thread.

I will write Jiras for (1) requests don't differentiate between setting a new property or changing an existing property, and (2) Changes need to include a session identifier so that the ObservationManager can handle the "noLocal" flag.

=====================

LockingTest
        testAddLockToNode - no PROPERTY_ADDED events received
        testRemoveLockFromNode - no PROPERTY_REMOVED events received
        
NodeRemovedTest
        testMultiNodesRemoved - no NODE_REMOVED event for child nodes when a parent is removed
        
NodeMovedTest
        testMoveWithRemove - fails with NPE (originalParent) in GraphSession.containsChangesWithExternalDependencies()
        
NodeReorderTest
        testNodeReorder - no events received (need to research what happens when node.orderBefore(sourcePath, destinationPath) is called)
        
PropertyAddedTest
        testSinglePropertyAdded - no events received since PROPERTY_ADDED changes are implemented as PROPERTY_CHANGED events
        testMultiPropertyAdded - no events received since PROPERTY_ADDED changes are implemented as PROPERTY_CHANGED events
        
PropertyChangedTest
        testSinglePropertyChangedWithAdded - too many events as PROPERTY_ADDED changes are being broadcast as PROPERTY_CHANGED events        
AddEventListenerTest
        testNodeType - path is /testroot/node2/node3 but should be /testroot/node1/node3 (need to research this one)
        testPath - should not have path /testroot/node1 (so does isDeep mean not to include parent path?)
        testIsDeepFalseNodeAdded - path is /testroot/node1 and should be /testroot/node1/node2 (expected test results seems wrong??)
        testIsDeepFalsePropertyAdded - no events since PROPERTY_ADDED changes are sent as PROPERTY_CHANGED events
        testNoLocalTrue - still have to implement "noLocal" check in ObservationManager
        testUUID - no events received since no PROPERTY_ADDED changes are implemented as PROPERTY_CHANGED events
        
WorkspaceOperationTest
        testCopy - no NODE_ADDED event generated for child node of copied parent node

> Add JSR-170 Observation Optional Feature
> ----------------------------------------
>
>                 Key: DNA-456
>                 URL: https://jira.jboss.org/jira/browse/DNA-456
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> JSR-170 defines several optional features.  The observation feature would provide notification of node and property changes to registered listeners.

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

        

From jira-events at lists.jboss.org  Thu Nov  5 10:56:05 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 5 Nov 2009 10:56:05 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-548) The Session That Graph
 Changes Originate From Should Be Available To The NetChangeObserver
Message-ID: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
------------------------------------------------------------------------------------------

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


There is no way for the ObservationManager to obtain the session from the NetChanges/Changes/ChangeRequest objects. The session identifier is needed to implement the event notification of the ObservationManager. Specifically, listeners are registered with a "noLocal" flag indicating if they want or don't want to receive events from the session that they are registered in.

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

        

From jira-events at lists.jboss.org  Thu Nov  5 11:11:05 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Thu, 5 Nov 2009 11:11:05 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-549) Creating A New
 Property And Changing An Existing Property Should Have Different
 ChangeRequest Types
Message-ID: <1946803342.1257437465795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

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
             Fix For: 0.7


There is no way to differentiate between when a new property is created and when an existing property is set. Both are handled using the SetPropertyRequest. The JCR spec clearly states the difference between these two cases as each one has their own event type.

Work to change to the relevant change requests, update connectors, and update the NetChangeObserver will need to be done.

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

        

From jira-events at lists.jboss.org  Mon Nov  9 12:06:05 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 9 Nov 2009 12:06:05 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-550) Add method to Graph to
 read a set of properties on multiple nodes
Message-ID: <1947989541.1257786365789.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Add method to Graph to read a set of properties on multiple nodes
-----------------------------------------------------------------

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


The JCR observation manager implementation needs to be able to read the primary type and mixins of many nodes, yet there's no efficient way to do this in Graph (or Graph.Batch).  The simplest case is to add a method to Graph that would take a set of property names and multiple Location objects, execute the requests as a single composite request, and return the read Property objects for each of the supplied Location objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 13 15:29:19 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Fri, 13 Nov 2009 15:29:19 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
Message-ID: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
-------------------------------------------------------------------------

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


Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.

It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 16 09:20:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 16 Nov 2009 09:20:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-552) Support BETWEEN and
 NOT BETWEEN in WHERE clause of SQL language and abstract query model
Message-ID: <454589555.1258381229697.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Support BETWEEN and NOT BETWEEN in WHERE clause of SQL language and abstract query model
----------------------------------------------------------------------------------------

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


Our search/query implementation will perform much better when it can detect a range of values in a criteria.  Currently, ranges can only be specified using the form "WHERE ... <dynamicOperand> <operator1> <staticOperand1> ... AND <dynamicOperand> <operator2> <staticOperand2> ..."  For example: 

    WHERE ... DEPTH(myType) >= 3 AND DEPTH(myType) <=6

SQL already has a BETWEEN operator (and corresponding NOT BETWEEN operator) that makes this not only more concise but also more easily understandable and obvious about the intent:

    WHERE ... DEPTH(myType) BETWEEN 3 and 6

This concept would also have to be added to the abstract query model, and in particular as a subclass of Constraint that has a DynamicOperand and two StaticOperand values.  And by adding this specialization of Constraint, we can add an optimizer rule that looks for ANDed constraints that represent a range on a DynamicOperand, and rewrite the constraints as a BETWEEN (or NOT BETWEEN).  

Note that a NOT BETWEEN would simply wrap a BetweenCriteria with a Not.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 16 09:22:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 16 Nov 2009 09:22:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-552) Support BETWEEN and
 NOT BETWEEN in WHERE clause of SQL language and abstract query model
In-Reply-To: <454589555.1258381229697.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1465624876.1258381349629.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-552:
------------------------------

    Component/s: Query
                 Search


> Support BETWEEN and NOT BETWEEN in WHERE clause of SQL language and abstract query model
> ----------------------------------------------------------------------------------------
>
>                 Key: DNA-552
>                 URL: https://jira.jboss.org/jira/browse/DNA-552
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, Query, Search
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Our search/query implementation will perform much better when it can detect a range of values in a criteria.  Currently, ranges can only be specified using the form "WHERE ... <dynamicOperand> <operator1> <staticOperand1> ... AND <dynamicOperand> <operator2> <staticOperand2> ..."  For example: 
>     WHERE ... DEPTH(myType) >= 3 AND DEPTH(myType) <=6
> SQL already has a BETWEEN operator (and corresponding NOT BETWEEN operator) that makes this not only more concise but also more easily understandable and obvious about the intent:
>     WHERE ... DEPTH(myType) BETWEEN 3 and 6
> This concept would also have to be added to the abstract query model, and in particular as a subclass of Constraint that has a DynamicOperand and two StaticOperand values.  And by adding this specialization of Constraint, we can add an optimizer rule that looks for ANDed constraints that represent a range on a DynamicOperand, and rewrite the constraints as a BETWEEN (or NOT BETWEEN).  
> Note that a NOT BETWEEN would simply wrap a BetweenCriteria with a Not.

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


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

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

    Component/s: JCR
                 Query
                 Search
                     (was: Connectors)
                     (was: Graph)
                     (was: API)


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

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

        

From jira-events at lists.jboss.org  Mon Nov 16 09:24:41 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 16 Nov 2009 09:24:41 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-468) Add XPath query
	language support
In-Reply-To: <19863639.1245358556324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <562355355.1258381481298.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-468:
------------------------------

    Component/s: Query
                 Search
                     (was: Graph)
                     (was: API)


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

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

        

From jira-events at lists.jboss.org  Tue Nov 17 08:33:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 08:33:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-553) File system connector
 should make it possible to extend/customize the properties on the nt:folder,
 nt:file, and nt:resource nodes
Message-ID: <1444934192.1258464809571.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

File system connector should make it possible to extend/customize the properties on the nt:folder, nt:file, and nt:resource nodes
---------------------------------------------------------------------------------------------------------------------------------

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


Using the JCR API to access files is a common use case for the  file system connector and our JCR implementation.  See the referenced forum thread.  

However, there are times when additional properties from the files (e.g., properties of PDF or MS Office files) are to be loaded onto the nt:folder, nt:file, and nt:resource nodes.  The current implementation makes this much more difficult to achieve than it should be, since it requires creating a whole new connector and subclassing most of the classes in the existing file system connector.

The existing classes should be changed so that it is far easier to add custom logic.  This change should be quite straightforward.

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

        

From jira-events at lists.jboss.org  Tue Nov 17 08:33:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 08:33:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-553) File system connector
 should make it possible to extend/customize the properties on the nt:folder,
 nt:file, and nt:resource nodes
In-Reply-To: <1444934192.1258464809571.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <312315449.1258464809591.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-553:
------------------------------

    Component/s: Connectors


> File system connector should make it possible to extend/customize the properties on the nt:folder, nt:file, and nt:resource nodes
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-553
>                 URL: https://jira.jboss.org/jira/browse/DNA-553
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Using the JCR API to access files is a common use case for the  file system connector and our JCR implementation.  See the referenced forum thread.  
> However, there are times when additional properties from the files (e.g., properties of PDF or MS Office files) are to be loaded onto the nt:folder, nt:file, and nt:resource nodes.  The current implementation makes this much more difficult to achieve than it should be, since it requires creating a whole new connector and subclassing most of the classes in the existing file system connector.
> The existing classes should be changed so that it is far easier to add custom logic.  This change should be quite straightforward.

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

        

From jira-events at lists.jboss.org  Tue Nov 17 13:47:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 13:47:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-552) Support BETWEEN and
 NOT BETWEEN in WHERE clause of SQL language and abstract query model
In-Reply-To: <454589555.1258381229697.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1768248648.1258483649615.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-552:
-----------------------------------

The abstract query model now has a new Constraint subclass called Between that has a DynamicOperand, a StaticOperand lower boundary, a StaticOperand upper boundary, and a flag for each boundary that specifies whether the boundary is included or excluded in the range.  This very capably handles all kinds of continuous ranges.

The dna-searc project was enhanced to support this new Constraint type for numeric values (long, double, decimal, and date).

The SQL language parser now handles the '<dynamicOperand> BETWEEN <staticOperandLowerBound> [EXCLUSIVE] AND <staticOperandUpperBound> [EXCLUSIVE]'.

Additionally, a query optimizer rule was created to look for pairs of Comparison constraints that can be merged or rewritten:
- two range constraints are replaced with a single Between constraint (e.g., 'table.column' >=4 and table.column <=10' replaced with 'table.column BETWEEN 4 AND 10', with the exclusive flags set properly)
- two range constraints that specify a range of a single value are replaced with a single equality constraint (e.g., 'table.column >=4 AND table.column <= 4' replaced with 'table.column = 4')
- unnecessary Comparison constraints are removed (e.g., given 'table.column < 4 AND table.column < 10' the latter constraint is removed)
- conflicting constraints that will never be satisfied (e.g., 'table.column < 4 AND table.column > 10), marking the ACCESS node as having no results (this is handled in the query processor)

The QueryProcessor was also changed to look for an ACCESS node with the (new) ACCESS_NO_RESULTS property, and to create a NoResultsComponent rather than a real access component.  This will work in that an access query will never be made when we know the range constraints are invalid, but it does not look for other always-false constraints nor does it optimize the plan.  (A RemoveEmptyAccessNodes optimizer plan was created, though it basically is a no-op at the moment.)


> Support BETWEEN and NOT BETWEEN in WHERE clause of SQL language and abstract query model
> ----------------------------------------------------------------------------------------
>
>                 Key: DNA-552
>                 URL: https://jira.jboss.org/jira/browse/DNA-552
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, Query, Search
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Our search/query implementation will perform much better when it can detect a range of values in a criteria.  Currently, ranges can only be specified using the form "WHERE ... <dynamicOperand> <operator1> <staticOperand1> ... AND <dynamicOperand> <operator2> <staticOperand2> ..."  For example: 
>     WHERE ... DEPTH(myType) >= 3 AND DEPTH(myType) <=6
> SQL already has a BETWEEN operator (and corresponding NOT BETWEEN operator) that makes this not only more concise but also more easily understandable and obvious about the intent:
>     WHERE ... DEPTH(myType) BETWEEN 3 and 6
> This concept would also have to be added to the abstract query model, and in particular as a subclass of Constraint that has a DynamicOperand and two StaticOperand values.  And by adding this specialization of Constraint, we can add an optimizer rule that looks for ANDed constraints that represent a range on a DynamicOperand, and rewrite the constraints as a BETWEEN (or NOT BETWEEN).  
> Note that a NOT BETWEEN would simply wrap a BetweenCriteria with a Not.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 17 13:47:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 13:47:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-552) Support BETWEEN and
 NOT BETWEEN in WHERE clause of SQL language and abstract query model
In-Reply-To: <454589555.1258381229697.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1522425588.1258483649658.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-552.
-------------------------------

    Resolution: Done


Marking this issue as resolved.  Further enhancements or improvements should be tracked under new issues.

> Support BETWEEN and NOT BETWEEN in WHERE clause of SQL language and abstract query model
> ----------------------------------------------------------------------------------------
>
>                 Key: DNA-552
>                 URL: https://jira.jboss.org/jira/browse/DNA-552
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph, Query, Search
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Our search/query implementation will perform much better when it can detect a range of values in a criteria.  Currently, ranges can only be specified using the form "WHERE ... <dynamicOperand> <operator1> <staticOperand1> ... AND <dynamicOperand> <operator2> <staticOperand2> ..."  For example: 
>     WHERE ... DEPTH(myType) >= 3 AND DEPTH(myType) <=6
> SQL already has a BETWEEN operator (and corresponding NOT BETWEEN operator) that makes this not only more concise but also more easily understandable and obvious about the intent:
>     WHERE ... DEPTH(myType) BETWEEN 3 and 6
> This concept would also have to be added to the abstract query model, and in particular as a subclass of Constraint that has a DynamicOperand and two StaticOperand values.  And by adding this specialization of Constraint, we can add an optimizer rule that looks for ANDed constraints that represent a range on a DynamicOperand, and rewrite the constraints as a BETWEEN (or NOT BETWEEN).  
> Note that a NOT BETWEEN would simply wrap a BetweenCriteria with a Not.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 17 16:08:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 16:08:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-553) File system
 connector should make it possible to extend/customize the properties on the
 nt:folder, nt:file, and nt:resource nodes
In-Reply-To: <1444934192.1258464809571.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1552845560.1258492111022.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-553:
-----------------------------------

Enhanced the file system connector so that it is much easier to define how non-standard properties can be made to appear on nt:folder, nt:file, and nt:resource nodes.  By default, the file system connector behaves as it has in the past: it only uses the standard properties defined by JCR for files, folders and content nodes.

There is a new CustomPropertiesFactory interface that defines several methods for getting and setting custom properties.  Simply implement this interface, and call FileSystemSource.setCustomPropertiesFactory(...) with an instance of your implementation.  (Or, optionally subclass FileSystemSource, set the factory in the subclass' constructor, and inherit all other functionality).

The connector uses this factory whenever it reads "nt:folder", "nt:file", or "nt:resource" nodes, and includes in these nodes the properties returned by the factory. The factory methods take several arguments, including the ExecutionContext (which can be used to obtain the PropertyFactory, value factories used to create property values, and even the MIME type detector), the java.io.File object, the Location (which includes the path), and other information.  Hopefully this is sufficient to construct the necessary custom properties.


> File system connector should make it possible to extend/customize the properties on the nt:folder, nt:file, and nt:resource nodes
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-553
>                 URL: https://jira.jboss.org/jira/browse/DNA-553
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Using the JCR API to access files is a common use case for the  file system connector and our JCR implementation.  See the referenced forum thread.  
> However, there are times when additional properties from the files (e.g., properties of PDF or MS Office files) are to be loaded onto the nt:folder, nt:file, and nt:resource nodes.  The current implementation makes this much more difficult to achieve than it should be, since it requires creating a whole new connector and subclassing most of the classes in the existing file system connector.
> The existing classes should be changed so that it is far easier to add custom logic.  This change should be quite straightforward.

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

        

From jira-events at lists.jboss.org  Tue Nov 17 16:25:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 16:25:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-553) File system connector
 should make it possible to extend/customize the properties on the nt:folder,
 nt:file, and nt:resource nodes
In-Reply-To: <1444934192.1258464809571.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1546656744.1258493129566.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-553.
-------------------------------

    Resolution: Done


I'll mark this issue as resolved, since I think it will make it much easier to handle custom properties like the use case mentioned on the forum.  If changes need to be made, we can reopen this issue.

> File system connector should make it possible to extend/customize the properties on the nt:folder, nt:file, and nt:resource nodes
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-553
>                 URL: https://jira.jboss.org/jira/browse/DNA-553
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Using the JCR API to access files is a common use case for the  file system connector and our JCR implementation.  See the referenced forum thread.  
> However, there are times when additional properties from the files (e.g., properties of PDF or MS Office files) are to be loaded onto the nt:folder, nt:file, and nt:resource nodes.  The current implementation makes this much more difficult to achieve than it should be, since it requires creating a whole new connector and subclassing most of the classes in the existing file system connector.
> The existing classes should be changed so that it is far easier to add custom logic.  This change should be quite straightforward.

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

        

From jira-events at lists.jboss.org  Tue Nov 17 16:29:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 17 Nov 2009 16:29:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-467) Add search/query
 support to the graph API
In-Reply-To: <27219418.1245358316391.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1517410888.1258493369561.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

Changed how the Queryable and QueryEngine use Schemata. Before, the schemata instance was passed into the engine, and used for all queries. But this meant that the schemata instance could change the Table objects it returns.  This would be more difficult to implement than if a different Schemata were passed with each query, since that Schemata instance can be a reflection of the tables at the time the query is implemented.  And, Schemata can then be made to be immutable, not only simplifying the implementation but also ensuring that the schema information doesn't change during the processing of a query.

Continued implementation of the dna-search components.  Current status is that the SearchEngine is nearly complete (feature-wise), but has had little testing.

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

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

        

From jira-events at lists.jboss.org  Mon Nov 23 10:52:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 10:52:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-550) Add method to Graph
 to read a set of properties on multiple nodes
In-Reply-To: <1947989541.1257786365789.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <469234584.1258991549782.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-550.
-------------------------------

    Resolution: Done


Added methods to Graph to allow reading of one or more properties on multiple nodes, all in a single operation

> Add method to Graph to read a set of properties on multiple nodes
> -----------------------------------------------------------------
>
>                 Key: DNA-550
>                 URL: https://jira.jboss.org/jira/browse/DNA-550
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The JCR observation manager implementation needs to be able to read the primary type and mixins of many nodes, yet there's no efficient way to do this in Graph (or Graph.Batch).  The simplest case is to add a method to Graph that would take a set of property names and multiple Location objects, execute the requests as a single composite request, and return the read Property objects for each of the supplied Location objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 10:56:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 10:56:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <7584180.1258991789527.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-551:
------------------------------

    Priority: Blocker  (was: Major)


> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 15:40:34 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 15:40:34 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-554) GraphSession does not
 correctly compute whether changes are in branch being saved or refreshed
Message-ID: <287401066.1259008834999.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

GraphSession does not correctly compute whether changes are in branch being saved or refreshed
----------------------------------------------------------------------------------------------

                 Key: DNA-554
                 URL: https://jira.jboss.org/jira/browse/DNA-554
             Project: DNA
          Issue Type: Bug
          Components: Graph
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Randall Hauch
             Fix For: 0.7


The GraphSession.Node.containsChangesWithExternalDependencies() does not work correctly because it returns a boolean value that is opposite to what the documentation describes. It should be reversed so that the documentation (and logic) are correct.

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

        

From jira-events at lists.jboss.org  Mon Nov 23 15:42:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 15:42:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-554) GraphSession does not
 correctly compute whether changes are in branch being saved or refreshed
In-Reply-To: <287401066.1259008834999.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1900482043.1259008950472.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-554.
-------------------------------

    Resolution: Done


Corrected the code so that it matches the documentation.  Also addressed the potential for a null pointer exception when the old parent of a node has been removed (because it was removed within the same session).

> GraphSession does not correctly compute whether changes are in branch being saved or refreshed
> ----------------------------------------------------------------------------------------------
>
>                 Key: DNA-554
>                 URL: https://jira.jboss.org/jira/browse/DNA-554
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> The GraphSession.Node.containsChangesWithExternalDependencies() does not work correctly because it returns a boolean value that is opposite to what the documentation describes. It should be reversed so that the documentation (and logic) are correct.

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

        

From jira-events at lists.jboss.org  Mon Nov 23 16:33:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Mon, 23 Nov 2009 16:33:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
Message-ID: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Requirement for extracting indexed content during parsing using TokenStream
---------------------------------------------------------------------------

                 Key: DNA-555
                 URL: https://jira.jboss.org/jira/browse/DNA-555
             Project: DNA
          Issue Type: Bug
          Components: Common, Graph
            Reporter: Barry LaFond


Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)

So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.

Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 16:35:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Mon, 23 Nov 2009 16:35:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1248947545.1259012129601.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-555:
-----------------------------

    Attachment: dna.patch


Patch containing code changes to Position, TokenStream, SqlParser, Commoni18n and associated test classes.

> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>            Reporter: Barry LaFond
>         Attachments: dna.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

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

Need a graph-specific SequencerOutput class to simplify testing sequencer results.
----------------------------------------------------------------------------------

                 Key: DNA-556
                 URL: https://jira.jboss.org/jira/browse/DNA-556
             Project: DNA
          Issue Type: Bug
          Components: Graph
            Reporter: Barry LaFond


While developing the test for the DdlSequencer, it would be beneficial to create a simplified graph oriented SequencerOutput class that provided 1) simple setProperty() and setReference() methods and performed a batched request.

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

        

From jira-events at lists.jboss.org  Mon Nov 23 18:06:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 18:06:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1285668532.1259017589590.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-555:
-----------------------------------

Patch looks pretty good, though I have a few minor nits:

1) The JavaDoc for TokenStream.nextPosition() was changed from "@throws NoSuchElementException if there is no next token" to "@throws NoSuchElementException if there is no previous token" - was this a copy/paste error?
2) The patch is adding the '.project' file under the 'target' directory, which is incorrect.  Make sure that does not get added.

> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>            Reporter: Barry LaFond
>         Attachments: dna.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 18:26:34 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 18:26:34 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-557) Upgrade RESTEasy from
 1.1.GA to 1.2.GA
Message-ID: <1552145973.1259018794887.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Upgrade RESTEasy from 1.1.GA to 1.2.GA
--------------------------------------

                 Key: DNA-557
                 URL: https://jira.jboss.org/jira/browse/DNA-557
             Project: DNA
          Issue Type: Thirdparty Change
          Components: Web Application
    Affects Versions: 0.6
            Reporter: Randall Hauch
            Assignee: Randall Hauch
            Priority: Blocker
             Fix For: 0.7


The 1.2.GA version of RESTEasy is now available, and this fixes some of the issues with the Maven dependency resolution.  Several of the dependencies (like Jettison and FastInfoset) have been removed, saving some unnecessary dependencies when not needed.  However, it does requires some changes to be made to the POM file in the 'dna-web-jcr-rest' project.  (For details, see http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.2.GA/userguide/html_single/index.html#Migration_from_older_versions).

Since 1.1.GA depended upon FastInfoset (which is not available in the JBoss Maven repository), our builds started failing recently.  This change will hopefully get around those issues, since we have no use/need for FastInfoset.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 18:28:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 18:28:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <598922961.1259018909581.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-555:
-----------------------------------

Not sure if I was clear, but correct the patch to not add the .project file, and it's fine to commit.

> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>            Reporter: Barry LaFond
>         Attachments: dna.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 18:39:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 18:39:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-557) Upgrade RESTEasy
 from 1.1.GA to 1.2.GA
In-Reply-To: <1552145973.1259018794887.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <469840818.1259019569615.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-557:
-----------------------------------

Upgraded the RESTEasy library to 1.2.GA, but still getting Hudson build errors related to RESTEasy dependencies:

[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss DNA JCR REST Library
[INFO]    task-segment: [clean, package]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /qa/local/hudson_workspace/workspace/DNA continuous on JDK1.5/trunk/web/dna-web-jcr-rest/target
[INFO] [resources:resources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /qa/local/hudson_workspace/workspace/DNA continuous on JDK1.5/trunk/web/dna-web-jcr-rest/src/main/resources
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jaxrs/1.2.GA/resteasy-jaxrs-1.2.GA.pom
3K downloaded
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jaxrs-all/1.2.GA/resteasy-jaxrs-all-1.2.GA.pom
18K downloaded
[WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for org/jboss/resteasy/resteasy-jaxrs-all/1.2.GA/resteasy-jaxrs-all-1.2.GA.pom - IGNORING
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/jaxrs-api/1.2.GA/jaxrs-api-1.2.GA.pom
882b downloaded
Downloading: http://repository.jboss.org/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://repository.exadel.com/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://download.java.net/maven/2//org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://repository.jboss.com/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://snapshots.jboss.org/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://jakarta.apache.org/commons/httpclient//org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: https://maven-repository.dev.java.net/nonav/repository/org.apache.httpcomponents/poms/httpclient-4.0.pom
370b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'ba3db41f985feef4b6190cb9b50e07ff7d4b5404'; remote = '<!DOCTYPE' - RETRYING
Downloading: https://maven-repository.dev.java.net/nonav/repository/org.apache.httpcomponents/poms/httpclient-4.0.pom
370b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'ba3db41f985feef4b6190cb9b50e07ff7d4b5404'; remote = '<!DOCTYPE' - IGNORING
[WARNING] POM for 'org.apache.httpcomponents:httpclient:pom:4.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.httpcomponents:httpclient at /home/hudson/.m2/repository/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
[WARNING] POM for 'org.apache.httpcomponents:httpclient:pom:4.0:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project org.apache.httpcomponents:httpclient at /home/hudson/.m2/repository/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.pom
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jaxb-provider/1.2.GA/resteasy-jaxb-provider-1.2.GA.pom
1K downloaded
Downloading: http://repository.jboss.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: http://repository.exadel.com/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: http://download.java.net/maven/2//com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: http://repository.jboss.com/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: http://snapshots.jboss.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: http://jakarta.apache.org/commons/httpclient//com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
Downloading: https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/poms/jaxb-impl-2.1.10.pom
363b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '9475634cb83204bae95409a911e5be46b82aea6d'; remote = '<!DOCTYPE' - RETRYING
Downloading: https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/poms/jaxb-impl-2.1.10.pom
363b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '9475634cb83204bae95409a911e5be46b82aea6d'; remote = '<!DOCTYPE' - IGNORING
[WARNING] POM for 'com.sun.xml.bind:jaxb-impl:pom:2.1.10:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project com.sun.xml.bind:jaxb-impl at /home/hudson/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
[WARNING] POM for 'com.sun.xml.bind:jaxb-impl:pom:2.1.10:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project com.sun.xml.bind:jaxb-impl at /home/hudson/.m2/repository/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.pom
[WARNING] POM for 'com.sun.xml.stream:sjsxp:pom:1.0.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project com.sun.xml.stream:sjsxp at /home/hudson/.m2/repository/com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.pom
[WARNING] POM for 'com.sun.xml.stream:sjsxp:pom:1.0.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM. for project com.sun.xml.stream:sjsxp at /home/hudson/.m2/repository/com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.pom
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jettison-provider/1.2.GA/resteasy-jettison-provider-1.2.GA.pom
2K downloaded
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jaxrs/1.2.GA/resteasy-jaxrs-1.2.GA.jar
452K downloaded
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/jaxrs-api/1.2.GA/jaxrs-api-1.2.GA.jar
42K downloaded
Downloading: http://repository.jboss.org/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: http://repository.exadel.com/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: http://download.java.net/maven/2//org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: http://repository.jboss.com/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: http://snapshots.jboss.org/maven2/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: http://jakarta.apache.org/commons/httpclient//org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar
Downloading: https://maven-repository.dev.java.net/nonav/repository/org.apache.httpcomponents/jars/httpclient-4.0.jar
370b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '0dc1467b24851fb8d6ef34cb91ef2436be64070a'; remote = '<!DOCTYPE' - RETRYING
Downloading: https://maven-repository.dev.java.net/nonav/repository/org.apache.httpcomponents/jars/httpclient-4.0.jar
370b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '0dc1467b24851fb8d6ef34cb91ef2436be64070a'; remote = '<!DOCTYPE' - IGNORING
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jaxb-provider/1.2.GA/resteasy-jaxb-provider-1.2.GA.jar
56K downloaded
Downloading: http://repository.jboss.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: http://repository.exadel.com/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: http://download.java.net/maven/2//com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: http://repository.jboss.com/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: http://snapshots.jboss.org/maven2/com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: http://jakarta.apache.org/commons/httpclient//com/sun/xml/bind/jaxb-impl/2.1.10/jaxb-impl-2.1.10.jar
Downloading: https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/jars/jaxb-impl-2.1.10.jar
363b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'cdeb7bda64fcfb261f968545ba6740ad68b8e18f'; remote = '<!DOCTYPE' - RETRYING
Downloading: https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.bind/jars/jaxb-impl-2.1.10.jar
363b downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'cdeb7bda64fcfb261f968545ba6740ad68b8e18f'; remote = '<!DOCTYPE' - IGNORING
Downloading: http://repository.jboss.org/maven2/org/jboss/resteasy/resteasy-jettison-provider/1.2.GA/resteasy-jettison-provider-1.2.GA.jar
28K downloaded
[INFO] [compiler:compile]
[INFO] Compiling 14 source files to /qa/local/hudson_workspace/workspace/DNA continuous on JDK1.5/trunk/web/dna-web-jcr-rest/target/classes
[HUDSON] Archiving /qa/local/hudson_workspace/workspace/DNA continuous on JDK1.5/trunk/web/dna-web-jcr-rest/pom.xml to /home/hudson/hudson_workspace/jobs/DNA continuous on JDK1.5/modules/org.jboss.dna$dna-web-jcr-rest/builds/2009-11-23_18-31-48/archive/org.jboss.dna/dna-web-jcr-rest/0.7-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
error: error reading /home/hudson/.m2/repository/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar; error in opening zip file


error: error reading /home/hudson/.m2/repository/org/apache/httpcomponents/httpclient/4.0/httpclient-4.0.jar; error in opening zip file


> Upgrade RESTEasy from 1.1.GA to 1.2.GA
> --------------------------------------
>
>                 Key: DNA-557
>                 URL: https://jira.jboss.org/jira/browse/DNA-557
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Web Application
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 1.2.GA version of RESTEasy is now available, and this fixes some of the issues with the Maven dependency resolution.  Several of the dependencies (like Jettison and FastInfoset) have been removed, saving some unnecessary dependencies when not needed.  However, it does requires some changes to be made to the POM file in the 'dna-web-jcr-rest' project.  (For details, see http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.2.GA/userguide/html_single/index.html#Migration_from_older_versions).
> Since 1.1.GA depended upon FastInfoset (which is not available in the JBoss Maven repository), our builds started failing recently.  This change will hopefully get around those issues, since we have no use/need for FastInfoset.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 20:43:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 20:43:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1926738210.1259027009680.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-551:
------------------------------

    Attachment: DNA-551-patch1.txt


Attached a (still incomplete) patch that JPAV has been working on.  John says one test is still failing, and I haven't yet reviewed it.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 23 21:19:01 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 23 Nov 2009 21:19:01 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-557) Upgrade RESTEasy
 from 1.1.GA to 1.2.GA
In-Reply-To: <1552145973.1259018794887.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1750797956.1259029141156.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-557:
-----------------------------------

Changed to RESTEasy 1.2.1.GA (which was literally just released a few hours ago), and added back in the exclusion of the "com.sun.xml.bind/jaxb-impl" dependency from "resteasy-jaxb-provider" artifact. I was able to replicate the Hudson build problem by cleaning out my local Maven repository (in ~/.m2/repository), and these two changes appears to have fixed the problem for the "dna-web-jcr-rest" project (at least locally).  Similar changes were required for the "dna-web-jcr-rest-client" project.

Committing the change, and hopefully the Hudson build will also be successful.

> Upgrade RESTEasy from 1.1.GA to 1.2.GA
> --------------------------------------
>
>                 Key: DNA-557
>                 URL: https://jira.jboss.org/jira/browse/DNA-557
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Web Application
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 1.2.GA version of RESTEasy is now available, and this fixes some of the issues with the Maven dependency resolution.  Several of the dependencies (like Jettison and FastInfoset) have been removed, saving some unnecessary dependencies when not needed.  However, it does requires some changes to be made to the POM file in the 'dna-web-jcr-rest' project.  (For details, see http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.2.GA/userguide/html_single/index.html#Migration_from_older_versions).
> Since 1.1.GA depended upon FastInfoset (which is not available in the JBoss Maven repository), our builds started failing recently.  This change will hopefully get around those issues, since we have no use/need for FastInfoset.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 10:49:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 24 Nov 2009 10:49:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-557) Upgrade RESTEasy from
 1.1.GA to 1.2.1.GA
In-Reply-To: <1552145973.1259018794887.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1415448397.1259077769616.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-557:
------------------------------

    Summary: Upgrade RESTEasy from 1.1.GA to 1.2.1.GA  (was: Upgrade RESTEasy from 1.1.GA to 1.2.GA)


Updated the title to reflect the latest RESTEasy version.

> Upgrade RESTEasy from 1.1.GA to 1.2.1.GA
> ----------------------------------------
>
>                 Key: DNA-557
>                 URL: https://jira.jboss.org/jira/browse/DNA-557
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Web Application
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 1.2.GA version of RESTEasy is now available, and this fixes some of the issues with the Maven dependency resolution.  Several of the dependencies (like Jettison and FastInfoset) have been removed, saving some unnecessary dependencies when not needed.  However, it does requires some changes to be made to the POM file in the 'dna-web-jcr-rest' project.  (For details, see http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.2.GA/userguide/html_single/index.html#Migration_from_older_versions).
> Since 1.1.GA depended upon FastInfoset (which is not available in the JBoss Maven repository), our builds started failing recently.  This change will hopefully get around those issues, since we have no use/need for FastInfoset.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 10:51:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 24 Nov 2009 10:51:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-557) Upgrade RESTEasy from
 1.1.GA to 1.2.1.GA
In-Reply-To: <1552145973.1259018794887.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1518542785.1259077889912.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-557.
-------------------------------

    Resolution: Done


Hudson finally worked, after the ~/.m2/repository/com/sun/xml cached artifacts were removed from the build machine and the build could rerun.

> Upgrade RESTEasy from 1.1.GA to 1.2.1.GA
> ----------------------------------------
>
>                 Key: DNA-557
>                 URL: https://jira.jboss.org/jira/browse/DNA-557
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Web Application
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 1.2.GA version of RESTEasy is now available, and this fixes some of the issues with the Maven dependency resolution.  Several of the dependencies (like Jettison and FastInfoset) have been removed, saving some unnecessary dependencies when not needed.  However, it does requires some changes to be made to the POM file in the 'dna-web-jcr-rest' project.  (For details, see http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.2.GA/userguide/html_single/index.html#Migration_from_older_versions).
> Since 1.1.GA depended upon FastInfoset (which is not available in the JBoss Maven repository), our builds started failing recently.  This change will hopefully get around those issues, since we have no use/need for FastInfoset.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 15:45:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 24 Nov 2009 15:45:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2003582155.1259095529948.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-555:
-----------------------------

    Attachment:     (was: dna.patch)


> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>            Reporter: Barry LaFond
>         Attachments: dna_555.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 15:45:30 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Tue, 24 Nov 2009 15:45:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1862848209.1259095530004.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Barry LaFond updated DNA-555:
-----------------------------

    Attachment: dna_555.patch


contains patches to dna-common, dna-graph, dna-jcr, dna-cnd

> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>            Reporter: Barry LaFond
>         Attachments: dna_555.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 16:34:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 24 Nov 2009 16:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <758702637.1259098469557.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-555:
------------------------------

        Fix Version/s: 0.7
    Affects Version/s: 0.6
             Assignee: Barry LaFond
           Complexity: Low


> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>         Attachments: dna_555.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 16:34:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 24 Nov 2009 16:34:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-555) Requirement for
 extracting indexed content during parsing using TokenStream
In-Reply-To: <376443116.1259012009583.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <284085936.1259098469594.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-555.
-------------------------------

    Resolution: Done


Per Barry: Marking as resolved, since the patch fixed the issue.

> Requirement for extracting indexed content during parsing using TokenStream
> ---------------------------------------------------------------------------
>
>                 Key: DNA-555
>                 URL: https://jira.jboss.org/jira/browse/DNA-555
>             Project: DNA
>          Issue Type: Bug
>          Components: Common, Graph
>    Affects Versions: 0.6
>            Reporter: Barry LaFond
>            Assignee: Barry LaFond
>             Fix For: 0.7
>
>         Attachments: dna_555.patch
>
>
> Complex DDL parsing requires additional Position information (Index In Content) as well as ability to extract designated segments of the token stream (original file character string)
> So...  a Position.getIndexInContent() method as well as appropriate constructor mods to handle an integer index variable.
> Also need a TokenStream.getContentBetween(position1, position2) to access the string segment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 17:10:29 2009
From: jira-events at lists.jboss.org (Tom Ruff (JIRA))
Date: Tue, 24 Nov 2009 17:10:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-558) DNA documentation
	problem
Message-ID: <1404112840.1259100629627.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

DNA documentation problem
-------------------------

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


This applies to the DNA Reference Guide at the following link:
http://docs.jboss.org/jbossdna/latest/manuals/reference/html/sequencing_framework.html#stream-sequencers

In chapter 7.2, Stream Sequencers, the following sentence left out a key word ("context").  
So this:
"The provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "

Should be this:
"The context provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "

Also, immediately above that in the code block the type for the context parameter isn't provided - with javadoc hyperlink - as it is for the other two parameters.  Yes, I know this should probably be a separate issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 24 17:14:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Tue, 24 Nov 2009 17:14:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-558) DNA documentation
	problem
In-Reply-To: <1404112840.1259100629627.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <133614247.1259100869589.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-558:
------------------------------

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


It's fine to have this issue deal with both issues.  Marking priority as 'critical' so that we're sure to fix.

> DNA documentation problem
> -------------------------
>
>                 Key: DNA-558
>                 URL: https://jira.jboss.org/jira/browse/DNA-558
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Tom Ruff
>            Priority: Critical
>             Fix For: 0.7
>
>
> This applies to the DNA Reference Guide at the following link:
> http://docs.jboss.org/jbossdna/latest/manuals/reference/html/sequencing_framework.html#stream-sequencers
> In chapter 7.2, Stream Sequencers, the following sentence left out a key word ("context").  
> So this:
> "The provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Should be this:
> "The context provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Also, immediately above that in the code block the type for the context parameter isn't provided - with javadoc hyperlink - as it is for the other two parameters.  Yes, I know this should probably be a separate issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 07:41:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 07:41:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-542) jcr:uuid Property in
 dna:lock Custom Type Needs To Be Renamed
In-Reply-To: <914862714.1256258585622.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1712895233.1259152889710.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-542.
---------------------------------

    Resolution: Done


I accidentally committed the fix for this when I committed the fix for DNA-518.  The old jcr:uuid and dna:lockedNode properties on the dna:lock node type were combined into a dna:lockedUuid property.  This "frees up" the jcr:uuid property so that nodes can have the dna:lock primary type and the mix:referenceable mixin type if this becomes useful in the future.

> jcr:uuid Property in dna:lock Custom Type Needs To Be Renamed
> -------------------------------------------------------------
>
>                 Key: DNA-542
>                 URL: https://jira.jboss.org/jira/browse/DNA-542
>             Project: DNA
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>
> The dna:lock custom node type (used to store information about an active lock) reuses the jcr:uuid and jcr:lockOwner properties.  However, using the jcr:uuid property in this manner means that the dna:lock node type can never be made referenceable later.  It also violates an assumption in the JpaConnector that a node's jcr:uuid refers to the UUID for that node and not some other node.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 08:11:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 08:11:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-558) DNA documentation
	problem
In-Reply-To: <1404112840.1259100629627.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <501434892.1259154689682.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-558:
--------------------------------

    Attachment: DNA-558.patch


There were a few missing entities in the custom.dtd for that document.  The attached patch adds entities for Sequencer, SequencerContext, and StreamSequencerContext

Thanks for catching this!

> DNA documentation problem
> -------------------------
>
>                 Key: DNA-558
>                 URL: https://jira.jboss.org/jira/browse/DNA-558
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Tom Ruff
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-558.patch
>
>
> This applies to the DNA Reference Guide at the following link:
> http://docs.jboss.org/jbossdna/latest/manuals/reference/html/sequencing_framework.html#stream-sequencers
> In chapter 7.2, Stream Sequencers, the following sentence left out a key word ("context").  
> So this:
> "The provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Should be this:
> "The context provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Also, immediately above that in the code block the type for the context parameter isn't provided - with javadoc hyperlink - as it is for the other two parameters.  Yes, I know this should probably be a separate issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 08:13:36 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 08:13:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-558) DNA documentation
	problem
In-Reply-To: <1404112840.1259100629627.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1765672231.1259154816878.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-558.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


Committed patch to resolve defect.

> DNA documentation problem
> -------------------------
>
>                 Key: DNA-558
>                 URL: https://jira.jboss.org/jira/browse/DNA-558
>             Project: DNA
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.6
>            Reporter: Tom Ruff
>            Assignee: Brian Carothers
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: DNA-558.patch
>
>
> This applies to the DNA Reference Guide at the following link:
> http://docs.jboss.org/jbossdna/latest/manuals/reference/html/sequencing_framework.html#stream-sequencers
> In chapter 7.2, Stream Sequencers, the following sentence left out a key word ("context").  
> So this:
> "The provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Should be this:
> "The context provides additional details about the information that is being sequenced, including the location and properties of the node being sequenced, the MIME type of the node being sequenced, and a Problems object where the sequencer can record problems that aren't severe enough to warrant throwing an exception. "
> Also, immediately above that in the code block the type for the context parameter isn't provided - with javadoc hyperlink - as it is for the other two parameters.  Yes, I know this should probably be a separate issue.

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


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

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

    Attachment: DNA-457_no_repo_source_capabilities.patch


Added one more patch (DNA-457_no_repo_source_capabilities.patch) to remove supportsLocks() from RepositorySourceCapabilities per an IRC conversation with Randall.  Coupled with the previous patch, this should re-resolve this defect.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 08:38:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 08:38:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-457) Add JSR-170 Locking
 Optional Feature
In-Reply-To: <12096963.1244747636309.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <399520721.1259156309779.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

    Resolution: Done


The last two patches resolve the reasons that this defect was re-opened.  Additional defects should be opened (a la DNA-541) for any other feature needs for locking.

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

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

        

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


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

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

The initial implementation of the XPath parser was added on Oct 3 in SVN revision #1286.  It still needs to be integrated in the JCR query implementation, however.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 09:28:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 09:28:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-549) Creating A New
 Property And Changing An Existing Property Should Have Different
 ChangeRequest Types
In-Reply-To: <1946803342.1257437465795.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <559925721.1259159310233.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 ]

Randall Hauch updated DNA-549:
------------------------------

    Priority: Blocker  (was: Major)


These are blockers for the release.

> 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
>            Priority: Blocker
>             Fix For: 0.7
>
>
> There is no way to differentiate between when a new property is created and when an existing property is set. Both are handled using the SetPropertyRequest. The JCR spec clearly states the difference between these two cases as each one has their own event type.
> Work to change to the relevant change requests, update connectors, and update the NetChangeObserver will need to be done.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 09:28:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 09:28:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-548) The Session That Graph
 Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2075457152.1259159310214.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-548:
------------------------------

    Priority: Blocker  (was: Major)


These are blockers for the release.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 09:46:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 09:46:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-49) Sequence DDL files
Message-ID: <95926994.1259160389750.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 ]

Randall Hauch updated DNA-49:
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
         Assignee: Barry LaFond  (was: Bojidar Penchev)
       Complexity: High  (was: Medium)
         Priority: Major  (was: Minor)


Barry has picked up this work, and has developed a very nice sequencer capable of parsing the more important DDL statements from several different dialects, and constructing a graph structure that is largely the same for all dialects (though some dialects will result in dialect-specific properties and maybe nodes). The sequencer attempts to detect the dialect by running multiple parsers and finding the one with the "best fit".

One very interesting capability of this sequencer is that, although only a subset of the (more common) DDL statements are supported, the sequencer is still extremely functional since it does still add all statements into the output graph, just without much detail other than just the statement text and the position in the DDL file.  Thus, if a DDL file contains statements the sequencer understands and statements that the sequencer does not understand, the graph will still contain all statements and those statements understood by the sequencer will have their full detail.  Since the underlying parsers are able to operate upon a single statement, it is possible to go back later (after the parsers have been enhanced to support additional DDL statements) and re-parse only those incomplete statements in the graph.  

Support for additional statements and additional dialects will be added in the future under different issues.

> 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  Wed Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-418) Support parsing of
 CREATE/ALTER/DROP TABLE statements for SQL Server
In-Reply-To: <25734005.1243094696311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <437948274.1259161230435.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-418.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TABLE statements for SQL Server
> --------------------------------------------------------------------
>
>                 Key: DNA-418
>                 URL: https://jira.jboss.org/jira/browse/DNA-418
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement ANTLR grammar for SQL Server dialect which  parse CREATE/ALTER/DROP TABLE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-421) Support parsing of
 CREATE/ALTER/DROP VIEW statements for Oracle SQL
In-Reply-To: <6154493.1243095056316.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <781904417.1259161230542.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-421.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP VIEW statements for Oracle SQL
> -------------------------------------------------------------------
>
>                 Key: DNA-421
>                 URL: https://jira.jboss.org/jira/browse/DNA-421
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for Oracle SQL dialect in order to parse CREATE/ALTER/DROP VIEW statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-425) Support parsing of
 CREATE/ALTER/DROP DATABASE statements for Oracle SQL
In-Reply-To: <24070475.1243095716328.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2073785081.1259161230638.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-425.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP DATABASE statements for Oracle SQL
> -----------------------------------------------------------------------
>
>                 Key: DNA-425
>                 URL: https://jira.jboss.org/jira/browse/DNA-425
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for Oracle SQL dialect in order to parse CREATE/ALTER/DROP DATABASE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-419) Parse CREATE/ALTER/DROP
 VIEW statements for MySQL
In-Reply-To: <25752842.1243094816306.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1565153869.1259161230498.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-419.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse CREATE/ALTER/DROP VIEW statements for MySQL
> -------------------------------------------------
>
>                 Key: DNA-419
>                 URL: https://jira.jboss.org/jira/browse/DNA-419
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Implement additional rules to the ANTLR grammar for MySQL dialect in order to parse CREATE/ALTER/DROP VIEW statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-423) Parse
 CREATE/ALTER/DROP/RENAME DATABASE statements for MySQL
In-Reply-To: <25815485.1243095476305.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1249940920.1259161230592.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-423.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse CREATE/ALTER/DROP/RENAME DATABASE statements for MySQL
> ------------------------------------------------------------
>
>                 Key: DNA-423
>                 URL: https://jira.jboss.org/jira/browse/DNA-423
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for MySQL dialect in order to parse CREATE/ALTER/DROP/RENAME DATABASE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-424) Support parsing of
 CREATE/ALTER/DROP DATABASE statements for PostgreSQL
In-Reply-To: <5944891.1243095596315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1720960478.1259161230614.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-424.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP DATABASE statements for PostgreSQL
> -----------------------------------------------------------------------
>
>                 Key: DNA-424
>                 URL: https://jira.jboss.org/jira/browse/DNA-424
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for PostgreSQL dialect in order to parse CREATE/ALTER/DROP DATABASE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-406) Find initial control
 sets of DDL files
In-Reply-To: <14352721.1242251506385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <698611145.1259161230250.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-406.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Find initial control sets of DDL files
> --------------------------------------
>
>                 Key: DNA-406
>                 URL: https://jira.jboss.org/jira/browse/DNA-406
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Parsing of  DDL files will be done with ANTLR  grammars for different dialects. Writing of grammar rules is precise process and it need constant feedback of how rules work. Control sets of DDL files for different  SQL dialects will ensure the feedback on every stage of grammar development. 
> Internet can be good source of DDL files with correct syntax, so this sub-task will involve series of searches over the network. Control set also will be used as resources for JUnit testing of the grammars.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-413) Create initial DDL
 grammar and test it.
In-Reply-To: <3199776.1242671105270.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1866024871.1259161230291.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-413.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Create initial DDL grammar and test it.
> ---------------------------------------
>
>                 Key: DNA-413
>                 URL: https://jira.jboss.org/jira/browse/DNA-413
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>            Priority: Minor
>             Fix For: 0.7
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Create initial ANTLR grammar that parse simple string "CREATE TABLE" , without significant of any additional white spaces.  After that implement JUnit class, which test the grammar. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-414) Parse
 CREATE/ALTER/DROP/RENAME TABLE statements for MySQL
In-Reply-To: <12173519.1242671345097.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <906538223.1259161230323.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-414.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse CREATE/ALTER/DROP/RENAME TABLE statements for MySQL
> ---------------------------------------------------------
>
>                 Key: DNA-414
>                 URL: https://jira.jboss.org/jira/browse/DNA-414
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 1 week, 2 days
>  Remaining Estimate: 1 week, 2 days
>
> Implement ANTLR grammar which parse CREATE/ALTER/DROP/RENAME TABLE statements for the MySQL DDL dialect. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-416) Support parsing of
 CREATE/ALTER/DROP TABLE statements for PostgreSQL
In-Reply-To: <23026412.1243094576363.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1467575119.1259161230383.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-416.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TABLE statements for PostgreSQL
> --------------------------------------------------------------------
>
>                 Key: DNA-416
>                 URL: https://jira.jboss.org/jira/browse/DNA-416
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Implement ANTLR grammar for PostgreSQL dialect which  parse CREATE/ALTER/DROP TABLE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-420) Support parsing of
 CREATE/ALTER/DROP VIEW statements for PostgreSQL
In-Reply-To: <444408.1243094936362.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1362583769.1259161230521.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-420.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP VIEW statements for PostgreSQL
> -------------------------------------------------------------------
>
>                 Key: DNA-420
>                 URL: https://jira.jboss.org/jira/browse/DNA-420
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for PostgreSQL dialect in order to parse CREATE/ALTER/DROP VIEW statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-417) Support parsing of
 CREATE/ALTER/DROP TABLE statements for Oracle SQL
In-Reply-To: <30425443.1243094576403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19172131.1259161230413.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-417.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TABLE statements for Oracle SQL
> --------------------------------------------------------------------
>
>                 Key: DNA-417
>                 URL: https://jira.jboss.org/jira/browse/DNA-417
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement ANTLR grammar for Oracle SQL dialect which parse CREATE/ALTER/DROP TABLE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-427) Parse CREATE/ALTER/DROP
 TRIGGERS statements for MySQL
In-Reply-To: <13776973.1243095967829.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1764638874.1259161230698.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-427.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse CREATE/ALTER/DROP TRIGGERS statements for MySQL
> -----------------------------------------------------
>
>                 Key: DNA-427
>                 URL: https://jira.jboss.org/jira/browse/DNA-427
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for MySQL dialect in order to parse CREATE/ALTER/DROP TRIGGERS statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-422) Support parsing of
 CREATE/ALTER/DROP VIEW statements for SQL Server
In-Reply-To: <926537.1243095356360.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2002871786.1259161230567.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-422.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP VIEW statements for SQL Server
> -------------------------------------------------------------------
>
>                 Key: DNA-422
>                 URL: https://jira.jboss.org/jira/browse/DNA-422
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for SQL Server dialect in order to parse CREATE/ALTER/DROP VIEW statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-426) Support parsing of
 CREATE/ALTER/DROP DATABASE statements for SQL Server
In-Reply-To: <28550254.1243095836330.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2051046461.1259161230662.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-426.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP DATABASE statements for SQL Server
> -----------------------------------------------------------------------
>
>                 Key: DNA-426
>                 URL: https://jira.jboss.org/jira/browse/DNA-426
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for SQL Server dialect in order to parse CREATE/ALTER/DROP DATABASE statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-429) Support parsing of
 CREATE/ALTER/DROP TRIGGERS statements for Oracle SQL
In-Reply-To: <29640666.1243096136313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2025421523.1259161230746.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-429.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TRIGGERS statements for Oracle SQL
> -----------------------------------------------------------------------
>
>                 Key: DNA-429
>                 URL: https://jira.jboss.org/jira/browse/DNA-429
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for Oracle SQL dialect in order to parse CREATE/ALTER/DROP TRIGGERS statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-430) Support parsing of
 CREATE/ALTER/DROP TRIGGERS statements for SQL Server
In-Reply-To: <2298943.1243096256316.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1390456000.1259161230770.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-430.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TRIGGERS statements for SQL Server
> -----------------------------------------------------------------------
>
>                 Key: DNA-430
>                 URL: https://jira.jboss.org/jira/browse/DNA-430
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for SQL Server dialect in order to parse CREATE/ALTER/DROP TRIGGERS statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-428) Support parsing of
 CREATE/ALTER/DROP TRIGGERS statements for PostgreSQL
In-Reply-To: <13346023.1243095968015.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29973604.1259161230723.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-428.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/ALTER/DROP TRIGGERS statements for PostgreSQL
> -----------------------------------------------------------------------
>
>                 Key: DNA-428
>                 URL: https://jira.jboss.org/jira/browse/DNA-428
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Implement additional rules to the ANTLR grammar for PostgreSQL dialect in order to parse CREATE/ALTER/DROP TRIGGERS statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-434) Support parsing of
 CREATE/DROP INDEX statements for SQL Server
In-Reply-To: <11999733.1243096616310.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1531733118.1259161230901.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-434.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/DROP INDEX statements for SQL Server
> --------------------------------------------------------------
>
>                 Key: DNA-434
>                 URL: https://jira.jboss.org/jira/browse/DNA-434
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Implement additional rules to the ANTLR grammar for SQL Server dialect in order to parse CREATE/DROP INDEX statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-435) Parse more statement
	for MySQL
In-Reply-To: <26722653.1243096736316.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <406022157.1259161230922.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-435.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse more statement for MySQL
> ------------------------------
>
>                 Key: DNA-435
>                 URL: https://jira.jboss.org/jira/browse/DNA-435
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Implement additional rules to the ANTLR grammar for MySQL dialect in order to parse more DDL statements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-433) Support parsing of
 CREATE/DROP INDEX statements for Oracle SQL
In-Reply-To: <9333880.1243096496326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <443256117.1259161230881.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-433.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/DROP INDEX statements for Oracle SQL
> --------------------------------------------------------------
>
>                 Key: DNA-433
>                 URL: https://jira.jboss.org/jira/browse/DNA-433
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Implement additional rules to the ANTLR grammar for Oracle SQL dialect in order to parse CREATE/DROP INDEX statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-432) Support parsing of
 CREATE/DROP INDEX statements for PostgreSQL
In-Reply-To: <26207283.1243096377340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <86156683.1259161230861.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-432.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Support parsing of CREATE/DROP INDEX statements for PostgreSQL
> --------------------------------------------------------------
>
>                 Key: DNA-432
>                 URL: https://jira.jboss.org/jira/browse/DNA-432
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Implement additional rules to the ANTLR grammar for PostgreSQL dialect in order to parse CREATE/DROP INDEX statements. Implement JUnit tests to test the correctness of parsing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 10:00:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:00:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-431) Parse CREATE/DROP INDEX
 statements for MySQL
In-Reply-To: <25736088.1243096377258.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <826805242.1259161230819.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-431.
-----------------------------

    Fix Version/s: 0.7
                       (was: Future Releases)
       Resolution: Won't Fix


These issues are out of date and no longer represent the work, since Barry picked up the work and approached it from a different direction.

> Parse CREATE/DROP INDEX statements for MySQL
> --------------------------------------------
>
>                 Key: DNA-431
>                 URL: https://jira.jboss.org/jira/browse/DNA-431
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Sequencers, Testing
>    Affects Versions: 0.4
>            Reporter: Bojidar Penchev
>            Assignee: Bojidar Penchev
>             Fix For: 0.7
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> Implement additional rules to the ANTLR grammar for MySQL dialect in order to parse CREATE/DROP INDEX statements. Implement JUnit tests to test the correctness of parsing.

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


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

Randall Hauch updated DNA-526:
------------------------------

        Fix Version/s: 0.7
    Affects Version/s: 0.7
             Assignee: Barry LaFond


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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 10:07:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:07:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-556) Need a graph-specific
 SequencerOutput class to simplify testing sequencer results.
In-Reply-To: <498100892.1259012856344.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <949711152.1259161650151.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-556:
------------------------------

          Component/s: Sequencers
        Fix Version/s: 0.7
    Affects Version/s: 0.7
             Assignee: Barry LaFond


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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 10:13:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:13:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1464632.1259162009712.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-546:
------------------------------

    Fix Version/s: 0.7


Targeting to 0.7, since it is a TCK-related issue

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 10:13:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:13:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-547) TCK Tests for Locking
 and Moving Nodes Fail for JPA Connector
In-Reply-To: <110540148.1256938805728.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <392393778.1259162009864.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-547:
------------------------------

    Fix Version/s: 0.7


Targeting to 0.7, since it is a TCK-related issue

> TCK Tests for Locking and Moving Nodes Fail for JPA Connector
> -------------------------------------------------------------
>
>                 Key: DNA-547
>                 URL: https://jira.jboss.org/jira/browse/DNA-547
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>
> Two of the TCK tests for the optional locking feature fail on the JPA connector.  As a result, the TCK tests for the locking feature have been removed from the JPA TCK integration test.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 10:21:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 10:21:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-507) Update developer
 documentation explaining use of Utility methods for instead of doPrivileged
In-Reply-To: <806875987.1251385464555.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <269767910.1259162489608.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-507.
-------------------------------

    Resolution: Won't Fix


Utility methods cannot be used for these system privilege blocks, so there is no need to document.

> Update developer documentation explaining use of Utility methods for instead of doPrivileged
> --------------------------------------------------------------------------------------------
>
>                 Key: DNA-507
>                 URL: https://jira.jboss.org/jira/browse/DNA-507
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Vijay Kiran Duvvuri
>             Fix For: 0.7
>
>
> The developer documentation needs to be updated after DNA-499 has been resolved. The proposed fix for DNA-499 is to introduce utility methods for Thread.currentThread().getContextClassLoader()  and method invocations using reflection.
> Please see DNA-499 for more information.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 11:52:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:52:29 -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: <856925472.1259167949603.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:
------------------------------

    Assignee: Randall Hauch  (was: Dan Florian)


We can do this pretty easily in Magnolia by creating an "Eclipse" item under the Downloads menu on http://www.jboss.org/dna and next to the "Maven" item.  That would of course correspond to a single page that describes the update site.  We can then put the actual update site under http://downloads.jboss.org, and reference it via the "Eclipse" page.

> Develop Update Site Website
> ---------------------------
>
>                 Key: DNA-536
>                 URL: https://jira.jboss.org/jira/browse/DNA-536
>             Project: DNA
>          Issue Type: Task
>          Components: Views
>    Affects Versions: 0.7
>            Reporter: Dan Florian
>            Assignee: Randall Hauch
>             Fix For: 0.7
>
>
> Develop web page where the update site archive can be downloaded from. Include instructions on how to use Eclipse's Update Manager to install the archive. Also include brief  instructions on how to use the feature. Might be nice to include instructions on (1) how to get JBoss running with the DNA REST server. Also might be nice to include instructions on how to build the archive using a development environment.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 11:57:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-506) Switch to JDK 6 (aka
 1.6) for baseline
In-Reply-To: <1489215044.1251318623589.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <724999328.1259168250217.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-506:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Retargeting to 1.0.

> Switch to JDK 6 (aka 1.6) for baseline
> --------------------------------------
>
>                 Key: DNA-506
>                 URL: https://jira.jboss.org/jira/browse/DNA-506
>             Project: DNA
>          Issue Type: Task
>          Components: Development Environment
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 1.0
>
>
> Change the POM file to use the JDK 1.6 compiler for JBoss DNA, and change the Getting Started and Reference Guides to reflect this.  We can change the version that we use, yet keep the target set to 1.5 (for now) to ensure that JBoss DNA can be used in applications that use J2SE 5.0.
> J2SE 5.0 (and JDK 5.0) is already in its end of life transition, and is slated for its end-of-life to be completed on October 30, 2009 [1].  Also, see the discussion on the forums regarding this change. [2]
> [1] http://java.sun.com/javase/downloads/index_jdk5.jsp
> [2] http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249314#4249314

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 11:57:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-514) Update Base64 class
In-Reply-To: <1095720300.1252013783533.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <264787628.1259168250154.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-514:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Retargeting to 1.0.

> Update Base64 class
> -------------------
>
>                 Key: DNA-514
>                 URL: https://jira.jboss.org/jira/browse/DNA-514
>             Project: DNA
>          Issue Type: Task
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>             Fix For: 1.0
>
>
> There is an updated version of the public domain Base64 class that we use, and it has a number of significant improvements and bug fixes.  However, it is no longer a drop-in replacement (plus we made a number of changes to fix formatting 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 Nov 25 11:57:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-464) Add use of file system
 connector to repositories example
In-Reply-To: <15709139.1245257456331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1506384680.1259168250284.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-464:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Retargeting to 1.0.

> Add use of file system connector to repositories example
> --------------------------------------------------------
>
>                 Key: DNA-464
>                 URL: https://jira.jboss.org/jira/browse/DNA-464
>             Project: DNA
>          Issue Type: Task
>          Components: Documentation, Examples, Federation
>    Affects Versions: 0.5
>            Reporter: Randall Hauch
>             Fix For: 1.0
>
>
> See DNA-462 for an issue raised by feu trying to use the file system connector in a federated repository.  The repositories example of the Getting Started document should show how to do this.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 11:57:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:57:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-450) Add support to
 programmatically configure more complicated repository sources (e.g.,
 federated) in DnaConfiguration
In-Reply-To: <26916616.1244656736782.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <598927062.1259168250334.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-450:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Retargeting to 1.0.

> Add support to programmatically configure more complicated repository sources (e.g., federated) in DnaConfiguration
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-450
>                 URL: https://jira.jboss.org/jira/browse/DNA-450
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Connectors, Federation
>    Affects Versions: 0.4
>            Reporter: Randall Hauch
>             Fix For: 1.0
>
>
> The DnaConfiguration allows setting up repository sources, but it doesn't provide a way to do anything but set properties on those sources.  The DnaConfiguration should provide a way of adding configuration content underneath the node that represents the source.  This would make it possible to programmatically repository sources that have more complicated configuration requirements.
> A workaround is to define the configuration in a file and then import that file.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 11:57:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 11:57: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: <2034294702.1259168250257.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 ]

Randall Hauch updated DNA-519:
------------------------------

    Fix Version/s: 1.0
                       (was: 0.7)


Retargeting to 1.0.

> 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.0
>
>
> 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  Wed Nov 25 12:37:35 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 12:37:35 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1825911384.1259170655346.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-551:
-----------------------------------

I've reviewed the patch, and there are several problems.

One federation unit test in 'dna-graph' is failing because the patch changes the behavior of some of the Location.create(...) methods that take an identification Property.  The patch was looking for the case where the supplied ID property has a name of "dna:uuid" and created a LocationWithPathAndUuid using the path and the first value of the ID property.  So if the ID property contains multiple UUIDs (as is the case in the federation case, when merging nodes with the same path but different UUIDs from multiple sources), then the UUID values other than the first were lost.

Another problem with the patch is that the Location.create(Path,UUID) method was checking for a null UUID and creating a Location properly (with just the Path) but was not returning it, so the method continued to create a LocationWithPathAndUuid using the path and null UUID reference.  This of course fails on the assertion (if assertions are enabled when running the tests).

Fixing these (locally) resulted in no unit test failures in 'dna-graph' or 'dna-repository'.  However, even with these fixes there is one TCK test failure in WorkspaceCloneTest.testCloneNodesTwice(), with the error:

javax.jcr.PathNotFoundException: Unable to find "{}testroot/{}node2/{}node1/{}node3"; lowest existing path is "/{}testroot/{}node2": Unable to find "{}testroot/{}node2/{}node1/{}node3"; lowest existing path is "/{}testroot/{}node2": Unable to find "{}testroot/{}node2/{}node1/{}node3"; lowest existing path is "/{}testroot/{}node2"
	at org.jboss.dna.jcr.JcrWorkspace.clone(JcrWorkspace.java:401)
	at org.apache.jackrabbit.test.api.WorkspaceCloneTest.testCloneNodesTwice(WorkspaceCloneTest.java:64)

I'll continue to investigate this error.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 13:05:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 13:05:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-559) GraphSession
 cloneImmediate fails to remove existing nodes from cache because of Set
 ordering variations
Message-ID: <1456838811.1259172329616.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

GraphSession cloneImmediate fails to remove existing nodes from cache because of Set ordering variations
--------------------------------------------------------------------------------------------------------

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


GraphSession.cloneImmediate(...) has a parameter that specifies whether any existing nodes should be removed (from the connector), and if this connector request succeeds and did remove those nodes, the method continues by attempting to purge these nodes from the cache.  However, the request collects in a Set the Location for each of the removed nodes, so the order of these nodes cannot be guaranteed.  And in fact when the cloneImmediate method walks them, the test was purging a parent node followed by a child node.  Since purging the parent also purged all children (and other descendants), attempting to purge the child results in an exception.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 13:10:36 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 13:10:36 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-559) GraphSession
 cloneImmediate fails to remove existing nodes from cache because of Set
 ordering variations
In-Reply-To: <1456838811.1259172329616.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <679163185.1259172636301.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-559:
-----------------------------------

The fix is relatively simple: check whether a node being purged is below a node that already was purged.

> GraphSession cloneImmediate fails to remove existing nodes from cache because of Set ordering variations
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-559
>                 URL: https://jira.jboss.org/jira/browse/DNA-559
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> GraphSession.cloneImmediate(...) has a parameter that specifies whether any existing nodes should be removed (from the connector), and if this connector request succeeds and did remove those nodes, the method continues by attempting to purge these nodes from the cache.  However, the request collects in a Set the Location for each of the removed nodes, so the order of these nodes cannot be guaranteed.  And in fact when the cloneImmediate method walks them, the test was purging a parent node followed by a child node.  Since purging the parent also purged all children (and other descendants), attempting to purge the child results in an exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 13:17:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 13:17:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-559) GraphSession
 cloneImmediate fails to remove existing nodes from cache because of Set
 ordering variations
In-Reply-To: <1456838811.1259172329616.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1401593250.1259173049663.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-559.
-------------------------------

    Resolution: Done


All unit tests pass, so marking as resolved.

> GraphSession cloneImmediate fails to remove existing nodes from cache because of Set ordering variations
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-559
>                 URL: https://jira.jboss.org/jira/browse/DNA-559
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> GraphSession.cloneImmediate(...) has a parameter that specifies whether any existing nodes should be removed (from the connector), and if this connector request succeeds and did remove those nodes, the method continues by attempting to purge these nodes from the cache.  However, the request collects in a Set the Location for each of the removed nodes, so the order of these nodes cannot be guaranteed.  And in fact when the cloneImmediate method walks them, the test was purging a parent node followed by a child node.  Since purging the parent also purged all children (and other descendants), attempting to purge the child results in an exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 13:43:37 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 13:43:37 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-390) BatchRequestBuilder
 Property/Create Folding Behavior
In-Reply-To: <28485819.1241112839899.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <205833348.1259174617558.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-390.
---------------------------------

    Resolution: Won't Fix
      Assignee: Brian Carothers


I'm withdrawing my own defect.  There was a simple workaround for this put in place months ago and I've yet to find another place where this behavior would be needed.

> BatchRequestBuilder Property/Create Folding Behavior
> ----------------------------------------------------
>
>                 Key: DNA-390
>                 URL: https://jira.jboss.org/jira/browse/DNA-390
>             Project: DNA
>          Issue Type: Feature Request
>          Components: API, Graph
>    Affects Versions: 0.3
>            Reporter: Brian Carothers
>            Assignee: Brian Carothers
>            Priority: Minor
>             Fix For: 0.7
>
>
> BatchRequestBuilder currently attempts to consolidate multiple set property and create calls for the same node into a single set property or create statement.  The consolidation process does not seem to respect SNS though.
> For example:
> 1. Create a node at /a/b
> 2. Set some properties on the node at location /a/b
> 3. Create another node at /a/b (same-name sibling)
> 4. Set some other properties on the node at location /a/b 
> The consolidation process sets the properties from step 4 onto the node created at step 1.  This overwrites the properties from step 2 where the property names are the same.
> There are a few workarounds in place right now.  One is to just consolidate the requests yourself prior to invoking the Graph API and adding commands to the batch.  It is possible that using the Path-based variants of the create node and set property commands would also work around this problem if the SNS indices were set correctly on the paths.  I've not tried this approach I think it would be fairly cumbersome and fragile as it would require the caller to track whether there are already any nodes with the same name at the same location and offset SNS indices accordingly.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 14:01:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 14:01:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1246209555.1259175689713.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-551:
-----------------------------------

The error was actually an unrelated bug in GraphSession (DNA-559).  The fix has been committed, and incorporating that fix to these changes gets us farther.  However, there still is another error in one of the unit tests in 'dna-connector-filesystem'.  The problem appears to be in AbstractConnectorTest, where one use of Location.isSame(Location) was not changed to use 'equals()'.  Fixing that makes all unit tests and integration tests pass (via a complete integration build).

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 14:03:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 14:03:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <637850734.1259175809588.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-551:
------------------------------

    Attachment: DNA-551-patch2.txt


Uploaded the patch file "DNA-551-patch2.txt" that contains all fixes to pass all tests.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt, DNA-551-patch2.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 25 14:30:29 2009
From: jira-events at lists.jboss.org (Barry LaFond (JIRA))
Date: Wed, 25 Nov 2009 14:30:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-49) Sequence DDL files
Message-ID: <1355283392.1259177429672.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=12496731#action_12496731 ] 

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

DESIGN SUMMARY - Randall's previous comment summarizes the basic behavior and intent of the DdlSequencer and it's underlying parsing framework.

The following ddl dialects are included with the first version: Oracle, Derby, Postgres and MySql

Each specific dialect extends a basic parser framework implementing the SQL 92 spec and includes

    - Detailed parsing of CREATE SCHEMA, CREATE TABLE and ALTER TABLE.
    - Partial parsing of DROP statements
    - General parsing of remaining schema definition statements (i.e. CREATE VIEW, CREATE DOMAIN, etc.
    - Does NOT parse SQL (i.e. SELECT, INSERT, UPDATE, etc....) statements.

Dialect flexibility is achieved through extending the base parser (StandardDdlParser) and registering sets of dialect-specific keywords and unique "statement start phrases" (example:  CREATE TRIGGER).  These registered values assist the tokenizer in identifying key elements in your DDL which enable the base-parser to efficiently navigate the tokens and build an object graph reflecting the intended structure of your DDL.



 

> 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  Wed Nov 25 15:19:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 15:19:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <471592125.1259180369597.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-551.
-------------------------------

    Resolution: Done
      Assignee: Johnny Verhaeg


Applied the second version of the patch ('DNA-551-patch2.txt'), after all unit and integration tests passed.  Basically, the Location.equals(...) and Location.isSame(...) method behaviors were switched, and the various uses corrected.  Now, the Location.equals(...) and Location.hashCode() methods behave in the traditional way, and can be used as keys in Maps (even when you might have partial Location objects and the Map might contain actual Location objects, or vice versa). 

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Johnny Verhaeg
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt, DNA-551-patch2.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

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


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

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

    Fix Version/s: 1.0
                       (was: 0.7)


Changing fix version to 1.0 as this was a lower priority task for 0.7.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 15:46:29 2009
From: jira-events at lists.jboss.org (Dan Florian (JIRA))
Date: Wed, 25 Nov 2009 15:46:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-535) A Synchronize Action
 Is Needed To Make Sure Workspace Resource Publishing State Agrees With The
 DNA Repositories
In-Reply-To: <676958315.1254495889266.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1114039624.1259181989797.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

    Fix Version/s: 1.0
                       (was: 0.7)


Changing fix version to 1.0 as this was not a requirement for 0.7 and the task is to big to complete in time remaining in the 0.7 release.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 19:37:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 19:37:29 -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: <957074001.1259195849859.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=12496779#action_12496779 ] 

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

Added fields to the UpdatePropertiesRequest and SetPropertyRequest to record which properties were created vs changed. Since this is a change to the request classes involving new methods that must be called when processing these requests, all the connectors were checked and changed if required. All tests pass.

> 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
>            Priority: Blocker
>             Fix For: 0.7
>
>
> There is no way to differentiate between when a new property is created and when an existing property is set. Both are handled using the SetPropertyRequest. The JCR spec clearly states the difference between these two cases as each one has their own event type.
> Work to change to the relevant change requests, update connectors, and update the NetChangeObserver will need to be done.

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

        

From jira-events at lists.jboss.org  Wed Nov 25 19:39:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Wed, 25 Nov 2009 19:39:29 -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: <1344534512.1259195969601.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 ]

Randall Hauch resolved DNA-549.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Marking as resolved, since this appears to have solved the issue.

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

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

        

From jira-events at lists.jboss.org  Wed Nov 25 21:26:30 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Wed, 25 Nov 2009 21:26:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-511) The JPA Source should
 provide a way of producing the DDL for the database dialect
In-Reply-To: <314441080.1251898044107.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1740024110.1259202390464.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-511:
--------------------------------

    Attachment: DNA-511.patch


Attached an uncommented patch for review.  The patch leverages the Hibernate SchemaExport class to generate the DDL for a given model.  The POM packages the code into an executable jar, so DDL for a given model in a given schema would be generated with this syntax:

java -jar dna-jpa-ddl-gen-0.7-SNAPSHOT-jar-with-dependencies.jar -dialect org.hibernate.dialect.Oracle10gDialect -model Basic -out /tmp

I'd appreciate any feedback on the patch.  If it looks ok, I'll clean it up, add some comments, and commit it.

> The JPA Source should provide a way of producing the DDL for the database dialect
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-511
>                 URL: https://jira.jboss.org/jira/browse/DNA-511
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>             Fix For: 0.7
>
>         Attachments: DNA-511.patch
>
>
> Hibernate is capable of dynamically creating the schema, but this is really only practical in a development environment.  Production environments will rarely (ever?) want to allow the software to change the database, so having the DDL for the database used by the JpaSource would be very useful to have.  Hibernate is capable of generating this, and we should provide a mechanism for producing the DDL for the configured dialect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 26 15:36:22 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 15:36:22 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <760394738.1259267782960.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-548:
-----------------------------------

The ExecutionContext serves as the universal mechanism by which the DNA code knows the context in which operations are performed, and is available to the connectors that process the requests, the session that creates the requests, and the Observation system that post-processes the (complete) requests.  The JcrRepository.login(...) method always creates a new ExecutionContext via the ExecutionContext.with(...), which means that every JcrSession implementation has a unique ExecutionContext.  Therefore, if we add a unique identifier to the ExecutionContext, that identifier would correspond to the Session instance.

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

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

        

From jira-events at lists.jboss.org  Thu Nov 26 15:41:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 15:41:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1830698680.1259268090184.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-548.
-------------------------------

    Resolution: Done
      Assignee: Randall Hauch


Added this identifier (a stringified UUID) to the ExecutionContext, and adds a 'contextId' to the Changes class.  Then, the RequestProcessor was changed to set the context ID for the Changes object that it creates.

Marking as resolved.

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

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

        

From jira-events at lists.jboss.org  Thu Nov 26 15:58:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 15:58:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-456) Add JSR-170
 Observation Optional Feature
In-Reply-To: <29781241.1244747516423.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <771612426.1259269109706.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

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

Both DNA-548 and DNA-549 have been completed.

> Add JSR-170 Observation Optional Feature
> ----------------------------------------
>
>                 Key: DNA-456
>                 URL: https://jira.jboss.org/jira/browse/DNA-456
>             Project: DNA
>          Issue Type: Feature Request
>          Components: JCR
>    Affects Versions: 0.5
>            Reporter: Brian Carothers
>            Assignee: Dan Florian
>             Fix For: 0.7
>
>
> JSR-170 defines several optional features.  The observation feature would provide notification of node and property changes to registered listeners.

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

        

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


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

Brian Carothers commented on DNA-546:
-------------------------------------

The root cause of this behavior is the Basic model's composite primary key for node entities (workspace ID, node UUID).  This approach is very efficient in general, but causes problems with the portions of the TCK that require replacement of nodes with the same UUIDs (e.g., document imports that contain nodes with a UUID that is already in use with the workspace).  In this case, the default implementation in the JCR layer tries to delete the existing node with a given UUID and then add a new node (usually in a different location) with the same UUID.  This would require the JPA session to contain two versions of the same entity (one being deleted and another being added).  This just doesn't work under the JPA spec.

So then the question becomes "how does this get fixed?"  One approach would be to modify the JCR import (and workspace copy and clone) code to implement an update of this type instead of a delete/insert strategy.  This approach would require a two-pass approach.  First, the UUIDs of all of the incoming nodes would have to be collected, then the potential nodes that might be deleted would have to be computed.  This set of added nodes would be a proper subset of the deleted nodes, since deleting a node implies deleting all of its ancestors as well.  After that, the nodes that would have been deleted and then inserted would have to be moved to their new location and their children removed, but this would have to be ordered carefully since the removed children may themselves be moved as part of the operation.  That's not everything that would need to happen to work around this, but it's already a lot.  And only one current (or planned) connector has this problem, so it's pretty debatable whether it should have been solved in the JCR layer anyway.

Alternatively, we could just add a new model for the JPA connector which was built to support this in the first place.  I'm going to try that first.

My proposed model is based on the current model (the "Basic" model) and in fact would reuse a fair amount of the common code.  The new model would have three main changes from the Basic model:

1.  It would have an artificial key to avoid the problem described in this defect.
2.  It would store the node and its properties in a single table (collapsing the ChildEntity and PropertiesEntity from the Basic model into a single NodeEntity)
3.  It would be based on the MapRepository so that it can reuse most of the working, debugged MapRequestProcessor implementation.

I expect to retain the mechanism for managing large properties and tracking references from the BasicModel.  I also am reusing the property serialization code since it's already been tested and shaken down.  

Any feedback on this approach is, as always, welcome.

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

       


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


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

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

    Attachment: DNA-546_map_node_change.patch


The first patch makes some preparatory tweaks to the MapRepository code.  MapNode is renamed to DefaultMapNode and now implements a new interface named MapNode.  Additionally, some bulk mutators are added.

The first part is a change that had been kicked around during the original development of the MapRepository code and, IIRC, was bypassed as one of those "if we need it later, we'll do it" changes.  I'm doing it now to enable the creation of a JpaNode for the new JPA connector model.  Instead of implementing the MapNode interface by managing state internally (like DefaultMapNode does), the JpaNode will be an adapter over a JPA entity.

The bulk mutators are added to help limit the number of times that the properties for a node need to be reserialized.

Since these changes are pretty safe and self-contained, I'm going to commit them without review.  

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_map_node_change.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

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


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

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

    Attachment:     (was: DNA-546_map_node_change.patch)


> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

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


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

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

    Attachment: DNA-546_map_node_change.patch


Attached updated patch.

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_map_node_change.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

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


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

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

    Attachment: DNA-546_jpa_connector_refactor.patch


Attached patch (DNA-546_jpa_connector_refactor.patch) that refactors the existing JPA connector framework to more readily support the new model that I'm working on.

The patch removes the relationship between the model and the request processor and adds a relationship between the model and its connection.  To work within the MapRepository framework, I had to be able to pass a reference to the MapRepository into the MapRequestProcessor.  This ruled out using the existing JpaConnection.  The cleanest way to isolate the reusable pieces of the code seemed to be to rename JpaConnection to BasicJpaConnection, move it into model.basic, and then replace Model.createRequestProcessor(...) with Model.createConnection(JpaSource).  This required a few changes to class visibility (but not constructor visibility) and the addition of some accessors to JpaSource.

Clearly, there are alternate ways to accomplish this same goal.  I am going to wait for some feedback before I commit this patch.


> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

From jira-events at lists.jboss.org  Thu Nov 26 21:59:37 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 21:59:37 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-511) The JPA Source
 should provide a way of producing the DDL for the database dialect
In-Reply-To: <314441080.1251898044107.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1212814434.1259290777560.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-511:
-----------------------------------

I like the way this code works.  I didn't quite understand that this is a utility (not sure what I was thinking), but this is really sweet.  I vote for a commit.

> The JPA Source should provide a way of producing the DDL for the database dialect
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-511
>                 URL: https://jira.jboss.org/jira/browse/DNA-511
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>             Fix For: 0.7
>
>         Attachments: DNA-511.patch
>
>
> Hibernate is capable of dynamically creating the schema, but this is really only practical in a development environment.  Production environments will rarely (ever?) want to allow the software to change the database, so having the DDL for the database used by the JpaSource would be very useful to have.  Hibernate is capable of generating this, and we should provide a mechanism for producing the DDL for the configured dialect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 26 22:05:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 22:05:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-560) Remove the
 'dna-jcr-gen' project because of licensing issues
Message-ID: <841433507.1259291129584.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Remove the 'dna-jcr-gen' project because of licensing issues
------------------------------------------------------------

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


The 'dna-jcr-gen' project (in 'util' directory) relies upon the Benerator library, which uses a library that isn't compatible with LGPL.  We don't distribute the library, but we still can't have code that uses Benerator.  So we need to remove the 'dna-jcr-gen' project.

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

        

From jira-events at lists.jboss.org  Thu Nov 26 22:09:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 22:09:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-560) Remove the
 'dna-jcr-gen' project because of licensing issues
In-Reply-To: <841433507.1259291129584.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <909124798.1259291369658.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-560.
-------------------------------

    Resolution: Done


Removed the project, so marking as resolved.

> Remove the 'dna-jcr-gen' project because of licensing issues
> ------------------------------------------------------------
>
>                 Key: DNA-560
>                 URL: https://jira.jboss.org/jira/browse/DNA-560
>             Project: DNA
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 'dna-jcr-gen' project (in 'util' directory) relies upon the Benerator library, which uses a library that isn't compatible with LGPL.  We don't distribute the library, but we still can't have code that uses Benerator.  So we need to remove the 'dna-jcr-gen' project.

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

        

From jira-events at lists.jboss.org  Thu Nov 26 22:29:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Thu, 26 Nov 2009 22:29:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Closed: (DNA-560) Remove the
 'dna-jcr-gen' project because of licensing issues
In-Reply-To: <841433507.1259291129584.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2024703187.1259292569609.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch closed DNA-560.
-----------------------------



All builds succeeded after removal, so marking as closed.

> Remove the 'dna-jcr-gen' project because of licensing issues
> ------------------------------------------------------------
>
>                 Key: DNA-560
>                 URL: https://jira.jboss.org/jira/browse/DNA-560
>             Project: DNA
>          Issue Type: Task
>          Components: JCR
>    Affects Versions: 0.7
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> The 'dna-jcr-gen' project (in 'util' directory) relies upon the Benerator library, which uses a library that isn't compatible with LGPL.  We don't distribute the library, but we still can't have code that uses Benerator.  So we need to remove the 'dna-jcr-gen' project.

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

        

From jira-events at lists.jboss.org  Fri Nov 27 10:03:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Fri, 27 Nov 2009 10:03:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-546) JCR Workspace and
 Session Imports Can Fail on JPA Connector
In-Reply-To: <831890952.1256938697316.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <572023480.1259334209954.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-546:
-----------------------------------

The DNA-546_jpa_connector_refactor.patch looks good.

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

From jira-events at lists.jboss.org  Fri Nov 27 11:51:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 27 Nov 2009 11:51:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-511) The JPA Source should
 provide a way of producing the DDL for the database dialect
In-Reply-To: <314441080.1251898044107.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1411343058.1259340689957.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers updated DNA-511:
--------------------------------

    Attachment: DNA-511_final.patch


Attached new version of previous patch that adds comments, documentation, and more tolerance for variations on the dialect parameter.

> The JPA Source should provide a way of producing the DDL for the database dialect
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-511
>                 URL: https://jira.jboss.org/jira/browse/DNA-511
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>             Fix For: 0.7
>
>         Attachments: DNA-511.patch, DNA-511_final.patch
>
>
> Hibernate is capable of dynamically creating the schema, but this is really only practical in a development environment.  Production environments will rarely (ever?) want to allow the software to change the database, so having the DDL for the database used by the JpaSource would be very useful to have.  Hibernate is capable of generating this, and we should provide a mechanism for producing the DDL for the configured dialect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 27 11:54:29 2009
From: jira-events at lists.jboss.org (Brian Carothers (JIRA))
Date: Fri, 27 Nov 2009 11:54:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-511) The JPA Source should
 provide a way of producing the DDL for the database dialect
In-Reply-To: <314441080.1251898044107.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1877618378.1259340869642.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Brian Carothers resolved DNA-511.
---------------------------------

    Resolution: Done
      Assignee: Brian Carothers


Committed patch to resolve defect.

> The JPA Source should provide a way of producing the DDL for the database dialect
> ---------------------------------------------------------------------------------
>
>                 Key: DNA-511
>                 URL: https://jira.jboss.org/jira/browse/DNA-511
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Connectors
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-511.patch, DNA-511_final.patch
>
>
> Hibernate is capable of dynamically creating the schema, but this is really only practical in a development environment.  Production environments will rarely (ever?) want to allow the software to change the database, so having the DDL for the database used by the JpaSource would be very useful to have.  Hibernate is capable of generating this, and we should provide a mechanism for producing the DDL for the configured dialect.

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


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

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

    Attachment: DNA-546_simple_model_WIP.patch


Attaching a snapshot of the work in progress in case anyone's curious.  This version mostly works, although it doesn't respect References in copy or clone operations and won't enforce referential integrity.  It also has some wonky behavior around committing changes that I can't seem to figure.  This causes race conditions that lead to failures when running the L2 TCK tests.

Having given that disclaimer, the structure of the code is just about where I think it should be.  It heavily leverages the MapRepository framework and the existing Basic model.  It does differ from the other MapRepository implementations in that it creates a new MapRepository instance with every JpaSource.getConnection call - the other implementations share the same MapRepository instance across multiple connections.

Feedback is welcome as always.  My intent is to take yet another look at the race condition on the commits and then work on integrating references.

> JCR Workspace and Session Imports Can Fail on JPA Connector
> -----------------------------------------------------------
>
>                 Key: DNA-546
>                 URL: https://jira.jboss.org/jira/browse/DNA-546
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors, JCR
>    Affects Versions: 0.6
>            Reporter: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-546_jpa_connector_refactor.patch, DNA-546_map_node_change.patch, DNA-546_simple_model_WIP.patch
>
>
> Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector.
> The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect.

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

        

From jira-events at lists.jboss.org  Sun Nov 29 22:52:29 2009
From: jira-events at lists.jboss.org (John Ament (JIRA))
Date: Sun, 29 Nov 2009 22:52:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Created: (DNA-561) Google Collections API
 compatibility issues w/ Weld/AS 6
Message-ID: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>

Google Collections API compatibility issues w/ Weld/AS 6
--------------------------------------------------------

                 Key: DNA-561
                 URL: https://jira.jboss.org/jira/browse/DNA-561
             Project: DNA
          Issue Type: Bug
          Components: Graph, JCR
    Affects Versions: 0.6
         Environment: Jboss as 6 M1
Weld 1.0.1 (Trunk)
DNA 0.7 Snapshot
            Reporter: John Ament
            Priority: Minor
             Fix For: 0.7


DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.

Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.

There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.

Setting complexity to medium since it requires changing a library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 29 22:54:29 2009
From: jira-events at lists.jboss.org (John Ament (JIRA))
Date: Sun, 29 Nov 2009 22:54:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-561) Google Collections API
 compatibility issues w/ Weld/AS 6
In-Reply-To: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <615301312.1259553269587.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

John Ament updated DNA-561:
---------------------------

    Attachment: dna-patch-weld.patch


This is the patch I referred to.  It probably could use some code review to check imports (only did it in notepad++, didn't feel like buggering around with eclipse).  As mentioned, it runs successfully and unit tests are completed.

These were the only two projects I found references to google collections in.

> Google Collections API compatibility issues w/ Weld/AS 6
> --------------------------------------------------------
>
>                 Key: DNA-561
>                 URL: https://jira.jboss.org/jira/browse/DNA-561
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, JCR
>    Affects Versions: 0.6
>         Environment: Jboss as 6 M1
> Weld 1.0.1 (Trunk)
> DNA 0.7 Snapshot
>            Reporter: John Ament
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: dna-patch-weld.patch
>
>   Original Estimate: 3 minutes
>  Remaining Estimate: 3 minutes
>
> DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.
> Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.
> There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.
> Setting complexity to medium since it requires changing a library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 29 22:56:29 2009
From: jira-events at lists.jboss.org (John Ament (JIRA))
Date: Sun, 29 Nov 2009 22:56:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-561) Google Collections API
 compatibility issues w/ Weld/AS 6
In-Reply-To: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <966912067.1259553389594.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

John Ament updated DNA-561:
---------------------------

     Original Estimate: 3 hours  (was: 3 minutes)
    Remaining Estimate: 3 hours  (was: 3 minutes)


> Google Collections API compatibility issues w/ Weld/AS 6
> --------------------------------------------------------
>
>                 Key: DNA-561
>                 URL: https://jira.jboss.org/jira/browse/DNA-561
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph, JCR
>    Affects Versions: 0.6
>         Environment: Jboss as 6 M1
> Weld 1.0.1 (Trunk)
> DNA 0.7 Snapshot
>            Reporter: John Ament
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: dna-patch-weld.patch
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.
> Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.
> There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.
> Setting complexity to medium since it requires changing a library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 30 10:35:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 10:35:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Updated: (DNA-561) Google Collections API
 compatibility issues w/ Weld/AS 6
In-Reply-To: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1534430967.1259595331476.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch updated DNA-561:
------------------------------

    Issue Type: Thirdparty Change  (was: Bug)
      Assignee: Randall Hauch


We'll get this in very soon.  Thanks for the patch!

> Google Collections API compatibility issues w/ Weld/AS 6
> --------------------------------------------------------
>
>                 Key: DNA-561
>                 URL: https://jira.jboss.org/jira/browse/DNA-561
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Graph, JCR
>    Affects Versions: 0.6
>         Environment: Jboss as 6 M1
> Weld 1.0.1 (Trunk)
> DNA 0.7 Snapshot
>            Reporter: John Ament
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: dna-patch-weld.patch
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.
> Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.
> There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.
> Setting complexity to medium since it requires changing a library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 30 12:09:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 12:09:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-561) Google Collections
 API compatibility issues w/ Weld/AS 6
In-Reply-To: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1324717012.1259600969749.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-561.
-------------------------------

    Resolution: Done


Marking as resolved.  If there is a problem with this change, please reopen this issue.

> Google Collections API compatibility issues w/ Weld/AS 6
> --------------------------------------------------------
>
>                 Key: DNA-561
>                 URL: https://jira.jboss.org/jira/browse/DNA-561
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Graph, JCR
>    Affects Versions: 0.6
>         Environment: Jboss as 6 M1
> Weld 1.0.1 (Trunk)
> DNA 0.7 Snapshot
>            Reporter: John Ament
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: dna-patch-weld.patch
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.
> Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.
> There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.
> Setting complexity to medium since it requires changing a library.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 30 12:09:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 12:09:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-561) Google Collections
 API compatibility issues w/ Weld/AS 6
In-Reply-To: <2045712011.1259553149735.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <1604826624.1259600969713.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-561:
-----------------------------------

Applied the patch and successfully ran all of the tests.  Nicely done, John!

Also uploaded the Google Collections 1.0RC3 (jar,sources,javadoc) to the JBoss Maven Repository.

> Google Collections API compatibility issues w/ Weld/AS 6
> --------------------------------------------------------
>
>                 Key: DNA-561
>                 URL: https://jira.jboss.org/jira/browse/DNA-561
>             Project: DNA
>          Issue Type: Thirdparty Change
>          Components: Graph, JCR
>    Affects Versions: 0.6
>         Environment: Jboss as 6 M1
> Weld 1.0.1 (Trunk)
> DNA 0.7 Snapshot
>            Reporter: John Ament
>            Assignee: Randall Hauch
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: dna-patch-weld.patch
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> DNA is using a google collections api from May 2008.  They are currently at 1.0 r 4.
> Weld, part of Java EE 6, also uses google collections, but a newer version, 1.0 r3.
> There are a number of API differences, mainly in how objects are instantiated (many of the methods used by DNA are replaced by create methods in the objects in question).   It makes writing an app that uses both DNA and Weld impossible (since both versions of google collections need to be loaded).  As a result, I have created a patch that will correct this.  Unit tests and functional tests are completed and work as I would expect.
> Setting complexity to medium since it requires changing a library.

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


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

Dan Florian reopened DNA-548:
-----------------------------



Reopening since the JcrSession.sessionId() is not matching up with the Changes.getContextId().

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

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

        

From jira-events at lists.jboss.org  Mon Nov 30 14:05:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 14:05:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <527921099.1259607929765.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-548:
-----------------------------------

The WorkspaceLockManager, JcrSession, and JcrWorkspace all use slightly different ExecutionContexts.  Now that IDs are associated with the context, we need to be more diligent about using the right one.

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

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

        

From jira-events at lists.jboss.org  Mon Nov 30 14:41:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 14:41:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <39880307.1259610090353.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-548:
-----------------------------------

Changed JcrWorkspace, JcrSession, and WorkspaceLockManager so that they use ExecutionContext more consistently. JcrWorkspace and JcrSession both share the exact same ExecutionContext instance, while WorkspaceLockManager was changed to expect the JcrSession in most of its methods so the lock manager can use the JcrSession's ExecutionContext in its operations.  (The latter also has the advantage of recording which sessions were performing the lock operations, since now the session's context is used for all lock operations.)

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

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

        

From jira-events at lists.jboss.org  Mon Nov 30 15:16:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 15:16:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-548) The Session That
 Graph Changes Originate From Should Be Available To The NetChangeObserver
In-Reply-To: <1620789066.1257436565827.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <449925405.1259612190295.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-548:
-----------------------------------

Found a few more cases where we were being inconsistent with ExecutionContext.

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

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

        

From jira-events at lists.jboss.org  Mon Nov 30 16:53:29 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 16:53:29 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Reopened: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <2068815669.1259618009856.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch reopened DNA-551:
-------------------------------



Found a couple of places where Location.isSame(Location) is still being used that should be Location.equals(Object), including several places in JavaDoc.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Johnny Verhaeg
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt, DNA-551-patch2.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 30 16:53:30 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 16:53:30 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Commented: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <539471766.1259618010034.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch commented on DNA-551:
-----------------------------------

Fixed a couple of calls to 'Location.isSame()' that should have been fixed earlier.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Johnny Verhaeg
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt, DNA-551-patch2.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.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 Nov 30 16:55:31 2009
From: jira-events at lists.jboss.org (Randall Hauch (JIRA))
Date: Mon, 30 Nov 2009 16:55:31 -0500 (EST)
Subject: [dna-issues] [JBoss JIRA] Resolved: (DNA-551) graph.Location's
 equals(Object) and hashCode() Methods Are Not Consistent
In-Reply-To: <2054300258.1258144159148.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
Message-ID: <537346880.1259618131799.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>


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

Randall Hauch resolved DNA-551.
-------------------------------

    Resolution: Done


Hopefully that is it, so marking as resolved for now.

> graph.Location's equals(Object) and hashCode() Methods Are Not Consistent
> -------------------------------------------------------------------------
>
>                 Key: DNA-551
>                 URL: https://jira.jboss.org/jira/browse/DNA-551
>             Project: DNA
>          Issue Type: Bug
>          Components: Graph
>    Affects Versions: 0.6
>            Reporter: Dan Florian
>            Assignee: Johnny Verhaeg
>            Priority: Blocker
>             Fix For: 0.7
>
>         Attachments: DNA-551-patch1.txt, DNA-551-patch2.txt
>
>
> Location.hashCode() and Location.equals(Object) need to be consistent. The current implementation of the base class and subclasses prevent logically equal locations (same path or same ID properties) from being used java.util.Map objects.
> It should be true that if one subtype of Location has the same path as a different subtype of Location, and only one of these objects has ID properties, those locations should be equal and should have the same hashCode.

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

        

