[JBoss JIRA] (CDI-318) @WithAnnotations types can appear on any supertype
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/CDI-318?page=com.atlassian.jira.plugin.sy... ]
Martin Kouba commented on CDI-318:
----------------------------------
[~antoinesabot-durand] I wonder if there's some convention to refer a specific part the spec text in javadoc. In this case the text in "11.5.6 ProcessAnnotatedType event" refers to "Section 11.4".
> @WithAnnotations types can appear on any supertype
> --------------------------------------------------
>
> Key: CDI-318
> URL: https://issues.jboss.org/browse/CDI-318
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Martin Kouba
> Assignee: Martin Kouba
> Priority: Minor
> Labels: CDI_api_chge, Ready_to_fix
> Fix For: 1.2 Proposed
>
>
> Is this intentional? Supertypes also include interfaces which are not very useful here as beans may inherit type-level metadata and members from superclasses only.
> Is there any special use-case for this?
--
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
10 years, 10 months
[JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand updated CDI-110:
-------------------------------------
Git Pull Request: https://github.com/cdi-spec/cdi/pull/28 (was: https://github.com/jboss/cdi/pull/28)
> Provide support for binding an invocation handler to an interface or abstract class
> -----------------------------------------------------------------------------------
>
> Key: CDI-110
> URL: https://issues.jboss.org/browse/CDI-110
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Inheritance and Specialization
> Affects Versions: 1.0
> Reporter: George Gastaldi
> Labels: cdi
> Fix For: TBD
>
>
> The purpose of this feature is to allow interfaces and abstract classes to be automatically implemented by an invocation handler to which all abstract method invocations are delegated. The invocation handler would get "bound" to the type using the same strategy as is used for interceptor binding.
> Binding type:
> {code:java}
> @Target({ METHOD, TYPE })
> @Retention(RetentionPolicy.RUNTIME)
> @ServiceHandlerBindingType
> public @interface EchoService {}
> {code}
> Invocation handler:
> {code:java}
> @ServiceHandler
> @EchoService
> public class EchoServiceHandler {
> @AroundInvoke
> public Object invoke(InvocationContext ctx) {
> return ctx.getMethod().getName().toString();
> }
> }
> {code}
> Usage:
> {code:java}
> @EchoService
> public interface HelloWorld {
> String helloWorld();
> }
> {code}
--
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
10 years, 10 months
[JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand updated CDI-392:
-------------------------------------
Assignee: Mark Struberg
> Clarify when the operations of BeanManager can be called
> --------------------------------------------------------
>
> Key: CDI-392
> URL: https://issues.jboss.org/browse/CDI-392
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Matus Abaffy
> Assignee: Mark Struberg
> Labels: CDI_spec_chge, Ready_to_fix
> Fix For: 1.2 Proposed
>
>
> The current version of spec. states (under 11.3. The BeanManager object): "Any operation of BeanManager may be called at any time during the execution of the application."
> This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that BeanManager's methods can be called (without causing exception) just after AfterDeploymentValidation event is fired might be helpful.
--
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
10 years, 10 months
Time for homework picking
by Antoine Sabot-Durand
Hi guys,
We've got a bunch of task ready to be fixed. So if you can/want, it’s time to pick a ticket. I’ve built a list of unassigned task ready to be fixed [1].
So make your choice by assigning the ticket to you or by asking me.
Don’t forget the workflow we approved on monday
Regards,
Antoine
[1] : https://issues.jboss.org/browse/CDI-410?filter=12320805
10 years, 10 months
[JBoss JIRA] (CDI-382) Clarify interceptors are not associated with the result of a producer method/field
by Mark Struberg (JIRA)
[ https://issues.jboss.org/browse/CDI-382?page=com.atlassian.jira.plugin.sy... ]
Mark Struberg commented on CDI-382:
-----------------------------------
Please try to not introduce a spec change.
I suggest a wording like 'Any InterceptorBinding of a producer field or producer method does not apply to the produced contextual instance but intercepts the invocation of the producer method or producer field itself'
It is possible that e.g. a producer method returns a contextual instance which is already wrapped with an interception-proxy.
> Clarify interceptors are not associated with the result of a producer method/field
> ----------------------------------------------------------------------------------
>
> Key: CDI-382
> URL: https://issues.jboss.org/browse/CDI-382
> Project: CDI Specification Issues
> Issue Type: Clarification
> Components: Interceptors
> Affects Versions: 1.1.PFD
> Reporter: Martin Kouba
> Assignee: Martin Kouba
> Labels: CDI_spec_chge, Ready_to_fix
> Fix For: 1.2 Proposed
>
>
> The interceptors part from CDI-59 resolution [1] is missing in the final version of the spec, probably lost during the Interceptors section transfer to the Interceptors 1.2 spec.
> [1] https://github.com/cdi-spec/cdi/pull/110
> "Interceptors are not associated with the return value of a producer method or the current value of a producer field."
--
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
10 years, 10 months