[
https://issues.apache.org/jira/browse/DELTASPIKE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament resolved DELTASPIKE-955.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.1
> Built in class deactivator
> --------------------------
>
> Key: DELTASPIKE-955
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration, Core, Documentation
> Affects Versions: 1.4.1
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.5.1
>
>
> 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)
