January 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-62) Clarify @Resource/@PersistenceContext/etc. on disabled alternatives

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-62?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-62: ------------------------- Fix Version/s: TBD > Clarify @Resource/@PersistenceContext/etc. on disabled alternatives > ------------------------------------------------------------------- > > Key: CDI-62 > URL: https://issues.jboss.org/browse/CDI-62 > Project: CDI Specification Issues > Issue Type: Bug > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > > Is it expected that the container validates these dependencies and fails deployment if they don't exist? I think it is, right? At least, I think some containers behave this way. Then we should say that this validation should *not* happen if the annotation appears in a class annotated @Alternative. I have no idea what the right language would be... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-12: ------------------------- Fix Version/s: TBD > Specifically exclude methods inherited from java.lang.Object from the list of business method invocations > --------------------------------------------------------------------------------------------------------- > > Key: CDI-12 > URL: https://issues.jboss.org/browse/CDI-12 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Priority: Optional > Fix For: TBD > > > Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. > - they are defined on the object; > - will be present on the contextual reference; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-91) Allow a producer to specialize a regular bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-91?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-91: ------------------------- Fix Version/s: TBD > Allow a producer to specialize a regular bean > --------------------------------------------- > > Key: CDI-91 > URL: https://issues.jboss.org/browse/CDI-91 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Inheritance and Specialization > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-58) Clarify that there can be multiple AnnotatedType instances per Java class

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-58?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-58: ------------------------- Fix Version/s: TBD > Clarify that there can be multiple AnnotatedType instances per Java class > ------------------------------------------------------------------------- > > Key: CDI-58 > URL: https://issues.jboss.org/browse/CDI-58 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-29) Method of accessing contexts regardless of active state

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-29?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-29: ------------------------- Fix Version/s: TBD > Method of accessing contexts regardless of active state > ------------------------------------------------------- > > Key: CDI-29 > URL: https://issues.jboss.org/browse/CDI-29 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Fix For: TBD > > > It would be practical to have a way of accessing contexts from the BeanManager regardless of their active state. Currently, contexts cannot be activated (e.g. Conversation) in a portable way because there is no way of getting the inactive context in order to activate it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-59) Clarify that interceptors/decorators don't apply to producers in resolution rules

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-59?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-59: ------------------------- Fix Version/s: TBD > Clarify that interceptors/decorators don't apply to producers in resolution rules > --------------------------------------------------------------------------------- > > Key: CDI-59 > URL: https://issues.jboss.org/browse/CDI-59 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Decorators, Interceptors, Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-87) Declarative control over classes including in bean archive scanning

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-87?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-87: ------------------------- Fix Version/s: TBD > Declarative control over classes including in bean archive scanning > ------------------------------------------------------------------- > > Key: CDI-87 > URL: https://issues.jboss.org/browse/CDI-87 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > > Weld introduced a XML syntax for this -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-9) Interceptors are not applied to custom bean types

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-9?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-9: ------------------------ Fix Version/s: TBD > Interceptors are not applied to custom bean types > ------------------------------------------------- > > Key: CDI-9 > URL: https://issues.jboss.org/browse/CDI-9 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors, Portable Extensions > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: TBD > > > Beans added through the SPI do not have interceptors applied. > Even though bean does not have a getInterceptorBindings() method, interceptors applied to stereotypes should still work. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-34) Make special note in the spec about beans that are @Named via a stereotype being unselectable with Instance.select()

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-34?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-34: ------------------------- Fix Version/s: TBD > Make special note in the spec about beans that are @Named via a stereotype being unselectable with Instance.select() > -------------------------------------------------------------------------------------------------------------------- > > Key: CDI-34 > URL: https://issues.jboss.org/browse/CDI-34 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Shane Bryzak > Priority: Minor > Fix For: TBD > > > For example, say we have the following bean: > public @Model class Foo implements IFoo { } > And we have the following injection point within another bean: > @Inject Instance<Foo> fooInstance; > It is not possible to select Foo via name using the Instance: > // This results in an UnsatisfiedDependencyException > Foo foo = fooInstance.select(new NamedLiteral("foo")).get(); > Instead, Foo must be annotated directly with the @Named annotation itself: > /* > * This Foo can be selected by name > */ > public @Named @RequestScoped Foo implements IFoo { } > This special case might be worthwhile mentioning in the next revision of the spec. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-15) Relax @Target annotation for CDI Scopes and Qualifiers

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-15?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-15: ------------------------- Fix Version/s: TBD (was: 1.1) > Relax @Target annotation for CDI Scopes and Qualifiers > ------------------------------------------------------ > > Key: CDI-15 > URL: https://issues.jboss.org/browse/CDI-15 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: TBD > > > In some cases it may make sense to apply a scope or qualifier in a place that was not envisaged by the spec but that would be useful for a portable extension. > For example, the @Constructs extension described at > http://www.seamframework.org/Weld/PortableExtensionsPackage#H-BeanDeclara... > is not possible because scopes and qualifiers can not be placed on constructors -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2011