December 2009 - dna-issues - Jboss List Archives

[JBoss JIRA] Commented: (DNA-49) Sequence DDL files

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-49?page=com.atlassian.jira.plugin.... ] Barry LaFond commented on DNA-49: --------------------------------- Finished DdlParsers Test. Working on adding an integration test to verify DdlSequencer contribution. > Sequence DDL files > ------------------ > > Key: DNA-49 > URL: https://jira.jboss.org/jira/browse/DNA-49 > Project: DNA > Issue Type: Feature Request > Components: Sequencers > Reporter: Randall Hauch > Assignee: Barry LaFond > Fix For: 0.7 > > > Create a sequencer that parses DDL files and generates the subgraph representing the relational schema. Multiple dialects should be supported, including those for Oracle, MS SqlServer, PostgreSQL, MySQL, and others. Ideally this could be done with one sequencer (since most users/admins won't care about which dialect a particular file is; they'll just want it sequenced). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-569) Enhance Graph.java's Subgraph object toString() method to show recursive node structure and properties.

by Barry LaFond (JIRA)

Enhance Graph.java's Subgraph object toString() method to show recursive node structure and properties. ------------------------------------------------------------------------------------------------------- Key: DNA-569 URL: https://jira.jboss.org/jira/browse/DNA-569 Project: DNA Issue Type: Bug Components: Graph Affects Versions: 0.7 Reporter: Barry LaFond Fix For: 0.7 While developing DdlSequencer tests, a need developed obtain a sub-graph of the sequenced DDL file and operate on the resultant nodes and properties. However, the Sub-graph was difficult to debug because viewing child nodes and properties were difficult to see in values view. By constructing a more descriptive/recursive toString() value for subgraph, it would make debugging and testing much easier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (DNA-526) IllegalStateException calling TokenStream.canConsume(String str) after consuming all tokens via canConsume(String[])

by Barry LaFond (JIRA)

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 Reporter: Barry LaFond 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-541) Locking Implementation Does Not Support Timeouts

by Brian Carothers (JIRA)

Locking Implementation Does Not Support Timeouts ------------------------------------------------ Key: DNA-541 URL: https://jira.jboss.org/jira/browse/DNA-541 Project: DNA Issue Type: Bug Components: JCR Reporter: Brian Carothers Assignee: Brian Carothers Fix For: 0.7 The locking implementation does not provide a means of expiring stale or old locks (other than having the original owner unlock them). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (DNA-571) JcrObservationManager's Logic For Filtering Events Based On Path Is Incorrect For Property Events

by Dan Florian (JIRA)

JcrObservationManager's Logic For Filtering Events Based On Path Is Incorrect For Property Events ------------------------------------------------------------------------------------------------- Key: DNA-571 URL: https://jira.jboss.org/jira/browse/DNA-571 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 The logic for filtering events based on the event path is incorrect for property events. Instead of using the property's node's parent it needs to use the node path. Changes to JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-570) JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect

by Dan Florian (JIRA)

JcrObservationManager's Logic For Filtering Events Based On Node Types Is Incorrect ----------------------------------------------------------------------------------- Key: DNA-570 URL: https://jira.jboss.org/jira/browse/DNA-570 Project: DNA Issue Type: Bug Components: JCR Affects Versions: 0.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 0.7 The logic was determining if the Event node's primary type or mixins were equal to or derived from one or more given types. This was backwards and was allowing too many events to get through. The logic should check if the collection or one or more given types are equal to or derived from the primary type or mixins of the Event node. Changes to JcrNodeManager and JcrObservationManager will be needed. And once fixed, uncomment the appropriate tests in JcrObservationManagerTest and JcrTckTest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-577) Change the default model of the JPA connector from 'Basic' to 'Simple'

by Randall Hauch (JIRA)

Change the default model of the JPA connector from 'Basic' to 'Simple' ---------------------------------------------------------------------- Key: DNA-577 URL: https://jira.jboss.org/jira/browse/DNA-577 Project: DNA Issue Type: Task Components: Connectors Affects Versions: 0.7 Reporter: Randall Hauch Fix For: 0.7 A new 'Simple' model was recently added to the JPA storage connector (see DNA-546), and that model is apparently feature-complete and working well. This new model also has solved several issues related to certain JCR functionality (see DNA-546), so it appears to actually be more functional than the 'Basic' model. The JPA connector's default model should be changed to 'Simple'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (DNA-576) SImple JPA Model Does Not Support Transparent Referential Integrity

by Brian Carothers (JIRA)

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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (DNA-546) JCR Workspace and Session Imports Can Fail on JPA Connector

by Brian Carothers (JIRA)

JCR Workspace and Session Imports Can Fail on JPA Connector ----------------------------------------------------------- Key: DNA-546 URL: https://jira.jboss.org/jira/browse/DNA-546 Project: DNA Issue Type: Bug Components: Connectors, JCR Affects Versions: 0.6 Reporter: Brian Carothers Importing a set of nodes from an XML file will fail if one of the imported nodes has the same jcr:uuid as an existing node in the graph and removeExisting is true and the new location for the imported node and its prior location are both accessed through the same JPA connector. The DocumentViewImportTest is disabled (commented out) in the JPA integration test as a result of this defect. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
13
0 / 0

[JBoss JIRA] Created: (DNA-547) TCK Tests for Locking and Moving Nodes Fail for JPA Connector

by Brian Carothers (JIRA)

TCK Tests for Locking and Moving Nodes Fail for JPA Connector ------------------------------------------------------------- Key: DNA-547 URL: https://jira.jboss.org/jira/browse/DNA-547 Project: DNA Issue Type: Bug Components: Connectors, JCR Affects Versions: 0.6 Reporter: Brian Carothers Priority: Minor Two of the TCK tests for the optional locking feature fail on the JPA connector. As a result, the TCK tests for the locking feature have been removed from the JPA TCK integration test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues December 2009