April 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-845) Do not bundle slf4j static logger binding in weld-servlet.jar

by Kariem Hussein (JIRA)

Do not bundle slf4j static logger binding in weld-servlet.jar ------------------------------------------------------------- Key: WELD-845 URL: https://issues.jboss.org/browse/WELD-845 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.1.0.Final Reporter: Kariem Hussein Bundling a static logger implementation with the weld-servlet.jar generates a warning that would not be necessary. The weld-servlet.jar (_uber jar_) is still (or arguably more) useful without the binding. Opened this ticket as [requested by Pete|http://seamframework.org/Community/Slf4jBindingInWeldservletjar#comm...] in response to a forum thread. This could be done similar to WELDSE-12 (requested in [this comment|https://issues.jboss.org/browse/WELDSE-12?focusedCommentId=125079...]). Assumed that WELDX and it successor SOLDER are not the right projects for this request. Related forum posts: * [slf4j Binding in weld-servlet.jar|http://seamframework.org/Community/Slf4jBindingInWeldser...] * [slf4j StaticLoggerBinder - This code should have never made it into the jar|http://seamframework.org/Community/Slf4jStaticLoggerBinderThisCodeSho...] * [Weld SE and slf4j|http://seamframework.org/Community/WeldSEAndSlf4j] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] (CDITCK-235) Add tests for BM injection into container event observers

by Jozef Hartinger (Created) (JIRA)

Add tests for BM injection into container event observers --------------------------------------------------------- Key: CDITCK-235 URL: https://issues.jboss.org/browse/CDITCK-235 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Jozef Hartinger Fix For: 1.1.0.CR1 {quote}Service providers may have observer methods, which may observe any event, including any container lifecycle event, and obtain an injected BeanManager reference.{quote} It's probably a failure to inject BeanManager in BeforeBeanDiscovery which causes https://issues.apache.org/jira/browse/TOMEE-33 Currently, the TCK tests the BM injection for the following types of events: * AfterBeanDiscovery * AfterDeploymentValidation We should extend the coverage and test every kind of container lifecycle event (BeforeBeanDiscovery, ProcessAnnotatedType, ...). -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] (WELD-1029) Rewrite enhanced metadata sources

by Jozef Hartinger (Created) (JIRA)

Rewrite enhanced metadata sources --------------------------------- Key: WELD-1029 URL: https://issues.jboss.org/browse/WELD-1029 Project: Weld Issue Type: Task Components: Performance and Scalability, Reflection layer Affects Versions: 1.1.4.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha2 Rewrite implementations of Annotated* to be lightweight stateless objects. The goal is to improve memory footprint as well as make these objects serializable. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] (WELD-51) Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WELD-51?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated WELD-51: -------------------------------- Assignee: Jozef Hartinger Fix Version/s: 2.0.0.Alpha2 (was: 1.2.0.Beta1) > Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl > ----------------------------------------------------------------------------------------- > > Key: WELD-51 > URL: https://issues.jboss.org/browse/WELD-51 > Project: Weld > Issue Type: Feature Request > Components: Reflection layer > Reporter: Pete Muir > Assignee: Jozef Hartinger > Priority: Critical > Fix For: 2.0.0.Alpha2 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WELD-53) Refactor reflection layer to be less of a memory hog

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WELD-53?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger resolved WELD-53. --------------------------------- Assignee: Jozef Hartinger Fix Version/s: 2.0.0.Alpha2 (was: 1.2.0.Beta1) Resolution: Done > Refactor reflection layer to be less of a memory hog > ---------------------------------------------------- > > Key: WELD-53 > URL: https://issues.jboss.org/browse/WELD-53 > Project: Weld > Issue Type: Feature Request > Components: Resolution (Typesafe and by Name) > Reporter: Pete Muir > Assignee: Jozef Hartinger > Priority: Blocker > Fix For: 2.0.0.Alpha2 > > > Currently the reflection layer stores too much information, meaning we waste valuable heap space. This comes about because we build "extended metadata" for every deployed class; however we don't need this extended metadata for every class, and we also only need it at boot time. Therefore the proposed redesign looks like: > 1) Create lightweight AnnotatedType implementations (work done, see https://github.com/pmuir/weld-core/tree/WELD-13_initial_slim) > 2) Use these to fire the ProcessAnnotatedType events as needed (using the "backed" annotated impls) > 2a) If the annotated type is unchanged, keep the backed annotated impl. This is the annotated impl that will be kept around at runtime, and is designed to be as slimline as possible for mem usage, delegating everything possible to existing objects > 2b) If the annotated type is changed, wrap it in an "unbacked" annotated type. This may seem unecessary, however it does mean we are providing a consistent view for debugging, error reporting etc. > 3) If a bean is required for the AnnotatedType, load extended metadata for it. > 3a) This should be pluggable by the container, allowing something like jandex to be used if desired > 3b) I would propose we use a Map like structure on load, so that the api looks like: > ExtendedAnnotatedType ExtendedMetadataLoader.load(AnnotatedType type); > 3c) This extended metadata should include all the rich information available today on WeldClass and co, including stuff like being able to load methods by parameter annotations, meta-annotation support etc. > 3d) Beans are created, using the extended metadata > 3e) this extended metadata should have no references to it after bootstrap, allowing it to be removed at next gc run > Notes: > * Creating a parallel hierarchy of classes is not possible whilst preserving immutability, so extended metadata objects are not linked to each other, you traverse the graph using annotated type impls -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (WELDRAD-30) There is no org.jboss.weld.environment.tomcat.WeldLifecycleListener in weld-servlet

by hantsy bai (JIRA)

There is no org.jboss.weld.environment.tomcat.WeldLifecycleListener in weld-servlet ----------------------------------------------------------------------------------- Key: WELDRAD-30 URL: https://issues.jboss.org/browse/WELDRAD-30 Project: Weld Archetypes Issue Type: Bug Reporter: hantsy bai I created a web project from jsf-weld-servlet archetype, and uncommented the following in META-INF/context.xml, when I started tomcat, it threw exceptions   I exploered the weld-servlet jar file, I can not find this class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (WELD-1107) beans.xml + Singleton EJB fails to deploy

by Harold Campbell (JIRA)

Harold Campbell created WELD-1107: ------------------------------------- Summary: beans.xml + Singleton EJB fails to deploy Key: WELD-1107 URL: https://issues.jboss.org/browse/WELD-1107 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final Environment: JBoss AS 7.1.1.Final Reporter: Harold Campbell Singleton EJBs in the presence of beans.xml fail to deploy with a weld error. Without the presence of beans.xml the EJB deploys and functions as expected. Here's the full deployment attempt log: 12:42:50,533 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hcamp/code/jboss-as-7.1.1.Final/standalone/data/content/3a/11b79a5d3167adc8ec204eedf44cec07a50450/content 12:42:50,561 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "rfpushtest.war" 12:42:55,891 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment rfpushtest.war 12:42:56,529 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named Poller in deployment unit deployment "rfpushtest.war" are as follows: java:global/rfpushtest/Poller!com.foo.rfpushtest.ejb.singleton.Poller java:app/rfpushtest/Poller!com.foo.rfpushtest.ejb.singleton.Poller java:module/Poller!com.foo.rfpushtest.ejb.singleton.Poller java:global/rfpushtest/Poller java:app/rfpushtest/Poller java:module/Poller 12:42:57,493 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: rfpushtest.war 12:42:57,653 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.5 (AS71) 12:42:57,817 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment rfpushtest.war 12:42:59,592 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-1) Solder Config XML provider starting... 12:42:59,595 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-1) Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider 12:42:59,658 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-1) Reading XML file: vfs:/content/rfpushtest.war/WEB-INF/beans.xml 12:42:59,699 INFO [org.jboss.solder.Version] (MSC service thread 1-1) Solder 3.1.0.Final (build id: 3.1.0.Final) 12:43:07,485 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."rfpushtest.war".component.Poller.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."rfpushtest.war".component.Poller.START: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:116) at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:130) at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more Caused by: javax.ejb.EJBException: java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.jboss.as.weld.injection.WeldEEInjection can not access a member of class com.foo.rfpushtest.ejb.singleton.Poller with modifiers "" at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:333) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 9 more Caused by: java.lang.RuntimeException: java.lang.IllegalAccessException: Class org.jboss.as.weld.injection.WeldEEInjection can not access a member of class com.foo.rfpushtest.ejb.singleton.Poller with modifiers "" at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:103) at org.jboss.as.weld.injection.WeldManagedReferenceFactory.getReference(WeldManagedReferenceFactory.java:77) at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:90) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) ... 18 more Caused by: java.lang.IllegalAccessException: Class org.jboss.as.weld.injection.WeldEEInjection can not access a member of class com.foo.rfpushtest.ejb.singleton.Poller with modifiers "" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) [rt.jar:1.6.0_26] at java.lang.Class.newInstance0(Class.java:349) [rt.jar:1.6.0_26] at java.lang.Class.newInstance(Class.java:308) [rt.jar:1.6.0_26] at org.jboss.as.weld.injection.WeldEEInjection.produce(WeldEEInjection.java:100) ... 26 more 12:43:07,792 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "rfpushtest.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"rfpushtest.war\".component.Poller.START" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"rfpushtest.war\".component.Poller.START: Failed to start service"}} 12:43:07,811 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment rfpushtest.war 12:43:07,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment rfpushtest.war in 173ms 12:43:07,954 INFO [org.jboss.as.controller] (management-handler-thread - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."rfpushtest.war".component.Poller.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."rfpushtest.war".component.Poller.START: Failed to start service -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] (WELD-1096) Observing an array fails randomly

by Ales Justin (JIRA)

Ales Justin created WELD-1096: --------------------------------- Summary: Observing an array fails randomly Key: WELD-1096 URL: https://issues.jboss.org/browse/WELD-1096 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.1.6.Final Reporter: Ales Justin Assignee: Marko Lukša Fix For: 1.2.0.Beta1 See forum and pull-request for more info. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] (WELD-1104) Don't execute checkstyle on every incremental build

by Fred Bricon (JIRA)

Fred Bricon created WELD-1104: --------------------------------- Summary: Don't execute checkstyle on every incremental build Key: WELD-1104 URL: https://issues.jboss.org/browse/WELD-1104 Project: Weld Issue Type: Bug Reporter: Fred Bricon The Weld parent pom tells m2e to execute checkstyle on every incremental builds, that is on every file save. This causes infinite build loops with m2e + JBoss Tools : JBIDE-11485 In Eclipse, checkstyle should either be run manually or via the checkstyle integration plugin (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=347556). Please consider the [pull request|https://github.com/weld/core/pull/191] fixing this issue. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] (WELD-1102) Bean type Foo<B extends Bar> not assignable to required type Foo<Bar<Integer>>

by Marko Lukša (JIRA)

Marko Lukša created WELD-1102: --------------------------------- Summary: Bean type Foo<B extends Bar> not assignable to required type Foo<Bar<Integer>> Key: WELD-1102 URL: https://issues.jboss.org/browse/WELD-1102 Project: Weld Issue Type: Bug Reporter: Marko Lukša Assignee: Marko Lukša There is a strange piece of code in {{org.jboss.weld.util.reflection.Reflections}}: {code} public static boolean isAssignableFrom(Class<?> rawType1, Type[] actualTypeArguments1, Type type2) { ... } else if (type2 instanceof TypeVariable<?>) { TypeVariable<?> typeVariable = (TypeVariable<?>) type2; if (isTypeBounded(rawType1, actualTypeArguments1, typeVariable.getBounds())) { <--- suspicious! return true; } } ... } public static boolean isTypeBounded(Type type, Type[] lowerBounds, Type[] upperBounds) { if (lowerBounds.length > 0) { if (!isAssignableFrom(type, lowerBounds)) { return false; } } if (upperBounds.length > 0) { if (!isAssignableFrom(upperBounds, type)) { return false; } } return true; } {code} What's strange is that {{isTypeBounded()}} is called with actualTypeArguments1, which are actual type arguments of type1 (and not type2!). The result is that the bean type {{Foo<B extends Bar>}} is assignable to {{Foo<Bar<Baz>>}} (if Baz extends Bar), but it is NOT assignable to {{Foo<Bar<Integer>>}} just because Bar is not assignable from Integer. -- 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, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2012