1 Reply Latest reply on Apr 13, 2008 7:06 PM by Brad Powell

    Problem Loading Facelet on Websphere

    Brad Powell Newbie

      I am a Seam newbie and I am trying to get a simple Helloworld application working on Websphere 6.1.0.15 using Seam 2.1.0.A1.  When I try and load a facelet, I get the following error:


                                       java.util.zip.ZipException: Bad file descriptor C:\Program%20Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installedApps\JAEGERNode07Cell\SeamHelloWorld.ear\lib\dom4j.jar
           at java.util.zip.ZipFile.open(Native Method)
           at java.util.zip.ZipFile.<init>(ZipFile.java:238)
           at java.util.jar.JarFile.<init>(JarFile.java:169)
           at java.util.jar.JarFile.<init>(JarFile.java:107)
           at com.sun.facelets.util.Classpath.getAlternativeJarFile(Classpath.java:124)
           at com.sun.facelets.util.Classpath.search(Classpath.java:67)
           at com.sun.facelets.compiler.TagLibraryConfig.loadImplicit(TagLibraryConfig.java:428)
           at com.sun.facelets.compiler.Compiler.initialize(Compiler.java:87)
           at com.sun.facelets.compiler.Compiler.compile(Compiler.java:104)
           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.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:95)
           at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:517)
           at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
           at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
           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:1076)
      



      When the exception is thrown, the page renders to the browser in an incomplete state.


      One curious thing I discovered is that if I add additional jars to the lib directory in the EAR, the exception will throw on the first jar file it finds, so it doesn't appear to be anything directly related to dom4j.  For example, I added antlr.jar to the lib directory, and afterwards the exception changed to:



      java.util.zip.ZipException: Bad file descriptor C:\Program%20Files\IBM\WebSphere\AppServer\profiles\AppSrv02\installedApps\JAEGERNode07Cell\SeamHelloWorld.ear\lib\antlr.jar
      



      Any ideas on how to resolve this would be appreciated.