November 2009 - dna-issues - Jboss List Archives

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

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-49?page=com.atlassian.jira.plugin.... ] 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-457) Add JSR-170 Locking Optional Feature

by Brian Carothers (JIRA)

Add JSR-170 Locking Optional Feature ------------------------------------ Key: DNA-457 URL: https://jira.jboss.org/jira/browse/DNA-457 Project: DNA Issue Type: Feature Request Components: JCR Affects Versions: 0.5 Reporter: Brian Carothers Fix For: 1.0 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

16 years, 5 months

2
16
0 / 0

[JBoss JIRA] Created: (DNA-558) DNA documentation problem

by Tom Ruff (JIRA)

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_f... 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

16 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (DNA-542) jcr:uuid Property in dna:lock Custom Type Needs To Be Renamed

by Brian Carothers (JIRA)

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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-555) Requirement for extracting indexed content during parsing using TokenStream

by Barry LaFond (JIRA)

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

16 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (DNA-557) Upgrade RESTEasy from 1.1.GA to 1.2.GA

by Randall Hauch (JIRA)

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...). 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

16 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-554) GraphSession does not correctly compute whether changes are in branch being saved or refreshed

by Randall Hauch (JIRA)

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

16 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-550) Add method to Graph to read a set of properties on multiple nodes

by Randall Hauch (JIRA)

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

16 years, 5 months

1
1
0 / 0

[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

by Randall Hauch (JIRA)

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

16 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-552) Support BETWEEN and NOT BETWEEN in WHERE clause of SQL language and abstract query model

by Randall Hauch (JIRA)

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

16 years, 5 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues November 2009