[weld-issues] [JBoss JIRA] Closed: (WELD-735) Custom registered Contexts should be auto exposed as Beans

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Dec 7 11:47:00 EST 2010


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

Pete Muir closed WELD-735.
--------------------------

         Assignee: Pete Muir
    Fix Version/s:     (was: TBC)
       Resolution: Rejected


It would be far better for people to register their own beans exposing the context object, giving themselves control over the qualifiers and types used.

Using BeanBuilder from Solder this is as simple as:

new BeanBuilder(beanManager).readFromType(context.getClass()).create();

However if we build this into Weld then we have to introduce some configuration mechanism etc.

> Custom registered Contexts should be auto exposed as Beans
> ----------------------------------------------------------
>
>                 Key: WELD-735
>                 URL: https://jira.jboss.org/browse/WELD-735
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Scopes & Contexts
>    Affects Versions: 1.1.0.Beta1
>            Reporter: Aslak Knutsen
>            Assignee: Pete Muir
>            Priority: Minor
>
> In Beta-1 all Built-In Contexts are now auto registered as Beans in Weld, Beans which you can Inject where you need to. But Custom registered contexts are not. It's normal to do the registration of a context and the activation of a context on two different locations in the code base, and being able to inject the context where the activation should accure sounds a lot nicer then some awkward static field or simmilar.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list