[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
13 years, 6 months
[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
13 years, 6 months
[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
13 years, 6 months
[JBoss JIRA] Created: (AS7-935) NPE in BasicComponentInstance.getInstance
by Carlo de Wolf (JIRA)
NPE in BasicComponentInstance.getInstance
-----------------------------------------
Key: AS7-935
URL: https://issues.jboss.org/browse/AS7-935
Project: Application Server 7
Issue Type: Bug
Components: EE, EJB
Affects Versions: 7.0.0.CR1
Reporter: Carlo de Wolf
Priority: Critical
{noformat}
java.lang.NullPointerException
at org.jboss.as.ee.component.BasicComponentInstance.getInstance(BasicComponentInstance.java:82)
at org.jboss.as.ee.component.ViewDescription$ComponentDispatcherInterceptor.processInvocation(ViewDescription.java:201)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287)
at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:66)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287)
at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53)
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBAS-9403) Legacy JBoss Application Server 5
by Bruce Lis (JIRA)
Legacy JBoss Application Server 5
---------------------------------
Key: JBAS-9403
URL: https://issues.jboss.org/browse/JBAS-9403
Project: Legacy JBoss Application Server 6
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: Windows 2003, jdk 1.6.25, Seam 2.2, Jboss 5.1 GA
Reporter: Bruce Lis
I am novice developer and start using JBOSS as my web server for my new development. I have no issue during all project cycle except when it was deployed into production.
The only issue I am having that when I am deployed my new application for the first time it hangs out for 2-3 min until first page displayed. Then it works perfectly until the next reboot of the Windows server. There is nothing logged and no messages in the server.log. Please help
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months