Uploaded image for project: 'XML-RPC'
  1. XML-RPC
  2. XMLRPC-191

Upgrade apache httpcomponents dependency to 4.1.x

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1.3
    • Fix Version/s: None
    • Component/s: Source
    • Labels:
      None

      Description

      Project currently depends on httpclient 3.x which has reached end of life (see http://hc.apache.org/index.html#Commons_HttpClient_legacy ). Please upgrade apache httpcomponents (http client) dependency to 4.1.x

      1. patch.txt
        87 kB
        Claude Warren
      2. XMLRPC-191.patch.txt
        38 kB
        Claude Warren
      3. XMLRPC-191.patch.txt
        38 kB
        Claude Warren

        Issue Links

          Activity

          Hide
          sslavic Stevo Slavic added a comment -

          This issue is related to XMLRPC-185 which concerns updating documentation. I guess this issue should be implemented first, and update documentation afterwards.

          Show
          sslavic Stevo Slavic added a comment - This issue is related to XMLRPC-185 which concerns updating documentation. I guess this issue should be implemented first, and update documentation afterwards.
          Hide
          claudenw Claude Warren added a comment -

          Given current date (aug 2012) httpcomponents is now at 4.2.x I recommend changing this to move to 4.2.x rather than 4.1.x

          Show
          claudenw Claude Warren added a comment - Given current date (aug 2012) httpcomponents is now at 4.2.x I recommend changing this to move to 4.2.x rather than 4.1.x
          Hide
          claudenw Claude Warren added a comment -

          patch to move code to httpcomponents 4.2.x

          Show
          claudenw Claude Warren added a comment - patch to move code to httpcomponents 4.2.x
          Hide
          claudenw Claude Warren added a comment -

          This patch is more extensively tested than the earlier patch.

          I have been able to make this work with the standard OAUTH authentication provided for httpcomponents.

          I believe that this code is stable.

          Show
          claudenw Claude Warren added a comment - This patch is more extensively tested than the earlier patch. I have been able to make this work with the standard OAUTH authentication provided for httpcomponents. I believe that this code is stable.
          Hide
          kdaniel Krzysztof Daniel added a comment -

          Are there any plans on this?

          Show
          kdaniel Krzysztof Daniel added a comment - Are there any plans on this?
          Hide
          sslavic Stevo Slavic added a comment -

          IMO best is to migrate away from xmlrpc.

          Show
          sslavic Stevo Slavic added a comment - IMO best is to migrate away from xmlrpc.
          Hide
          kdaniel Krzysztof Daniel added a comment -

          Any recommended replacement?

          Show
          kdaniel Krzysztof Daniel added a comment - Any recommended replacement?
          Hide
          sslavic Stevo Slavic added a comment -

          REST is popular these days.

          Show
          sslavic Stevo Slavic added a comment - REST is popular these days.
          Hide
          asoldano Alessio Soldano added a comment -

          JAXWS is the natural replacement for JAXRPC. There're multiple compliant implementations available, e.g. Apache CXF.

          Show
          asoldano Alessio Soldano added a comment - JAXWS is the natural replacement for JAXRPC. There're multiple compliant implementations available, e.g. Apache CXF.
          Hide
          claudenw Claude Warren added a comment -

          While it may be advisable to move away from xmlrpc there are a number of published services that use it. Given this situation continued support for xmlrpc should, in my mind, be continued. If support for the XMLRPC code is not going to continue, I believe that the XMLRPC component should be retired from the apache code

          I find it unfortunate that I submitted an XMLRPC patch to remove the dependency and it was never accepted or discussed.

          Show
          claudenw Claude Warren added a comment - While it may be advisable to move away from xmlrpc there are a number of published services that use it. Given this situation continued support for xmlrpc should, in my mind, be continued. If support for the XMLRPC code is not going to continue, I believe that the XMLRPC component should be retired from the apache code I find it unfortunate that I submitted an XMLRPC patch to remove the dependency and it was never accepted or discussed.

            People

            • Assignee:
              Unassigned
              Reporter:
              sslavic Stevo Slavic
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development