12:03 a.m.
Allow proxying of abstract classes (Service Handler)
----------------------------------------------------
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.1 (Proposed)
Reporter: George Gastaldi
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:05 a.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Allow injection of abstract classes (Service Handler)
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi updated CDI-110:
--------------------------------
Summary: Allow injection of abstract classes (Service Handler) (was: Allow proxying
of abstract classes (Service Handler))
Allow injection of abstract classes (Service Handler)
-----------------------------------------------------
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.1 (Proposed)
Reporter: George Gastaldi
Labels: cdi
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:05 a.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Allow injection of abstract classes (Service Handler)
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
It should use the same binding strategy as is used by interceptors
Allow injection of abstract classes (Service Handler)
-----------------------------------------------------
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.1 (Proposed)
Reporter: George Gastaldi
Labels: cdi
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:07 a.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Allow injection of abstract classes (Service Handler)
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
{quote}
<mojavelinux> so you would have @ServiceHandler on the invocation handler
<mojavelinux> @ServiceHandler on the @ServiceHandlerBindingType
<mojavelinux> and then whatever that annotation is, you annotate the interface
<mojavelinux> also, another key thing that the current service handler is missing
<mojavelinux> is that it should be possible to have an abstract class with regular
methods that are not intercepted
<mojavelinux> only methods which have no implementation get handled
{quote}
Allow injection of abstract classes (Service Handler)
-----------------------------------------------------
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.1 (Proposed)
Reporter: George Gastaldi
Labels: cdi
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:36 a.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Allow injection of abstract classes (Service Handler)
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-110:
-------------------------------
A more apt title for this JIRA is:
"Provide support for binding an invocation handler to an interface or abstract
class"
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}
@ServiceHandlerBindingType
@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}
Allow injection of abstract classes (Service Handler)
-----------------------------------------------------
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.1 (Proposed)
Reporter: George Gastaldi
Labels: cdi
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Allow injection of abstract classes (Service Handler)
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-110:
--------------------------
Fix Version/s: TBD
Affects Version/s: 1.0
(was: 1.1 (Proposed))
Allow injection of abstract classes (Service Handler)
-----------------------------------------------------
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
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 a.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-110:
--------------------------
Summary: Provide support for binding an invocation handler to an interface or
abstract class (was: Allow injection of abstract classes (Service Handler))
Description:
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}
@ServiceHandlerBindingType
@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}
was:
According to mojavelinux:
{quote}
<mojavelinux> service handler, interceptors and decorators are all complementary
<mojavelinux> and cdi is missing the first...which we now realize
{quote}
CDI 1.1 should provide a way to inject abstract classes by specifying a ServiceHandler
(Check
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Assigned: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned CDI-110:
-----------------------------
Assignee: George Gastaldi
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 p.m.
New subject: [JBoss JIRA] Assigned: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
This is so perfect. So this allow implementing proxies and mixins. You can
specify an interface and then implement it else where (i.e., as a
interceptor).
I think this is a huge feature for writing extensions.
With this feature, it should also be able to add mixins to any class. I.e.,
all of your domain classes implement create, read, update methods via
mixins.
Make sure we don't exclude the mixin case.
On Wed, Apr 27, 2011 at 10:03 AM, Pete Muir (JIRA) <
jira-events(a)lists.jboss.org> wrote:
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...]
Pete Muir reassigned CDI-110:
-----------------------------
Assignee: George Gastaldi
> 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
> Assignee: George Gastaldi
> Labels: cdi
> Fix For: 1.1 (Proposed)
>
>
> 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}
> @ServiceHandlerBindingType
> @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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
--
*Rick Hightower*
(415) 968-9037
Profile <http://www.google.com/profiles/RichardHightower>
1:20 p.m.
New subject: [JBoss JIRA] Assigned: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
Rick, could you add this requirement to the issue so that we don't loose it.
On 27 Apr 2011, at 19:18, Rick Hightower wrote:
This is so perfect. So this allow implementing proxies and mixins.
You can specify an interface and then implement it else where (i.e., as a interceptor).
I think this is a huge feature for writing extensions.
With this feature, it should also be able to add mixins to any class. I.e., all of your
domain classes implement create, read, update methods via mixins.
Make sure we don't exclude the mixin case.
On Wed, Apr 27, 2011 at 10:03 AM, Pete Muir (JIRA) <jira-events(a)lists.jboss.org>
wrote:
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir reassigned CDI-110:
-----------------------------
Assignee: George Gastaldi
> 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
> Assignee: George Gastaldi
> Labels: cdi
> Fix For: 1.1 (Proposed)
>
>
> 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}
> @ServiceHandlerBindingType
> @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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
--
Rick Hightower
(415) 968-9037
Profile
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
12:03 p.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-110:
--------------------------
Fix Version/s: 1.1 (Proposed)
(was: TBD)
This issue is being handled by George Gastaldi, a member of the CDI 1.1 EG.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:47 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower commented on CDI-110:
---------------------------------------
This is so perfect. So this allows implementing proxies and mixins. You can specify an
interface and then implement it else where (i.e., as a interceptor).
This is a feature I used a lot with Spring AOP.
I think this is a huge feature for writing extensions.
With this feature, it should also be able to add mixins to any class. I.e., all of your
domain classes implement create, read, update methods via mixins.
Let's make sure we don't exclude the mixin case.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:53 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower commented on CDI-110:
---------------------------------------
When I wrote Crank, I wrote a finder method mixin capability similar to the one in this
article.
http://www.ibm.com/developerworks/java/library/j-genericdao/index.html
You should be able to do something like this with this feature.
http://code.google.com/p/krank/wiki/UsingDAO
See the section http://code.google.com/p/krank/wiki/UsingDAO.
One of the first things I am going to do when this feature is implemented is write an
example extension (and article) that uses it to mixin JPA 2 named queries with a DAO by
convention.
This is what I would want to use a feature like this for.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:55 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower edited comment on CDI-110 at 4/27/11 2:53 PM:
----------------------------------------------------------------
When I wrote Crank, I wrote a finder method mixin capability similar to the one in this
article.
http://www.ibm.com/developerworks/java/library/j-genericdao/index.html
You should be able to do something like this with this feature.
http://code.google.com/p/krank/wiki/UsingDAO
See the section http://code.google.com/p/krank/wiki/UsingDAO. (see section Using DAO
methods to Named Queries mapping)
One of the first things I am going to do when this feature is implemented is write an
example extension (and article) that uses it to mixin JPA 2 named queries with a DAO by
convention.
This is what I would want to use a feature like this for.
was (Author: rhigh):
When I wrote Crank, I wrote a finder method mixin capability similar to the one in
this article.
http://www.ibm.com/developerworks/java/library/j-genericdao/index.html
You should be able to do something like this with this feature.
http://code.google.com/p/krank/wiki/UsingDAO
See the section http://code.google.com/p/krank/wiki/UsingDAO.
One of the first things I am going to do when this feature is implemented is write an
example extension (and article) that uses it to mixin JPA 2 named queries with a DAO by
convention.
This is what I would want to use a feature like this for.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
Link to Seam Solder ServiceHandler feature:
http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha...
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:18 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
SOLDER-51 has some discussion about it also.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
It´s not possible to assign multiple ServiceHandlers to an interface, as
InvocationContext.proceed() call should not be allowed
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-110:
-------------------------------
Though I suppose you could say that InvocationContext.proceed() merely means to proceed
with the interceptors, but delegate to a void operation once all interceptors have be
exhausted.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-110:
-------------------------------
{quote}
This is so perfect. So this allows implementing proxies and mixins. You can specify an
interface and then implement it else where (i.e., as a interceptor).
This is a feature I used a lot with Spring AOP.
I think this is a huge feature for writing extensions.
{quote}
+1!
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
Then what would be the difference between a ServiceHandler and an Interceptor ?
As stated before, the goal of a ServiceHandler is to provide an implementation to an
abstract class or an interface.
I believe that allowing multiple ServiceHandler(s) would lead to confusion, as when to
create an Interceptor and when to create a ServiceHandler.
Thoughts welcome
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
Any suggestions for the package name holding these annotations ? I thought of something
like "javax.servicehandler" to follow the same naming standard as with
"javax.decorator" and "javax.interceptor"
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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}
@ServiceHandlerBindingType
@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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:42 p.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi updated CDI-110:
--------------------------------
Description:
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}
was:
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}
@ServiceHandlerBindingType
@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}
Replaced @ServiceHandlerBindingType on impl class by @ServiceHandler
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
I started some work on
https://github.com/gastaldi/cdi/tree/CDI-110/api/src/main/java/javax/serv....
I am working in this branch and will generate a pull request when it´s done.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-110:
-------------------------------
javax.servicehandler is fine for now, likely will need changing.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-110:
-------------------------------
Make sure to specify how normal methods are handled for completeness (to avoid any
ambiguities).
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:23 a.m.
New subject: [JBoss JIRA] Updated: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi updated CDI-110:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: 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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 p.m.
New subject: [JBoss JIRA] Commented: (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Richard Hightower commented on CDI-110:
---------------------------------------
Forgive the over explanation, just trying to be clear....
An interceptor typically intercepts concrete classes.
Say LibraryServiceImpl needs a LogInterceptor, or a TransactionInterceptor, or whatever.
The interceptor is sort of a dynamic decorator design pattern instead of implementing the
same interface as the service impl, it uses reflection constructs so that it can intercept
any concrete class (ignore CDI decorators for a moment) with the same cross cutting
service I.e, logging, transactions, security, etc.
So later the same two interceptors can implement the BankServiceImpl (class).
Ok at this point hopefully we are on the same page....
What I am asking and hoping is that I can have an interceptor intercept calls to an
interface like LibraryService and use the same constructs to provide an implementation of
an arbitrary interface ( or any abstract class).
Thus there is no final proceed. The interceptor is the implementation. So if I wanted to
provide an interceptor that translated method calls into REST calls then I could have an
interceptor called RESTInterceptor that decorates the LibraryService interface and I can
intercept calls and turn those into rest calls for a remote client automatically where
LibraryService is an interface and nor a class. I could also intercept calls to
LibraryService with JMSInterceptor and implement the methods by sending JMS messages.
In the past I used this technique with Spring interceptors to create methods on the fly
that accessed JPA named queries. You could also do this with mixin support.
The plumbing is there already. The leap from implementing interceptors for concrete
classes to intercepting interfaces so that the interfaces have an implementation is not
that far off in scope or implementation.
AspectJ has it. Spring 1.0 has it. Spring 2 improved it. I think CDI should have it.
I thought I saw someone discussing it for CDI 1.1 at some point and thought it would be in
the summary.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:43 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
IMHO, Interceptors should not be seen as the implementation of an abstract class or
interface. They allow adding cross-cutting aspects on the implementation which should rely
on a concrete class, or a ServiceHandler if needed.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:57 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
Maybe we should require that Service Handler implementations to implement the
InvocationHandler interface. WDYT ?
See: http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/InvocationHand...
Or even better: Rename ServiceHandler to InvocationHandler feature
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi edited comment on CDI-110 at 12/13/11 9:59 AM:
---------------------------------------------------------------
Maybe we should require Service Handler implementations to implement the InvocationHandler
interface. WDYT ?
See: http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/InvocationHand...
Or even better: Rename ServiceHandler to InvocationHandler feature
was (Author: gastaldi):
Maybe we should require that Service Handler implementations to implement the
InvocationHandler interface. WDYT ?
See: http://docs.oracle.com/javase/7/docs/api/java/lang/reflect/InvocationHand...
Or even better: Rename ServiceHandler to InvocationHandler feature
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 p.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-110:
-------------------------------
Could work, do you want to explore that in the spec changes?
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 p.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-110:
-------------------------------------
I'll rather ping the list for opinions about it.
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
Assignee: George Gastaldi
Labels: cdi
Fix For: 1.1 (Proposed)
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:18 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-110:
--------------------------
Assignee: (was: George Gastaldi)
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
11:18 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-110:
--------------------------
Fix Version/s: TBD
(was: 1.1 (Proposed))
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
Assignee: 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
11:33 a.m.
New subject: [JBoss JIRA] (CDI-110) Provide support for binding an invocation handler to an interface or abstract class
[
https://issues.jboss.org/browse/CDI-110?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-110:
----------------------------------------
In OpenEJB and TomEE we have something pretty close for EJBs (since in CDI world it is
done with extensions) and we called the annotation @Proxy(MyInvocationhandler.class)
IMO the annotation name shouldnt be linked to the interface to implement
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
4492
days inactive
5032
days old
34 comments
10 participants
participants (10)
-
Dan Allen (JIRA) -
George Gastaldi (Commented) (JIRA)
-
George Gastaldi (Issue Comment Edited) (JIRA)
-
George Gastaldi (JIRA)
-
Pete Muir -
Pete Muir (Commented) (JIRA)
-
Pete Muir (JIRA)
-
Richard Hightower (JIRA)
-
Rick Hightower -
Romain Manni-Bucau (JIRA)