Re: Latest Trinidad trunk not working

2007-03-31 Thread Matthias Wessendorf
Hello Venk, the WAR file has! to contain the the JARs of ONE jsf impl (myfaces OR ri). The trunk is JSF 1.1; Target is J2EE 1.3 and/or J2EE 1.4. In a JSF 1.2 world, there shouldn't be JARs from a JSF-IMPL in the WAR. The target are Java EE 5 containers, which support JSF 1.2 by default. Even

Re: Latest Trinidad trunk not working

2007-03-30 Thread Matthias Wessendorf
Hi Venk, the demo itself runs w/ MyFaces. Your stack is talking about Sun RI snip com.sun.faces.context.ExternalContextImpl. /snip You can't have two JSF impls in one app. The good news is, that JSF 1.2 removes the odd requirement for *adding* a JSF runtime to your projects, since the

Re: Latest Trinidad trunk not working

2007-03-30 Thread Scott O'Bryan
Also Ven, That error, although it should never show up if everything is configured correctly, should not really effect things that badly. It it logged when something like the resource servlet tries to disable the configurators after a FacesContext has already been obtained. All it means is

Re: Latest Trinidad trunk not working

2007-03-30 Thread venkata guddanti
OK the errors go away if I remove the jsf-impl.jar from the WEB-INF\lib directory in the deployed war file in tomcat. I believe the war file should not include the jsf-impl.jar. I wonder if the demo pom file is not right. Thanks, Venkata On 3/30/07, Scott O'Bryan [EMAIL PROTECTED] wrote: