November 2008 - dna-issues - Jboss List Archives

[JBoss JIRA] Closed: (DNA-201) Provide a facility for clients to obtain context-level traces/logs of activity

by Randall Hauch (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-201?page=com.atlassian.jira.plugin... ] Randall Hauch closed DNA-201. ----------------------------- Verified this issue has been resolved. Transitioning to 'closed' state. > Provide a facility for clients to obtain context-level traces/logs of activity > ------------------------------------------------------------------------------ > > Key: DNA-201 > URL: https://jira.jboss.org/jira/browse/DNA-201 > Project: DNA > Issue Type: Feature Request > Components: API, Graph > Reporter: Randall Hauch > Assignee: Randall Hauch > Fix For: 0.2 > > > It's desirable to allow a client to submit a request and be able to then obtain a log of events/activities that occurred while processing/fulfilling that request. The log should allow the times to be displayed relative to the starting point, making it very easy for the user to see when and how long each event/activity required. This information is also completely specific to the actions involved in handling the request, and would not include any messages involved in handling other requests. -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-251) Upgrade JBoss Cache to 2.2.1GA

by Randall Hauch (JIRA)

Upgrade JBoss Cache to 2.2.1GA ------------------------------ Key: DNA-251 URL: https://jira.jboss.org/jira/browse/DNA-251 Project: DNA Issue Type: Thirdparty Change Components: Connectors Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.3 JBoss Cache has released 2.2.1GA, which is a patch fix over the version we're using (2.2.0GA). Upgrade the JBoss Cache Connector to use 2.2.1GA. (There is also 3.0.0CR1, but that's a major upgrade that includes API changes that are not compatible with our JBoss Cache connector.) -- 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

17 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (DNA-249) Document how to create a custom connector

by Randall Hauch (JIRA)

Document how to create a custom connector ----------------------------------------- Key: DNA-249 URL: https://jira.jboss.org/jira/browse/DNA-249 Project: DNA Issue Type: Task Components: Connectors, Documentation Affects Versions: 0.3 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Blocker Fix For: 0.3 Section 5.4 of the DNA 0.2 Reference Guide (http://www.jboss.org/file-access/default/members/dna/freezone/docs/0.2/ma...) is not filled out, pending the redesign of the requests. Since this work is now finished, we need to write this section. -- 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

17 years, 5 months

1
1
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

17 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

17 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (DNA-248) Simplify the ActivityMonitor framework

by Randall Hauch (JIRA)

Simplify the ActivityMonitor framework -------------------------------------- Key: DNA-248 URL: https://jira.jboss.org/jira/browse/DNA-248 Project: DNA Issue Type: Task Components: Common Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.3 The ActivityMonitor framework (formerly named ProgressMonitor) is pretty complicated and difficult to use (or at least requires too much code to use properly). Plus, it doesn't really have the ability to capture a contextual history of activities/tasks. The amount of work and % complete really seems useful only for a UI and asynchronous monitoring capability, so that seem inappropriate here. This framework should be simplified to support the main use cases, especially as its supposed to be used for allowing connectors to know the requests have been canceled (see DNA-217). These include: - ability to determine if a task has been cancelled - ability to record the duration and completion status of tasks and subtasks - ability to record problems the occurred during tasks -- 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

17 years, 5 months

1
2
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

17 years, 5 months

1
2
0 / 0

[JBoss JIRA] Updated: (DNA-36) Federate content from SVN and other SCM systems

by Serge Emmanuel Pagop (JIRA)

[ https://jira.jboss.org/jira/browse/DNA-36?page=com.atlassian.jira.plugin.... ] Serge Emmanuel Pagop updated DNA-36: ------------------------------------ Fix Version/s: 0.4 (was: 0.3) Affects Version/s: 0.4 move to 0.4 > Federate content from SVN and other SCM systems > ----------------------------------------------- > > Key: DNA-36 > URL: https://jira.jboss.org/jira/browse/DNA-36 > Project: DNA > Issue Type: Feature Request > Components: Connectors > Affects Versions: 0.4 > Reporter: Randall Hauch > Assignee: Serge Emmanuel Pagop > Priority: Minor > Fix For: 0.4 > > > Create a connector for the federation engine that contributes and exposes content stored in a source control management (SCM) system into the federated repository. This would enable integration of files managed by SVN (or CVS, etc.) to be accessible via JCR. -- 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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (DNA-246) org.jboss.dna.common.util.DateUtilTest failed with failed with jdk1.5.0_16 and jdk1.6.0_10

by Sergiy Litsenko (JIRA)

org.jboss.dna.common.util.DateUtilTest failed with failed with jdk1.5.0_16 and jdk1.6.0_10 ------------------------------------------------------------------------------------------ Key: DNA-246 URL: https://jira.jboss.org/jira/browse/DNA-246 Project: DNA Issue Type: Bug Components: Common Affects Versions: 0.3 Environment: Maven version: 2.0.9 Java version: 1.5.0_16, 1.6.0_10 OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows" [user.timezone]=[Australia/Sydney] Reporter: Sergiy Litsenko Test set: org.jboss.dna.common.util.DateUtilTest ------------------------------------------------------------------------------- Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec <<< FAILURE! shouldConvertDateToStringAndBack(org.jboss.dna.common.util.DateUtilTest) Time elapsed: 0.016 sec <<< FAILURE! java.lang.AssertionError: Expected: is <Sun Feb 03 14:22:49 EST 2008> got: <Sun Feb 03 13:22:49 EST 2008> at org.junit.Assert.assertThat(Assert.java:502) at org.junit.Assert.assertThat(Assert.java:492) at org.jboss.dna.common.util.DateUtilTest.shouldConvertDateToStringAndBack(DateUtilTest.java:57) 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:585) 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:585) 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

17 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (DNA-247) Remove DateUtil class and StringUtil.readableString(...) methods

by Randall Hauch (JIRA)

Remove DateUtil class and StringUtil.readableString(...) methods ---------------------------------------------------------------- Key: DNA-247 URL: https://jira.jboss.org/jira/browse/DNA-247 Project: DNA Issue Type: Task Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Fix For: 0.3 The DateUtil class provides some of the same functionality that is already available in Joda Time, which is being used by 'dna-graph'. Since this class is used very little (really, just by the tests and by StringUtil.readableString methods), we should just remove the DateUtil class. Also, by ensuring that Property.toString() returns a readable string, and that the Value classes all have readable toString() methods, then we can use List.toString(), Set.toString(), Property.toString(), and Map.toString(). The toString() method on arrays is crappy, but this can easily be fixed by using "Arrays.asList(array).toString()". This means that we can then delete the StringUtil.readableString(...) 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

17 years, 5 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

dna-issues November 2008