[EXTCDI-66] deactivatable default implementations

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Component/s: Core, JEE-BV1-Module, JEE-JPA1-Module, JEE-JSF12-Module, JEE-JSF20-Module, JSE-Message, JSE-Scripting, Trinidad Support
• Assignee: Gerhard Petracek
• Reporter: Gerhard Petracek
• Created: 29/Sep/10 09:49
• Updated: 15/Mar/11 23:52
• Resolved: 15/Mar/11 23:52

Description

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

Issue Links

• is related to: EXTCDI-71 ClassDeactivator configuration via JNDI
• relates to: EXTCDI-26 CDI Extensions should be disabled by default