March 2014 - cdi-dev - Jboss List Archives

Invisible yet important modification on cdi-spec.org

by Antoine Sabot-Durand

Hi All, I’ve been working since thursday on the website to prepare it for new contents and contributions. As I worked mainly on foundation, nothing is visible from the website. You can check the « new » version on staging URL [1]. Except for a few colors and pixel here and there, you should find the same site (let me know if I missed something before I switch to this new version tomorrow probably). So what was done ? : - Update to Awestruct 0.5.3 (version 0.5.4 is still in Release Candidate), - Update to Bootstap 3.1.1 (to avoid adding content with a « legacy » framework). Was a long work because a lot of things changed in templating. - Review Awestruct packaging to be able to generate the site and launch it more easily (it has been a hell to sort the problems out) - Clean all the css and ruby dependencies hell we had before. You can check the new Readme that gives all information regarding Awestruct usage and contribution. These modification are still in their own branch (bootstrap3) to check if I didn’t missed something. Please take a few minutes to test the new approach with Rake that is described in the README file and tell me if you encountered issues (didn’t have windows and linux box to test). Website Next step : - figure out why Jira plugin does’ work - work on the tutorial. I’ll send an other email on the subject. Antoine [1] : http://www.cdi-spec.org/staging/ [2] : https://github.com/cdi-spec/cdi-spec.org/blob/bootstrap3/README.adoc

10 years, 7 months

1
0
0 / 0

Scope of what bean archives an extension applies to

by John D. Ament

Hi all, Quick question. This is mostly from playing around with Weld SE 2.1.2, so I'm not sure if my question is going to be Weld SE specific or be generally applied. Looking through the spec, I did not see any obvious indications of this. What is the scope of the application of an Extension class? Suppose I had a JAR file that had META-INF/services/javax.enterprise.inject.spi.Extension with the contents of some extension class. Should the application of that extension class apply to all JARs within the same classpath? If that extension were listed in a WAR file, would it apply to the WAR and all JAR modules? John

10 years, 7 months

4
5
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-392: ------------------------------------- I agree with Mark that the current wording of the non-portable mode does not imply anything. > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-408) bean-discovery-mode="annotated" and Producers/Observers in @Dependent beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-408?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-408: ------------------------------- Right, I would prefer to keep bean defining annotations reasonably simple to understand. > bean-discovery-mode="annotated" and Producers/Observers in @Dependent beans > --------------------------------------------------------------------------- > > Key: CDI-408 > URL: https://issues.jboss.org/browse/CDI-408 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Reporter: Jens Schumann > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge > Fix For: 1.2 Proposed > > > Right now bean-discovery-mode="annotated" skips beans that are not annotated with an bean-defining annotation even if they contain an observer method or producer method/field. I would not recommend having (not annotated) @Dependent beans with @Observes or @Produces - I just had them by accident while playing around with Wildfly. > However there are two impacts: > 1. Someone might be confused by ignored @Producer's. Not a major issue here, the CDI runtime will report it. We could optionally document the behavior in the spec, so it's clear to everyone. However I think it's inconsistent, since @Produces may contain a scope (and has a default scope too). Therefore I would vote for @Produces support in bean-discovery-mode="annotated". Of course the enclosing class is not a managed bean that may be injected somewhere. > 2. Since Observer methods in "not annotated" beans fail silently this can be a major issue for applications, especially if you migrate from CDI 1.0 (CDI 1.0 source code and CDI 1.0 thinking model). Therefore I believe @Observer methods have to be included in bean-discovery-mode="annotated" even if the enclosing bean does not have a bean-defining annotation. Of course the enclosing class is not a managed bean that may be injected somewhere. > I understand that the proposal above might have negative impacts on class scanning performance in bean-discovery-mode="annotated". However silently failing @Observes can be a major cause of defects that have to be treated because of technical and political reasons. Technical - because it may cause bugs. And political - because in my experience many people are still skeptical that CDI events are a trustworthy achievement[1]. Possibly skipped observer methods won't make live easier. > If you believe the proposal would kill the original intent of bean-discovery-mode="annotated" please document the impact for Producers and Observers in the spec and even in the XSD. > -- > [1] I have trained a couple hundred people in using CDI and CDI events. And every time I have to argument against the uncertainty on event delivery: "How do I know which observers are active?", "Who ensures that event's are delivered?"... I personally LOVE events;) > > Btw: Which JIRA version is CDI 1.1 Final? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-392: ------------------------------- I think Mark makes a good point here. > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

Updated Invitation: CDI 1.2 MR meeting @ Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 (Perso)

by antoine.sabotdurand＠gmail.com

This event has been changed. Title: CDI 1.2 MR meeting Proposed agenda : - Ready to fix review and assignation - Discussion on other ticket - Progess and obstacles View your event at http://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazRi.... View your event at http://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazRi.... (changed) When: Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 Paris Where: IRC #jsr346 Channel on Freenode Calendar: Perso Who: (Guest list has been hidden at organizer's request) Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazR... Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cdi-dev(a)lists.jboss.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

10 years, 7 months

1
0
0 / 0

Updated Invitation: CDI 1.2 MR meeting @ Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 (Perso)

by antoine.sabotdurand＠gmail.com

This event has been changed. Title: CDI 1.2 MR meeting Proposed agenda : - Ready to fix review and assignation - Discussion on other ticket - Progess and obstacles View your event at http://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazRi.... (changed) When: Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 Paris Where: IRC #jsr346 Channel on Freenode Calendar: Perso Who: (Guest list has been hidden at organizer's request) Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazR... Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cdi-dev(a)lists.jboss.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

10 years, 7 months

1
0
0 / 0

Invitation: CDI 1.2 MR meeting @ Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 (Perso)

by Antoine Sabot-Durand

You have been invited to the following event. Title: CDI 1.2 MR meeting Proposed agenda : - Ready to fix review and assignation - Discussion on other ticket - Progess and obstacles When: Weekly from 6pm to 7pm on Monday from Mon Jan 27 to Mon Mar 31 Paris Where: IRC #jsr346 Channel on Freenode Calendar: Perso Who: (Guest list has been hidden at organizer's request) Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzcwczNhZGhoOGQwazR... Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cdi-dev(a)lists.jboss.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-392: ------------------------------------------ Ok, so what is your opinion [~jharting] about keeping or removing this non portable mode to simplify the spec? > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-392: ------------------------------------- Weld 2.x does implement the non-portable mode. > Clarify when the operations of BeanManager can be called > -------------------------------------------------------- > > Key: CDI-392 > URL: https://issues.jboss.org/browse/CDI-392 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Matus Abaffy > Assignee: Mark Struberg > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application." > This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2014