[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3568:
----------------------------------
Priority: Major (was: Critical)
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.1.1
>
> Attachments: hello.zip, HelloWorldServlet.java
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3568:
----------------------------------
Fix Version/s: jbossws-cxf-4.1.1
(was: jbossws-cxf-4.2)
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Priority: Critical
> Fix For: jbossws-cxf-4.1.1
>
> Attachments: hello.zip, HelloWorldServlet.java
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3577) Turn RequestHandler and LifecycleHandler into singletons
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3577:
-------------------------------------
Summary: Turn RequestHandler and LifecycleHandler into singletons
Key: JBWS-3577
URL: https://issues.jboss.org/browse/JBWS-3577
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-integration, jbossws-native
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-4.1.1, jbossws-native-4.1.1
We currently create new instances of RequestHandler and LifecycleHandler for each endpoint of each deployment, but there's no real reason for that as they really have no status (or -in case of native- the status really belongs to the endpoint itself). We should have singletons there, to save memory and also considering the lookup of the implementation to use through SPIProviderResolver is possibly expensive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3576) Centralize ServerConfig retrieval
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3576:
-------------------------------------
Summary: Centralize ServerConfig retrieval
Key: JBWS-3576
URL: https://issues.jboss.org/browse/JBWS-3576
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-4.1.1
The same retrieval mechanism of the current ServerConfig implementation instance is repeated in multiple places in jbossws-common and jbossws-cxf codebase; most of them could be factored out in a centralized location (once the server integration classloader is set into the ClassLoaderProvider utility class)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Richard Opalka updated JBWS-3568:
---------------------------------
Attachment: HelloWorldServlet.java
Same context ('ws' in this case) can be published only once. I updated your servlet sample accordingly (see attachment).
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Priority: Critical
> Fix For: jbossws-cxf-4.2
>
> Attachments: hello.zip, HelloWorldServlet.java
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Richard Opalka updated JBWS-3568:
---------------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/3646
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Priority: Critical
> Fix For: jbossws-cxf-4.2
>
> Attachments: hello.zip
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3568:
----------------------------------
Fix Version/s: jbossws-cxf-4.2
> Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
> ----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3568
> URL: https://issues.jboss.org/browse/JBWS-3568
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes"
> Reporter: Magesh Bojan
> Priority: Critical
> Fix For: jbossws-cxf-4.2
>
> Attachments: hello.zip
>
>
> Deploying attached sample creates the following error:
> ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sample]] (ServerService Thread Pool -- 55) JBWEB000289: Servlet Hello threw load() exception: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint."ws.deployment"."org.jboss.servlet.hello.BaseWebService" is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:193)
> at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:131)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:123)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:102)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.servlet.hello.HelloWorldServlet.init(HelloWorldServlet.java:78) [classes:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final.jar:1.0.2.Final]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_30]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_30]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3378) JAXWS handlers (like JAXRPC handlers are) have to be executed in EJB component interceptor
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3378?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3378:
----------------------------------
Fix Version/s: jbossws-cxf-4.2
> JAXWS handlers (like JAXRPC handlers are) have to be executed in EJB component interceptor
> ------------------------------------------------------------------------------------------
>
> Key: JBWS-3378
> URL: https://issues.jboss.org/browse/JBWS-3378
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf, jbossws-integration
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-cxf-4.2
>
>
> JSR 109 - Version 1.3 - Chapter 6.2.2.4 Security
>
> Handlers associated with a Port component run after authorization has occurred and before the business logic
> method of the Service Implementation bean is dispatched to. For JAX-RPC or JAX-WS Service endpoints,
> Handlers run after the container has performed the security constraint checks associated with the servlet
> element that defines the Port component. For EJB based service implementations, Handlers run after method
> level authorization has occurred.
> JSR 109 - Version 1.3 - Chapter 6.2.2.5 Transactions
> Handlers run under the transaction context of the component they are associated with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3574?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3574:
--------------------------------------
Also passing against:
[supervoid][/home/ropalka/svn/jbossas/branches/JBPAPP_5_1]>svn info
Path: .
Working Copy Root Path: /home/ropalka/svn/jbossas/branches/JBPAPP_5_1
URL: https://svn.jboss.org/repos/jbossas/branches/JBPAPP_5_1
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 113905
Node Kind: directory
Schedule: normal
Last Changed Author: jcacek
Last Changed Rev: 113846
Last Changed Date: 2012-11-27 13:55:55 +0100 (Tue, 27 Nov 2012)
Note that I'm using latest JBossWS CXF & JBoss EAP 5x upstreams.
> SignEncryptGCMTestCase fails even if Bouncy Castle is installed
> ---------------------------------------------------------------
>
> Key: JBWS-3574
> URL: https://issues.jboss.org/browse/JBWS-3574
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-3.1.2
> Environment: JBoss Web Services - Stack CXF 3.1.2.SP12, Oracle JDK 1.7.0_09 with Bouncy Castle installed (both bcprov-ext-jdk15on-147.jar and bcprov-jdk15on-147.jar), RHEL 5 x86
> Reporter: Martin Vecera
> Assignee: Richard Opalka
> Attachments: TEST-org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.xml
>
>
> I run WS-CXF integration test suite against SOA-P 5.3.1 and I faces issues with security tests due to missing Bouncy Castle installation. After installing it, there is still a test that fails:
> java.lang.Exception: Please check that the Bouncy Castle provider is installed.
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:65)
> Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot encrypt data
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy38.sayHello(Unknown Source)
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:61)
> ... 30 more
> Caused by: org.apache.cxf.ws.policy.PolicyException: Cannot encrypt data
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.policyNotAsserted(AbstractBindingBuilder.java:283)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryption(AsymmetricBindingHandler.java:319)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:141)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:90)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:139)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:77)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> ... 32 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years