The problem is that JSF needs access to the jars in a uniform spot to configure the runtime. The spec says that it should act this way.
Probably the best way around this is to see if your servlet container supports aliasing the jars. I'm running websphere, and i think there's a way that I could keep my jars in a common directory, but have my apps all reference them as though they were in their WEB-INF/lilb directories. On Thu, 30 Dec 2004 15:21:53 +0100, Alessandro Polverini <[EMAIL PROTECTED]> wrote: > On Thu, 2004-12-30 at 08:04 -0600, Heath Borders wrote: > > I think the FacesConfigurator requires that they be in the WEB-INF/lib > > directory, I think putting them anywhere else starts making > > assumptions about your web container. > > So if I have 10 (or 100) web applications I need to have 10 (or 100) > copies of the *same* jars over and over? > > That seems a waste of space and resources to me. For example, when a new > release is out, it's better to upgrade just one set of jars (like I do, > for example with JSTL), instead of redeploy all the web applications, > and look for the ones using myfaces. > > Is there any way to overcome the problem? > > Thanks for the reply, > Alex > > -- -Heath Borders-Wing [EMAIL PROTECTED]
