[jboss-jira] [JBoss JIRA] (WFLY-3194) ApplicationClient container can not use a declarative method to activate EJBClientInterceptors

[Wolf-Dieter Fink (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wolf-Dieter Fink updated WFLY-3194:
-----------------------------------

    Component/s: Application Client

    
> ApplicationClient container can not use a declarative method to activate EJBClientInterceptors
> ----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3194
>                 URL: https://issues.jboss.org/browse/WFLY-3194
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Application Client
>         Environment: appclient
>            Reporter: Wolf-Dieter Fink
>              Labels: application-scoped, ejb
>
> With the java services approach it is possible to add a client side interceptor by adding the services file META-INF/services/org.jboss.ejb.client.EJBClientInterceptor to activate the interceptor if the class is accessable.
> The file must be added to the client.jar in case of a simple standalone client.
> And to the ejb.jar if the interceptor is used inside a server application.
> For the appclient I expect that add this file to 
>   EAR/client.jar/META-INF/services
> will do the same.
> Nevertheless adding the file to ear/META_INF ear/ejb.jar/META-INF do not woth either.
> Also adding the class to the client.jar, as ear module or as server module with dependency did not work.
> All theses Interceptors can be used if the client Main method add this with the JBoss API.
> A working example can be found here 
>   https://github.com/wfink/jboss-eap-quickstarts/tree/application-client/app-client
> For the example with the services approach try
>   https://github.com/wfink/jboss-eap-quickstarts/tree/application-client-withServices/app-client

--
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