[
https://issues.apache.org/jira/browse/XMLRPC-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann updated XMLRPC-135:
-----------------------------------
Fix Version/s: (was: 3.0)
(was: 3.1)
This won't make it in 3.1. I see a need for a general rework on the server
side, which seems to confuse some users. The concept of interceptors might fit
into that nicely. But that's a topic for 3.2 or 4.0.
> intercept method calls (on the client and on the server side)
> -------------------------------------------------------------
>
> Key: XMLRPC-135
> URL: https://issues.apache.org/jira/browse/XMLRPC-135
> Project: XML-RPC
> Issue Type: Improvement
> Affects Versions: 3.0, 3.1
> Reporter: Mario Linke
>
> This extension is to integrate cross-cutting concerns (AOP), how stopping the
> time, logging or transform args and return value.
> public interface Interceptor {
>
> public void beforeMethodInvocation (InterceptorContext
> pInterceptorContext);
> public void afterMethodInvocation (InterceptorContext
> pInterceptorContext);
> public void onError (Throwable pThrowable);
> }
> public final class InterceptorContext {
>
> private Method method = null;
> private Object[] args = null;
> private Object result = null;
> }
> InterceptorContext is analog to the XmlRpcRequest, extended to the result
> and the method object.
> Extend the XmlRpcController to register the Interceptors:
> - addInterceptor
> - removeInterceptor
> - getInterceptorByNumber
> and delegate before and after event:
> by the client to XmlRpcWorker
> by the server to the XmlRpcHandler
> Mario
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
