You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2010/09/29 11:49:33 UTC

[jira] Created: (EXTCDI-66) deactivatable default implementations

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


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.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (EXTCDI-66) deactivatable default implementations

Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/EXTCDI-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved EXTCDI-66.
------------------------------------

    Fix Version/s: 1.0.0-SNAPSHOT
       Resolution: Fixed

> 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
>             Fix For: 1.0.0-SNAPSHOT
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.