Proposed move of components.xml location

[jtucker]

I'm suggesting that components.xml be moved from it's hard-coded location at /WEB-INF/components.xml to simply be loaded from the classpath.

The main reason is that I'm having to do workarounds when using SeamTest to include the WEB-INF directory in my test classpath.

I can't think of any advantage to keeping it in WEB-INF but I'd like to know if I'm missing something before I log it in JIRA!

[gavin.king]

Actually I don't love WEB-INF as a place for it. But I'm not sure where it should go. META-INF in the ear? the ejb-jar? I'm really not certain...

[jtucker]

My vote is either META-INF or right next to components.properties at the root of the classpath.

[rdewell]

Please just don't break the ability to have multiple WARs in the same EAR!

[gavin.king]

Yes, good point. So it naturally belongs in the war.

[jtucker]

Except it doesn't help my case where it's not being loaded in my SeamTests unless I explicitly copy /WEB-INF/ to my classpath.

This proposal may also be relevant for JBSEAM-255 - testing components inside containers but outside JSF lifecycles.

Would a cascading configuration be more suitable where a components.xml from the ejb-jar could be merged with a components.xml in the war? Or would support for WAR-specific components.properties suffice?

I'm happy to contribute the changes required if we can agree on an approach.

[gavin.king]

I don't really understand why this is a problem ... it works in the directory structure used for the examples...

[jtucker]

Yeah it's easy enough with an ant build, but not with a maven directory structure or running the eclipse TestNG plugin. I'm working around by including a second WEB-INF directory in a source folder which only contains components.xml.