October 2008 - dna-issues - Jboss List Archives

[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

[JBoss JIRA] Created: (DNA-217) Connector SPI should have protocol for cancelling operations

by Randall Hauch (JIRA)

Connector SPI should have protocol for cancelling operations ------------------------------------------------------------ Key: DNA-217 URL: https://jira.jboss.org/jira/browse/DNA-217 Project: DNA Issue Type: Task Components: Connectors, SPI Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.2 The Connector SPI needs a specific way for calls to the connector to be canceled. Currently, most of the methods throw InterruptedException, which is a painful (and confusing) way to handle it. This exception should be removed while the use of ProgressMonitor be added. Additionally, we may want to consider modifying the ProgressMonitor framework so that it's possible for it to threat Thread.interrupt() as a cancellation (whereby it would use that, in addition to the internal flag, to determine whether the monitor is canceled. This may require an additional method whereby the code checking "isCanceled()" acknowledges that it is canceling what it's doing (so that the ProgressMonitor can call Thread.interrupted() to clear the interrupted state). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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

1
4
0 / 0

[JBoss JIRA] Created: (DNA-233) create a sub maven module project for svn connector

by Serge Emmanuel Pagop (JIRA)

create a sub maven module project for svn connector --------------------------------------------------- Key: DNA-233 URL: https://jira.jboss.org/jira/browse/DNA-233 Project: DNA Issue Type: Sub-task Components: Connectors Affects Versions: 0.3 Reporter: Serge Emmanuel Pagop Assignee: Serge Emmanuel Pagop Priority: Minor Fix For: 0.3 create the maven module for svn connector named dna-connector-svn and also prepare some resources for some testcases -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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

1
2
0 / 0

[JBoss JIRA] Created: (DNA-181) Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context

by Johnny Verhaeg (JIRA)

Consolidate security, messages, and progress within the ExecutionContext and make framework consistent in its use and passing of this context --------------------------------------------------------------------------------------------------------------------------------------------- Key: DNA-181 URL: https://jira.jboss.org/jira/browse/DNA-181 Project: DNA Issue Type: Feature Request Components: API, SPI Affects Versions: 0.1 Reporter: Johnny Verhaeg Fix For: 0.2 We are already passing around an ExecutionContext to various parts of the DNA framework, and in some places a progress monitor that in turn contains problems encountered (as of DNA-75). We're now looking into security information that also needs to be passed around during login and execution, and it's now evident that a better way to handle all of these information types would be to consolidate all of it within the execution context and make it the common "token" that is consistently passed between all framework components, including the SPI. Messages, progress, security, etc., should always be dealt with in relation to a particular context, and contexts may be hierarchical in nature. For example, the messages, problems, and progress for a particular operation should be recorded in a manner that ties them to that operation's execution within whatever context it occurred, which will have been initiated as part of a broader context, that being either a higher-level or composite operation or, at the very least, within the context of the client's session. Recording information in this manner should make it easier to audit, debug, providing complex logging facilities, etc. "Problems" should be treated more generically as simply "Messages", allowing the framework much for flexibility to handle context-specific information, such as messages specific to an operation or executed command. The entire logging framework can then work off of these messages rather than leaving it to SPI implementors to determine when something should be logged, added as a problem/message, or both. The framework contains only a few other types of information, none of which should be dangerous to pass around, and any of which can be further protected if necessary via context wrappers that may, for instance, return immutable versions of that 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

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-244) Change support for problems to more generic messages

by Johnny Verhaeg (JIRA)

Change support for problems to more generic messages ---------------------------------------------------- Key: DNA-244 URL: https://jira.jboss.org/jira/browse/DNA-244 Project: DNA Issue Type: Sub-task Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-84) Use quotes consistently in I18n localization property files

by Randall Hauch (JIRA)

Use quotes consistently in I18n localization property files ----------------------------------------------------------- Key: DNA-84 URL: http://jira.jboss.com/jira/browse/DNA-84 Project: DNA Issue Type: Task Reporter: Randall Hauch Assigned To: Randall Hauch Priority: Minor Fix For: 0.2 We appear to be using single quotes and double quotes in our localization messages. Single quotes are used by MessageFormat (which we're not using), but we should use double quotes to be more consistent. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (DNA-241) Make a thread-safe progress monitor accessible from execution contexts

by Johnny Verhaeg (JIRA)

Make a thread-safe progress monitor accessible from execution contexts ---------------------------------------------------------------------- Key: DNA-241 URL: https://jira.jboss.org/jira/browse/DNA-241 Project: DNA Issue Type: Sub-task Affects Versions: 0.2 Reporter: Johnny Verhaeg Assignee: Johnny Verhaeg Fix For: 0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (DNA-243) Change (and move) XML Sequencer to use more general-purpose XML importer

by Randall Hauch (JIRA)

Change (and move) XML Sequencer to use more general-purpose XML importer ------------------------------------------------------------------------ Key: DNA-243 URL: https://jira.jboss.org/jira/browse/DNA-243 Project: DNA Issue Type: Task Components: Sequencers Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.3 The XmlSequencer is currently used as the XML importer. The importer will be changed (in DNA-242) to be a separate and more general-purpose class, but the XmlSequencer should be changed to use this more general importer component. Also, the XML sequencer should be made a regular sequencer project (under "extensions" directory). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues October 2008