June 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-189) Event qualifiers - empty set

by Jozef Hartinger (Created) (JIRA)

Event qualifiers - empty set ---------------------------- Key: CDI-189 URL: https://issues.jboss.org/browse/CDI-189 Project: CDI Specification Issues Issue Type: Bug Components: Events Affects Versions: 1.1.EDR1, 1.0 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.EDR2 The spec says: {quote} An event comprises: * A Java object—the event object * A (*possibly empty*) set of instances of qualifier types—the event qualifiers {quote} while at the same it says that: {quote} *Every* event has the qualifier @javax.enterprise.inject.Any, even if it does not explicitly declare this qualifier. {quote} which impliest that a set of qualifiers of an event cannot be empty. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-192) Unify coding style of the SPI interfaces

by Jozef Hartinger (Created) (JIRA)

Unify coding style of the SPI interfaces ---------------------------------------- Key: CDI-192 URL: https://issues.jboss.org/browse/CDI-192 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Priority: Trivial Fix For: 1.1 (Proposed) The [JLS|http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html...] says: {quote} For compatibility with older versions of the Java platform, it is permitted but discouraged, as a matter of style, to redundantly specify the abstract modifier for methods declared in interfaces. It is permitted, but strongly discouraged as a matter of style, to redundantly specify the public modifier for interface methods. {quote} The vast majority of CDI API interfaces specifies the public modifier while leaving out the abstract modifier, however, there are exceptions: {code:JAVA} public interface Context { ... boolean isActive(); } {code} {code:JAVA} public interface BeanAttributes<T> { public abstract Set<Type> getTypes(); public abstract Set<Annotation> getQualifiers(); ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-209) BeanManager.createProducer missing in the API

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-209: ----------------------------------- Summary: BeanManager.createProducer missing in the API Key: CDI-209 URL: https://issues.jboss.org/browse/CDI-209 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) The spec says: {quote} The method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedMethod or AnnotatedField or throws an IllegalArgumentException if there is a definition error associated with the producer method or field. {quote} However, the createProducer() method is not defined in the API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-199) Mean to observe or intercept Conversation.begin

by Anthony O. (Created) (JIRA)

Mean to observe or intercept Conversation.begin ----------------------------------------------- Key: CDI-199 URL: https://issues.jboss.org/browse/CDI-199 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Anthony O. As Pete Muir suggested me in that [stackoverflow question|http://stackoverflow.com/questions/8340676/how-to-observe-or-int...], I'm asking here the possibility of observing or intercepting {{Conversation.begin}} method calls (or other methods on the {{Conversation}} object), event if it's a built-in bean. Has this already been the subject of a debate ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (CDI-196) Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values.

by Shruthi Nanjundaswamy (Created) (JIRA)

Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values. --------------------------------------------------------------------------------------------------- Key: CDI-196 URL: https://issues.jboss.org/browse/CDI-196 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts Reporter: Shruthi Nanjundaswamy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] (CDI-237) missing beans.xml

by Craig Ringer (JIRA)

Craig Ringer created CDI-237: -------------------------------- Summary: missing beans.xml Key: CDI-237 URL: https://issues.jboss.org/browse/CDI-237 Project: CDI Specification Issues Issue Type: Feature Request Environment: N/A, any Java EE 6 Reporter: Craig Ringer Priority: Minor It's common, especially for new users of Java EE and CDI, for confusion to arise because of a missing or misplaced beans.xml file. Injection sites that should be injected are null, interceptors don't run, etc. People experienced with CDI immediately spot what's wrong, but if you haven't worked with EE much it can throw you quite badly. It's particularly problematic when beans.xml exists, but isn't where the server expects it to be. This can happen when a jar-layout archive is deployed as a .war or vice versa (something newbies can and will do), or when beans.xml is placed in META-INF/ for a war archive where it's supposed to be in WEB-INF/ . It would be very helpful if it were possible to efficiently detect an archive that uses javax.inject.* annotations without a beans.xml file and issue a warning. To enhance the usability of CDI and its accessibility to new developers, IMO the spec should encourage this. A deployment error when javax.inject.Inject etc are used without a beans.xml file isn't appropriate, as there may be non-CDI code using those annotations, but a warning would make a big difference to usability. It's possible this is better done in an application-server specific context rather than as anything to do with the CDI specification, since the AS is scanning the archive during deployment anyway. If that's the case, it's probably best to move this issue to the JBoss AS 7 JIRA. If it's possible for a CDI impl to *efficiently* detect javax.inject.* and warn, though, it'd be a good thing to encourage in the spec. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
3
0 / 0

ProcessSessionBean type declaration

by Martin Kouba

Hello everyone, does anyone know why ProcessSessionBean type declaration is "ProcessSessionBean<X> extends ProcessManagedBean<Object>" and not "ProcessSessionBean<X> extends ProcessManagedBean<X>"? Also there is no comment for type parameter X. Thanks Martin -- Martin Kouba JBoss Quality Assurance Engineer CDI TCK lead E-mail: mkouba(a)redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic

12 years, 6 months

2
4
0 / 0

[JBoss JIRA] (CDI-238) Clarify enablement of a specialized bean

by Jozef Hartinger (JIRA)

12 years, 7 months

2
1
0 / 0

do we like to define a DeploymentException type?

by Mark Struberg

Hi! While reviewing the DeltaSpike MessageBundleExtension, I (again) came to the point where I didn't knew which Exception to take. It might be nice to have a DeploymentException which indicates that a CDI Extension detected a logical problem which is _not_ caused by some technical problems. E.g. if a certain annotation must not be used in conjunction with another one. In our case @MessageBundle must only be used on Interfaces. We collect all those problems during ProcessAnnotatedType and add them as AfterBeanDiscovery#addDefinitionError. A well defined DeploymentException could help indicating such 'logical' problems, wdyt? LieGrue, strub

12 years, 7 months

3
3
0 / 0

Re: [cdi-dev] Decision needed: cdi-dev search on search.jboss.org

by Dan Allen

Ooops, I messed up the subject line. This is about cdi-dev (there is a parallel discussion for forge-dev, hence the confusion). Please comment on the JIRA. They are currently planning on excluding these messages, but I agree they should be included in the case of cdi-dev. -Dan On Thu, Jun 14, 2012 at 11:56 AM, Pete Muir <pmuir(a)redhat.com> wrote: > Probably they should, it's where a lot of the useful info is… > > On 14 Jun 2012, at 16:53, Dan Allen wrote: > > > See the JIRA ORG-1402 [1] about a question regarding which posts on > cdi-dev to index. The question is whether the emails from JIRA should be > indexed. > > > > Also, this is just an FYI that cdi-dev is being added to the search > application (search.jboss.org). > > > > -Dan > > > > [1] https://issues.jboss.org/browse/ORG-1402 > > > > -- > > Dan Allen > > Principal Software Engineer, Red Hat | Author of Seam in Action > > Registered Linux User #231597 > > > > http://google.com/profiles/dan.j.allen > > http://mojavelinux.com > > http://mojavelinux.com/seaminaction > > > > _______________________________________________ > > cdi-dev mailing list > > cdi-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/cdi-dev > > -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://google.com/profiles/dan.j.allen http://mojavelinux.com http://mojavelinux.com/seaminaction

12 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev June 2012