[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15520961#comment-15520961
 ] 

John D. Ament edited comment on DELTASPIKE-1206 at 9/25/16 3:12 PM:
--------------------------------------------------------------------

Good idea Mark.  However, what do we do if something doesn't work? From what I 
remember, OWB older versions are generally sensitive to the contents of 
{{beans.xml}}, in so much that CDI 1.1 scan tags cause it to crash.  In the 
past, we have discussed and agreed to make a DS 2.0 that targets CDI 2.0.  See 
also, e.g. 
https://lists.apache.org/thread.html/5d9baec12e1340a38c01453924570660bb25ff56e9539ae28d0ecdf3@1460035517@%3Cdev.deltaspike.apache.org%3E
 and our May board report 
https://cwiki.apache.org/confluence/display/DeltaSpike/DeltaSpike_BoardReport_2016-05


was (Author: johndament):
Good idea Mark.  However, what do we do if something doesn't work? From what I 
remember, OWB older versions are generally sensitive to the contents of 
{{beans.xml}}, in so much that CDI 1.1 scan tags cause it to crash.  In the 
past, we have discussed and agreed to make a DS 2.0 that targets CDI 2.0.  See 
also, e.g. 
https://lists.apache.org/thread.html/5d9baec12e1340a38c01453924570660bb25ff56e9539ae28d0ecdf3@1460035517@%3Cdev.deltaspike.apache.org%3E

> support for CDI 2.0 <trim/> feature
> -----------------------------------
>
>                 Key: DELTASPIKE-1206
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1206
>             Project: DeltaSpike
>          Issue Type: Bug
>    Affects Versions: 1.7.1
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.7.2
>
>
> CDI 2.0 will add support for only picking up beans with an explicit scope 
> annotation. This reduced the memory footprint while also speeding up the 
> bootstrapping.
> See https://issues.jboss.org/browse/CDI-420
> We should add this annotation to our beans.xml and verify that we still work. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to