August 2018 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-2897) Unable to deploy Web services war file on jbossAs

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-2897?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-2897: --------------------------------------- [~krishnan.a.sampath], please understand that you're commenting on an issue that was last updated 8.5 yrs ago and talking about a JBoss AS and JDK that are not supported anymore. If you have a support contract, please get in touch with the right contact, otherwise simply evaluate upgrading to a recent version. > Unable to deploy Web services war file on jbossAs > -------------------------------------------------- > > Key: JBWS-2897 > URL: https://issues.jboss.org/browse/JBWS-2897 > Project: JBoss Web Services > Issue Type: Bug > Environment: Linux lhmdjbo1 2.6.18-164.9.1.el5 #1 SMP Wed Dec 9 03:30:34 EST 2009 s390x s390x s390x GNU/Linux,,,Red Hat Enterprise Linux Server release 5.4 (Tikanga) > Reporter: Anil Yeruva > Priority: Minor > > 15:05:18,537 ERROR [MainDeployer] Could not create deployment: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/ > org.jboss.wsf.spi.deployment.WSFDeploymentException: java.lang.NullPointerException > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.getWebservicesMetaData(ArchiveDeployerHook.java:138) > at org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPreJSE.isWebServiceDeployment(JAXRPCDeployerHookPreJSE.java:140) > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87) > at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79) > at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) > at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy45.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy9.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) > at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:417) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > : > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy5.deploy(Unknown Source) > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) > at org.jboss.Main.boot(Main.java:200) > at org.jboss.Main$1.run(Main.java:508) > at java.lang.Thread.run(Thread.java:811) > Caused by: > java.lang.NullPointerException > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.getWebservicesMetaData(ArchiveDeployerHook.java:128) > ... 79 more > 15:05:18,544 INFO [EARDeployer] Init J2EE application: file:/var/lib/jbossas/server/default/deploy/middleware.ear/ > 15:05:19,230 INFO [TomcatDeployer] deploy, ctxPath=/middleware, warUrl=.../deploy/middleware.ear/middleware.war/ > 15:05:19,382 INFO [EARDeployer] Started J2EE application: file:/var/lib/jbossas/server/default/deploy/middleware.ear/ > 15:05:19,383 ERROR [URLDeploymentScanner] Incomplete Deployment listing: > --- Incompletely deployed packages --- > org.jboss.deployment.DeploymentInfo@330474c { url=file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/ } > deployer: MBeanProxyExt[jboss.web:service=WebServer] > status: Deployment FAILED reason: java.lang.NullPointerException > state: FAILED > watch: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/WEB-INF/web.xml > altDD: null > lastDeployed: 1264449918167 > lastModified: 1216141210000 > mbeans: > org.jboss.deployment.DeploymentInfo@d90e20ef { url=file:/var/lib/jbossas/server/default/deploy/SDIear.ear/ } > deployer: org.jboss.deployment.EARDeployer@75277527 > status: Deployment FAILED reason: Could not create deployment: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/; - nested throwable: (org.jboss.wsf.spi.deployment.WSFDeploymentException: java.lang.NullPointerException) > state: FAILED > watch: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/META-INF/application.xml > altDD: null > lastDeployed: 1264449918167 > lastModified: 1216141210000 > mbeans: > Please help me regarding this issue.. > Note: When I deployed same application file in Websphere application server it's working good. > Thanks, > Anil Yeruva > ITS in Raleigh -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4136) Upgrade BouncyCastle to 1.60

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4136: ------------------------------------- Summary: Upgrade BouncyCastle to 1.60 Key: JBWS-4136 URL: https://issues.jboss.org/browse/JBWS-4136 Project: JBoss Web Services Issue Type: Component Upgrade Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.4.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-2897) Unable to deploy Web services war file on jbossAs

by Krishnan Aravamudan Sampath (JIRA)

[ https://issues.jboss.org/browse/JBWS-2897?page=com.atlassian.jira.plugin.... ] Krishnan Aravamudan Sampath commented on JBWS-2897: --------------------------------------------------- I face this issue with JBoss 5.1.0-GA and JRE 1.6.0_45. It fails to read the Web Services URI from the webservices.xml. Earliest attention is required for this problem. > Unable to deploy Web services war file on jbossAs > -------------------------------------------------- > > Key: JBWS-2897 > URL: https://issues.jboss.org/browse/JBWS-2897 > Project: JBoss Web Services > Issue Type: Bug > Environment: Linux lhmdjbo1 2.6.18-164.9.1.el5 #1 SMP Wed Dec 9 03:30:34 EST 2009 s390x s390x s390x GNU/Linux,,,Red Hat Enterprise Linux Server release 5.4 (Tikanga) > Reporter: Anil Yeruva > Priority: Minor > > 15:05:18,537 ERROR [MainDeployer] Could not create deployment: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/ > org.jboss.wsf.spi.deployment.WSFDeploymentException: java.lang.NullPointerException > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.getWebservicesMetaData(ArchiveDeployerHook.java:138) > at org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPreJSE.isWebServiceDeployment(JAXRPCDeployerHookPreJSE.java:140) > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87) > at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79) > at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) > at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy45.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy9.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) > at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:417) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > : > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:618) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy5.deploy(Unknown Source) > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) > at org.jboss.Main.boot(Main.java:200) > at org.jboss.Main$1.run(Main.java:508) > at java.lang.Thread.run(Thread.java:811) > Caused by: > java.lang.NullPointerException > at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.getWebservicesMetaData(ArchiveDeployerHook.java:128) > ... 79 more > 15:05:18,544 INFO [EARDeployer] Init J2EE application: file:/var/lib/jbossas/server/default/deploy/middleware.ear/ > 15:05:19,230 INFO [TomcatDeployer] deploy, ctxPath=/middleware, warUrl=.../deploy/middleware.ear/middleware.war/ > 15:05:19,382 INFO [EARDeployer] Started J2EE application: file:/var/lib/jbossas/server/default/deploy/middleware.ear/ > 15:05:19,383 ERROR [URLDeploymentScanner] Incomplete Deployment listing: > --- Incompletely deployed packages --- > org.jboss.deployment.DeploymentInfo@330474c { url=file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/ } > deployer: MBeanProxyExt[jboss.web:service=WebServer] > status: Deployment FAILED reason: java.lang.NullPointerException > state: FAILED > watch: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/WEB-INF/web.xml > altDD: null > lastDeployed: 1264449918167 > lastModified: 1216141210000 > mbeans: > org.jboss.deployment.DeploymentInfo@d90e20ef { url=file:/var/lib/jbossas/server/default/deploy/SDIear.ear/ } > deployer: org.jboss.deployment.EARDeployer@75277527 > status: Deployment FAILED reason: Could not create deployment: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/SDI.war/; - nested throwable: (org.jboss.wsf.spi.deployment.WSFDeploymentException: java.lang.NullPointerException) > state: FAILED > watch: file:/var/lib/jbossas/server/default/deploy/SDIear.ear/META-INF/application.xml > altDD: null > lastDeployed: 1264449918167 > lastModified: 1216141210000 > mbeans: > Please help me regarding this issue.. > Note: When I deployed same application file in Websphere application server it's working good. > Thanks, > Anil Yeruva > ITS in Raleigh -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated JBWS-4135: -------------------------------- Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/81, https://github.com/jbossws/jbossws-cxf/pull/82 (was: https://github.com/jbossws/jbossws-cxf/pull/81) > TCCL not set for JBoss WS deployment > ------------------------------------ > > Key: JBWS-4135 > URL: https://issues.jboss.org/browse/JBWS-4135 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf, jbossws-integration > Reporter: Brad Maxwell > Assignee: Ivo Studensky > Fix For: jbossws-cxf-5.2.4.Final > > > After JBEAP-5527 , the TCCL is no longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated JBWS-4135: -------------------------------- Assignee: Ivo Studensky (was: Alessio Soldano) > TCCL not set for JBoss WS deployment > ------------------------------------ > > Key: JBWS-4135 > URL: https://issues.jboss.org/browse/JBWS-4135 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf, jbossws-integration > Reporter: Brad Maxwell > Assignee: Ivo Studensky > Fix For: jbossws-cxf-5.2.4.Final > > > After JBEAP-5527 , the TCCL is no longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated JBWS-4135: -------------------------------- Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/81 > TCCL not set for JBoss WS deployment > ------------------------------------ > > Key: JBWS-4135 > URL: https://issues.jboss.org/browse/JBWS-4135 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf, jbossws-integration > Reporter: Brad Maxwell > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.4.Final > > > After JBEAP-5527 , the TCCL is no longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated JBWS-4135: ------------------------------- Description: After JBEAP-5527 , the TCCL is no longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. was: After JBEAP-5527 , the TCCL is not longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. > TCCL not set for JBoss WS deployment > ------------------------------------ > > Key: JBWS-4135 > URL: https://issues.jboss.org/browse/JBWS-4135 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf, jbossws-integration > Reporter: Brad Maxwell > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.4.Final > > > After JBEAP-5527 , the TCCL is no longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4135: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.4.Final > TCCL not set for JBoss WS deployment > ------------------------------------ > > Key: JBWS-4135 > URL: https://issues.jboss.org/browse/JBWS-4135 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf, jbossws-integration > Reporter: Brad Maxwell > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.4.Final > > > After JBEAP-5527 , the TCCL is not longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

by Brad Maxwell (JIRA)

Brad Maxwell created JBWS-4135: ---------------------------------- Summary: TCCL not set for JBoss WS deployment Key: JBWS-4135 URL: https://issues.jboss.org/browse/JBWS-4135 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf, jbossws-integration Reporter: Brad Maxwell Assignee: Alessio Soldano After JBEAP-5527 , the TCCL is not longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4134) Add mechanism for SecurityDomainContext cleanup

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4134?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4134: ---------------------------------- Assignee: Alessio Soldano > Add mechanism for SecurityDomainContext cleanup > ----------------------------------------------- > > Key: JBWS-4134 > URL: https://issues.jboss.org/browse/JBWS-4134 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.3.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2018