[JBoss JIRA] Created: (JBWS-2728) Review JBossWS EJB integration
by Richard Opalka (JIRA)
Review JBossWS EJB integration
-------------------------------
Key: JBWS-2728
URL: https://jira.jboss.org/jira/browse/JBWS-2728
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-integration
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1
We're depending on EJB real deployers.
We need to investigate whether we really
need to depend on these EJB deployers.
Maybe using JBoss meta data will could sufficient?
Some time ago also Adrian Brock wrote (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4059197#4059197):
---
Even after this, there are lots of issues about whether webservices should be
depending on things like ejb3 at all. It should certainly have access to its metadata for
deployment purposes, which is one of the reasons we have started a
"metadata" project so projects can share each others models.
---
The only possible problem that comes to my mind is
whether we're able to implement JBossWS injections
without depending on EJB real deployers?
--
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
12 years, 11 months
[JBoss JIRA] Created: (JBWS-2882) Give setMTOMEnabled higher priority for clients
by Darran Lofthouse (JIRA)
Give setMTOMEnabled higher priority for clients
-----------------------------------------------
Key: JBWS-2882
URL: https://jira.jboss.org/jira/browse/JBWS-2882
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.3.0
Presently JBossWS clients call setMTOMEnabled to indicate if MTOM should be enabled for the call, however JBossWS then scans the known types for an @XmlMimeType annotation to decide if the call is eligible for MTOM.
The MTOM optimisation however applies to all binary types and not just the ones annotated with @XmlMimeType. The call to setMTOMEnabled should be sufficient to enable MTOM without requiring the check for @XmlMimeType
--
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
13 years
[JBoss JIRA] Created: (JBWS-3088) Failures/regressions with WSTF Scenario 3 (JAXWS + WSA) intreop tests on AS trunk/CXF and AS 6.0.0.M3/Native
by Andrew Dinn (JIRA)
Failures/regressions with WSTF Scenario 3 (JAXWS + WSA) intreop tests on AS trunk/CXF and AS 6.0.0.M3/Native
------------------------------------------------------------------------------------------------------------
Key: JBWS-3088
URL: https://jira.jboss.org/browse/JBWS-3088
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-native
Affects Versions: jbossws-native-3.3.1, jbossws-cxf-3.3.1
Reporter: Andrew Dinn
The WSTF interop test scenarios include two scenarios for checking WS interopability, SC002 and Sc003:
http://www.wstf.org/docs/scenarios/sc002/sc002.xml
http://www.wstf.org/docs/scenarios/sc003/sc003.xml
The first tests basic JaxWS functionality. The second tests JaxWS with WSA functionality.
We have two implementations which both previously worked on AS 4 and AS 5.0.1 using JBossWS Native. For historical reasons the code for both tests is located in the TS repo:
http://anonsvn.jboss.org/repos/labs/labs/jbosstm/workspace/interop/WSTFSC...
I updated these in response to JBWS-3069 to try so as to make it possible to run them on
i) AS 6.0.0.M3 using WS-Native
ii) the current AS trunk using WS-CXF and including CXF 2.2.9 patched the fixes supplied for JBWS-3069
There are regressions for four of the eight Sc003 Asynchronous test cases on 6.0.0.M3/Native i.e. tests 3, 4, 7 and 8
There are failures for seven of these eight test cases on trunk/CXF i.e. test 2, ... 7
The eight Async tests in our implementation check what happens when a JaxWS request is provided with a non-null/anonymous FaultTo and ReplyTo address in various combinations of cases. These are now a subset of the cases defined in the test spec. In particular we always supply both ReplyTo and FaultTo (they always identify the same response/fault handling service). The combinations of cases we implement are:
1 MEP= OneWay, Exception=No, MU=no
2 MEP= OneWay, Exception=Yes, MU=no
3 MEP= RPC, Exception=No, MU=no
4 MEP= RPC, Exception=Yes, MU=no
5 MEP= OneWay, Exception=No, MU=yes
6 MEP= OneWay, Exception=Yes, MU=yes
7 MEP= RPC, Exception=No, MU=yes
8 MEP= RPC, Exception=Yes, MU=yes
Thes cases are explained as follows:
MEP:
The service implements a one way message which merely saves an input value for later use. It also implements an RPC style message which accepts an input value and returns a response. This field indicates which request is made.
Exception:
Depending on the value of an input parameter to the service request the service implementation bean will either complete correctly or throw a WebServiceException. This field determines which behaviour is employed in the test.
MU:
The request may include a MustUnderstand header which will not be understood. The service is not expected to understand this header so the WS stack should return a MustUnderstand fault in cases where MU is yes and it is appropriate to return a fault.
The tests are now slightly out sync with the latest test spec which no longer defines Fault dispatch for OneWay messages when ReplyTo or FaultTo is specified. This is a shame as XTS sends OneWay requests which use a MU header for the transaction context and needs to know when the other end cannot understand this header. Anyway, these tests now have different outcomes and it needs to be decided whether this is important to us or not.
The outcomes expected by the tests (and met on 5.0.1) are
1) No fault or reply returned to response endpoint
2) "FaultingNotify" Fault dispatched to response endpoint
3) Result dispatched to response endpoint, no result or fault on back channel
4) "Server" Fault with "FaultingNotify" fault string dispatched to response endpoint, no result or fault on back channel
5) "MustUnderstand" fault dispatched to response endpoint
6) "MustUnderstand" fault dispatched to response endpoint, no result or fault on back channel 87) "MustUnderstand" fault dispatched to response endpoint, no result or fault on back channel
7) "MustUnderstand" fault dispatched to response endpoint, no result or fault on back channel
The actual results for trunk/CXF are
1) as expected
2) No fault dispatched
3) Result dispatched on back channel
4) "Server" fault dispatched to response endpoint but with incorrect Action
5) No fault dispatched to response endpoint
6) No fault dispatched to response endpoint
7) "MustUnderstand" fault dispatched to response endpoint but with incorrect Action
8) "MustUnderstand" fault dispatched to response endpoint but with incorrect Action
The actual results for 6.0.0.M3/Native are
1) as expected
2) as expected
3) Result dispatched on back channel
4) Client side unmarshalling exception " Unsupported content type: text/html"
5) as expected
6) as expected
7) Client side unmarshalling exception " Unsupported content type: text/html"
8) Client side unmarshalling exception " Unsupported content type: text/html"
It may be that the tests need revising or modifying to cover more/different scenarios in the test spec so we can do a more full check of JaxWS interoperability. Whatever is done with them they really need to be kept up to date with the WS releases. The client needs to be run regularly against its own service implementation on the trunk CXF and Native releases to make sure our releases are at least internally consistent with expectations. . This could easily be automated via a hudson job as has been done for the XTS unit tests.
I think the job of maintaining, running and monitoring these tests internally needs to be taken over by the WS team. I am still very happy to install and check the Sc002/3 web app on the public JBossTS server used for interop testing where we expose the Sc007 XTS interop test service and client.
--
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
13 years, 4 months
[JBoss JIRA] Created: (JBWS-3026) Injecting EJB into Webservice via @EJB(mappedName="MyBean/remote")
by Jens Mander (JIRA)
Injecting EJB into Webservice via @EJB(mappedName="MyBean/remote")
------------------------------------------------------------------
Key: JBWS-3026
URL: https://jira.jboss.org/jira/browse/JBWS-3026
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-native
Affects Versions: jbossws-native-3.2.2, jbossws-cxf-3.2.2
Environment: JBossAS 5.1
Reporter: Jens Mander
Situation: two different projects (bean and webservice-project)
First projet (Bean)
@Stateless
@Remote(MyBeanRemote.class)
@Local(MyBeanLocal.class)
public class MyBean implements MyBeanRemote, MyBeanLocal {
@PersistenceContext
EntityManager em;
/**
* Default constructor.
*/
public MyBean() {
}
....
}
Second project (webservice)
@SOAPBinding(style = Style.RPC)
@WebService(serviceName = "MyService", portName = "MyServicePort", wsdlLocation = "/WEB-INF/wsdl/MyService.wsdl")
public class MyServiceImpl implements MyService {
@EJB(mappedName="MyBean/remote")
MyBean bean;
...
}
Deploying causes no problems but injecting the beaninstance into the webservice while instanciating the service fails with:
java.net.URISyntaxException: Illegal character in path at index 35: file:/C:/Entwicklung/jboss-5.1.0.GA Native/server/default/data/wsdl/MyService.war/MyService.wsdl
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at java.net.URL.toURI(Unknown Source)
at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.setOperationMetaData(MessageContextJAXWS.java:142)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:179)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
11:32:25,328 ERROR [InjectionException] Cannot inject field annotated with @EJB annotation: de.hd.bean.MyBean de.hd.produktservice.MyServiceImpl.psr
org.jboss.ejb3.common.resolvers.spi.UnresolvableReferenceException: Could not resolve reference [EJB Reference: beanInterface 'de.hd.bean.MyBean', beanName '', mappedName 'MyBean/remote'] for DeploymentUnit AbstractVFSDeploymentContext@2840278{vfsfile:/C:/Entwicklung/jboss-5.1.0.GA%20Native/server/default/deploy/MyService.war/}
at org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver.resolveEjb(FirstMatchEjbReferenceResolver.java:73)
at org.jboss.webservices.integration.injection.EJBBeanReferenceResolver.resolveField(EJBBeanReferenceResolver.java:88)
at org.jboss.wsf.common.injection.resolvers.AbstractReferenceResolver.resolve(AbstractReferenceResolver.java:80)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:361)
at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:111)
at org.jboss.wsf.common.invocation.InvocationHandlerJAXWS.onEndpointInstantiated(InvocationHandlerJAXWS.java:75)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.getTargetBean(AbstractInvocationHandlerJSE.java:81)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:119)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:222)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
11:32:25,343 ERROR [InvocationHandlerJAXWS] Method invocation failed with exception: Cannot create endpoint instance:
java.lang.IllegalStateException: Cannot create endpoint instance:
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.getTargetBean(AbstractInvocationHandlerJSE.java:85)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:119)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:222)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.wsf.common.injection.InjectionException: Cannot inject field annotated with @EJB annotation: de.hd.bean.MyBean de.hd.produktservice.MyServiceImpl.psr
at org.jboss.wsf.common.injection.InjectionException.rethrow(InjectionException.java:106)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:367)
at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:111)
at org.jboss.wsf.common.invocation.InvocationHandlerJAXWS.onEndpointInstantiated(InvocationHandlerJAXWS.java:75)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.getTargetBean(AbstractInvocationHandlerJSE.java:81)
... 28 more
Caused by: org.jboss.ejb3.common.resolvers.spi.UnresolvableReferenceException: Could not resolve reference [EJB Reference: beanInterface 'de.hd.bean.MyBean', beanName '', mappedName 'MyBean/remote'] for DeploymentUnit AbstractVFSDeploymentContext@2840278{vfsfile:/C:/Entwicklung/jboss-5.1.0.GA%20Native/server/default/deploy/MyService.war/}
at org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver.resolveEjb(FirstMatchEjbReferenceResolver.java:73)
at org.jboss.webservices.integration.injection.EJBBeanReferenceResolver.resolveField(EJBBeanReferenceResolver.java:88)
at org.jboss.wsf.common.injection.resolvers.AbstractReferenceResolver.resolve(AbstractReferenceResolver.java:80)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:361)
... 31 more
11:32:25,359 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.IllegalStateException: Cannot create endpoint instance:
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.getTargetBean(AbstractInvocationHandlerJSE.java:85)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:119)
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:222)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:502)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:299)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:206)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.wsf.common.injection.InjectionException: Cannot inject field annotated with @EJB annotation: de.hd.bean.MyBean de.hd.produktservice.MyServiceImpl.psr
at org.jboss.wsf.common.injection.InjectionException.rethrow(InjectionException.java:106)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:367)
at org.jboss.wsf.common.injection.InjectionHelper.injectResources(InjectionHelper.java:111)
at org.jboss.wsf.common.invocation.InvocationHandlerJAXWS.onEndpointInstantiated(InvocationHandlerJAXWS.java:75)
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.getTargetBean(AbstractInvocationHandlerJSE.java:81)
... 28 more
Caused by: org.jboss.ejb3.common.resolvers.spi.UnresolvableReferenceException: Could not resolve reference [EJB Reference: beanInterface 'de.hd.bean.MyBean', beanName '', mappedName 'MyBean/remote'] for DeploymentUnit AbstractVFSDeploymentContext@2840278{vfsfile:/C:/Entwicklung/jboss-5.1.0.GA%20Native/server/default/deploy/MyService.war/}
at org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver.resolveEjb(FirstMatchEjbReferenceResolver.java:73)
at org.jboss.webservices.integration.injection.EJBBeanReferenceResolver.resolveField(EJBBeanReferenceResolver.java:88)
at org.jboss.wsf.common.injection.resolvers.AbstractReferenceResolver.resolve(AbstractReferenceResolver.java:80)
at org.jboss.wsf.common.injection.InjectionHelper.injectEJBAnnotatedAccessibleObjects(InjectionHelper.java:361)
... 31 more
Looking up the bean via JNDI works perfectly with;
Context ctx = new InitialContext();
MyBeanRemote psr = (MyBeanRemote) ctx.lookup("MyBean/remote");
Deploying the projects bundelt in one ear-file works also.
--
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
13 years, 4 months
[JBoss JIRA] Created: (JBWS-2192) Asynchronous calls not thread safe
by Thomas Diesler (JIRA)
Asynchronous calls not thread safe
----------------------------------
Key: JBWS-2192
URL: http://jira.jboss.com/jira/browse/JBWS-2192
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Thomas Diesler
Fix For: jbossws-native-3.0.3
Darran sais:
I am currently looking at a support case where the customer is getting a number of errors with asynchronous JAX-WS invocations using a AsyncHandler.
I am running a couple of test cases against the two EAP releases and I am able to reproduce the behaviour that the customer is seeing but I just quickly wanted to double check what should be thread safe.
I have an async method on the SEI that returns a Future instance and takes an AsyncHandler as a parameter: -
@WebMethod(operationName = "lookup")
public Future<?> lookupAsync(final Person person,
AsyncHandler<TelephoneNumber> handler);
This pattern seems to suggest that after the call has been made any further interaction will be with the Future instance or the handler which then makes it look as though the Port is free to service other requests.
However if I submit multiple requests using the same Port then the outgoing requests start to get mixed up.
Should it be possible to re-use the same Port / SEI Proxy for multiple calls without worries of messages being mixed up?
I would have thought if the Port was not supposed to be re-used the get methods for the response would be on the Port instance and not need to use this returned interface.
I have attached the client I am using to reproduce the errors.
Creating a new Port for each request does overcome this issue but they are trying to avoid this especially as the existing Port should have passed the last request off to another thread for processing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months