[
https://issues.apache.org/jira/browse/JSPWIKI-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134396#comment-18134396
]
Arturo Bernal commented on JSPWIKI-204:
---------------------------------------
Checked in the current code (upstream master).
The library has not been upgraded: the root pom still sets xmlrpc.version to
2.0.1 for the dependency xmlrpc:xmlrpc, and jspwiki-main declares it. In the
main module the only class that uses org.apache.xmlrpc is PingWeblogsComFilter,
which is a client that pings an external service. The server side, the handlers
that the report is about (the XML-RPC interface of the wiki), is in the module
jspwiki-xmlrpc, which is not listed among the modules of the root pom, so it is
not part of the default build; and the XML-RPC servlet is commented out in the
web.xml of the war.
So the request is still open for the dependency, but its reach today is small:
a client filter in the main module and a server module that is not built by
default. Whether to move to Apache XML-RPC 3.x, replace the library, or drop
the module is a decision for the maintainers; I did not try to run the
Transclude plugin from the report. Leaving the issue open.
> 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
> 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)
