June 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-500) rhq code merge

by Jeff Zhang (JIRA)

rhq code merge -------------- Key: JBJCA-500 URL: https://issues.jboss.org/browse/JBJCA-500 Project: IronJacamar Issue Type: Task Components: Management Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta4 from http://jopr-ironjacamar-plugin.googlecode.com/svn/trunk -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBJCA-77) Verify OSGi information in all manifests

by Jesper Pedersen (JIRA)

Verify OSGi information in all manifests ---------------------------------------- Key: JBJCA-77 URL: https://jira.jboss.org/jira/browse/JBJCA-77 Project: JBoss JCA Issue Type: Task Components: Common, Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.0.0.Beta1 Verify that the OSGi information in all the MANIFEST.MF files are correct. This information needs to be kept in sync from this point on. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (AS7-958) resource-adapters from standalone.xml loose metadata in detyped model

by Stefano Maestri (JIRA)

resource-adapters from standalone.xml loose metadata in detyped model --------------------------------------------------------------------- Key: AS7-958 URL: https://issues.jboss.org/browse/AS7-958 Project: Application Server 7 Issue Type: Bug Reporter: Stefano Maestri Assignee: Stefano Maestri -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8044) Make it easier to configure boot logging file

by jaikiran pai (JIRA)

Make it easier to configure boot logging file --------------------------------------------- Key: JBAS-8044 URL: https://jira.jboss.org/browse/JBAS-8044 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Logging Affects Versions: 6.0.0.M3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 6.0.0.M4 As explained in the referenced forum thread, it would be a lot easier to configure JBoss AS boot logging, if the logging.properties file is placed outside the run.jar. Please refer to the referenced forum thread for more details. -- 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

15 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBEE-75) Provide JAXWS api that uses AS7 module classloading

by Alessio Soldano (JIRA)

Provide JAXWS api that uses AS7 module classloading --------------------------------------------------- Key: JBEE-75 URL: https://issues.jboss.org/browse/JBEE-75 Project: JBoss JavaEE APIs Issue Type: Feature Request Reporter: Alessio Soldano Assignee: Shelly McGowan Our version of JAXWS api uses the original mechanisms for detecting the javax.xml.ws.spi.Provider class to use and create a new instance of. On AS7 we need to hide our implementations from the client runtime classpath; as a result of that we can't "pollute" the thread context classloader with the jbossws / cxf / etc. impl jars, so the JAXWS api Provider impl detection (that is based upon service loader) won't work properly. Moreover, there's likely to be a requirement for supporting the option of users overriding the JAXWS provider impl to use in a given deployment. So, our jaxws api should be able (at least) to dynamically load the jbossws jaxws client implementation module (without affecting the TCCL) and use that for resolving the javax.xml.ws.spi.Provider to use. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-3068) The ResourceType should support more extensions for the same type

by Marco Piraccini (JIRA)

The ResourceType should support more extensions for the same type ----------------------------------------------------------------- Key: JBRULES-3068 URL: https://issues.jboss.org/browse/JBRULES-3068 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.2.0.CR1 Reporter: Marco Piraccini Assignee: Mark Proctor Priority: Minor If I try to get the reource type using: String resourceName = "test.bpmn2" ResourceType = ResourceType.determineResourceType(resourceName); ...the resource type is not correctly detected, since only ONE default extension is supported (the BPMN2 type is related to the ".bpmn" extension). The ResourceType should have one default extansions and a list of supported extensions fo r the same type. If so, the ResourceType.BPMN2 declaration should be: /** jBPM BPMN2 Language */ public static final ResourceType BPMN2 = addResourceTypeToRegistry( "BPMN2","jBPM BPMN2 Language","bpmn", "bpmn2" ); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6185) JBoss MBeans in JConsole no longer works

by jaikiran pai (JIRA)

JBoss MBeans in JConsole no longer works ----------------------------------------- Key: JBAS-6185 URL: https://jira.jboss.org/jira/browse/JBAS-6185 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-5.0.0.CR2 Environment: JBossAS-5 CR2, Sun Java 1.5, Windows 2003 Reporter: jaikiran pai Assignee: Dimitris Andreadis Displaying of JBoss MBeans in JConsole as explained here http://www.jboss.org/community/docs/DOC-10521 , no longer works because of the classpath issue. Maybe related to the refactoring of org\jboss\system\server\jmx\* classes into jboss-system-jmx.jar in JBoss-5. More details about this issue can be found in the linked forum thread. -- 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, 1 month

11
23
0 / 0

[JBoss JIRA] Created: (JBRULES-1699) BRMS: Cannot easily remove data when creating a test scenario

by Jaroslaw Kijanowski (JIRA)

BRMS: Cannot easily remove data when creating a test scenario ------------------------------------------------------------- Key: JBRULES-1699 URL: https://jira.jboss.org/jira/browse/JBRULES-1699 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I create a test scenario and add a fact in the Given section. If I want to remove it, I have to add a field. Then two "minus" signs appear, on for the field and one for the whole fact. Same for the Expect section and globals. -- 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, 1 month

5
12
0 / 0

[JBoss JIRA] Created: (AS7-965) Implement EJB 3 Security

by Carlo de Wolf (JIRA)

Implement EJB 3 Security ------------------------ Key: AS7-965 URL: https://issues.jboss.org/browse/AS7-965 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: Carlo de Wolf Assignee: Darran Lofthouse Priority: Critical Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (AS7-859) On same named private lifecycle callbacks the super class callback is not called

by Carlo de Wolf (JIRA)

On same named private lifecycle callbacks the super class callback is not called -------------------------------------------------------------------------------- Key: AS7-859 URL: https://issues.jboss.org/browse/AS7-859 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Priority: Critical {noformat} diff --git a/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBChild.java b/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SF index 7f32869..97fe239 100644 --- a/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBChild.java +++ b/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBChild.java @@ -37,7 +37,7 @@ public class SFSBChild extends SFSBParent { public static boolean childPostConstructCalled = false; @PostConstruct - public void child() { + private void postConstruct() { childPostConstructCalled = true; Assert.assertTrue(SFSBParent.parentPostConstructCalled); Assert.assertTrue(InterceptorParent.parentPostConstructCalled); diff --git a/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBParent.java b/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/S index d356784..e8d13c4 100644 --- a/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBParent.java +++ b/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/ejb/interceptor/lifecycle/order/SFSBParent.java @@ -33,7 +33,7 @@ public class SFSBParent { public static boolean parentPostConstructCalled = false; @PostConstruct - public void parent() { + private void postConstruct() { parentPostConstructCalled = true; Assert.assertTrue(InterceptorChild.childPostConstructCalled); Assert.assertTrue(InterceptorParent.parentPostConstructCalled); {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
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 June 2011