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

Kalle Kivimaa commented on JSPWIKI-204:
---------------------------------------

An additional reason for upgrading the xml-rpc to 3.1 is that it would help in 
getting the JSPWiki package (back) in Debian, as that would require either 
having full source included in the JSPWiki source package or build-depending on 
only such components that are in Debian (xml-rpc is at version 3.1 in Debian).

This isn't time-critical, as there are still other dependencies missing, namely 
jsonrpc (should probably migrate to jabsorb, as jsonrpc isn't maintained any 
more), jrcs-diff, sandler and akismet, and I need to package these first (or 
include the source), and getting new packages into Debian at the moment is 
non-trivial, as the project is close to releasing the new version.

Is it really that bad to have two more jars in the lib?


> 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
>            Priority: Minor
>             Fix For: 2.8.1
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to