[jira] [Reopened] (SANDBOX-400) Switch the Base graph implementation underlying data structures to the thread safe version
[ https://issues.apache.org/jira/browse/SANDBOX-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reopened SANDBOX-400: looks like the Concurrent data structures downgraded the implementations, rolling back the modifications and creating the concurrent separated version Switch the Base graph implementation underlying data structures to the thread safe version -- Key: SANDBOX-400 URL: https://issues.apache.org/jira/browse/SANDBOX-400 Project: Commons Sandbox Issue Type: Improvement Components: Graph Reporter: Simone Tripodi Assignee: Simone Tripodi Even if it won't help on shielding from race conditions, switching to Concurrent* version of adapted data structures would make current Graph implementations more consistent when working in a multi-thread environment -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (DIGESTER-153) Add Constructor support to ObjectCreateRule
[ https://issues.apache.org/jira/browse/DIGESTER-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reopened DIGESTER-153: - sorry for bugging again on this, unfortunately there still is a case where the lazy loader fails ;( When classes have not the default empty constructor, CGLIB complains {code} java.lang.IllegalArgumentException: Superclass has no null constructors but no arguments were given at net.sf.cglib.proxy.Enhancer.emitConstructors(Enhancer.java:721) at net.sf.cglib.proxy.Enhancer.generateClass(Enhancer.java:499) at net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:216) at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377) at net.sf.cglib.proxy.Enhancer.create(Enhancer.java:285) at org.apache.commons.digester3.ObjectCreateRule.createLazyProxy(ObjectCreateRule.java:283) at org.apache.commons.digester3.ObjectCreateRule.begin(ObjectCreateRule.java:262) at org.apache.commons.digester3.Digester.startElement(Digester.java:1350) {code} you can test it simply by removing the empty constructor in {{org.apache.commons.digester3.TestBean}} Thanks a lot for your help in advance! Add Constructor support to ObjectCreateRule --- Key: DIGESTER-153 URL: https://issues.apache.org/jira/browse/DIGESTER-153 Project: Commons Digester Issue Type: Improvement Affects Versions: 3.2 Reporter: Simone Tripodi Assignee: Simone Tripodi Fix For: 3.2 As shown in the past, the stack method of Digester has some [limitations |http://markmail.org/message/wick27gw6n5weqk2] for fully support the Constructors - it basically cannot use elements in the body as constructor arguments - but it could support arguments extracted from attributes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (DIGESTER-153) Add Constructor support to ObjectCreateRule
[ https://issues.apache.org/jira/browse/DIGESTER-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reopened DIGESTER-153: - Unfortunately the LazyLoader still fails under certain circumstances: imagine an XML snippet like: {code} toplevel bean double=9.99 booleantrue/boolean float5.5/float /bean /toplevel {code} and the mapped bean is of the type {code} class MyBean { private float floatProperty; public MyBean( double doubleProperty, boolean booleanProperty ) ... } {code} what happens is that not all constructor parameters are correctly collected because the object is created in the {{begin()}} method when {{toplevel/bean}} matches. I don't know at that oint if it is possible creating a Stub that simply collects methods that can be called when invoking the {{end()}} method when {{toplevel/bean}} element is closed... Add Constructor support to ObjectCreateRule --- Key: DIGESTER-153 URL: https://issues.apache.org/jira/browse/DIGESTER-153 Project: Commons Digester Issue Type: Improvement Affects Versions: 3.2 Reporter: Simone Tripodi Assignee: Simone Tripodi Fix For: 3.2 As shown in the past, the stack method of Digester has some [limitations |http://markmail.org/message/wick27gw6n5weqk2] for fully support the Constructors - it basically cannot use elements in the body as constructor arguments - but it could support arguments extracted from attributes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (DIGESTER-153) Add Constructor support to ObjectCreateRule
[ https://issues.apache.org/jira/browse/DIGESTER-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reopened DIGESTER-153: - I just thought that using CGLIB to proxy Object creation, the {{ObjectCreationRule}} would fully support arguments coming from everywhere. Need some time to give tries. Add Constructor support to ObjectCreateRule --- Key: DIGESTER-153 URL: https://issues.apache.org/jira/browse/DIGESTER-153 Project: Commons Digester Issue Type: Improvement Affects Versions: 3.2 Reporter: Simone Tripodi Assignee: Simone Tripodi Fix For: 3.2 As shown in the past, the stack method of Digester has some [limitations |http://markmail.org/message/wick27gw6n5weqk2] for fully support the Constructors - it basically cannot use elements in the body as constructor arguments - but it could support arguments extracted from attributes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CHAIN-60) In certain build configurations unit tests fail with the following message: testDefault: Correct command count expected:17 but was:19
[ https://issues.apache.org/jira/browse/CHAIN-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reopened CHAIN-60: - Assignee: Simone Tripodi Patch not applied yet - issue still open ;) In certain build configurations unit tests fail with the following message: testDefault: Correct command count expected:17 but was:19 - Key: CHAIN-60 URL: https://issues.apache.org/jira/browse/CHAIN-60 Project: Commons Chain Issue Type: Bug Affects Versions: 1.2, 1.3, 2.0 Environment: {noformat} Operating system : Linux(unknown) Java Home version : java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Builder version : Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_AU, platform encoding: UTF-8 OS name: linux version: 2.6.32-31-server arch: amd64 Family: unix {noformat} Reporter: Elijah Zupancic Assignee: Simone Tripodi Fix For: 2.0 Attachments: chain-60.diff This bug occurs only on *some* build configurations. On my laptop and on the continuum build server it occurs every time, but when I try to replicate on different boxes with the exact same jvm and operating system, it is not repeatable. Moreover, this bug was happening in the 1.2 and 1.3 versions of chain and was no a result of changes introduced in 2.0. The full output of the bug is as follows: {noformat} /commons/proper/chain/trunk/pom.xml ( 1173817 ) /commons/proper/chain/trunk/src/assembly ( 1173817 ) /commons/proper/chain/trunk/src/main/assembly (from /commons/proper/chain/trunk/src/assembly:1172686) ( 1173817 ) /commons/proper/chain/trunk/src/test/java/org/apache/commons/chain/config/test-config-2.xml ( 1173817 ) /commons/proper/chain/trunk/src/test/java/org/apache/commons/chain/config/test-config.xml ( 1173817 ) /commons/proper/chain/trunk/src/test/resources ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache/commons ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache/commons/chain ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache/commons/chain/config ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache/commons/chain/config/test-config-2.xml (from /commons/proper/chain/trunk/src/test/java/org/apache/commons/chain/config/test-config-2.xml:1172686) ( 1173817 ) /commons/proper/chain/trunk/src/test/resources/org/apache/commons/chain/config/test-config.xml (from /commons/proper/chain/trunk/src/test/java/org/apache/commons/chain/config/test-config.xml:1172686) ( 1173817 ) Changed: simonetripodi @ Wed 21 Sep 2011 20:02:11 + Comment: parent reference updated to version 22 Files changed: /commons/proper/chain/trunk/pom.xml ( 1173818 ) Changed: simonetripodi @ Wed 21 Sep 2011 20:03:47 + Comment: added missing release metadata Files changed: /commons/proper/chain/trunk/pom.xml ( 1173819 ) Changed: simonetripodi @ Wed 21 Sep 2011 20:05:35 + Comment: 4 spaces replaced with 2 spaces, as generally adopted in commons Files changed: /commons/proper/chain/trunk/pom.xml ( 1173821 ) Dependencies Changes: No dependencies changed Build Definition: POM filename: pom.xml Goals: clean deploy Arguments: --batch-mode -Pjava-1.5 Build Fresh: false Always Build: false Default Build Definition: true Schedule: COMMONS_SCHEDULE Profile Name: Maven 2.2.1 Description: Default Maven 2 Build Definition (Java 1.5) Test Summary: Tests: 125 Failures: 1 Errors: 0 Success Rate: 99 Total time: 1.1960001 Test Failures: ConfigParserTestCase testDefault :