That's quite possible. I'm looking at it now. According to the posts, this only happens on the 7.2 prerelease? Builds before and after that point don't get the warning? On 2/13/2013 8:19 AM, Jaikiran Pai wrote: > A user just reported a potential problem with the multi-JSF feature and > the recent changes to the module loading, w.r.t the layered > distributions architecture [2]. The > org.jboss.as.jsf.deployment.JSFModuleIdFactory [3] relies on the > module.path filesystem path to find the JSF modules. Reading through the > layered distributions architecture and the goals of the new filesystem > layout for modules, I think the multi-JSF feature design itself might > need a relook in terms of how the users add those modules, right? > > > [1] https://community.jboss.org/thread/221254?tstart=0 > [2] > https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... > [3] > https://github.com/jbossas/jboss-as/blob/master/jsf/subsystem/src/main/ja... > [4] https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature > > -Jaikiran > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On Wednesday 13 February 2013 07:06 PM, ssilvert(a)redhat.com wrote: > That's quite possible. I'm looking at it now. According to the posts, > this only happens on the 7.2 prerelease? Builds before and after that > point don't get the warning? I haven't personally given it a try.

What I was curious was should those modules installed for multi-JSF feature be considered as "user modules" (which requires it to be located at a specific location in the filesystem, outside of the "system" folder)or should users be allowed to stick those modules within the "system" folder (I don't think so).

-Jaikiran > On 2/13/2013 8:19 AM, Jaikiran Pai wrote: >> A user just reported a potential problem with the multi-JSF feature and >> the recent changes to the module loading, w.r.t the layered >> distributions architecture [2]. The >> org.jboss.as.jsf.deployment.JSFModuleIdFactory [3] relies on the >> module.path filesystem path to find the JSF modules. Reading through the >> layered distributions architecture and the goals of the new filesystem >> layout for modules, I think the multi-JSF feature design itself might >> need a relook in terms of how the users add those modules, right? >> >> >> [1] https://community.jboss.org/thread/221254?tstart=0 >> [2] >> https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... >> [3] >> https://github.com/jbossas/jboss-as/blob/master/jsf/subsystem/src/main/ja... >> [4] https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature >> >> -Jaikiran >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev