December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-814) Resources injected to producer fields fail to be produced

by John Ament (JIRA)

Resources injected to producer fields fail to be produced --------------------------------------------------------- Key: WELD-814 URL: https://issues.jboss.org/browse/WELD-814 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.CR3 Reporter: John Ament When you inject a resource in to a bean (session, managed, cdi, etc), the producer field that can be bound to it fails to deploy, at least under AS 6. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-813) Assign a known ProtectionDomain to Weld proxies to enable code-source based permissions by a user

by Sivakumar Thyagarajan (JIRA)

Assign a known ProtectionDomain to Weld proxies to enable code-source based permissions by a user ------------------------------------------------------------------------------------------------- Key: WELD-813 URL: https://issues.jboss.org/browse/WELD-813 Project: Weld Issue Type: Bug Reporter: Sivakumar Thyagarajan I am investigating if we can atleast have a user-level workaround for the Security Manager issue (WELD-32 and corresponding GlassFish issue http://java.net/jira/browse/GLASSFISH-15078) as that may not be fixed in 1.1.0.Final. The Weld-generated proxies uses the default ProtectionDomain [1], as the proxies are generated using ClassLoader.defineClass(String name, byte[] b, int off, int len). This prevents a user specify an application specific permission grant to get Weld working in a SM, and having to provide the suppressAccessChecks Permission for all classes. Please consider modifying defining the generated proxy to use a known PD (such as the PD of the proxied Class or some other known PD/CodeSource), to enable users to provide explicit Permissions for Weld generated proxies [1] https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/wel... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-202) EnterpriseEventInheritanceTest -- incorrect assumption

by Sivakumar Thyagarajan (JIRA)

EnterpriseEventInheritanceTest -- incorrect assumption ------------------------------------------------------ Key: CDITCK-202 URL: https://issues.jboss.org/browse/CDITCK-202 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR1 Reporter: Sivakumar Thyagarajan This is an issue similar to CDITCK-74. The following tests in 1.0.2.SP1 fails with GlassFish org.jboss.jsr299.tck.tests.event.observer.enterprise.EnterpriseEventInheritenceTest.testNonStaticObserverMethodInherited org.jboss.jsr299.tck.tests.event.observer.enterprise.EnterpriseEventInheritenceTest.testNonStaticObserverMethodIndirectlyInherited Farmer.observeEggLaying [1] still tries to record using "this" and EventPayload.recordVisit() [2] still uses the passed object's class. This may not work in environments where the EJB Bean is subclassed as is the case with Glassfish. For instance in GlassFish, we see the following [class org.jboss.jsr299.tck.tests.event.observer.enterprise._LazyFarmer_Serializable, class org.jboss.jsr299.tck.tests.event.observer.enterprise._Farmer_Serializable] Daemon Thread [http-thread-pool-8080(1)] (Suspended (breakpoint at line 45 in EnterpriseEventInheritenceTest)) EnterpriseEventInheritenceTest.testNonStaticObserverMethodInherited() line: 45 Need to fix the test so that is agnostic of EJB implementation strategy -- either see if the recorded classes are assignable from the original EJBs or have the 2 EJBs have a method that returns their respective names. [1] http://anonsvn.jboss.org/repos/weld/cdi-tck/tags/1.0.2.SP1/impl/src/main/... and [2] http://anonsvn.jboss.org/repos/weld/cdi-tck/tags/1.0.2.SP1/impl/src/main/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (WELD-808) Performance drop after introducing observer checks

by Marius Bogoevici (JIRA)

Performance drop after introducing observer checks -------------------------------------------------- Key: WELD-808 URL: https://issues.jboss.org/browse/WELD-808 Project: Weld Issue Type: Bug Components: Events Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.Final Fix for WELD-805 has created a performance regression: http://hudson.qa.jboss.com/hudson/view/Weld/job/perf-weld-numberguess-str... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (WELD-807) Regression in proxy generation for Glassfish

by Marius Bogoevici (JIRA)

Regression in proxy generation for Glassfish -------------------------------------------- Key: WELD-807 URL: https://issues.jboss.org/browse/WELD-807 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.CR3 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.Final Post WELD-804, proxies generated in Glassfish may fail with a CNFE, if the proxy bean type is a java.*/javax.* class. Solution: instead of automatically assuming that the classloader of a given class must be used for proxy generation, use ProxyServices for deciding (the default implementation of ProxyServices will be modified to use the classloader of that particular class). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Updated: (WELD-811) Hierarchy injection is not working with external annotation type.

by Rogerio Baldini (JIRA)

[ https://issues.jboss.org/browse/WELD-811?page=com.atlassian.jira.plugin.s... ] Rogerio Baldini updated WELD-811: --------------------------------- Steps to Reproduce: Create an extension wrapping an annotation type in class using injected fields (or methods) of its superclass. class Foo { @Inject BeanManager beanManager; } class Bar extends Foo { // beanManager will be null. } public <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) { AnnotatedType<T> w = wrapAnnotatedType(pat.getAnnotatedType()); pat.setAnnotatedType(w); } was: Create an extension wrapping an annotation type in class using injected fields (or methods) of its superclass. class Foo { @Inject BeanManager beanManager; } class Bar extends Foo { // beanManager will be null. } public <T> void processAnnotatedType(@Observes ProcessAnnotatedType<T> pat) { AnnotatedType<T> w = handleAnnotatedType(pat.getAnnotatedType()); pat.setAnnotatedType(w); } > Hierarchy injection is not working with external annotation type. > ----------------------------------------------------------------- > > Key: WELD-811 > URL: https://issues.jboss.org/browse/WELD-811 > Project: Weld > Issue Type: Bug > Components: Weld SPI > Affects Versions: 1.1.0.CR3 > Reporter: Rogerio Baldini > > In WeldClassImpl constructor, superclass is set as an Object.class when annotatedType is instanceof ExternalAnnotatedType (discovered flag). Why? > This behavior causes a non injection of superclasses fields and methods. Is this correct ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[JBoss JIRA] Created: (CDITCK-168) extensions.processBean.ProcessBean event count issue

by Scott Ferguson (JIRA)

extensions.processBean.ProcessBean event count issue ---------------------------------------------------- Key: CDITCK-168 URL: https://jira.jboss.org/browse/CDITCK-168 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR1 Environment: any Reporter: Scott Ferguson The issue is in an assertion in extensions.processBean.ProcessBeanTest, counting the number of times the Cowshed bean raises a discovery event. There are three tests affected by this issue: extensions.processBean.ProcessBeanTest testProcessProducerFieldEvent() testProcessProducerMethodEvent() extensions.processBean.ProcessSessionBeanTest testProcessSessionBeanEvent() specifically testProcessProducerMethodEvent() 79: assert ProcessBeanObserver.getCowShedProcessBeanCount() == 2; testProcessProducerFieldEvent() 102: assert ProcessBeanObserver.getChickenHutchProcessBeanCount() == 2; testProcessSessionBeanEvent() 63: assert ProcessBeanObserver.getElephantProcessBeanCount() == 2; But I can't see how this number is 2 instead of 1. The Cowshed looks like: public class Cowshed { @Produces public Cow getDaisy() { ... } } So there should be 3 relevant extension events fired: ProcessBean<Cowshed> ProcessProducerMethod<Cowshed, Cow> ProcessBean<Cow> I double checked the ProcessProducerMethod interface: ProcessProducerMethod<T,X> extends ProcessBean<X> which is where the ProcessBean<Cow> comes from, but I don't see where the 2nd ProcessBean<Cowshed> comes from. The ProcessSessionBean issue is essentially the same -- 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

14 years

3
8
0 / 0

[JBoss JIRA] Created: (WELD-806) PopulateDatabase must not handle transactions programmatically

by Marius Bogoevici (JIRA)

PopulateDatabase must not handle transactions programmatically -------------------------------------------------------------- Key: WELD-806 URL: https://issues.jboss.org/browse/WELD-806 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.1.0.CR3 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.Final see JBAS-8762 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (WELD-801) Publican best practices-compliant documentation

by Laura Bailey (JIRA)

Publican best practices-compliant documentation ----------------------------------------------- Key: WELD-801 URL: https://issues.jboss.org/browse/WELD-801 Project: Weld Issue Type: Feature Request Components: Documentation Reporter: Laura Bailey Assignee: Laura Bailey Update Weld documentation to conform to Publican best-practices. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (WELD-805) Weld must validate that the observer methods of a SessionBean are static or business methods

by Marius Bogoevici (JIRA)

Weld must validate that the observer methods of a SessionBean are static or business methods -------------------------------------------------------------------------------------------- Key: WELD-805 URL: https://issues.jboss.org/browse/WELD-805 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.1.0.CR3 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.Final This is required by the specification TCK test: org.jboss.jsr299.tck.tests.event.broken.observer.notBusinessMethod.EJBObserverMethodNotBusinessMethodTest#testObserverMethodOnEnterpriseBeanNotBusinessMethodOrStaticFails -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010