August 2012 - cdi-dev - Jboss List Archives

by pmuir＠redhat.com

The following is a new meeting request: Subject: CDI 1.1 weekly meeting Organiser: Peter Muir <pmuir(a)redhat.com> Time: 16:00:00 GMT+00:00 - 17:00:00 GMT+00:00 Recurrence: Every Monday. No end date. Effective Aug 13, 2012. Invitees: "cdi-dev(a)lists.jboss.org" <cdi-dev(a)lists.jboss.org>, Joseph Bergmark/Durham/IBM <bergmark(a)us.ibm.com>, Mike Brock <cbrock(a)redhat.com> *~*~*~*~*~*~*~*~*~* Weekly CDI 1.1 meeting http://www.timeanddate.com/worldclock/converted.html?iso=20120803T15&p1=0... We will try to use Google Hangout, join #jsr346 10 minutes before the meeting to request an invite. Otherwise switch to the phone teleconference, see https://docs.google.com/spreadsheet/pub?key=0ApqHbXzB1R1gdGRFWXB4TVpNeWFJ... for details.

12 years, 4 months

1
0
0 / 0

CDI 1.1 weekly meeting

by pmuir＠redhat.com

The following is a new meeting request: Subject: CDI 1.1 weekly meeting Organiser: Peter Muir <pmuir(a)redhat.com> Time: Monday, 13 August 2012, 16:00:00 GMT+00:00 - 17:00:00 GMT+00:00 Invitees: "cdi-dev(a)lists.jboss.org" <cdi-dev(a)lists.jboss.org>, Joseph Bergmark/Durham/IBM <bergmark(a)us.ibm.com> *~*~*~*~*~*~*~*~*~* Weekly CDI 1.1 meeting http://www.timeanddate.com/worldclock/converted.html?iso=20120803T15&p1=0... We will try to use Google Hangout, join #jsr346 10 minutes before the meeting to request an invite. Otherwise switch to the phone teleconference, see https://docs.google.com/spreadsheet/pub?key=0ApqHbXzB1R1gdGRFWXB4TVpNeWFJ... for details.

12 years, 4 months

1
0
0 / 0

Bean Validation 1.1 method validation

by Pete Muir

Hi all Gunnar raised https://issues.jboss.org/browse/CDI-242 which is a very nice idea. But the question is, who should define this interceptor. IMO it should be Bean Validation. Thoughts?

12 years, 4 months

2
2
0 / 0

Weekly meeting

by Pete Muir

All We need to get a weekly meeting setup to run over issues. At the end of each meeting we'll sort out what issues we will look at for the next meeting. People who want to attend, please respond with: * the timezone you are normally in * what times and days you can do (either in your local time, or UTC) I'm expecting these people to reply :-) * Mark Struberg * Martin Kouba * Jozef Hartinger * Mike Brock But everyone is welcome! pete

12 years, 4 months

7
9
0 / 0

[JBoss JIRA] (CDI-248) Provide means to observe a group of qualified events ("Qualifier Inheritance"?)

by Jens Schumann (JIRA)

Jens Schumann created CDI-248: --------------------------------- Summary: Provide means to observe a group of qualified events ("Qualifier Inheritance"?) Key: CDI-248 URL: https://issues.jboss.org/browse/CDI-248 Project: CDI Specification Issues Issue Type: Feature Request Components: Concepts, Events Reporter: Jens Schumann We have been using CDI events for application development quite extensively. For instance we use events to propagate entity lifecycle events (@Created/@Updated/@Deleted Customer customer) or GUI selections (@Selected/@Deselected Customer customer) and implement related business logic in event observers. (e.g. send email for newly created customers, clear cached values on select/deselect/create/update/delete ...). This works quite well, however we have noticed that especially our JSF Presentation Tier contains lots of observer methods implementing the same behavior for a group of related CDI events. Example: {code} public class XyzBean { public void onCustomerCreate(@Observes @Created Customer customer) { reset();} public void onCustomerUpdate(@Observes @Updated Customer customer) { reset();} public void onCustomerDelete(@Observes @Deleted Customer customer) { reset();} } {code} Looks ugly, doesn't it? The above example could be improved if CDI would be able to observe a group of qualified events, e.g. public void onCustomerLifeCycleEvent(@Observes @LifeCycleChange Customer customer) { reset(); } - ignore method and qualifier names for now. Since Java does not support annotation inheritance grouping could be achieved using "qualified qualifier annotations": {code} @Qualifier public @interface LifeCycleChange @Qualifier @LifeCycleChange public @interface Created @Qualifier @LifeCycleChange public @interface Updated @Qualifier @LifeCycleChange public @interface Deleted @Qualifier public @interface SelectionChange @Qualifier @SelectionChange public @interface Selected @Qualifier @SelectionChange public @interface Deselected {code} WDYT? Side effects? Problems? -- 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, 4 months

2
3
0 / 0

[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, 4 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, 4 months

3
2
0 / 0

[JBoss JIRA] (CDI-237) missing beans.xml

by Craig Ringer (JIRA)

Craig Ringer created CDI-237: -------------------------------- Summary: missing beans.xml Key: CDI-237 URL: https://issues.jboss.org/browse/CDI-237 Project: CDI Specification Issues Issue Type: Feature Request Environment: N/A, any Java EE 6 Reporter: Craig Ringer Priority: Minor It's common, especially for new users of Java EE and CDI, for confusion to arise because of a missing or misplaced beans.xml file. Injection sites that should be injected are null, interceptors don't run, etc. People experienced with CDI immediately spot what's wrong, but if you haven't worked with EE much it can throw you quite badly. It's particularly problematic when beans.xml exists, but isn't where the server expects it to be. This can happen when a jar-layout archive is deployed as a .war or vice versa (something newbies can and will do), or when beans.xml is placed in META-INF/ for a war archive where it's supposed to be in WEB-INF/ . It would be very helpful if it were possible to efficiently detect an archive that uses javax.inject.* annotations without a beans.xml file and issue a warning. To enhance the usability of CDI and its accessibility to new developers, IMO the spec should encourage this. A deployment error when javax.inject.Inject etc are used without a beans.xml file isn't appropriate, as there may be non-CDI code using those annotations, but a warning would make a big difference to usability. It's possible this is better done in an application-server specific context rather than as anything to do with the CDI specification, since the AS is scanning the archive during deployment anyway. If that's the case, it's probably best to move this issue to the JBoss AS 7 JIRA. If it's possible for a CDI impl to *efficiently* detect javax.inject.* and warn, though, it'd be a good thing to encourage in the spec. -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] (CDI-242) Support Bean Validation 1.1 method validation

by Gunnar Morling (JIRA)

Gunnar Morling created CDI-242: ---------------------------------- Summary: Support Bean Validation 1.1 method validation Key: CDI-242 URL: https://issues.jboss.org/browse/CDI-242 Project: CDI Specification Issues Issue Type: Feature Request Components: Java EE integration Reporter: Gunnar Morling CDI should integrate with Bean Validation to support the [method validation|http://beanvalidation.org/1.1/spec/#d0e2147] feature defined in BV 1.1. BV specifies an annotation [@MethodValidated|http://beanvalidation.org/1.1/spec/#validationapi-triggeringmethodvalidation] which could be used as interceptor binding annotation: {code} @MethodValidated public class OrderService { public OrderService(@NotNull CreditCardProcessor creditCardProcessor) { //... } public void placeOrder( @NotNull @Size(min=3, max=20) String customerCode, @NotNull Item item, @Min(1) int quantity) { //... } } {code} -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] (CDI-241) Support dependency injection within Bean Validation constraint validators

by Gunnar Morling (JIRA)

Gunnar Morling created CDI-241: ---------------------------------- Summary: Support dependency injection within Bean Validation constraint validators Key: CDI-241 URL: https://issues.jboss.org/browse/CDI-241 Project: CDI Specification Issues Issue Type: Feature Request Components: Java EE integration Reporter: Gunnar Morling CDI should integrate with Bean Validation to support dependency injection within BV {{ConstraintValidator}} implementations. >From the BV 1.1 [spec early draft|http://beanvalidation.org/1.1/spec/#bootstrapping-usageandcontainer...]: {quote} Java EE should obey the rules defined above and enable Context and Dependency Injection (CDI) support to {{ValidatorFactory}} instances. In particular: * Let {{Validator}} and {{ValidatorFactory}} object be injectable. * Use a default {{ConstraintValidatorFactory}} implementation that returns CDI managed {{ConstraintValidator}} objects. The scope of these instances is dependent as the Bean Validation provider is responsible for them. * Provide CDI managed instances of {{ConstraintValidatorFactory}}, {{MessageInterpolator}} and {{TraversableResovler}} if customized classes are requested in the XML deployment descriptor. {quote} -- 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, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2012