2016-07-08 11:18 GMT+02:00 Gerhard Petracek <[email protected]>:
> hi romain, > > we could add an (additional) config-option to disable it. > > Issue is more about the default since it pops up when dropping DS. The deactivation itself can be done with the previous config. > with deltaspike v2 we can > - drop the entries in our beans.xml files > - remove GlobalInterceptorExtension (+ annotate the classes directly) > > +1 > regards, > gerhard > > > > 2016-07-08 0:42 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > Hello guys, > > > > thanks > > to org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension > > we promote our interceptors with a @Priority but if they are provided in > > beans.xml too we got warnings on some servers. > > > > Should we rework this logic or our packaging? > > > > wdyt? > > > > > > Side note: my workaround is: > > > > > > > deactivate.org.apache.deltaspike.core.impl.interceptor.GlobalInterceptorExtension > > = true > > org.apache.deltaspike.core.spi.activation.ClassDeactivator = > > org.apache.deltaspike.core.impl.activation.DefaultClassDeactivator > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> | JavaEE Factory > > <https://javaeefactory-rmannibucau.rhcloud.com> > > >
