The following issue has been updated:
Updater: James Carman (mailto:[EMAIL PROTECTED])
Date: Thu, 2 Sep 2004 6:26 AM
Comment:
Here's another example where the MethodInterceptor is assigned to the factory
using DI rather than making the factory class abstract. Here, the
MethodInterceptor can be another service within the registry.
Changes:
Attachment changed to MethodInterceptorFactory.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/HIVEMIND-45?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-45
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-45
Summary: Create interceptor factory supporting aopalliance
MethodInterceptors
Type: Wish
Status: Open
Priority: Minor
Project: HiveMind
Assignee: Howard M. Lewis Ship
Reporter: James Carman
Created: Sat, 14 Aug 2004 7:00 AM
Updated: Thu, 2 Sep 2004 6:26 AM
Description:
The aopalliance project (http://aopalliance.sourceforge.net) provides standard
interfaces for defining MethodInterceptors, akin to HiveMind's concept of
service interceptors. HiveMind (library or contrib) should provide a mechanism
for plugging in an aopalliance MethodInterceptors. If it did, then HiveMind
users could plug in implementations of pre-defined interceptors (Hibernate for
example).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
