December 2013 - cdi-dev - Jboss List Archives

by Antoine Sabot-Durand

Hi all, I didn’t receive any extra wishes for the MR. So I guess we have a final list here (except if you bring your issues in live in the last minute). I propose the following agenda : 1. Discussion on the last ticket pending : CDI-395 Public fields in extensions should not be allowed [1] 2. Last second ticket if any 3. Starting the MR Regards, Antoine [1] https://issues.jboss.org/browse/CDI-395

10 years, 4 months

3
3
0 / 0

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

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-404?page=com.atlassian.jira.plugin.sy... ] Arne Limburg commented on CDI-404: ---------------------------------- Two options here, I guess: 1. Make @Interceptor and @Decorator a bean-defining annotation 2. Define, that the container must detect the problem that there is an interceptor or decorator enabled through beans.xml that is no bean, because it has no bean-defining annotation. > 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.1.1 (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, 4 months

1
0
0 / 0

Producer wrapper

by Mark Struberg

1. Producer / InjectionTarget might create instances which are wrapped in proxies. 2. event observer methods are allowed to be private and thus are not in the proxies. 3. extensions are allowed to 'decorate' InjectionTargets and Producers. This means that we need some unwrap method in the spec, right? Currently this does not York. LieGrue, strub

10 years, 4 months

2
1
0 / 0

Preparing CDI 2.0

by Antoine Sabot-Durand

Hi all, I really like to gather community feedback on CDI to prepare the coming CDI 2.0 JSR proposal. It will help us to deliver something nearer from user’s need and will have the side effect to make some buzz around CDI. I propose the following steps : 1. Open an informal idea box. A google form with which anybody could send us 3 wishes for CDI 2.0. It could be launch now and be open until midd-january for instance 2. Compiling these ideas + Our wishes idea + JIRA already open , we’ll prose a survey to obtain priorities on all the topic. It could be open from end-januray to mid-february (could be more depending on Java EE 8 launch timeframe) 3. Create the prioritize list of feature for CDI 2.0 4. Propose a JSR for CDI 2.0 in March-april including the list of prioritize items. Other side-effect from this is the possibility to gain new contributor to the specification in the process. Your feedback, ideas, concern about this idea are as always, welcome. Regards, Antoine

10 years, 4 months

1
0
0 / 0

MR issue list

by Antoine Sabot-Durand

Hi all, Just posted list of 22 issue we discussed these last weeks and their adoption status in MR [1]. So, 18 issues were already included, 3 were rejected and one still need input from implementations team : CDI-395 Public fields in extensions should not be allowed [2]. As I said in my previous mail we could still add a few more ticket (if they are not big) to discuss during our next meeting (monday 16th). So send the tickets ! [1] http://www.cdi-spec.org/news/2013/12/11/CDI-1-2MR-issues-list/ [2] https://issues.jboss.org/browse/CDI-395 Antoine Sabot-Durand

10 years, 4 months

1
0
0 / 0

monday's meeting notes

by Antoine Sabot-Durand

Hi all, You’ll find monday’s meeting notes here [1]. As mentioned in the notes we still have time to examine other easy tickets (would say between 5 and 10) to decide their inclusion in MR. So if you have wishes feel free to send them before the closing of the list after next meeting. Antoine [1] http://www.cdi-spec.org/news/2013/12/09/EG-meeting/

10 years, 4 months

1
0
0 / 0

Java EE 8 features survey

by Linda DeMichiel

As part of our early planning for Java EE 8, at JavaOne we held a "Meet the Spec Leads" BOF and a Java EE Platform expert group meeting to gather input about features to consider. A summary of the results of from that effort are linked here https://java.net/projects/javaee-spec/lists/jsr342-experts/archive/2013-1.... Our intent was to use the input from those gatherings to prepare a survey to collect feedback from the entire community, similar to what we had done a year ago for Java EE 7 issues. We've just launched this broader Java EE 8 features survey. Due to its length, we are running it in two parts. Part 1 is now live at https://www.surveymonkey.com/s/KGV7RWS We plan to release part 2 in mid/late January. Once we gather, distill, and announce the results, our plan will be to ask for further feedback to help us prioritize among items that receive significant support. Please participate and help us spread the word. thanks, -Linda

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-318) @WithAnnotations types can appear on any supertype

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-318?page=com.atlassian.jira.plugin.sy... ] Martin Kouba edited comment on CDI-318 at 12/9/13 12:26 PM: ------------------------------------------------------------ Actually this is an inconsistency between the spec wording and javadoc. An example: {code} @Target({ TYPE, METHOD, PARAMETER, FIELD, CONSTRUCTOR }) @Retention(RUNTIME) @Inherited public @interface Marker { } @Marker public interface Foo { } public class Bar implements Foo { } {code} and observer: {code} public void observeMarker(@WithAnnotations({ Marker.class }) @Observes ProcessAnnotatedType<?> pat) { } {code} @WithAnnotations javadoc defines the PAT for Bar should be observed (CDI does not follow JSL rules here) whereas the spec text states CDI should follow JSL rules. was (Author: mkouba): Actually this is not a real issue but rather a hint for clarification. An example: {code} @Target({ TYPE, METHOD, PARAMETER, FIELD, CONSTRUCTOR }) @Retention(RUNTIME) @Inherited public @interface Marker { } @Marker public interface Foo { } public class Bar implements Foo { } {code} and observer: {code} public void observeMarker(@WithAnnotations({ Marker.class }) @Observes ProcessAnnotatedType<?> pat) { } {code} I think PAT for Bar should be observed because @Marker is inherited (CDI follows JSL rules here). The question is whether this makes sense because "A bean may inherit type-level metadata and members from its superclasses", not superinterfaces. > @WithAnnotations types can appear on any supertype > -------------------------------------------------- > > Key: CDI-318 > URL: https://issues.jboss.org/browse/CDI-318 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Priority: Minor > Labels: cdi-1.1-mr > > Is this intentional? Supertypes also include interfaces which are not very useful here as beans may inherit type-level metadata and members from superclasses only. > Is there any special use-case for this? -- 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, 4 months

1
0
0 / 0

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

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-410?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated CDI-410: -------------------------------- Labels: cdi-1.1-mr (was: ) > @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-1.1-mr > > 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, 4 months

1
0
0 / 0

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

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-411?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated CDI-411: -------------------------------- Labels: cdi-1.1-mr (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-1.1-mr > > 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2013