having a a4j view handler in the stack without trinidad looks troublesome. Have you ensured that you have the trinidad filter setup as the very first filter in the web.xml?
BTW, it is not recommended to you a4j with trinidad, they are not fully compatible, especially with Ajax Andrew On 3/28/08, James Clinton <[EMAIL PROTECTED]> wrote: > Hi, > > > > Having problems trying to fit Trinidad into an existing > Tomahawk/Facelets based application which uses A4J libraries. > > > > I have looking thru the examples believe I have configured the app > correctly to now support Trinidad including: > > > > - <default-render-kit-id/> in faces-config.xml > > - trinidad-config.xml > > - org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER in web.xml > > > > Following exception is thrown immediately. > > > > java.lang.IllegalStateException: No RenderingContext > > at > org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin(CoreRenderer > .java:194) > > at > org.apache.myfaces.trinidadinternal.renderkit.htmlBasic.HtmlFormRenderer > .encodeBegin(HtmlFormRenderer.java:56) > > at > javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:6 > 64) > > at > com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSuppo > rt.java:232) > > at > com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSuppo > rt.java:239) > > at > com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSuppo > rt.java:239) > > at > com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:5 > 80) > > at > org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrappe > r.java:108) > > at > org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java > :216) > > at > org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderRespon > seExecutor.java:41) > > at > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132 > ) > > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140) > > > > Any advice appreciated. > > > > J. > > > >
