October 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1093) Remove workaround for ARQ-818

by Andrew Rubinger (JIRA)

Andrew Rubinger created WELD-1093: ------------------------------------- Summary: Remove workaround for ARQ-818 Key: WELD-1093 URL: https://issues.jboss.org/browse/WELD-1093 Project: Weld Issue Type: Task Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Andrew Rubinger A workaround to ARQ-818 was introduced in: https://github.com/weld/core/commit/432aa77a4f392ab499e5f283a9d2d6e4719a0db8 Remove this hack and perform the relevant upgrades when they become available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (WELD-1040) Support Java Web Start

by Alexandre Gattiker (Created) (JIRA)

Support Java Web Start ---------------------- Key: WELD-1040 URL: https://issues.jboss.org/browse/WELD-1040 Project: Weld Issue Type: Bug Components: Java SE Support Affects Versions: 1.1.5.Final, 1.1.4.Final Reporter: Alexandre Gattiker Attachments: weld-webstart-bug.zip ClassLoader.getResources("META-INF/beans.xml") returns remote server URLs in the format "http://..." Weld's FileSystemURLHandler tries to open these URLs as files, which leads to: java.lang.RuntimeException: Error handling file http:/localhost:8080/weld-webstart-war-0.0.1-SNAPSHOT/webstart/weld-webstart-jar.jar at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handleArchiveByFile(FileSystemURLHandler.java:80) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handle(FileSystemURLHandler.java:58) at org.jboss.weld.environment.se.discovery.url.URLScanner.scan(URLScanner.java:102) at org.jboss.weld.environment.se.discovery.url.WeldSEUrlDeployment.<init>(WeldSEUrlDeployment.java:39) at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:130) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:80) at com.example.TestApp.main(TestApp.java:12) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.javaws.Launcher.executeApplication(Launcher.java:1914) at com.sun.javaws.Launcher.executeMainClass(Launcher.java:1847) at com.sun.javaws.Launcher.doLaunchApp(Launcher.java:1609) at com.sun.javaws.Launcher.run(Launcher.java:138) at java.lang.Thread.run(Thread.java:680) Caused by: 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:127) at java.util.zip.ZipFile.<init>(ZipFile.java:143) at org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler.handleArchiveByFile(FileSystemURLHandler.java:71) ... 15 more I am attaching a demo project that also contains a proposed fix, using com.sun.jnlp.JNLPClassLoader#getJarFile(URL) to retrieve the location of the locally cached copy of the JAR. As this is an internal class it is accessed by reflection. The getJarFile method only exists in JRE 6, not in JRE 5. Add to org.jboss.weld.environment.se.discovery.url.FileSystemURLHandler: if (urlPath.startsWith("http:") || urlPath.startsWith("https:")) { ClassLoader cl; if (Thread.currentThread().getContextClassLoader() != null) { cl = Thread.currentThread().getContextClassLoader(); } else { cl = getClass().getClassLoader(); } // see http://javasourcecode.org/html/open-source/jdk/jdk-6u23/com/sun/jnlp/JNLP... // public JarFile getJarFile(URL url) throws IOException { Method m = cl.getClass().getMethod("getJarFile", URL.class); // returns a reference to the local cached copy of the JAR JarFile jarFile = (JarFile) m.invoke(cl, new URL(urlPath)); urlPath = jarFile.getName(); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
6
0 / 0

[JBoss JIRA] (WELD-1234) A removed session-scoped stateful EJB renders the whole session scope unusable

by Marko Lukša (JIRA)

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] (WELD-1236) Deserialization fails for bean containing intercepted methods with primitive or array-typed parameters

by Marko Lukša (JIRA)

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] (WELD-1231) Implement CDI-58

by Jozef Hartinger (JIRA)

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (WELD-1230) Implement CDI-139

by Jozef Hartinger (JIRA)

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (WELD-1228) Switch to using proxies for interceptors/decorators

by Jozef Hartinger (JIRA)

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] (WELD-1229) Implement CDI-269

by Jozef Hartinger (JIRA)

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (WELD-1226) Implement CDI-254

by Jozef Hartinger (JIRA)

12 years, 10 months

2
4
0 / 0

[JBoss JIRA] (WELD-1174) Incorrect interceptor invocation order when combining CDI interceptors with @Interceptors

by Marko Lukša (JIRA)

12 years, 10 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2012