July 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-942) Analyze FindBugs report

by Jozef Hartinger (JIRA)

Analyze FindBugs report ----------------------- Key: WELD-942 URL: https://issues.jboss.org/browse/WELD-942 Project: Weld Issue Type: Task Affects Versions: 1.1.1.Final Reporter: Jozef Hartinger Since WELD-851 has been resolved, the FindBugs analysis is working again. It currently reports ~100 reports. Please review these warnings and either implement code changes or use FindBugs annotations to suppress these warnings. The latest report is available at http://ci.jboss.org/jenkins/job/Weld-trunk-findbugs/lastSuccessfulBuild/f... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (WELDX-51) Create a single jar file for Weld SE that includes all dependencies

by Pete Muir (JIRA)

Create a single jar file for Weld SE that includes all dependencies ------------------------------------------------------------------- Key: WELDX-51 URL: https://jira.jboss.org/jira/browse/WELDX-51 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir Fix For: Java SE 1.0.0.CR3 To make using Weld SE easy, we should create a single jar (primarily for use at runtime, at compile time you would depend just on cdi-api of course) * cdi-api * weld-api * weld-spi * weld-core * weld-se -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
14
0 / 0

[JBoss JIRA] Created: (WELD-876) BeanXmlParser fails when woodstock is the underlying parser

by Stuart Douglas (JIRA)

BeanXmlParser fails when woodstock is the underlying parser ----------------------------------------------------------- Key: WELD-876 URL: https://issues.jboss.org/browse/WELD-876 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Priority: Minor BeansXmlParser has the following code: try { parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaLanguage", "http://www.w3.org/2001/XMLSchema"); parser.setProperty("http://java.sun.com/xml/jaxp/properties/schemaSource", loadXsds()); } catch (IllegalArgumentException e) { // No op, we just don't validate the XML } However, the actual exception thrown (according to the javadoc) is a SAXNotRecognizedException or a SAXNotSupportedException, which means that if the underlying SAX impl does not support those properties then parsing will fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-880) CNFEs for Seam 3 optional dependencies on AS 7

by Nicklas Karlsson (JIRA)

CNFEs for Seam 3 optional dependencies on AS 7 ---------------------------------------------- Key: WELD-880 URL: https://issues.jboss.org/browse/WELD-880 Project: Weld Issue Type: Bug Affects Versions: 1.1.1.Final Environment: AS 7 beta2 Reporter: Nicklas Karlsson Assignee: Stuart Douglas Deploying the seam 3 international module on AS 7 is currently not possible because the optional dependencies are not optional and fails on yoda-time not missing. See linked issue -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-896) Weld 1.1: injection of stateless session beans fails intermittently with @EJB; @Startup not working

by yangju (JIRA)

Weld 1.1: injection of stateless session beans fails intermittently with @EJB; @Startup not working --------------------------------------------------------------------------------------------------- Key: WELD-896 URL: https://issues.jboss.org/browse/WELD-896 Project: Weld Issue Type: Bug Components: Built-in beans Affects Versions: 1.1.0.CR3 Environment: Jboss AS 6 Final, windows Reporter: yangju Priority: Critical Injection of stateless session beans with @EJB fails sometimes. It seems it fails intermittently. It fails more if there are many injections into the bean. This is very frustrating as we cannot anticipate when it will fail. Also, @Startup is not working. The bean cannot be started even we set it as as @Singleton and @Startup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-925) It is impossible to Veto a session bean

by Stuart Douglas (JIRA)

It is impossible to Veto a session bean --------------------------------------- Key: WELD-925 URL: https://issues.jboss.org/browse/WELD-925 Project: Weld Issue Type: Bug Reporter: Stuart Douglas If an EJB's AnnotatedType is vetoed then the bean is still installed in BeanDeployer.createBeans -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-928) Weld should log failure to load a class at a higher level than DEBUG

by Stuart Douglas (JIRA)

Weld should log failure to load a class at a higher level than DEBUG -------------------------------------------------------------------- Key: WELD-928 URL: https://issues.jboss.org/browse/WELD-928 Project: Weld Issue Type: Bug Affects Versions: 1.1.1.Final Reporter: Stuart Douglas Priority: Critical Fix For: 1.1.2.Final At the moment weld logs failure to load a class at a log level of debug, which is not displayed by default. Due to the new modular class loading in AS7 these types of errors will become much more frequent, and the user is given no debug information to determine where the problem is. Changing the default log level to DEBUG for org.jboss.weld.Bootstrap is not an option as this is to verbose. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-941) Log stacktrace following "WELD-000119 Not generating any bean definitions" at TRACE level.

by Ondrej Zizka (JIRA)

Log stacktrace following "WELD-000119 Not generating any bean definitions" at TRACE level. ------------------------------------------------------------------------------------------ Key: WELD-941 URL: https://issues.jboss.org/browse/WELD-941 Project: Weld Issue Type: Enhancement Affects Versions: 1.1.1.Final Reporter: Ondrej Zizka Currently, the stack trace is logged at DEBUG level, which makes it hard to filter (see below). I suggest to log it with TRACE for that reason. {code} 08:32:33.999 DEBUG [main] org.jboss.weld.Bootstrap WELD-000119 Not generating any bean definitions from org.jboss.logging.JBossLogManagerProvider because of underlying class loading error 08:32:34.001 DEBUG [main] org.jboss.weld.Bootstrap catching org.jboss.weld.resources.spi.ResourceLoadingException: java.lang.NoClassDefFoundError: Lorg/jboss/logmanager/Logger$AttachmentKey; at org.jboss.weld.environment.se.discovery.url.WeldSEResourceLoader.classForName(WeldSEResourceLoader.java:70) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:83) at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:133) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:192) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:370) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:87) at org.jboss.jawabot.JawaBotApp.main(JawaBotApp.java:64) Caused by: java.lang.NoClassDefFoundError: Lorg/jboss/logmanager/Logger$AttachmentKey; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at org.jboss.weld.environment.se.discovery.url.WeldSEResourceLoader.classForName(WeldSEResourceLoader.java:58) ... 6 more Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Logger$AttachmentKey at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 10 more {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-575) Definition/DeploymentExceptions thrown by an AnnotationModel are wrapped by a ComputationException

by Marius Bogoevici (JIRA)

Definition/DeploymentExceptions thrown by an AnnotationModel are wrapped by a ComputationException -------------------------------------------------------------------------------------------------- Key: WELD-575 URL: https://jira.jboss.org/browse/WELD-575 Project: Weld Issue Type: Feature Request Components: Reflection layer Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Assignee: Pete Muir Fix For: 1.1.0.BETA1 If an exception is thrown while evaluating a Function, the exception is wrapped by a ComputationException. As a result, the exceptions thrown by the AnnotationModel subclasses (Stereotype, InterceptionBinding) - which indicate a definition error detected while parsing the annotation are thrown as ComputationExceptions by the framework. An illustration for this can be found in MetaAnnotationStore.getInterceptionBindingModel, although this needs to be done in a more general fashion. -- 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

12 years, 9 months

4
5
0 / 0

[JBoss JIRA] Updated: (WELD-1) Add tests for multiple wars in an ear

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WELD-1?page=com.atlassian.jira.plugin.sys... ] Stuart Douglas updated WELD-1: ------------------------------ Fix Version/s: 1.2.0.Beta1 (was: 1.1.2.Final) > Add tests for multiple wars in an ear > ------------------------------------- > > Key: WELD-1 > URL: https://issues.jboss.org/browse/WELD-1 > Project: Weld > Issue Type: Feature Request > Components: Bootstrap and Metamodel API, Scopes & Contexts > Reporter: Pete Muir > Fix For: 1.2.0.Beta1 > > > This is a typical area of weakness in Seam etc. due to misuse of singletons etc. > Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2011