December 2013 - cdi-dev - Jboss List Archives

by Antoine Sabot-Durand

Hi all, Meetings notes are available on cdi-spec website [1]. Let me know if you have correction or things I forgotten. Antoine [1] http://www.cdi-spec.org/news/2013/12/02/EG-meeting/

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: -------------------------------- Workaround Description: Map the CDI Conversation Filter in web.xml and set character encoding in a filter that executes before the CDI filter http://weld.cdi-spec.org/documentation/#3 Workaround: Workaround Exists > 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 > > 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

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

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-411: ----------------------------------- Summary: 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 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

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

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-410: ----------------------------------- Summary: @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 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

EG meeting publish on web site

by Antoine Sabot-Durand

Hi all, Just to let you know that I published meeting minutes on the website. in the news section [1] I also did some minor change to the site : - Removed « major issues section » which wasn’t working (will put it back after I figured out how to make it work again) - Added link to G+ and Twitter Before adding tutorial, howtos and a page pouting CDI initiatives and extensions, I plan to do a little more work on UI and navigation. Roughly, I plan to change the navigation with a more classical navbar on the top, Upgrade to awestruct 0.5.3 and bootstrap 3.x (started the migration) and integrated our ml from Nabble embedded or an other service if you know a better one. Your input, ideas, help is off course most welcome. Antoine [1] http://www.cdi-spec.org/news/

10 years, 4 months

1
0
0 / 0

Fwd: Today's hangout agenda

by Antoine Sabot-Durand

Hi all I propose the following Agenda 1) Pete will do a feed back on Java EE EG conf call we had on tuesday 2) Issues discussion I propose we try to deal with this issues. If we don’t have enough time, we’ll have some more next week CDI-405 Reword the description of @RequestScoped and @ApplicationScoped in section 2.4.1 CDI-401 Clarify the meaning of "bean class local view" CDI-398 Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type CDI-392 Clarify when the operations of BeanManager can be called CDI-386 Two examples in section 5.2.4 contradict the rules of the same section CDI-382 Clarify interceptors are not associated with the result of a producer method/field CDI-381 Additional implementations of Request Context CDI-379 Clarify life cycle of RequestScoped CDI-77 Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans The hangout link is here : https://plus.google.com/hangouts/_/calendar/YW50b2luZS5zYWJvdGR1cmFuZEBnb... Antoine Sabot-Durand ——————————————— Twitter : @antoine_sd CDI co-spec lead & eco-system development Agorava tech lead

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-398) Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-398?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-398: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-398 > URL: https://issues.jboss.org/browse/CDI-398 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Labels: 12-02-13-EGM, cdi-1.1-mr > > Section 2.2.1 says: > {quote} > Almost any Java type may be a bean type of a bean: > • A bean type may be an array type. > {quote} > and: > {quote} > A type variable is not a legal bean type. A parameterized type that contains a wildcard type parameter is not a legal bean type. > {quote} > This should be clarified that array types that have a type variable or a parameterized type that contains a wildcard type parameter as the array's component type are also not legal bean types. > Also, all other sections that mention type variables/wildcards should also be reviewed and, if necessary, updated to also specifically mention array types with these kinds of component types. -- 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-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: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > 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: 12-02-13-EGM, cdi-1.1-mr > > @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, 4 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 updated CDI-392: ------------------------------------- Labels: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > 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 > Labels: 12-02-13-EGM, cdi-1.1-mr > > 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, 4 months

1
0
0 / 0

[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: 12-02-13-EGM cdi-1.1-mr (was: cdi-1.1-mr) > 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: 12-02-13-EGM, cdi-1.1-mr > > 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, 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