[jboss-jira] [JBoss JIRA] (WFLY-3657) Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046319#comment-13046319 ] 

Alessio Soldano commented on WFLY-3657:
---------------------------------------

I confirm this is a bug; basically, org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor is not considering @HandlerChain annotation that could be on service endpoint interfaces referenced by @WebService(endpointInterface="..." ) on endpoint implementations.
This is covered by JSR-181 spec, section 4.6.1:
"The @HandlerChain annotation MAY be present on the endpoint interface and service
implementation bean. The service implementation bean’s @HandlerChain is used if
@HandlerChain is present on both."

> Injection not working on JAXWS handlers specified with @HandlerChain on service endpoint interfaces
> ---------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3657
>                 URL: https://issues.jboss.org/browse/WFLY-3657
>             Project: WildFly
>          Issue Type: Bug
>          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.3.11#6341)