Nuno Sousa schrieb: > Thanks Richard and Simon, > I had the tomahawk jar file in my project /lib folder, i though it was > automaticaly moved to JBoss WEB-INF/lib, after building, but i had to > move it manually. > Now i don't have any errors on AP server startup, but the tomahawk > components aren't getting rendered, i'm getting this messages: > > (...) > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.PRETTY_HTML' found, using default value true > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using > default value true > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.AUTO_SCROLL' found, using default value false > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value > /faces/myFacesExtensionResource > 15:13:45,174 INFO [MyfacesConfig] No context init parameter > 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default > value true > 15:13:45,174 INFO [MyfacesConfig] Starting up Tomahawk on the > RI-JSF-Implementation. > 15:13:45,256 ERROR [STDERR] 15/Abr/2008 15:13:45 > org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit > createResponseWriter > SEVERE: No RenderingContext has been created. > (...) > > > It's maybe any fault on web.xml?
Everything looks ok for tomahawk; those INFO messages are normal. Looks like some kind of trinidad problem, but I know nothing about trinidad. You might get more help by starting a new email thread with "trinidad" in the subject line. Regards, Simon
