January 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-199) Mean to observe or intercept Conversation.begin

by Anthony O. (Created) (JIRA)

Mean to observe or intercept Conversation.begin ----------------------------------------------- Key: CDI-199 URL: https://issues.jboss.org/browse/CDI-199 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Anthony O. As Pete Muir suggested me in that [stackoverflow question|http://stackoverflow.com/questions/8340676/how-to-observe-or-int...], I'm asking here the possibility of observing or intercepting {{Conversation.begin}} method calls (or other methods on the {{Conversation}} object), event if it's a built-in bean. Has this already been the subject of a debate ? -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-196) Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values.

by Shruthi Nanjundaswamy (Created) (JIRA)

Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values. --------------------------------------------------------------------------------------------------- Key: CDI-196 URL: https://issues.jboss.org/browse/CDI-196 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts Reporter: Shruthi Nanjundaswamy -- 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, 5 months

3
2
0 / 0

Weld 2.0.0.Alpha1 released

by Jozef Hartinger

I am proud to announce the very first alpha release of Weld 2 which implements the Early Draft of CDI 1.1. For more details see the blog entry http://in.relation.to/Bloggers/Weld200Alpha1Released

12 years, 11 months

1
0
0 / 0

easy solution for class visibility checks?

by Mark Struberg

Hi folks! I just had an idea which is so simple that I just cannot believe it! So please review and ping me if I missed something. This topic is related to CDI-18 (BDA dropping) and CDI-129 (@EnterpriseApplicationScoped) What is the problem with CDI-1.0? Well, CDI-1.0 says nothing about class visibility, but instead tries to solve all those issues by introducing the BeanDefinitionArchive (BDA). This in turn creates more harm than good. An example of such a broken use case would be that it is currently allowed to have a public class @Singleton MyService {} residing in shared EAR jar being @Specialized by a public class @Singleton MySpecializedService extends MyService {} residing in WEB-INF/classes of one single webapp. Obviously (with a JSR-316 conform 'sane' classloader hierarchy set up) this will not work. Because MySpecializedService is not visible from the EAR nor the other webapps (because of the ClassLoader isolation). In CDI-18 I proposed to add the following rules: > The container must ensure that for any > * @Specializes @NScoped class Y extends X and > * @Alternative @NScoped class Y implements X > class Y is accessible by all classes which can access X in the same @NScoped context. The problem now is: how does a custom 3rd party scope determine those rules? Because the issue is not only valid for @EnterpriseApplicationScoped. Just imagine to add a @SystemScoped which is a singleton-per-JVM (residing in the System or extension ClassLoader), or a @ClusterScoped, ... Today I realized that the *only* relevant thing is actually if the context maintaining the scope of 'class Y' (see definition above) can see the class Y. It is just not valid to write a @EnterpriseApplicationScoped public class MyService if the EnterpriseApplicationScopedContext cannot see MyService. The easiest solution would be to add a method to Context which checks the visibility at startup: boolean isVisible(Class beanClass) or boolean isVisible(String className) (need to think about which one works better, esp with different scenarios) Of course since #addContext is only in AfterBeanDiscovery, we need to do this in some 'verifyDeployment' phase after the bean scanning. wdyt? Is the intention clear? Or should I bring more samples about how that would work? Is there any flaw in there which I have overlooked? LieGrue, strub

12 years, 12 months

6
18
0 / 0

[JBoss JIRA] (CDI-50) Ability to veto beans, both unconditionally and based on classes visible

by Martin Kouba (Commented) (JIRA)

[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys... ] Martin Kouba commented on CDI-50: --------------------------------- Example code in spec should also be fixed to use fully qualified class names {code} @Requires({Customer.class, Supplier.class}) public class Order { ... } {code} to: {code} @Requires({"com.foo.Customer", "com.foo.Supplier"}) public class Order { ... } {code} > Ability to veto beans, both unconditionally and based on classes visible > ------------------------------------------------------------------------ > > Key: CDI-50 > URL: https://issues.jboss.org/browse/CDI-50 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > > This should support both a straight veto, and conditional based on classes available. > Seam Solder supports this as @Veto and @Requires({Foo.class, Bar.class}). > Mark Struberg proposed using @Optional -- 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

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2012