You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Ron Smeral (JIRA)" <ji...@apache.org> on 2015/05/05 16:54:59 UTC
[jira] [Resolved] (DELTASPIKE-885) Static DeltaSpike configuration
should be easy to find in code base
[ https://issues.apache.org/jira/browse/DELTASPIKE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Smeral resolved DELTASPIKE-885.
-----------------------------------
Resolution: Fixed
> Static DeltaSpike configuration should be easy to find in code base
> -------------------------------------------------------------------
>
> Key: DELTASPIKE-885
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-885
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Reporter: Ron Smeral
> Assignee: Ron Smeral
> Priority: Minor
> Fix For: 1.4.0
>
>
> Currently the following interfaces are used for static configuration of DeltaSpike itself:
> * org.apache.deltaspike.testcontrol.impl.jsf.MyFacesTestBaseConfig
> * org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig
> * org.apache.deltaspike.scheduler.impl.SchedulerBaseConfig
> * org.apache.deltaspike.jsf.api.config.base.JsfBaseConfig
> * org.apache.deltaspike.core.api.config.base.CoreBaseConfig
> They all use {{TypedConfig}} but that doesn't seem like a sufficient identifier of DeltaSpike configuration.
> I suggest the following:
> * make all of the above mentioned interface implement a new marker interface {{DeltaSpikeBaseConfig}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)