September 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Closed: (CDI-88) Fix ProcessObserverMethod javadoc to match spec

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-88?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-88. ------------------------ Resolution: Rejected Reverted > Fix ProcessObserverMethod javadoc to match spec > ----------------------------------------------- > > Key: CDI-88 > URL: https://issues.jboss.org/browse/CDI-88 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API, Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Reopened: (CDI-88) Fix ProcessObserverMethod javadoc to match spec

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-88?page=com.atlassian.jira.plugin.sys... ] Pete Muir reopened CDI-88: -------------------------- I'm reopening this, I don't believe the breaking change is justified any more. > Fix ProcessObserverMethod javadoc to match spec > ----------------------------------------------- > > Key: CDI-88 > URL: https://issues.jboss.org/browse/CDI-88 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API, Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-86: ------------------------------ https://github.com/jboss/cdi/pull/49 is a pull which resolves this plus CDI-80 in a compatible fashion. > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-86: ------------------------------ I have updated the pull req with Jozef's suggestion. Jozef, can you spin the idea about extending this to non-built-in scopes to a new issue please? > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (CDI-158) Extension support for non CDI beans

by Aslak Knutsen (JIRA)

Extension support for non CDI beans ----------------------------------- Key: CDI-158 URL: https://issues.jboss.org/browse/CDI-158 Project: CDI Specification Issues Issue Type: Tracker Components: Java EE integration Affects Versions: 1.0 Reporter: Aslak Knutsen Fix For: 1.1 (Proposed) CDI Extensions in EE6 can only rewrite/change/work upon CDI registered beans. This should be extended to include _any_ EE component. e.g. * Change/Add @Resource InjectionPoint in a EJB * Change/Add @Path on JAX-RS Resource handlers * Change/Add @MassageDriven on a MDB * Change/Add JPA Annotations * Change/Add @TransactionAttributes on EJBs * Change/Add @RunAs on EJBs * Change/Add @WebService on EJBs * Change/Add @WebServlet etc. on Servlets -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
8
0 / 0

RequestScoped and Injection Points

by John D. Ament

CDI Experts Was wondering if you could help me understand rationale. In request scoped objects, when you create a producer method that creates request scoped instances, why is there no access to the underlying injection point? Let's say that you have a qualifier with a single String value attribute that is nonbinding; let's say @JmsDestination. You have the following injection points: @Inject @JmsDestination("jms/MyQueue") MessageProducer queueProducer; @Inject @JmsDestination("jms/MyTopic") MessageProducer topicProducer; In this case, two distinct MessageProducers should be injected. The CDI container should be able to differentiate the two, since they have different values on the qualifier. However, CDI disallows this since the producer methods used to create them would not have access to the injection point. If a second injection point is found, CDI should return the same instance. I hope it doesn't sound like I'm babbling, but I wanted to put the question out there to see if it's something that could be addressed. Regards, John

12 years, 7 months

4
14
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-86: ------------------------------------ Actually, the qualifier would need to look like this: @Initialized(ApplicationScoped.class) Object object > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-86: ------------------------------------ The idea I had about this was to make @Intialized and @Destroyed qualifiers and reuse the existing scope annotations e.g: @Initialized(@ApplicationScoped) Object object This way we remove the possible confusion from having both @Session and @SessionScoped, ... It is possible to take this idea even further and require that the container fires the events not only for the build-in contexts but for any context registered with the container (e.g. @Initialized(@ViewScoped) Object object). That would require further changes in the API since currently a Context implementation has not way of telling the container that it was initialized / destroyed. > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-27) Support declarative transactions on managed beans

by Reza Rahman (JIRA)

[ https://issues.jboss.org/browse/CDI-27?page=com.atlassian.jira.plugin.sys... ] Reza Rahman commented on CDI-27: -------------------------------- As Pete stated, separating the EJB services from the component model is already on the agenda for the EJB EG. It's just a matter of time before that gets hashed out. Until then, I don't think much can be done for this specific feature in the CDI EG. > Support declarative transactions on managed beans > ------------------------------------------------- > > Key: CDI-27 > URL: https://issues.jboss.org/browse/CDI-27 > Project: CDI Specification Issues > Issue Type: Tracker > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-27) Support declarative transactions on managed beans

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-27?page=com.atlassian.jira.plugin.sys... ] Mark Struberg commented on CDI-27: ---------------------------------- A possible way to implement / specify this would be to reuse the javax.ejb.TransactionAttribute annotation but handle it as InterceptorBinding in CDI beans. So instead of @Transactional(transaction=REQUIRES_NEW) we could use @javax.ejb.TransactionAttribute(value=REQUIRES_NEW) javax.ejb.TransactionAttribute is a simple annotation atm. We could add this as interceptor binding via our CDI Extension SPI I'm not sure though what that would mean for EJBs in return. They would have to ignore this special Interceptor if the annotation is applied on an EJB. > Support declarative transactions on managed beans > ------------------------------------------------- > > Key: CDI-27 > URL: https://issues.jboss.org/browse/CDI-27 > Project: CDI Specification Issues > Issue Type: Tracker > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2011