You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2011/03/21 16:42:05 UTC

[jira] [Reopened] (OWB-532) create a new BeanManager#isInUse()

     [ https://issues.apache.org/jira/browse/OWB-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg reopened OWB-532:
-------------------------------


we can imo effectively kill JSFUtil#isOwbApplication() and all other usages of OpenWebBeansConfiguration#PROPERTY_OWB_APPLICATION now, isn't?

> create a new BeanManager#isInUse()
> ----------------------------------
>
>                 Key: OWB-532
>                 URL: https://issues.apache.org/jira/browse/OWB-532
>             Project: OpenWebBeans
>          Issue Type: New Feature
>          Components: Lifecycle
>    Affects Versions: 1.0.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.1.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Sometimes it's useful to know if OWB really got used from an application. Depending on this we could implement performance tweaks, like e.g. disabling the WebBeansELResolver for non-CDI apps.
> This would be very usefull in EE scenarios if the OWB jars are available in the classpath but CDI doesn't get used by a WebApp.
> I'll just separate BeanManagerImpl#addBean() into a 'public' version for standard beans and a #addInternalBean for adding BeanManagerBean and stuff.
> #addBean() will set a isInUse = true; whereas addInternalBean will not touch this flag.

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