hi romain,
we can provide it for sure (or just a simple spi).
as you know, we always add useful parts once it makes sense (to add them).
regards,
gerhard
2017-10-05 11:04 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> Can we provide a way to handle it more naturally? @Named("mypool") could be
> nice if we dont have the pool in the map then we try to look it up as a
> bean? Nothing urgent but probably something to enrich since the manager is
> in impl so scope=runtime from our convention which doesnt help to integrate
> with it. wdyt?
>
>
> 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>
>
> 2017-10-05 10:08 GMT+02:00 Gerhard Petracek <gpetra...@apache.org>:
>
> > hi romain,
> >
> > just extend ThreadPoolManager and annotate your custom implementation
> with
> > @Specializes.
> >
> > regards,
> > gerhard
> >
> >
> >
> > 2017-10-04 11:18 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> >
> > > Hi guys,
> > >
> > > i saw that the @Futureable code moved to interceptor strategy which is
> > > probably good but I don't see anymore how to register a custom pool in
> > > the org.apache.deltaspike.core.impl.future.ThreadPoolManager. Was it
> > > dropped or moved somewhere else?
> > >
> > > 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>
> > >
> >
>
