[JBoss JIRA] (CDI-74) State explicitely that Decorators must be implemented using subclassing
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-74:
-------------------------
Description:
Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter).
This ensures that:
(1) fields on pseudo scoped managed beans are accessible
(2) there's no restriction on what kinds of constructors may a managed bean have
(3) no extra bean instances are created when a managed bean is created
was:
Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter).
This ensures that:
- fields on pseudo scoped managed beans are accessible
- there's no restriction on what kinds of constructors may a managed bean have
- no extra bean instances are created when a managed bean is created
Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-May/002506.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-May/002506.html)
> State explicitely that Decorators must be implemented using subclassing
> -----------------------------------------------------------------------
>
> Key: CDI-74
> URL: https://issues.jboss.org/browse/CDI-74
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Decorators
> Affects Versions: 1.0
> Reporter: Marius Bogoevici
> Fix For: 1.1 (Proposed)
>
>
> Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter).
> This ensures that:
> (1) fields on pseudo scoped managed beans are accessible
> (2) there's no restriction on what kinds of constructors may a managed bean have
> (3) no extra bean instances are created when a managed bean is created
--
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, 9 months
[JBoss JIRA] (CDI-74) State explicitely that Decorators must be implemented using subclassing
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.sys... ]
Pete Muir commented on CDI-74:
------------------------------
Working through this:
(1) I have clarified that due CDI-6, produce must return an instance that can be reflected on
(2) There is currently no restriction on what kind of constructor a dependent scoped bean may have, but I will try to explicitly state this
(3) I'm not we can specify this, it's really an impl issue
> State explicitely that Decorators must be implemented using subclassing
> -----------------------------------------------------------------------
>
> Key: CDI-74
> URL: https://issues.jboss.org/browse/CDI-74
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Decorators
> Affects Versions: 1.0
> Reporter: Marius Bogoevici
> Fix For: 1.1 (Proposed)
>
>
> Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter).
> This ensures that:
> - fields on pseudo scoped managed beans are accessible
> - there's no restriction on what kinds of constructors may a managed bean have
> - no extra bean instances are created when a managed bean is created
--
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, 9 months
[JBoss JIRA] (CDI-221) Throw definition error if the set of decorated types of a decorator is empty
by Marko Lukša (JIRA)
Marko Lukša created CDI-221:
-------------------------------
Summary: Throw definition error if the set of decorated types of a decorator is empty
Key: CDI-221
URL: https://issues.jboss.org/browse/CDI-221
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Marko Lukša
I propose the following addition to section 8.1:
"If the set of decorated types of a decorator is empty, the container automatically detects the problem and treats it as a definition error."
This would be helpful in cases where the developer is not aware that a decorator and decorated bean must share the same interface, and thinks that a decorator can be defined simply by extending the decorated class (as in the following example).
{code}
public class MyBean {
public Object foo() {...}
}
@Decorator
public class MyDecorator extends MyBean {
@Inject @Delegate MyBean delegate;
public Object foo() {...}
}
{code}
Even though the spec does explicitly state that "superclasses are not decorated types of the decorator", throwing an error would probably save some people's debugging time.
--
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, 9 months
[JBoss JIRA] (CDI-219) Support Request Scope for EJB @Singleton @PostConstruct methods
by Guido Bonazza (JIRA)
Guido Bonazza created CDI-219:
---------------------------------
Summary: Support Request Scope for EJB @Singleton @PostConstruct methods
Key: CDI-219
URL: https://issues.jboss.org/browse/CDI-219
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts, Java EE integration
Affects Versions: 1.0
Reporter: Guido Bonazza
A Request context should be available in @PostConstruct methods of EJB Singletons.
This is a completion of section 6.7.1 of the CDI 1.0 spec, which covers @Asynchronous and @Timeout EJB methods.
Probably the container should ensure that a new context is always created for the @PostConstruct invocation, to be coherent with section 4.8.3 of the EJB 3.1 spec, which specifies the transactional behavior of @Singleton @PostConstruct.
--
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, 9 months