[
https://issues.jboss.org/browse/WFLY-3657?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on WFLY-3657:
---------------------------------------
Sorry, I didn't have time yet to figure out where the bug actually is, however it
comes from the @HandlerChain not being specified on the service endpoint implementation
class (but on the service endpoint interface). I need to verify if the specs actually say
something on this, but it's likely a bug. You can workaround the problem by adding
@HandlerChain(file = "MessagingServicePortType_handler.xml") in your
MessagingServiceEndpointImpl .
JAXWS handlers do not support injection
---------------------------------------
Key: WFLY-3657
URL:
https://issues.jboss.org/browse/WFLY-3657
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 8.1.0.Final
Environment: Ubuntu 12.04
JDK 1.8.0_11
Reporter: Thomas Kriechbaum
Assignee: Alessio Soldano
Attachments: jaxws-handler-war.zip, wildfly-test-soapui-project.xml
According to the JavaEE spec JAXWS-handlers should support injection (@Inject, @EJB),
@PostConstruct and @PreDestroy.
In my test case (top-down approach, handler class is defined within *_handler.xml)
@PostCunstruct works, but managed beans (CDI, EJB) are not injected via @Inject or @EJB.
Possible workaround for EJBs: manual JNDI-lookup within @PostConstruct method. For
CDI-managed beans you have to lookup the BeanManager and load the desired bean yourself.
It seems, that this issue should have been addressed by WFLY-2362. But it is still does
not work.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)