[
https://issues.jboss.org/browse/JBIDE-17675?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-17675:
----------------------------------------
{quote}
All DeltaSpike Configuration objects implement this interface so they can be found more
easily. There is no other functionality implied with this interface.
DeltaSpike uses a _Typesafe Configuration_ approach. Instead of writing a properties file
or XML, you just implement one of the configuration interfaces which will then be picked
up as CDI bean. If there is already a default configuration for some functionality in
DeltaSpike, you can use @Specializes or @Alternative to change those.
{quote}
It means we should treat all implementation of DeltaSpikeConfig as CDI beans.
[~scabanovich] can we do it without introducing new problems with performance?
Validation error for subclasses of DeltaSpike JsfModuleConfig class
-------------------------------------------------------------------
Key: JBIDE-17675
URL:
https://issues.jboss.org/browse/JBIDE-17675
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi, cdi-extensions
Affects Versions: 4.2.0.Beta3
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.2.0.Beta3
1. Clone deltaspike repo:
{code}git clone
https://git-wip-us.apache.org/repos/asf/deltaspike.git{code}
2. Import *deltaspike/examples* as an existing Maven project into JBT.
3. Open
/deltaspike-jsf-playground/src/main/java/org/apache/deltaspike/playground/PlaygroundJsfModuleConfig.java
with Java Editor
4. There is a validation error:
*Managed bean class annotated @Specializes must directly extend the bean class of another
managed bean [JSR-299 ยง3.1.4]*
This error probably is a bug of CDI tools. We need to investigate it.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)