-
1. Re: In test mode testing Weld loads wrong beans.xml
alesj Mar 3, 2013 5:41 PM (in response to shay_matasaro)This is a problem of ShrinkwrapClassLoader not filtering system classpath properly.
I remember a JIRA issue about it, but cannot find it atm.
-
2. Re: In test mode testing Weld loads wrong beans.xml
shay_matasaro Mar 3, 2013 8:42 PM (in response to alesj)This is pretty basic functionality , Is there a way to work around it rather then deleting the main beans.xml every time I run tests ?
-
3. Re: In test mode testing Weld loads wrong beans.xml
alesj Mar 4, 2013 3:37 AM (in response to shay_matasaro)1 of 1 people found this helpfulIs there a way to work around it rather then deleting the main beans.xml every time I run tests ?
Perhaps rename both, so they have non-CDI specific names as originals,
only to have proper CDI names once in Shrinkwrap archive.
-
4. Re: In test mode testing Weld loads wrong beans.xml
bmajsak Mar 4, 2013 4:15 AM (in response to shay_matasaro)Or try some managed container instead to have full control what's deployed.
-
5. Re: In test mode testing Weld loads wrong beans.xml
shay_matasaro Mar 4, 2013 1:59 PM (in response to alesj)Even after renaming both files Weld stil manages to find some bean.xml , it sees classes from the current jar but not my correct beans.xml, I am going to add some logging to weld core to see whats going on.
regarding managed container , I only need CDI support , is there a really light weight managed container for that?
Shay
-
6. Re: In test mode testing Weld loads wrong beans.xml
shay_matasaro Mar 4, 2013 8:14 PM (in response to shay_matasaro)I have upgraded weld to version 2.0.0 beta 3 and the issue seems to be resolved , although looking at the fixes list i don't see anything that could explein this