[jboss-jira] [JBoss JIRA] Commented: (JBAS-8024) Weld deployments fail with "Error in zip file" message
[
https://jira.jboss.org/browse/JBAS-8024?page=com.atlassian.jira.plugin.sy...
]
John Bailey commented on JBAS-8024:
-----------------------------------
I am not really sure this is something that can be fixed in VFS. If you look at the
source of com.sun.faces.config.AnnotationScanner.processClasspath it is misshandling the
URL and attempting to force it into a JAR file URL. There is no way for VFS allow for
this to happen. That being said, the AnnotationScanner can not be fixed, so the solution
is going to have to require a translation from a VFS URL to something that is actually
consumable by the AnnotationsScanner. There are several ways this can be done. Let me
trace the origin of the call path and see where the correct URL can be used.
Weld deployments fail with "Error in zip file" message
------------------------------------------------------
Key: JBAS-8024
URL: https://jira.jboss.org/browse/JBAS-8024
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: 6.0.0.M3
Reporter: jaikiran pai
Assignee: John Bailey
Priority: Critical
Fix For: 6.0.0.M4
Attachments: rf4app-1.0-SNAPSHOT.war, weld-numberguess.war
More than one user has now reported that weld deployments which used to work in earlier
AS versions (6.0.0.M2) have started failing in M3 with the following error:
18:51:45,567 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] :
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [:1.6.0_17]
at java.util.zip.ZipFile.<init>(ZipFile.java:114) [:1.6.0_17]
at java.util.jar.JarFile.<init>(JarFile.java:133) [:1.6.0_17]
at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:67)
[:1.6.0_17]
at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:214) [:1.6.0_17]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_17]
at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:198) [:1.6.0_17]
at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:50)
[:1.6.0_17]
at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:68)
[:1.6.0_17]
at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104)
[:1.6.0_17]
at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:71)
[:1.6.0_17]
at
com.sun.faces.config.AnnotationScanner.processClasspath(AnnotationScanner.java:290)
[:2.0.2-FCS]
at
com.sun.faces.config.AnnotationScanner.getAnnotatedClasses(AnnotationScanner.java:215)
[:2.0.2-FCS]
at
com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:765)
[:2.0.2-FCS]
at
com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:736)
[:2.0.2-FCS]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[:1.6.0_17]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_17]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:329)
[:2.0.2-FCS]
at
com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:223)
[:2.0.2-FCS]
at
org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:72)
[:6.0.0.20100429-M3]
Please see the referenced forum thread for the complete details
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira