[ 
https://issues.apache.org/jira/browse/JSPWIKI-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18135370#comment-18135370
 ] 

Arturo Bernal commented on JSPWIKI-204:
---------------------------------------

Thanks Jürgen for the pointers. In master the only use of xmlrpc-2.0.1 was 
PingWeblogsComFilter; the jspwiki-xmlrpc module has no pom and is not built. 
Pull request https://github.com/apache/jspwiki/pull/567 removes the library: 
the filter sends its weblogUpdates.ping call with the HTTP client of the JDK, 
and the war no longer contains any xmlrpc jar. A new test runs the filter 
against a local HTTP server. The ping to rpc.weblogs.com itself was not tried, 
and the full jspwiki-main suite was not run.

This removes the dependency instead of upgrading it to XML-RPC 3.1, which would 
need three jars for that one call. I leave the issue open for review.

> Consider upgrading xmlrpc.jar to a more recent version
> ------------------------------------------------------
>
>                 Key: JSPWIKI-204
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-204
>             Project: JSPWiki
>          Issue Type: Improvement
>    Affects Versions: 2.6.1
>         Environment: Debian (etch), Tomcat 5.5
>            Reporter: Steve Dahl
>            Assignee: Janne Jalkanen
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: STRIPES/JCR-3.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> I couldn't find this issue in the database, and didn't want to see it get 
> lost.
> I've been having trouble with the Transclude plugin in JSPWiki 2.6.x, and the 
> analysis to date suggests that the problem is that XML-RPC is using an 
> outdated and incomplete XML parser.
> The conversation in jspwiki-user ended more or less with this:
> >> We are using an older version of Apache XML-RPC and the current
> >> version (3.1) doesn't use MinML. We haven't upgraded because of
> >> time constraints and not wanting to break something that isn't
> >> broken. This does sound a bit broken though.
> > Yup, it sounds like a very good reason for an upgrade.  Could someone 
> > please open up a task in the JIRA tracker?



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to