July 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-226) Update CDI TCK release notes

by Martin Kouba (JIRA)

Update CDI TCK release notes ---------------------------- Key: CDITCK-226 URL: https://issues.jboss.org/browse/CDITCK-226 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Priority: Minor https://github.com/weld/build -- 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

[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

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (WELDRAD-31) Test failed when ran jsf-weld-servlet

by hantsy bai (JIRA)

Test failed when ran jsf-weld-servlet -------------------------------------- Key: WELDRAD-31 URL: https://issues.jboss.org/browse/WELDRAD-31 Project: Weld Archetypes Issue Type: Bug Components: jsf-weld-servlet-webapp Affects Versions: jsf-weld-servlet-webapp-1.0.1.Beta1 Reporter: hantsy bai I created a web project from jsf-weld-servlet-webapp, and add seam3 persistence in project, when ran test, it failed. I do not know why it need hibernate search? ------------------------------------------------------------------ 2011-7-21 8:31:20 org.jboss.weld.bootstrap.WeldBootstrap <clinit> 信息: WELD-000900 1.1.0 (Final) 2011-07-21 08:31:20,581 DEBUG org.jboss.seam.persistence.HibernatePersistencePro vider - no Hibernate Search java.lang.ClassNotFoundException: Could not load class org.hibernate.search.Vers ion with the context class loader org.jboss.shrinkwrap.classloader.ShrinkWrapCla ssLoader@1ff7a1e or any of the additional ClassLoaders: [] at org.jboss.seam.solder.reflection.Reflections.classForName(Reflections .java:386) at org.jboss.seam.persistence.HibernatePersistenceProvider.<clinit>(Hibe rnatePersistenceProvider.java:60) at org.jboss.seam.persistence.hibernate.HibernateManagedSessionExtension Impl.<clinit>(HibernateManagedSessionExtensionImpl.java:65) at org.jboss.seam.persistence.hibernate.HibernateManagedSessionExtension .<init>(HibernateManagedSessionExtension.java:51) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct orAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.ServiceLoade r.prepareInstance(ServiceLoader.java:297) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.ServiceLoade r.loadService(ServiceLoader.java:262) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.ServiceLoade r.loadServiceFile(ServiceLoader.java:218) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.ServiceLoade r.reload(ServiceLoader.java:181) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.ServiceLoade r.iterator(ServiceLoader.java:370) at org.jboss.weld.bootstrap.ExtensionBeanDeployer.addExtensions(Extensio nBeanDeployer.java:93) at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootst rap.java:334) at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContaine r.startContainer(TestContainer.java:258) at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContain er.deploy(WeldEEMockContainer.java:71) at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(Containe rDeployer.java:62) at org.jboss.arquillian.impl.handler.ContainerDeployer.callback(Containe rDeployer.java:50) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager. java:63) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractE ventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeClass(EventTes tRunnerAdaptor.java:96) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:162) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:18 6) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute( Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:35) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4 Provider.java:115) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider .java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.inv oke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(Suref ireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(S urefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java: 69) 2011-07-21 08:31:20,805 INFO org.jboss.seam.solder.Version - Seam Solder 3.0.0. Final (build id: 3.0.0.Final) 2011-07-21 08:31:20,827 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Seam Config XML provider starting... 2011-07-21 08:31:20,829 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Loading XmlDocumentProvider: org.jboss.seam.config.xml.bootstrap.Resource LoaderXmlDocumentProvider 2011-07-21 08:31:20,842 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Reading XML file: file:/E:/MyWorks/bifincan/bifincan-web/target/classes/M ETA-INF/beans.xml 2011-07-21 08:31:20,886 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Reading XML file: jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam /solder/seam-solder-impl/3.0.0.Final/seam-solder-impl-3.0.0.Final.jar!/META-INF/ beans.xml 2011-07-21 08:31:20,888 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Reading XML file: jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam /solder/seam-solder/3.0.0.Final/seam-solder-3.0.0.Final.jar!/META-INF/beans.xml 2011-07-21 08:31:20,891 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Reading XML file: jar:file:/E:/Users/hantsy/.m2/repository/org/jboss/seam /persistence/seam-persistence-impl/3.0.0.Final/seam-persistence-impl-3.0.0.Final .jar!/META-INF/beans.xml 2011-07-21 08:31:20,904 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Adding XML Defined Bean: org.jboss.seam.transaction.SeSynchronizations 2011-07-21 08:31:20,927 INFO org.jboss.seam.config.xml.bootstrap.XmlConfigExten sion - Adding XML Defined Bean: org.jboss.seam.transaction.EntityTransaction Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.882 sec <<< FA ILURE! Running com.dna.bifincan.HelloWorldTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Results : Tests in error: com.dna.bifincan.BeanManagerTest: org.jboss.weld.exceptions.DeploymentExceptio n: WELD-001408 Unsatisfied dependencies for type [EntityManager] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.transacti on.EntityTransaction.entityManager] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.549s [INFO] Finished at: Thu Jul 21 08:31:21 GMT+08:00 2011 [INFO] Final Memory: 9M/23M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2. 7.2:test (default-test) on project bifincan-web: There are test failures. [ERROR] [ERROR] Please refer to E:\MyWorks\bifincan\bifincan-web\target\surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc -- 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-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

12 years, 9 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

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-946) Better format of "interceptor class specified twice" message.

by Ondrej Zizka (JIRA)

Better format of "interceptor class specified twice" message. ------------------------------------------------------------- Key: WELD-946 URL: https://issues.jboss.org/browse/WELD-946 Project: Weld Issue Type: Enhancement Components: Interceptors and Decorators Reporter: Ondrej Zizka Currently, the message is on a single line, usually very long one. {code} WELD-001416 Enabled interceptor class [<class>org.jboss.weld.environment.se.jpa.JpaTransactionInterceptor</class> in file:/home/ondra/work-unrelated/CDI-SE-JPA/target/classes/META-INF/beans.xml@10, <class>org.jboss.weld.environment.se.jpa.JpaTransactionInterceptor</class> in file:/home/ondra/work-unrelated/CDI-SE-JPA/src/main/java/META-INF/beans.xml@10] specified twice {code} Adding some newlines would improve readability: {code} WELD-001416 Enabled interceptor class specified twice: <class>org.jboss.weld.environment.se.jpa.JpaTransactionInterceptor</class> in file:/home/ondra/work-unrelated/CDI-SE-JPA/target/classes/META-INF/beans.xml@10, <class>org.jboss.weld.environment.se.jpa.JpaTransactionInterceptor</class> in file:/home/ondra/work-unrelated/CDI-SE-JPA/src/main/java/META-INF/beans.xml@10] {code} -- 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] Updated: (WELD-81) Add some smoke tests to core-test

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/WELD-81?page=com.atlassian.jira.plugin.sy... ] Ales Justin updated WELD-81: ---------------------------- Fix Version/s: TBC (was: 1.1.2.Final) > Add some smoke tests to core-test > --------------------------------- > > Key: WELD-81 > URL: https://issues.jboss.org/browse/WELD-81 > Project: Weld > Issue Type: Feature Request > Components: Testing Infrastructure (Mocks and Harness Integration) > Reporter: Pete Muir > Priority: Optional > Fix For: TBC > > > Weld is currently missing a set of smoke tests, a suite that exercises the key details of CDI (e.g. managed beans, session beans, observers, decorators, interceptors, servlet integration, jsf integration, the various contexts) but that doesn't delve into every specific of the spec. IOW a suite of say 50 tests that can run quickly, even in container. > These would be very useful to run with extensions such as Solder added to ensure that they don't alter the default behaviour accidentally or for testing non-spec-compliant containers such as Tomcat, Jetty or GAE. -- 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

[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

12 years, 9 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

12 years, 9 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

12 years, 9 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2011