You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-auto@ws.apache.org by "Jochen Wiedmann (JIRA)" <xm...@ws.apache.org> on 2008/08/05 16:56:44 UTC

[jira] Resolved: (XMLRPC-125) Ease extending XmlRpcServlet

     [ https://issues.apache.org/jira/browse/XMLRPC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Wiedmann resolved XMLRPC-125.
------------------------------------

       Resolution: Won't Fix
    Fix Version/s: 3.1.1
         Assignee: Jochen Wiedmann

As far as I can tell, these are obsolete in the meantime.


> Ease extending XmlRpcServlet
> ----------------------------
>
>                 Key: XMLRPC-125
>                 URL: https://issues.apache.org/jira/browse/XMLRPC-125
>             Project: XML-RPC
>          Issue Type: Improvement
>          Components: Source
>    Affects Versions: 3.1
>            Reporter: Jimisola Laursen
>            Assignee: Jochen Wiedmann
>             Fix For: 3.1.1
>
>         Attachments: XMLRPC-125.diff
>
>
> Short story:  XmlRpcServlet is not easy to extend since 1) instance variables are private and 2) newPropertyHandlerMapping(URL url) method that often needs to be extended contains logic and potential bug fixes to risk to be missed.
> Long story: the long story is that two classes needs to be extended only to be able to change what methods are to be registered in AbstractReflectiveHandlerMapping.registerPublicMethods (this is done by extending isHandlerMethod).
> I'd prefer a solution where AbstractReflectiveHandlerMapping nor XmlRpcServlet needs to be extended.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.