September 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Created: (DNA-143) Create tests for child node definition counts and quoted strings in the grammar unit tests

by Dan Florian (JIRA)

Create tests for child node definition counts and quoted strings in the grammar unit tests ------------------------------------------------------------------------------------------ Key: DNA-143 URL: http://jira.jboss.com/jira/browse/DNA-143 Project: DNA Issue Type: Sub-task Reporter: Dan Florian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (DNA-144) Parser should throw exception if parsing of CND does not complete successfully

by Dan Florian (JIRA)

Parser should throw exception if parsing of CND does not complete successfully ------------------------------------------------------------------------------ Key: DNA-144 URL: http://jira.jboss.com/jira/browse/DNA-144 Project: DNA Issue Type: Sub-task Reporter: Dan Florian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (DNA-91) Implement node type management

by Randall Hauch (JIRA)

Implement node type management ------------------------------ Key: DNA-91 URL: http://jira.jboss.com/jira/browse/DNA-91 Project: DNA Issue Type: Sub-task Reporter: Randall Hauch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (DNA-114) Create MS Office file sequencer

by Randall Hauch (JIRA)

Create MS Office file sequencer ------------------------------- Key: DNA-114 URL: http://jira.jboss.com/jira/browse/DNA-114 Project: DNA Issue Type: Task Components: Sequencers Reporter: Randall Hauch Fix For: 0.2 Create a single sequencer that is capable of sequencing the MS Office files, including MS Word, MS Excel, and MS PowerPoint. All of the files' standard metadata (author, title, word count, page count, etc.) should be extracted, as should metadata specific to the different kinds of files. For example, the sequencer should extract all of the content of the Excel spreadsheets, while it should extract at least the slide titles (and ideally thumbnails). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (DNA-153) Add support for Microsoft Word document metadata

by Randall Hauch (JIRA)

Add support for Microsoft Word document metadata ------------------------------------------------ Key: DNA-153 URL: http://jira.jboss.com/jira/browse/DNA-153 Project: DNA Issue Type: Sub-task Components: Sequencers Reporter: Randall Hauch Fix For: 0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (DNA-88) Incorporate JCR TCK tests

by Randall Hauch (JIRA)

Incorporate JCR TCK tests ------------------------- Key: DNA-88 URL: http://jira.jboss.com/jira/browse/DNA-88 Project: DNA Issue Type: Sub-task Reporter: Randall Hauch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (DNA-174) Should ensure single versions required for 3rd-party dependencies within same classloader

by Johnny Verhaeg (JIRA)

Should ensure single versions required for 3rd-party dependencies within same classloader ----------------------------------------------------------------------------------------- Key: DNA-174 URL: http://jira.jboss.com/jira/browse/DNA-174 Project: DNA Issue Type: Task Components: Development Environment Affects Versions: 0.1 Reporter: Johnny Verhaeg Priority: Minor Fix For: 0.2 We should write a script that will be executed after the build and produce some reports indicating: - The list of 3rd-party dependencies, both direct & indirect - Any potential conflicts in dependency versions between projects or other dependencies - A tree of non-test-related dependencies by project Developers would then need only to add classloader knowledge into the mix when handling dependency version conflict resolution. It would be nice if the resulting reports could be accessed in the same manner as build & test results via Hudson. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (DNA-219) XML Sequencer should handle decoding names and values containing escape characters

by Johnny Verhaeg (JIRA)

XML Sequencer should handle decoding names and values containing escape characters ---------------------------------------------------------------------------------- Key: DNA-219 URL: https://jira.jboss.org/jira/browse/DNA-219 Project: DNA Issue Type: Bug Components: Sequencers Affects Versions: 0.2 Reporter: Johnny Verhaeg Fix For: 0.3 The XML Sequencer doesn't currently handle names and values that have been encoded to account for illegal characters in an XML document. For example, node names containing spaces, such as "My Documents", will be encoded as "My_x0020_Documents" in the XML file. See JCR spec sections 6.4.3 and 6.4.4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (DNA-231) org.jboss.dna.graph.xml.XmlSequencerTest failed with jdk 1.6 (not with jdk 1.5)

by Serge Emmanuel Pagop (JIRA)

org.jboss.dna.graph.xml.XmlSequencerTest failed with jdk 1.6 (not with jdk 1.5) ------------------------------------------------------------------------------- Key: DNA-231 URL: https://jira.jboss.org/jira/browse/DNA-231 Project: DNA Issue Type: Bug Components: SPI Affects Versions: 0.3 Environment: Testing on Mac OS x 10.5 with Java(TM) SE Runtime Environment (build 1.6.0_05-b13-120) Reporter: Serge Emmanuel Pagop Assignee: Randall Hauch Priority: Minor Fix For: 0.3 maybe a jdk 1.5 bug, because of the decode of the entity > - the output with with jdk 1.5 expected: "/a/b/c@title => /d/e/f" actual: "/a/b/c@title => /d/e/f" - the output with with jdk 1.6 ( the specific entity ">" is replaced with the corresponding character ">") expected: "/a/b/c@title => /d/e/f" actual: "/a/b/c@title = > /d/e/f" --- Error trace ------------------------------------------------------------------------------- Test set: org.jboss.dna.graph.xml.XmlSequencerTest ------------------------------------------------------------------------------- Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.147 sec <<< FAILURE! shouldSequenceElementContent(org.jboss.dna.graph.xml.XmlSequencerTest) Time elapsed: 0.506 sec <<< FAILURE! java.lang.AssertionError: Expected: is "/a/b/c@title => /d/e/f" got: "/a/b/c@title = > /d/e/f" at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.graph.xml.XmlSequencerTest.verifyString(XmlSequencerTest.java:225) at org.jboss.dna.graph.xml.XmlSequencerTest.shouldSequenceElementContent(XmlSequencerTest.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (DNA-223) XML sequencer does not properly handle namespaces of unqualified attributes

by Randall Hauch (JIRA)

XML sequencer does not properly handle namespaces of unqualified attributes --------------------------------------------------------------------------- Key: DNA-223 URL: https://jira.jboss.org/jira/browse/DNA-223 Project: DNA Issue Type: Bug Components: Sequencers Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 I've been looking at the XML sequencer behavior, and I was a little surprised to find out that it treats unqualified attributes (i.e., those without a namespace prefix) as inheriting the namespace of the parent element. For example, this XML document: <dna:system xmlns:dna="http://www.jboss.org/dna" xmlns:jcr="http://www.jcp.org/jcr/1.0">  <dna:sources> <sourceA name="Cars" dna:classname="org.jboss.dna.connector.inmemory.InMemoryRepositorySource" retryLimit="3" /> <sourceB name="Aircraft" dna:classname="org.jboss.dna.connector.inmemory.InMemoryRepositorySource" /> </dna:sources> </dna:system> is imported so that the "retryLimit" attribute is turned into a "dna:retryLimit" property. That property, however, should use the default namespace. I'm not sure whether this was intended, but I don't believe this behavior is correct. Yes, unqualified child elements do inherit the namespace of their parent, but attributes do not. According to the spec (http://www.w3.org/TR/xml-names/#defaulting), emphasis mine: "The scope of a default namespace declaration extends from the beginning of the start-tag in which it appears to the end of the corresponding end-tag, excluding the scope of any inner default namespace declarations. In the case of an empty tag, the scope is the tag itself. "A default namespace declaration applies to all unprefixed element names within its scope. Default namespace declarations do not apply directly to attribute names; the interpretation of unprefixed attributes is determined by the element on which they appear. "If there is a default namespace declaration in scope, the expanded name corresponding to an unprefixed element name has the URI of the default namespace as its namespace name. If there is no default namespace declaration in scope, the namespace name has no value. The namespace name for an unprefixed attribute name always has no value. In all cases, the local name is local part (which is of course the same as the unprefixed name itself)." Unfortunately, none of the examples in the spec seem to show the behavior for attributes. But here are a few links that seem to agree with my interpretation: http://www.twoscomplement.com/2008/03/16/xml-attribute-namespaces/ http://annevankesteren.nl/2005/03/null-namespace -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues September 2008