[
https://issues.jboss.org/browse/JBTM-999?page=com.atlassian.jira.plugin.s...
]
Paul Robinson edited comment on JBTM-999 at 2/22/12 11:31 AM:
--------------------------------------------------------------
After talking to Alessio, we think the solution is to lookup the endpoint instance in a
SOAP handler and then delegate to the CDI interceptor. Alessio has some sample code for
doing this:
http://fpaste.org/nMOa/
The plan is to start out using getEndpointInstanceCXF(...). This is CXF specific, but
works for all web service calls (including @OneWay). JBossWS is/will be CXF only for the
foreseeable future, so not a problem. Once we have this working, Alessio will hide this
call behind an SPI, giving us a stack neutral way of looking up the endpoint. Alessio also
suggested that a JBossWS integration test be created to make sure this is not broken in
the future.
was (Author: paul.robinson):
After talking to Alessio, we think the solution is to lookup the endpoint instance in
a SOAP handler and then delegate to the CDI interceptor. Alesio has some sample code for
doing this:
http://fpaste.org/nMOa/
The plan is to start out using getEndpointInstanceCXF(...). This is CXF specific, but
works for all web service calls (including @OneWay). JBossWS is/will be CXF only for the
foreseeable future, so not a problem. Once we have this working, Alessio will hide this
call behind an SPI, giving us a stack neutral way of looking up the endpoint. Alessio also
suggested that a JBossWS integration test be created to make sure this is not broken in
the future.
Support plain old JAX-WS services in TXFramework
-------------------------------------------------
Key: JBTM-999
URL:
https://issues.jboss.org/browse/JBTM-999
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: TXFramework
Affects Versions: 5.0.0.M1
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
Currently the TXFramework only supports JAX-WS services that are implemented as EJBs.
This is because the TXFramework relies heavily on CDI. Plain old JAX-WS services don't
seem to be considered by the CDI implementation.
Need to find out of this is due to a limitation in JBossWS, or whether I missed something
when coding up my service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira