March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-489) check and complete NonTxConnectionManagerTestCase

by Stefano Maestri (JIRA)

check and complete NonTxConnectionManagerTestCase -------------------------------------------------- Key: JBJCA-489 URL: https://issues.jboss.org/browse/JBJCA-489 Project: IronJacamar Issue Type: Feature Request Reporter: Stefano Maestri Assignee: Stefano Maestri We need to complete this test case that currently just check getConnection. Moreover we need to move it and more generally refactor test cases packaging for core module -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-485) TestSuite: verify AdminObject deployment, obj types and properties

by Stefano Maestri (JIRA)

TestSuite: verify AdminObject deployment, obj types and properties ------------------------------------------------------------------ Key: JBJCA-485 URL: https://issues.jboss.org/browse/JBJCA-485 Project: IronJacamar Issue Type: Feature Request Reporter: Stefano Maestri Assignee: Stefano Maestri verify AdminObject deployment, obj types and properties. We only verify atm that annotated AdminObject class is correctly processed from an annotation point of view in org.jboss.jca.deployers.annotations.AnnotationsTestCase. testProcessAdministeredObject. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-479) Fine grained Metadata validation

by Stefano Maestri (JIRA)

Fine grained Metadata validation -------------------------------- Key: JBJCA-479 URL: https://jira.jboss.org/browse/JBJCA-479 Project: IronJacamar Issue Type: Feature Request Components: Common Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.Beta4 We need a way to validate metadata both created from parsers and from merging or annotations -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-484) make *.sh execute permission on in release package

by Jeff Zhang (JIRA)

make *.sh execute permission on in release package -------------------------------------------------- Key: JBJCA-484 URL: https://issues.jboss.org/browse/JBJCA-484 Project: IronJacamar Issue Type: Task Components: Build Affects Versions: 1.0.0.Beta3 Reporter: Jeff Zhang Assignee: Jeff Zhang svn/jbossas/projects/jboss-jca/trunk/build/ironjacamar-1.0.0.Beta4$ find . -name *sh | xargs ls -l -rw-r--r-- 1 jizhang jizhang 1562 2010-12-29 11:23 ./bin/run.sh -rw-r--r-- 1 jizhang jizhang 52 2010-12-29 11:23 ./doc/codegenerator/codegenerator.sh -rw-r--r-- 1 jizhang jizhang 462 2010-12-29 11:23 ./doc/validator/validator.sh go to -rwxr-xr-x -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-491) add docant document library into performance branch

by Jeff Zhang (JIRA)

add docant document library into performance branch --------------------------------------------------- Key: JBJCA-491 URL: https://issues.jboss.org/browse/JBJCA-491 Project: IronJacamar Issue Type: Task Components: Documentation, Performance Reporter: Jeff Zhang Assignee: Jeff Zhang -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-473) docant support (ant for jdocbook)

by Jeff Zhang (JIRA)

docant support (ant for jdocbook) --------------------------------- Key: JBJCA-473 URL: https://jira.jboss.org/browse/JBJCA-473 Project: IronJacamar Issue Type: Task Components: Documentation Reporter: Jeff Zhang Assignee: Jeff Zhang jdocbook has many good feature, but it has just maven plugin. I write a ant task for jdocbook, we can use it in our project -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBJCA-263) Support template replace for ds.xml

by Jeff Zhang (JIRA)

Support template replace for ds.xml ----------------------------------- Key: JBJCA-263 URL: https://jira.jboss.org/jira/browse/JBJCA-263 Project: JBoss JCA Issue Type: Feature Request Components: Core Reporter: Jeff Zhang Assignee: Jesper Pedersen template value like ${max.pool} could be replaced in the ds.xml -- 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

14 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (LOGBRIDGE-5) Unreferenced loggers retain their settings when log4j configuration changes

by David Lloyd (JIRA)

Unreferenced loggers retain their settings when log4j configuration changes --------------------------------------------------------------------------- Key: LOGBRIDGE-5 URL: https://issues.jboss.org/browse/LOGBRIDGE-5 Project: Log Bridge Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR2 Because the old loggers are not cleared first. All known loggers which were not reconfigured should have their level cleared as part of the update. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSER-123) StackOverflowError is suppressed

by Karl Brodowsky (JIRA)

StackOverflowError is suppressed -------------------------------- Key: JBSER-123 URL: https://issues.jboss.org/browse/JBSER-123 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Environment: win32 (Microsoft Windows [Version 6.0.6002]), JBoss 5.1.GA, Hibernate 3.3.1.GA Reporter: Karl Brodowsky Assignee: Clebert Suconic I am running JBoss with Hibernate and I am persisting objects that reference each other in a way that allows infinite recursion when following all references without keeping track of which instances have already been visited. I am getting a gigabyte of log-output and the app-server becomes unusable. Debugging reveals that this situation occurs during passivation (I can neither confirm nor exclude that it occurs in other situations as well). Debugging reveals that in method writeSlotWithMethod of RegularObjectPersister (line 127) an exception e is caught and wrapped in an IOException. In the case that I observed this was an InvocationTargetException that itself wraps an StackOverflowError. Without breakpoint a deep structure wrapping of a large number of exceptions with InvocationTargetException containing IOException containing InvocationTargetException occurs. The primary bug is that the stackOverflow occurs anyway, but I am assuming that that issue is already addressed by other bug reports. In this piece of code it is important that the InvocationTargetException is handled separately, unpacked and in case the target of the InvocationTargetException is already IOException, RunTimeException or Error it is rethrown as is without (ultimately endless) wrapping in IOException. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2241) Restore user's settings and portlets to default

by Brian Dill (JIRA)

Restore user's settings and portlets to default ----------------------------------------------- Key: JBPORTAL-2241 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2241 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.6 Final Reporter: Brian Dill Allow portal users to restore their portal to the original settings/portlets. Excerpt from discussion with Thomas Heute. "They could store the location of the reference as a portal object property of the copied page. And copy what exists for 'Copy this page to my dashboard' link. If the referenced page didn't change, they could then delete the current page, and copy the one referenced as portal object property." -- 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

14 years, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2011