January 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-401) Clarify the meaning of "bean class local view"

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-401?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-401: ------------------------------------- Labels: CDI_spec_chge Ready_to_fix (was: ) > Clarify the meaning of "bean class local view" > ---------------------------------------------- > > Key: CDI-401 > URL: https://issues.jboss.org/browse/CDI-401 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > 3.2.2 Bean types of a session bean: > {quote} > The unrestricted set of bean types for a session bean contains all local interfaces of the bean and their superinterfaces. If the session bean has a *bean class local view*, the unrestricted set of bean types contains the bean class and all superclasses. > ... > {quote} > AFAIK the EJB spec does not define anything like "bean class local view". I believe the CDI spec is referencing *No-Interface View* here (a variation of the local view that exposes the non-static public methods of the bean class without the use of a separate business interface). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-404) adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated"

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-404?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-404: ------------------------------------- Labels: CDI_spec_chge CDI_tck_chge (was: ) > adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated" > ----------------------------------------------------------------------------------------------- > > Key: CDI-404 > URL: https://issues.jboss.org/browse/CDI-404 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Tang Yong > Labels: CDI_spec_chge, CDI_tck_chge > Fix For: 1.2 Proposed > > > [1] and [2] has reported an issue about > bean-discovery-mode="annotated". Although there are some workarounds for > the issue, I think that in the future, we should support interceptor > implict scanning while an user uses bean-discovery-mode="annotated". > Apparently, just as bean-discovery-mode="annotated", CDI Spec and > Interceptor Spec are disconnected. > [1]:https://java.net/jira/browse/GLASSFISH-20667 > [2]:http://stackoverflow.com/questions/17258639/interceptor-issue-with-jav... > About detailed discussion, please seeing the following, > https://java.net/projects/javaee-spec/lists/users/archive/2013-09/message/7 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-404) adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated"

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-404?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-404: ------------------------------------------ I think Option 1 in [~arnelim] comment should be chosen : {{@Interceptor}} and {{@Decorator}} should become bean defining annotation. We'll propbably extend the annotations list for bean defining annotation with CDI-406, so why not add these 2 as well ? > adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated" > ----------------------------------------------------------------------------------------------- > > Key: CDI-404 > URL: https://issues.jboss.org/browse/CDI-404 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Tang Yong > Fix For: 1.2 Proposed > > > [1] and [2] has reported an issue about > bean-discovery-mode="annotated". Although there are some workarounds for > the issue, I think that in the future, we should support interceptor > implict scanning while an user uses bean-discovery-mode="annotated". > Apparently, just as bean-discovery-mode="annotated", CDI Spec and > Interceptor Spec are disconnected. > [1]:https://java.net/jira/browse/GLASSFISH-20667 > [2]:http://stackoverflow.com/questions/17258639/interceptor-issue-with-jav... > About detailed discussion, please seeing the following, > https://java.net/projects/javaee-spec/lists/users/archive/2013-09/message/7 -- 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, 11 months

1
0
0 / 0

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-408?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-408: ------------------------------------- Labels: CDI_spec_chge (was: ) > 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 > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-411) CDI conversation activation conflicts with the Servlet spec

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-411?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-411: ------------------------------------- Labels: CDI_spec_chge CDI_tck_chge (was: ) > CDI conversation activation conflicts with the Servlet spec > ----------------------------------------------------------- > > Key: CDI-411 > URL: https://issues.jboss.org/browse/CDI-411 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Labels: CDI_spec_chge, CDI_tck_chge > Fix For: 1.2 Proposed > > > The Servlet specification says: > {quote} > If the client hasn't set character encoding and the request data is encoded with a > different encoding than the default as described above, breakage can occur. To > remedy this situation, a new method setCharacterEncoding(String enc) has been > added to the ServletRequest interface. Developers can override the character > encoding supplied by the container by calling this method. It must be called prior to > parsing any post data or reading any input from the request. Calling this method > once data has been read will not affect the encoding. > {quote} > The CDI specification says: > {quote} > The container provides a filter with the name "CDI Conversation Filter", which may be mapped in web.xml, allowing the > user alter when the conversation is associated with the servlet request. If this filter is not mapped in any web.xml in the > application, the conversation associated with a Servlet request is determined at the beginning of the request before calling any > service() method of any servlet in the web application, calling the doFilter() method of any servlet filter in the web > application and before the container calls any ServletRequestListener or AsyncListener in the web application. > {quote} > and > {quote} > The long-running conversation associated with a request may be propagated to any Servlet request via use of a request > parameter named cid containing the unique identifier of the conversation. > {quote} > This implies that in the default setup (CDI Conversation Filter not mapped), a CDI implementation is required to determine the conversation at the beginning of the request. That means that it has to read the "cid" parameter before any listener/filter/servlet is invoked. Reading the "cid" parameter causes the request body to be read. Therefore, if a listener/filter/servlet attempts to set the request character encoding using the aforementioned setCharacterEncoding(String enc) method, this never has any effect because a CDI implementation has already read the request body using the default encoding. > This can be worked around by mapping the CDI Conversation Filter and adding a custom encoding-setting filter before it. However, in the default configuration this issue often causes confusion. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-405) Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-405?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-405: ------------------------------------------ These issue are all related to what should be told about scope in CDI and what should be left to other spec. > Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1 > -------------------------------------------------------------------------------- > > Key: CDI-405 > URL: https://issues.jboss.org/browse/CDI-405 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > @RequestScoped and @ApplicationScoped are not servlet-specific (see sections 6.7.1 and 6.7.3 for more use cases). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-405) Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-405?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-405: ------------------------------------- Labels: CDI_spec_chge Ready_to_fix (was: ) > Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1 > -------------------------------------------------------------------------------- > > Key: CDI-405 > URL: https://issues.jboss.org/browse/CDI-405 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > @RequestScoped and @ApplicationScoped are not servlet-specific (see sections 6.7.1 and 6.7.3 for more use cases). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-406) Make stereotypes bean defining annotations

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-406?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-406: ------------------------------------- Labels: CDI_spec_chge CDI_tck_chge Ready_to_fix (was: CDI_impl_chge CDI_spec_chge CDI_tck_chge Ready_to_fix) > Make stereotypes bean defining annotations > ------------------------------------------ > > Key: CDI-406 > URL: https://issues.jboss.org/browse/CDI-406 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Labels: CDI_spec_chge, CDI_tck_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > For example @Model -- 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, 11 months

1
0
0 / 0

Adding new label to ticket ready for fix

by Antoine Sabot-Durand

Hi all, Just to inform you that when I label a ticket with « Ready_to_fix », I also try to add label regarding impact on different part of CDI : CDI_api_chge : fix will change API and/or Javadoc CDI_spec_chge : fix will change specification document CDI_tck_chge : fix will change TCK and Implementation I may missed some impact but it’s an indication for people that will work on these points. Antoine Sabot-Durand ——————————————— Twitter : @antoine_sd CDI co-spec lead & eco-system development Agorava tech lead

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (CDI-410) @RequestScoped Javadoc outdated

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-410?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-410: ------------------------------------- Labels: CDI_api_chge Ready_to_fix (was: CDI_api Ready_to_fix) > @RequestScoped Javadoc outdated > ------------------------------- > > Key: CDI-410 > URL: https://issues.jboss.org/browse/CDI-410 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Labels: CDI_api_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The Javadoc for [@RequestScoped|http://docs.jboss.org/cdi/api/1.1/javax/enterprise/context/RequestScoped.html] is since CDI 1.1 out of sync with the [specification|http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#request_co...] -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2014