[seam-dev] Issue resolved with JBoss AS 7 CR1 and Seam Social

[Pete Muir]

I believe Stuart intended to make it work in WEB-INF, but there are a lot of issues with loading it from there, largely because there is no guarantee that the Servlet container has started when Seam Config is started. And Java EE itself offers to API to read from the web root.

This is resolved in CDI 1.1 as we offer the ability to read the .xml files as an InputStream using the ProcessModule event on startup.

On 4 Jul 2011, at 18:21, Jason Porter wrote:

> The suggested file is sem-beans.XML in the place you put it, but in short, yes, I believe this is expected. 
> 
> Sent from my iPhone
> 
> On Jul 4, 2011, at 8:20, Antoine Sabot-Durand <antoine at sabot-durand.net> wrote:
> 
>> Hi all,
>> 
>> Just to let you know I managed to run social Web App example with Jboss 7-CR1. The trick was to have 2 beans.xml file. One in META-INF for Seam-Config to read beans configuration and one in WEB-INF in order to having the server exposing CDI bean for JSF view. I drop the Seam-Faces and its dependency Seam-International since I don't need them and they cashed the deployment.
>> 
>> If I put config info in WEB-INF/beans.xml, Seam-Config doesn't read them and if I don't put beans.xml in WEB-INF my JSF views don't access CDI bean (LE doesn't trigger any code). I don't know if it's the expected behavior for Seam-Config to read beans.xml only in META-INF....
>> 
>> 
>> Antoine SABOT-DURAND
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
> 
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev