August 2013 - cdi-dev - Jboss List Archives

CDI TCK 1.0.5.CR1 and 1.1.1.CR1 released

by Martin Kouba

Hello everyone, release candidates of bugfix versions for CDI 1.0 and CDI 1.1 were published - see the lists of resolved issues below. 1.0.5.CR1 - https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%221.0.5.CR1%22%2... - known issues: - https://issues.jboss.org/browse/CDITCK-364 - not synced in maven central repo, though TCK 1.0.x has some non-centralized dependencies, so JBoss maven repo is needed anyway 1.1.1.CR1 - https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%221.1.1.CR1%22%2... Any feedback is highly appreciated! Martin -- Martin Kouba JBoss Quality Assurance Engineer CDI TCK lead Red Hat, Czech Republic

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-397) Clarify Section 6.6.3 regarding singletons

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-397: ----------------------------------- Summary: Clarify Section 6.6.3 regarding singletons Key: CDI-397 URL: https://issues.jboss.org/browse/CDI-397 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.1.FD Reporter: Jozef Hartinger Priority: Minor Fix For: TBD The section 6.6.3 Passivation capable dependencies states: {quote} all singleton beans are passivation capable dependencies {quote} Clearly the specification intents to address *singleton session beans* but the current wording does not make that explicit and users confuse this line and consider javax.inject.Singleton-scoped beans also to be passivation capable dependencies. The spec should instead say that: {quote} all singleton *session* beans are passivation capable dependencies {quote} -- 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

11 years, 4 months

1
0
0 / 0

[Community] Announcement: Planed outage: 2013-08-24 5:00 PM UTC

by Libor Krzyžanek

Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] updated the announcement <b>Announcement</b>: "Planed outage: 2013-08-24 5:00 PM UTC" To view the announcement, visit: https://community.jboss.org/index.jspa -------------------------------------------------------------- Forums/Wiki/Blogs at community.jboss.org will be unavailable for about 4 hours due to upgrade. -------------------------------------------------------------- Announcement expires on August 28, 2013

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-396) Miss leading JavaDoc for Interceptor SPI

by Aslak Knutsen (JIRA)

Aslak Knutsen created CDI-396: --------------------------------- Summary: Miss leading JavaDoc for Interceptor SPI Key: CDI-396 URL: https://issues.jboss.org/browse/CDI-396 Project: CDI Specification Issues Issue Type: Bug Components: Javadoc and API Affects Versions: 1.0 Reporter: Aslak Knutsen class javax.enterprise.inject.spi.Interceptor has the following JavaDoc: {code} Represents an enabled {@linkplain javax.interceptor interceptor}. {code} The JavaDoc and http://docs.jboss.org/cdi/spec/1.0/html/spi.html#abd SPI Doc seems to imply that you can do the following in a Extension: {code} public void enableInterceptor(@Observes AfterBeanDiscovery beans) { beans.addBean(MyInterceptorType()) } {code} While you can add them, they are still not _enabled_, which can only be done via beans.xml in CDI 1.0. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-395) Public fields in extensions should not be allowed

by Marko Lukša (JIRA)

Marko Lukša created CDI-395: ------------------------------- Summary: Public fields in extensions should not be allowed Key: CDI-395 URL: https://issues.jboss.org/browse/CDI-395 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.PFD Reporter: Marko Lukša Since the container must provide an @ApplicationScoped bean for every extension and since a proxy must be injected into injection points requesting this bean, it should be clear that extensions should not be allowed to have public fields. The spec doesn't specify this explicitly, but it should - like it does for non-dependent managed beans. The container should treat this as a definition error, otherwise people may end up accessing these public fields of extensions and getting weird errors. See also WELD-1474 -- 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

11 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2013