hi romain, not really. 1 interceptor could have n strategies as candidates (e.g. see TransactionStrategy for which we provide multiple implementations out-of-the-box). that's the whole concept. the marker interfaces is just to find all strategies in a project easily. we have it since 02/2011 (back then it was codi) and a lot of users are using it (during the dev. process) and i haven't heard about any concern (from users).
regards, gerhard 2018-04-24 19:31 GMT+02:00 Romain Manni-Bucau <[email protected]>: > Le 24 avr. 2018 19:18, "Gerhard Petracek" <[email protected]> a écrit : > > it was always just a marker-interface to list all interceptor-strategies > easily. > > > But if it is just interceptors, doesnt @Interceptor fulfills that already? > > My only concern is exposing it in api to user where it is actually a dead > interface. > > > regards, > gerhard > > > > 2018-04-24 13:47 GMT+02:00 Thomas Andraschko <[email protected] > >: > > > basically +1 > > but its still used currently > > > > > > 2018-04-23 11:46 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > > > Hi guys, > > > > > > Do we still need InterceptorStrategy? > > > > > > If not, can we deprecate it and remove it from our built-in > interceptors? > > > > > > Romain Manni-Bucau > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > <https://rmannibucau.metawerx.net/> | Old Blog > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > > > rmannibucau> | > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > > <https://www.packtpub.com/application-development/java- > > > ee-8-high-performance> > > > > > >
