[JBoss JIRA] (JBWS-3549) Web Service with EJB endpoint failed when Provider is implemented
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3549?page=com.atlassian.jira.plugin.... ]
Jim Ma updated JBWS-3549:
-------------------------
Fix Version/s: (was: jbossws-cxf-4.2)
Affects Version/s: (was: jbossws-cxf-4.1.0.Final)
> Web Service with EJB endpoint failed when Provider is implemented
> -------------------------------------------------------------------
>
> Key: JBWS-3549
> URL: https://issues.jboss.org/browse/JBWS-3549
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: Windows
> Reporter: Michael Abramov
> Assignee: Alessio Soldano
>
> The EJB web service created with implementation of Provider interface is failed :
> 19:51:38,451 ERROR [org.jboss.as.webservices.invocation.InvocationHandlerEJB3] (http--127.0.0.1-8080-1) Method invocation failed with exception: null: java.lang.IllegalStateException
> at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.getEJBMethod(InvocationHandlerEJB3.java:150)
> at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:121)
--
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
11 years, 4 months
[JBoss JIRA] (JBWS-3549) Web Service with EJB endpoint failed when Provider is implemented
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3549?page=com.atlassian.jira.plugin.... ]
Jim Ma updated JBWS-3549:
-------------------------
Fix Version/s: jbossws-cxf-4.2
Affects Version/s: jbossws-cxf-4.1.0.Final
> Web Service with EJB endpoint failed when Provider is implemented
> -------------------------------------------------------------------
>
> Key: JBWS-3549
> URL: https://issues.jboss.org/browse/JBWS-3549
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: jbossws-cxf-4.1.0.Final
> Environment: Windows
> Reporter: Michael Abramov
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.2
>
>
> The EJB web service created with implementation of Provider interface is failed :
> 19:51:38,451 ERROR [org.jboss.as.webservices.invocation.InvocationHandlerEJB3] (http--127.0.0.1-8080-1) Method invocation failed with exception: null: java.lang.IllegalStateException
> at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.getEJBMethod(InvocationHandlerEJB3.java:150)
> at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:121)
--
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
11 years, 4 months
[JBoss JIRA] (JBWS-3578) CLONE - Web Service with EJB endpoint failed when Provider is implemented
by Jim Ma (JIRA)
Jim Ma created JBWS-3578:
----------------------------
Summary: CLONE - Web Service with EJB endpoint failed when Provider is implemented
Key: JBWS-3578
URL: https://issues.jboss.org/browse/JBWS-3578
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Environment: Windows
Reporter: Jim Ma
Assignee: Alessio Soldano
The EJB web service created with implementation of Provider interface is failed :
19:51:38,451 ERROR [org.jboss.as.webservices.invocation.InvocationHandlerEJB3] (http--127.0.0.1-8080-1) Method invocation failed with exception: null: java.lang.IllegalStateException
at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.getEJBMethod(InvocationHandlerEJB3.java:150)
at org.jboss.as.webservices.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:121)
--
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
11 years, 4 months
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Magesh Bojan (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Magesh Bojan commented on JBWS-3568:
------------------------------------
If I reverse the PR, then only one Endpoint gets published.
> 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, HelloWorldServlet.java-fix
>
>
> 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
11 years, 4 months
[JBoss JIRA] (JBWS-3568) Registering endpoints with EndpointPublisher using same context results in DuplicateServiceException
by Magesh Bojan (JIRA)
[ https://issues.jboss.org/browse/JBWS-3568?page=com.atlassian.jira.plugin.... ]
Magesh Bojan reopened JBWS-3568:
--------------------------------
There is a regression after the PR. Now the new fixed Servlet shows this in the log{noformat}11:02:51,356 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /sample
11:02:51,372 INFO [org.jboss.ws.cxf.metadata] (ServerService Thread Pool -- 65) JBWS024061: Adding service endpoint metadata: id=HelloWebService
address=http://localhost:8080/ws/HelloWebService
implementor=org.jboss.servlet.hello.BaseWebService
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://test}HeyWebService
portName={http://test}HeyWebServicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelComponentViewName -> null]
11:02:51,419 INFO [org.jboss.ws.cxf.metadata] (ServerService Thread Pool -- 65) JBWS024061: Adding service endpoint metadata: id=HeyWebService
address=http://localhost:8080/ws/HeyWebService
implementor=org.jboss.servlet.hello.BaseWebService
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://test}HeyWebService
portName={http://test}HeyWebServicePort
wsdlLocation=null
mtomEnabled=false
properties=[org.jboss.as.webservices.metadata.modelComponentViewName -> null]
11:02:51,465 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (ServerService Thread Pool -- 65) Creating Service {http://test}HeyWebService from class org.jboss.servlet.hello.BaseWebService
11:02:51,497 INFO [org.apache.cxf.endpoint.ServerImpl] (ServerService Thread Pool -- 65) Setting the server's publish address to be http://localhost:8080/ws/HelloWebService
11:02:51,512 INFO [org.jboss.ws.cxf.deployment] (ServerService Thread Pool -- 65) JBWS024074: WSDL published to: file:/C:/ESB/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws.deployment/HeyWebService.wsdl
11:02:51,512 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (ServerService Thread Pool -- 65) Creating Service {http://test}HeyWebService from class org.jboss.servlet.hello.BaseWebService
11:02:51,528 INFO [org.apache.cxf.endpoint.ServerImpl] (ServerService Thread Pool -- 65) Setting the server's publish address to be http://localhost:8080/ws/HeyWebService
11:02:51,544 INFO [org.jboss.ws.cxf.deployment] (ServerService Thread Pool -- 65) JBWS024074: WSDL published to: file:/C:/ESB/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws.deployment/HeyWebService.wsdl{noformat}
Although the address and id are different, notice the port and service names are same.
> 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, HelloWorldServlet.java-fix
>
>
> 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
11 years, 4 months
[JBoss JIRA] (JBWS-3551) Extend UnifiedVirtualFile API with no-check findChild methods
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3551?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3551:
----------------------------------
Fix Version/s: jbossws-cxf-4.1.1
jbossws-native-4.1.1
(was: jbossws-cxf-4.2)
> Extend UnifiedVirtualFile API with no-check findChild methods
> -------------------------------------------------------------
>
> Key: JBWS-3551
> URL: https://issues.jboss.org/browse/JBWS-3551
> 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, jbossws-native-4.1.1
>
>
> The UnifiedVirtualFile abstraction in quite used for accessing file/resources in deployments. Most of the time, though, the lookup of unified virtual file children leads to nothing (the required resource is simply missing) and a localized IOException is thrown. In most scenarios, that's not an actual "error", the procedure just implies trying multiple locations, and the exception is trapped and in most cases not even logged.
> We need new flavors of findChild(String child) and getChildren() methods also accepting a boolean flag to suppress exception, log a message (if the log level is enabled) and return null / empty collection if nothing is found.
> The new methods are to then to be used for instance to speed-up the jbossws-common ResourceResolverImpl, which currently badly affects performances in the jbossws-cxf stack, being is used whenever the Apache CXF resource resolver manager is also used.
--
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
11 years, 4 months
[JBoss JIRA] (JBWS-3551) Extend UnifiedVirtualFile API with no-check findChild methods
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3551?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3551:
----------------------------------
Fix Version/s: (was: jbossws-native-4.1.1)
> Extend UnifiedVirtualFile API with no-check findChild methods
> -------------------------------------------------------------
>
> Key: JBWS-3551
> URL: https://issues.jboss.org/browse/JBWS-3551
> 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 UnifiedVirtualFile abstraction in quite used for accessing file/resources in deployments. Most of the time, though, the lookup of unified virtual file children leads to nothing (the required resource is simply missing) and a localized IOException is thrown. In most scenarios, that's not an actual "error", the procedure just implies trying multiple locations, and the exception is trapped and in most cases not even logged.
> We need new flavors of findChild(String child) and getChildren() methods also accepting a boolean flag to suppress exception, log a message (if the log level is enabled) and return null / empty collection if nothing is found.
> The new methods are to then to be used for instance to speed-up the jbossws-common ResourceResolverImpl, which currently badly affects performances in the jbossws-cxf stack, being is used whenever the Apache CXF resource resolver manager is also used.
--
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
11 years, 4 months
[JBoss JIRA] (JBWS-3573) Review Coverity reports for JBossWS projects
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/JBWS-3573?page=com.atlassian.jira.plugin.... ]
Richard Opalka commented on JBWS-3573:
--------------------------------------
10020 - we don't care about violations in tests
10027 - we don't care about violations in tests
10019 - ignoring default encoding issue for NullPrintStream - there's never written anything to that stream - no need to deal with encodings there
10039 - out of date - sources are not in sync with trunk
10038 - out of date - sources are not in sync with trunk
10037 - out of date - sources are not in sync with trunk
10032 - fixed - maxSize made volatile in MemoryBufferRecorder
10013 - this is by design, AbstractReferenceResolver is used only for fields & methods inspection
10033 - fixed - NPE
10025 - design decision to not to provide default for switch statement
10014 - according to method comment - this is needed because of some portability issues
10022 - fixed - tmpfile return value
10018 - fixed - method removed
10017 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10016 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10041 - we don't care about violations in tests
10053 - we don't care about violations in tests
10049 - we don't care about violations in tests
10040 - we don't care about violations in tests
10061 - fixed - ps leak
10051 - System.exit intentional (by design)
10048 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10060 - fixed ps leak
10050 - System.exit intentional (by design)
10047 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10046 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10059 - fixed ps leak
10055 - not implemented yet - probably will be in the future, thus leaving it as it is now
10045 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10058 - fixed ps leak
10054 - not implemented yet - probably will be in the future, thus leaving it as it is now
10044 - I'm affraid to touch this :( (encoding issue - until we have encoding tests in place)
10057 - ModulesTasks is used for testing purposes only - ignoring this issue
10056 - ModulesTasks is used for testing purposes only - ignoring this issue
10052 - ModulesTasks is used for testing purposes only - ignoring this issue
10043 - ModulesTasks is used for testing purposes only - ignoring this issue
10042 - ModulesTasks is used for testing purposes only - ignoring this issue
> Review Coverity reports for JBossWS projects
> --------------------------------------------
>
> Key: JBWS-3573
> URL: https://issues.jboss.org/browse/JBWS-3573
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: productization
> Reporter: Rostislav Svoboda
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.1.1, jbossws-native-4.1.1
>
>
> http://station5.brq.redhat.com:8080
> Analyzed trunks for:
> * JBossWS API
> * JBossWS SPI
> * JBossWS Common
> * JBossWS Common Tools
> * JBossWS CXF
> * JBossWS Native
--
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
11 years, 4 months