[weld-dev] How to avoid classes being picked as managed beans?
Dan Allen
dan.j.allen at gmail.com
Wed Mar 9 16:04:04 EST 2011
On Wed, Mar 9, 2011 at 15:59, aalmiray <aalmiray at yahoo.com> wrote:
>
> mojavelinux wrote:
> >
> > Another approach is to use Weld's scanning configuration. That is a
> > non-portable solution, though, so you'd have weigh that. If I'm not
> > mistaken, that feature is being discussed for CDI 1.1.
> >
> >
> http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html/configure.html#d0e5767
> >
>
> Indeed. Those scan/exclusion features will come in handy. Hope they make it
> to CDI 1.1; in the meantime I'll resort to a custom Extension as a I need
> to
> filter out some beans by type too.
>
Here's the issue report for that proposal:
https://issues.jboss.org/browse/CDI-87
If you come across some feature/extension point that you think would help
improve CDI, please feel empowered to propose a change/addition to CDI.
You're experience using CDI in Griffon will give you a unique perspective.
> Thanks again for the quick response
>
You bet.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20110309/34a223fc/attachment.html
More information about the weld-dev
mailing list