[
https://issues.apache.org/jira/browse/EXTCDI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek reopened EXTCDI-66:
------------------------------------
Assignee: Gerhard Petracek
> deactivatable default implementations
> -------------------------------------
>
> Key: EXTCDI-66
> URL: https://issues.apache.org/jira/browse/EXTCDI-66
> Project: MyFaces CODI
> Issue Type: New Feature
> Components: Core, JEE-BV1-Module, JEE-JPA1-Module, JEE-JSF12-Module,
> JEE-JSF20-Module, JSE-Message, JSE-Scripting, Trinidad Support
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 0.9.0
>
>
> it should be possible to deactivate classes which aren't pluggable via the
> codi-config and which are activated per default.
> esp. implementations which are configured via
> - faces-config
> - extension
> - bean.xml
> files.
> that allows e.g. to tweak codi in cases of features/implementations which are
> available out-of-the-box.
> convention for an implementation of ClassDeactivator:
> class-name: org.apache.myfaces.extensions.cdi.ClassDeactivator
> e.g.:
> package org.apache.myfaces.extensions.cdi;
> import org.apache.myfaces.extensions.cdi.core.api.AbstractClassDeactivator;
> public class ClassDeactivator extends AbstractClassDeactivator
> {
> protected void deactivateClasses()
> {
> addDeactivatedClass(...);
> addDeactivatedClass(...);
> }
> }
> or via vm param:
> -Dorg.apache.myfaces.extensions.cdi.ClassDeactivator=custom.ClassDeactivator
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
