May 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-176) Decorator Elements in beans.xml use <decorator> not <class>

by Pete Muir (JIRA)

Decorator Elements in beans.xml use <decorator> not <class> ----------------------------------------------------------- Key: CDITCK-176 URL: https://jira.jboss.org/browse/CDITCK-176 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3 Affected tests: testPassivationCapableBeanWithNonPassivatingDecoratorBeanConstructorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor.DecoratorWithNonPassivatingBeanConstructorTest) testPassivationCapableBeanWithNonPassivatingInitializerInDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod.DecoratorWithNonPassivatingInitializerMethodTest) testPassivationCapableBeanWithNonPassivatingDecoratorInjectedFieldFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField.DecoratorWithNonPassivatingInjectedFieldTest) testEnterpriseBeanWithNonPassivatingDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator.EnterpriseBeanWithNonPassivatingDecoratorTest) testDecoratorListedTwiceInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml.DecoratorListedTwiceInBeansXmlTest) testNonExistantDecoratorClassInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.nonExistantClassInBeansXml.NonExistantDecoratorClassInBeansXmlTest) -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-897) java.lang.ClassFormatError: Illegal classname - org/jboss/jsr299/tck/tests/extensions/alternative...

by Kyle Grucci (JIRA)

java.lang.ClassFormatError: Illegal classname - org/jboss/jsr299/tck/tests/extensions/alternative... ---------------------------------------------------------------------------------------------------- Key: WELD-897 URL: https://issues.jboss.org/browse/WELD-897 Project: Weld Issue Type: Bug Environment: All platforms - but noticed on Solaris x86 Reporter: Kyle Grucci The CDI TCK passes all tests when run using Glassfish 3.x with Oracle's JDK 1.6.0_24. However, when we change to use Oracle's JDK 1.6.0_25 patch, deployment of some of the test war files to the autodeploy directory of Glassfish results in the errors below. Talking with Pete Muir, it appears that the JDK has tightened something and is now exposing a bug in Weld. [#|2011-05-03T13:02:50.870-0400|SEVERE|glassfish3.2|javax.enterprise.system.to ols.admin.org.glassfish.deployment.admin|_ThreadID=17;_ThreadName=Thread-1;|Ex ception while loading the app : by java.lang.ClassFormatError: Illegal class name "org/jboss/jsr299/tck/tests/extensions/alternative/metadata/org$jboss$weld$bea n-org$jboss$jsr299$tck$tests$extensions$alternative$metadata$AlternativeMetada taTest-ManagedBean-org$jboss$jsr299$tck$tests$extensions$alternative$metadata$ Grocery[@javax$enterprise$context$RequestScoped()@org$jboss$jsr299$tck$tests$e xtensions$alternative$metadata$Cheap()@org$jboss$jsr299$tck$tests$extensions$a lternative$metadata$GroceryInterceptorBinding()@org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$NamedStereotype()]{org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$Grocery$bread[@javax$enterprise$inject$Produces() ]$org$jboss$jsr299$tck$tests$extensions$alternative$metadata$Grocery$fruit[@ja vax$inject$Inject()@org$jboss$jsr299$tck$tests$extensions$alternative$metadata $Cheap()]$org$jboss$jsr299$tck$tests$extensions$alternative$meta data$Grocery$vegetables[@javax$inject$Inject()]$org$jboss$jsr299$tck$tests$ext ensions$alternative$metadata$Grocery$getMilk[@javax$enterprise$inject$Produces ()]( org.jboss.weld.exceptions.WeldException: by java.lang.ClassFormatError: Illegal class name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-707) Intercepted bean method notifyAll() cannot be declared final

by Adam Warski (JIRA)

Intercepted bean method notifyAll() cannot be declared final ------------------------------------------------------------ Key: WELD-707 URL: https://jira.jboss.org/browse/WELD-707 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Adam Warski This started showing up after upgrading from M4 to M5, so to Weld 1.1.0. I'm using weldx, and as per the conversation on IRC with Pete this may be the cause. Exact message: WELD-001504 Intercepted bean method [method] public final native pl.softwaremill.service.organization.OrganizationService.notifyAll() (intercepted by pl.softwaremill.cdiext.transaction.TransactionalInterceptor) cannot be declared final -- 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

13 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (WELD-744) Interceptor and Decorator validation assumes that producer fields and methods will be public

by Pete Muir (JIRA)

Interceptor and Decorator validation assumes that producer fields and methods will be public -------------------------------------------------------------------------------------------- Key: WELD-744 URL: https://jira.jboss.org/browse/WELD-744 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.CR1 Needs to iterate over the class hierarchy looking at declared methods -- 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

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-906) Jetty 7.2+ container incorrectly identified as Jetty 7 container

by Ben Sommerville (JIRA)

Jetty 7.2+ container incorrectly identified as Jetty 7 container ---------------------------------------------------------------- Key: WELD-906 URL: https://issues.jboss.org/browse/WELD-906 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Ben Sommerville Priority: Minor Weld-servlet can identify a jetty 7.3 or 7.4 environment as a Jetty 7.0 environment (similar problem to WELD-879 but for Jetty not tomcat) In Listener.java it checks for a Jetty 7 container before checking for a Jetty 7.2+ container. The version 7 check looks for the presence of org.eclipse.jetty.servlet.ServletHandler which is present (but not necessarily visible) in all jetty 7.x environments. By default this class won't be found in Jetty 7.2+, but in this case Weld won't actually work. To run Weld under Jetty 7.2+ you need to expose some of the server classes that are normally hidden, and if you don't explicitly exclude the ServletHandler class the environment is detected as Jetty 7 not 7.2+ The suggested fix would be to reverse the order in which containers are checked and check for JettyPost72Container before checking for JettyContainer You can work around this issue by using META-INF/services to specify container or setting the ServletHandler class as a server class so that the web app can't see it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-657) Align instructions for running examples with Jetty

by Jozef Hartinger (JIRA)

Align instructions for running examples with Jetty -------------------------------------------------- Key: WELD-657 URL: https://jira.jboss.org/browse/WELD-657 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.0.Beta2 The examples/jsf/numberguess/readme.txt file describes how to run the example on Jetty using Eclipse. The reference documentation provides instructions for running the example on Jetty both from command line and Eclipse. These two information sources should be merged to provide the same instructions (or reference the other source). -- 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

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (WELDX-88) StartMain should support shutdown

by Edvin Syse (JIRA)

StartMain should support shutdown --------------------------------- Key: WELDX-88 URL: https://jira.jboss.org/jira/browse/WELDX-88 Project: Weld Extensions Issue Type: Feature Request Components: Weld Extensions Affects Versions: Java SE 1.0.1 Environment: n/a Reporter: Edvin Syse Priority: Minor When starting a project with org.jboss.weld.environment.se.StartMain, one would assume that weld.shutdown() would be run upon jvm shutdown, but it is not. This could easily be fixed with a minor adjustment. Please see the attached StartMain.java. -- 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

13 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-407) Provide warnings if AnnotatedType is not sensible

by Pete Muir (JIRA)

Provide warnings if AnnotatedType is not sensible ------------------------------------------------- Key: WELD-407 URL: https://jira.jboss.org/jira/browse/WELD-407 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 For example, if there are no constructors specified at all, or if the javaMember doesn't belong to the actual class hierarchy of the annotatedType -- 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

13 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-388) Fluent messages

by Nicklas Karlsson (JIRA)

Fluent messages --------------- Key: WELD-388 URL: https://jira.jboss.org/jira/browse/WELD-388 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Priority: Minor Make error messages read more fluent instead of the "Message : detail" format sometimes seen -- 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

13 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-539) Upgrade Weld examples to use shared Jetty/Tomcat plugins

by Pete Muir (JIRA)

Upgrade Weld examples to use shared Jetty/Tomcat plugins -------------------------------------------------------- Key: WELD-539 URL: https://jira.jboss.org/browse/WELD-539 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Fix For: 1.0.2.CR1 -- 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

13 years, 6 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2011