Hi folks!
The ProjectStageProducer currently uses a static field, thus we only have 1
ProjectStage per EAR if DeltaSpike gets shipped in the EARs /lib folder
(opposed to each WAR).
I personally don't think this is a problem - au contráire, I think it makes
sense to have all WARs using the
+1
regards,
gerhard
2013/6/3 Romain Manni-Bucau rmannibu...@gmail.com
+1,
ear = 1 app so having 2 project stages would lead to stupid issues IMO
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*
For us DS v0.5 should be focused on the JSF module and particularly
on porting CODI scopes top get rid of CODI asap. ie:
- port the CODI Conversation and related scopes to DS (Group etc.)
- Enhance the WindowScope. (at least
https://issues.apache.org/jira/browse/DELTASPIKE-374 )
- port the
1+ For JSF stuff The bridge between JSF ExceptionHandler and DS Exception
Handling feels like pretty low hanging fruit? The implementation from Seam
Faces seems good to me, maybe use BeanManagerProvider to fire the event
instead.
1+ For JPA Generic Repository. But if it hinders the plan to
[
https://issues.apache.org/jira/browse/DELTASPIKE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673180#comment-13673180
]
Cody Lerum edited comment on DELTASPIKE-341 at 6/3/13 2:55 PM:
