You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2015/08/17 03:05:45 UTC
[jira] [Updated] (DELTASPIKE-955) Built in class deactivator
[ https://issues.apache.org/jira/browse/DELTASPIKE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John D. Ament updated DELTASPIKE-955:
-------------------------------------
Description:
Add a built in ClassDeactivator that maybe reads from apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I noticed was that there's no built in support for deactivation (via plain configuration). If look at https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems like one of the key features missing is to add a property, e.g.
{code}
deactivate.fqcn=true
{code}
Which would deactivate that class. Seems like a cool native deactivator that we could bundle in by default, but still activate via config.
was:
Add a built in ClassDeactivator that maybe reads from apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I noticed was that there's no built in support for deactivation (via plain configuration). If look at https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems like one of the key features missing is to add a property, e.g.
```
deactivate.fqcn=true
```
Which would deactivate that class. Seems like a cool native deactivator that we could bundle in by default, but still activate via config.
> Built in class deactivator
> --------------------------
>
> Key: DELTASPIKE-955
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.4.1
> Reporter: John D. Ament
>
> Add a built in ClassDeactivator that maybe reads from apache-deltaspike.properties
> Today I was reimplementing DS for the data module. One of the things I noticed was that there's no built in support for deactivation (via plain configuration). If look at https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems like one of the key features missing is to add a property, e.g.
> {code}
> deactivate.fqcn=true
> {code}
> Which would deactivate that class. Seems like a cool native deactivator that we could bundle in by default, but still activate via config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)