Thanks a lot, could you please tell us if some problems using Myfaces 1.2 on WAS 6.1 will come up?
I hope not, of course :) Thanks. Stefano. 2008/6/11 Luhtala Santeri <[EMAIL PROTECTED]>: > I haven't yet tested fully the whole application but at the moment I run > Myfaces 1.2.3 + Facelets 1.1.14 + Trinidad 1.2.8 +Tomahawk 1.1.7-SNAPSHOT. > Seems to be working fine. > > S > > -----Original Message----- > From: Stefano Panero [mailto:[EMAIL PROTECTED] > Sent: 11. kesäkuuta 2008 13:30 > To: MyFaces Discussion > Subject: Re: Problems with WAS 6.1.0.15 and MyFaces and Facelets and Trinidad > > Hi, > > could you tell me which of those stacks does work, please? > > IBM WAS 6.1.0.15 Embedded JSF implementation (Which is SUN JSF > 1.1_something) + Facelets 1.1.11 + Trinidad 1.0.6 + Tomahawk > 1.1.7-SNAPSHOT > MyFaces 1.1.5 + Facelets 1.1.11 + Trinidad 1.0.6 + Tomahawk 1.1.7-SNAPSHOT > MyFaces 1.2.3 + Facelets 1.1.14 + Trinidad 1.2.8 + > ------------------------------------ > SUN RI 1.2_04-b07 + > ----------------------------------------------------------------- > > Thanks a lot, > Stefano. > > > 2008/6/11 Luhtala Santeri <[EMAIL PROTECTED]>: >> This is now resolved. >> >> >> >> This was because relative paths to resources were handled differently in WAS >> 6.1 compared to Jetty. And therefore those resources referenced in our >> composition components and taglibs were not found. It's pain in the ass >> though that I had to remote debug Facelets to find this out. It would be >> good if the Facelets Compiler would give some useful info in these >> situations. >> >> >> >> S >> >> >> >> ________________________________ >> >> From: Luhtala Santeri >> Sent: 10. kesäkuuta 2008 13:56 >> To: [email protected] >> Subject: Problems with WAS 6.1.0.15 and MyFaces and Facelets and Trinidad >> >> >> >> We have now tried to make our application run on WAS with several different >> configurations. >> IBM WAS 6.1.0.15 Embedded JSF implementation (Which is SUN JSF >> 1.1_something) + Facelets 1.1.11 + Trinidad 1.0.6 + Tomahawk 1.1.7-SNAPSHOT >> MyFaces 1.1.5 + Facelets 1.1.11 + Trinidad 1.0.6 + Tomahawk 1.1.7-SNAPSHOT >> MyFaces 1.2.3 + Facelets 1.1.14 + Trinidad 1.2.8 + >> ------------------------------------ >> SUN RI 1.2_04-b07 + >> ----------------------------------------------------------------- >> >> >> >> This stuff is working fine with Jetty. With the second combination >> mentioned. >> >> All of the mentioned configurations have resulted with this same stacktrace: >> >> [6/9/08 16:20:05:017 EEST] 00000029 lifecycle W executePhase(RENDER_RESPONSE >> 6,[EMAIL PROTECTED]) >> threw exception >> javax.faces.FacesException: Stream closed >> at >> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:135) >> at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) >> at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) >> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1068) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1009) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) >> at >> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:238) >> at >> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:195) >> at >> org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138) >> at >> org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:235) >> at >> com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:771) >> at >> com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679) >> at >> com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:539) >> at >> com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) >> at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3357) >> at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267) >> at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811) >> at >> com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455) >> at >> com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383) >> at >> com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) >> at >> com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) >> at >> com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) >> at >> com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) >> at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) >> at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) >> at >> com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743) >> at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) >> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) >> Caused by: java.io.IOException: Stream closed >> at java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:145) >> at java.io.BufferedInputStream.fill(BufferedInputStream.java:229) >> at java.io.BufferedInputStream.read1(BufferedInputStream.java:267) >> at java.io.BufferedInputStream.read(BufferedInputStream.java:324) >> at java.io.FilterInputStream.read(FilterInputStream.java:113) >> at com.sun.facelets.compiler.SAXCompiler.writeXmlDecl(SAXCompiler.java:253) >> at com.sun.facelets.compiler.SAXCompiler.doCompile(SAXCompiler.java:229) >> at com.sun.facelets.compiler.Compiler.compile(Compiler.java:105) >> at >> com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:197) >> at >> com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144) >> at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:293) >> at >> com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:241) >> at com.sun.facelets.tag.UserTagHandler.apply(UserTagHandler.java:98) >> at >> com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) >> at >> com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64) >> at >> com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:131) >> at >> com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:310) >> at >> com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:280) >> at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68) >> at >> com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) >> at >> com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314) >> at >> com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169) >> at >> com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) >> at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) >> at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) >> at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) >> at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) >> at >> com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:144) >> at >> com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113) >> at >> com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) >> at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25) >> at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95) >> at >> com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524) >> at >> com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567) >> at >> javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:178) >> at >> org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:176) >> at >> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) >> ... 36 more >> >> Common to all other configuration but the first mentioned is that the JSF >> jars and the Facelets el jars are in ${WAS_INTALL_ROOT}/lib/ext and they are >> included in WAS Reference library. And this library is referenced by a >> SERVER LEVEL classloader. This was the only way to really load those >> different JSF implementations over IBM's embedded one. Although it should >> have been possible just to set the application classloader policy to >> PARENT_LAST.(According to IBM...and common sense.) >> >> To be more specific we can get to the first page in application(xhtml) and >> login page(jsp). But the first really 'functional' page is where the fun >> stops. >> >> Any help would be appreciated. >> >> Santeri >> >> >
