Re: pages not rendered anymore after update from 1.1.6 to 1.2.8

Hi The example available here: http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/examples/tiles/ works with jsf 1.2 and tomahawk12-1.1.x (to execute it try mvn clean -Djsf=12 -Dtomahawk=12 jetty:run) Note that use jsf 1.2 and tomahawk-1.1.x does not work, because some changes in ViewHandle

Re: pages not rendered anymore after update from 1.1.6 to 1.2.8

I'd suggest using facelets instead of Tiles. Tiles was never designed to work with JSF. Facelets provides similar templating capability and was designed to improve on shortcomings of JSP and JSF. Facelets is also part of JSF 2.0 -Richard On Tue, Dec 8, 2009 at 8:24 AM, Michael Heinen wrote: > T

please remove me from this list

Thank-you. = Patrick Breen Web Software Developer, Corporate Systems Johnson Inc. Phone..: (709) 737-1173 Email: pbr...@johnson.ca = Quote of the month... I have often repented speaking, but never of hol

Re: pages not rendered anymore after update from 1.1.6 to 1.2.8

Hi Michael, I suspect your problem is mainly related to tiles - I also tried to migrate and didnt succeed. See my working config tiles 2.0.6. myfaces 1.2.8 richfaces 3.3.1 GA Hope it will help 2009/12/8 Michael Heinen > Little progress: > 1) I have to use > "org.apache.myfaces.tomahawk.app

RE: pages not rendered anymore after update from 1.1.6 to 1.2.8

Little progress: 1) I have to use "org.apache.myfaces.tomahawk.application.jsp.JspTilesTwoViewHandlerImpl" instead of "org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl" 2) I have to use version 2.0.5! Tiles 1 is not working with JspTilesTwoViewHandlerImpl and newer versions

RE: pages not rendered anymore after update from 1.1.6 to 1.2.8

Thanks Richard, I tried this finally with a simple page in this project. TILES is the culprit. My simple page is now rendered with tomahawk tags after I removed context param org.ajax4jsf.VIEW_HANDLERS=org.apache.myfaces.tomahawk.application.jsp.JspTilesViewHandlerImpl from web.xml. The conten

Re: pages not rendered anymore after update from 1.1.6 to 1.2.8

Have you tried just having a page with a JSF outputText tag to see if that works? (No tiles or Richfaces) I would start from there and then add other tags to narrow down where the problem is. -R

RE: pages not rendered anymore after update from 1.1.6 to 1.2.8

The order seems to be correct to me: RichFaces Filter richfaces org.ajax4jsf.Filter ... MyFacesExtensionsFilter org.apache.myfaces.webapp.filter.ExtensionsFilter maxFileSize 20m ... richfaces Faces Servlet REQUEST FORWAR

Re: pages not rendered anymore after update from 1.1.6 to 1.2.8

WARN] [D57992BA5C47A836C0EBE03C0224EB3B] webapp.BaseFilter checkMyFacesExtensionsFilter: MyFaces Extensions Filter should be configured to execute *AFTER* RichFaces filter. Refer to SRV.6.2.4 section of Servlets specification on how to achieve that. Sent from my iPhone On Dec 8, 2009, at 6

RE: pages not rendered anymore after update from 1.1.6 to 1.2.8

The attachments didn't work. Here is the content: Initialization: [2009-12-08 14:44:01,308] main [ INFO] [] webapp.StartupServletContextListener dispatchInitializationEvent: Checking for plugins:org.apache.myfaces.FACES_INIT_PLUGINS ... [2009-12-08 14:44:01,730] main [DEBUG] [] webxml.WebXmlPars

pages not rendered anymore after update from 1.1.6 to 1.2.8

Hi, I tried to update my webApp from myfaces 1.1.6, tomahawk 1.1.7 and richfaces 3.1.5 to JSF 1.2 After some problems the webapp finally started but no page is rendered anymore. Instead of the pages I get only empty screens without any content at all! I am still using Tiles1 (from struts1.1jar)

'action' attribute of Tomahawk schedule is not working properly.

Hi all, I am having tag in my app. it's action has the value="#activityEditContext.editAppointment()}" where activityEditContext is my bean and it's editAppointment() method redirect it to a page from where appointment is edited. When we returned back after saving appointment from appointment

Re: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

You're welcome! OK, well now it's clear. The problem is that AbstractFacesInitializer checks the web.xml for FacesServlet entries. This is achieved by looking at every servlet entry in the web.xml and checking if the class is either javax.faces.webapp.FacesServlet or a class that implements org.ap

Please specify a valid renderkit-id.

Hello, can you help me with this Error Message? RenderKit for renderKitId : tobago on viewId : /adressApplication.xml could not be retrieved. Please specify a valid renderkit-id. Caused by: java.lang.NullPointerException - RenderKit for renderKitId : tobago on viewId : /adressApplication.xml c

RE: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

Found the solution. My Wrapper has to implement DelegatedFacesServlet. -Original Message- From: Michael Heinen [mailto:michael.hei...@recommind.com] Sent: Dienstag, 8. Dezember 2009 09:45 To: MyFaces Discussion Subject: RE: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factorie

RE: update from 1.1.6 to 1.2.8 -> IllegalStateException: No Factories configured for this Application

Thanks Jakob. Now I see following WARN message: [2009-12-08 09:31:50,287] main [ WARN] [] webapp.AbstractFacesInitializer initFaces: No mappings of FacesServlet found. Abort initializing MyFaces. I specified a Wrapper around the FacesServlet for better exception handling. This worked well with m