quality@glassfish.java.net

Re: Back to b66 for me

From: Judy Tang <Judy.J.Tang_at_Sun.COM>
Date: Tue, 13 Oct 2009 01:42:36 -0700

Hi Wouter,

Thanks for reporting this issue, a very good test case. Hope java.net
works for you, it seems working for me now.

Judy

Wouter van Reeven wrote:
> Hi all,
>
>
> Yesterday I used ./bin/pkg image-update to update GlassFish v3 b66 to
> b67. Today I tried to deploy an ear file to b67 and it failed. I then
> removed GFv3 and installed b67 using the unix script. Upon deploying
> the ear once more I again got the same error:
>
> [#|2009-10-13T10:07:49.752+0200|SEVERE|glassfish|javax.enterprise.system.container.web.org.glassfish.web.loader|_ThreadID=31;_ThreadName=Thread-3;|IOException {0} when trying to scan the applications classes and libraries
> java.util.zip.ZipException: error in opening zip file
> at java.util.zip.ZipFile.open(Native Method)
> at java.util.zip.ZipFile.<init>(ZipFile.java:114)
> at java.util.jar.JarFile.<init>(JarFile.java:133)
> at java.util.jar.JarFile.<init>(JarFile.java:70)
> at org.glassfish.web.loader.ServletContainerInitializerUtil.getInitializerList(ServletContainerInitializerUtil.java:244)
>
> The next error I get is
>
> [#|2009-10-13T10:07:49.758+0200|SEVERE|glassfish|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=31;_ThreadName=Thread-3;|WebModule[/JFall2009-war]StandardWrapper.Throwable
> java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory
> at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
> at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
> at javax.faces.webapp.FacesServlet.init(FacesServlet.java:166)
>
> However, scanning all jars I do find the
> javax.faces.context.FacesContextFactory class:
>
> ./modules/jsf-api.jar
> 422:javax/faces/context/FacesContextFactory.class
>
> I guess something fishy is going on. Since I am preparing a presentation
> based on GlassFish v3 I am going back to build 66. I will create an
> issue for this.
>
>
> Thanks, Wouter
>
>