May 2012 - cdi-dev - Jboss List Archives

[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

11 years, 8 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

11 years, 8 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

11 years, 8 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

11 years, 8 months

3
2
0 / 0

Problem with CDI and weblogic

by Mehdi Heidarzadeh

Hi @all I have a bean annotated with @Named and @RequestScoped. It is working perfectly in Glassfish 3.1.2 but when I deploy it in Weblogic 12.1.1 I get the following error! Caused By: org.jboss.weld.exceptions.DefinitionException: WELD-000075 Normal scoped managed bean implementation class has a public field: public@Named @RequestScoped class com.x.y.web.monitoring.MonitoringController I don't have any public field in my bean!!! all of them are private and I use getters and setters. Is this a bug in weblogic 12.1.1 ? How can I update weld version in weblogic? Thanks in advance. -- Mehdi Heidarzadeh Ardalani Independent JEE Consultant, Architect and Developer. http://www.TheBigJavaBlog.com

11 years, 10 months

3
2
0 / 0

@NonBinding Array[]

by Romain Manni-Bucau

Hi, wonder if there is a reason why the behavior associated to an array without @NonBinding annotation in qualifier is "depending on the implementation". Any known reason? - Romain

11 years, 11 months

2
1
0 / 0

Spec clarification on what scopes are active during @PostConstruct of remote EJBs or @Startup

by Joseph Bergmark

The 1.0 spec doesn't appear to directly address if even the application scope is active during @PostConstruct for remote EJBs or @Startup EJBs, but does somewhat address @PreDestroy callback. A previous thread in March brought up supporting request scope in @PostConstruct as well. Is it worth opening an issue to track this, or am I missing something that currently makes this clear? Sincerely, Joe Bergmark WebSphere Development bergmark(a)us.ibm.com

11 years, 11 months

2
1
0 / 0

[JBoss JIRA] (CDI-26) Bootstrap API for CDI

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-26?page=com.atlassian.jira.plugin.sys... ] Mark Struberg commented on CDI-26: ---------------------------------- The more I think about it, the more I'm sure that we need to push this to the EE7 umbrella spec. Booting the CDI container alone is nice, but by far not sufficient. EJB has already an API to boot the container (javax.ejb.embeddable.EJBContainer), CDI might get one too. But still the user will end up not being able to start his whole environment! Imagine a situation where a user likes to use openejb or JBossAS7-embedded in a SE environment. Starting the container alone would not be enough. Otoh one could argue that in those cases a user might easily use the containers native implementation specific classes directly. Wdyt? > Bootstrap API for CDI > --------------------- > > Key: CDI-26 > URL: https://issues.jboss.org/browse/CDI-26 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > Weld and other CDI impls allow an embedded mode. > See http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#... for example -- 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

11 years, 11 months

1
0
0 / 0

How to process the scope in JEE7

by Hantsy Bai

Hi, CDI introduced NormalScope to create custom scope, I noticed there is another similar one in the JSR330, @Scope(and @Singleton) annotation, and there is also another "State management" standalone spec in JEE7. Is there some cooperation with them in JEE7? and what is the successor of JSR 330 in JEE7? Regards Hantsy

11 years, 11 months

4
5
0 / 0

CDI have any plan to process Transaction?

by Hantsy Bai

Hi, I have read some content about the spec 1.1, but I want to know if there is a plan to provide a new transaction annotation...for EBJ or none EJB proramming. For example, provide a @Transactional annotation like Seam2 or Spring 3.1...and make it work in Servlet container(none JTA transation, jdbc only) or full profile container such as JBoss, Glassfish(JTA transaction by default) seamlessly. Automatically detect the Transaction will be used, or configure in beans.xml file. Regards Hantsy

11 years, 12 months

5
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2012