July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1357) JSR-88 support

by Brian Stansberry (JIRA)

JSR-88 support -------------- Key: AS7-1357 URL: https://issues.jboss.org/browse/AS7-1357 Project: Application Server 7 Issue Type: Task Reporter: Brian Stansberry Priority: Blocker Required for EE full profile certification. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (AS7-1318) CommonContainerConfiguration should contain managementAddress

by Rostislav Svoboda (JIRA)

CommonContainerConfiguration should contain managementAddress ------------------------------------------------------------- Key: AS7-1318 URL: https://issues.jboss.org/browse/AS7-1318 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.0.0.Final Reporter: Rostislav Svoboda Assignee: Andrew Rubinger Fix For: 7.1.0.Alpha1 CommonContainerConfiguration (org.jboss.as.arquillian.container) should contain managementAddress. AS7 can be configured to use different IP addresses for management and public interface. This could be problem for testing in remote mode. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (AS7-1174) Arquillian Containers can not be used as a general purpose Container Adapter due to a internal deployment registry

by Aslak Knutsen (JIRA)

Arquillian Containers can not be used as a general purpose Container Adapter due to a internal deployment registry ------------------------------------------------------------------------------------------------------------------ Key: AS7-1174 URL: https://issues.jboss.org/browse/AS7-1174 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.0.0.CR1 Reporter: Aslak Knutsen The CommonDeployableContainer keeps a registry of deployed deployments and their unique id in memory between deploy and undeploy. So unless the deployment you try to undeploy was deployed using the same instance of the Container it can't be undeployed. This cause problems for use of the Container in e.g. SeamForge or MavenPlugin, where the JVM is taken up and down between deploy/undeploy operations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-8739) org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase ---------------------------------------------------------- Key: JBAS-8739 URL: https://issues.jboss.org/browse/JBAS-8739 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: 6.0.0.Final All tests failing: testEarManagedComponentNames testMdb testSfsb testSlsb testSlsbLocal with: Component not found; no managed object with name "testEjb3xMetrics.jar/BEAN" in: [] Stacktrace junit.framework.AssertionFailedError: Component not found; no managed object with name "testEjb3xMetrics.jar/SLSB" in: [] at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.getAndTestManagedComponent(Ejb3MetricsUnitTestCase.java:453) at org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase.testSlsb(Ejb3MetricsUnitTestCase.java:255) These tests were passing with EJB 3 depchain 1.0.0-alpha-32 and failing with 1.0.0-alpha-34 (do not have results of these tests with 1.0.0-alpha-33) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8245) Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.profileservice.test.Ejb3MetricsUnitTestCase -------------------------------------------------------------- Key: JBAS-8245 URL: https://jira.jboss.org/browse/JBAS-8245 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3, Test Suite Reporter: Brian Stansberry Fix For: 6.0.0.Final http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-8834) org.jboss.test.web.test.Enc*UnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.Enc*UnitTestCase ---------------------------------------- Key: JBAS-8834 URL: https://issues.jboss.org/browse/JBAS-8834 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan org.jboss.test.web.test.EncXmlUnitTestCase.testAltRequestInfoServlet org.jboss.test.web.test.EncAnnotationsUnitTestCase.testAltRequestInfoServlet java.io.IOException: Expected reply code:200, actual=500 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8835) org.jboss.test.web.test.NamingServletUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.NamingServletUnitTestCase ------------------------------------------------- Key: JBAS-8835 URL: https://issues.jboss.org/browse/JBAS-8835 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.1 org.jboss.test.web.test.NamingServletUnitTestCase.testAppContextRoot org.jboss.test.web.test.NamingServletUnitTestCase.testGlobalContextRoot junit.framework.AssertionFailedError: FIXME: don't know what to expect naming!ROOT not bound -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8821) org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.ejb3.async.test.AsyncSessionBeanUnitTestCase ----------------------------------------------------------- Key: JBAS-8821 URL: https://issues.jboss.org/browse/JBAS-8821 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Shelly McGowan Assignee: Andrew Rubinger Fix For: TBD-6.x testLocalRemote: junit.framework.AssertionFailedError: Remote async call should be able to be cancelled testLocalCancel: junit.framework.AssertionFailedError: Local async call should be able to be cancelled -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-3149) ObjectTypeNodes are not handled correctly during Marshalling

by Mark Proctor (JIRA)

ObjectTypeNodes are not handled correctly during Marshalling ------------------------------------------------------------ Key: JBRULES-3149 URL: https://issues.jboss.org/browse/JBRULES-3149 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.3.0.Beta1 The OTN's are not handled correctly in marshalling. This is where the facthandles are added back into the OTN directly, it doesn't obey all interfaces and super classes. This is fixed in 5.3, but it'll need to be manuall backported to 5.2.x. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3101) Right Input triggering doesn't work for Queries

by Mark Proctor (JIRA)

Right Input triggering doesn't work for Queries ----------------------------------------------- Key: JBRULES-3101 URL: https://issues.jboss.org/browse/JBRULES-3101 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.3.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011