Details

    • Type: Story Story
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Fedora 3.6
    • Component/s: Fedora
    • Labels:
      None

      Description

      Fedora has used Axis 1.3 for quite some time. We need to move away from this as the 1.x line is no longer maintained. This will also allow us to properly support modern soap with attachments.

      Need to make a decision on the library to use. CXF looks like a good candidate: http://cxf.apache.org/

        Issue Links

          Activity

          Hide
          Chris Wilper added a comment -
          Need to consider why/why not run Axis 2?
          Show
          Chris Wilper added a comment - Need to consider why/why not run Axis 2?
          Hide
          Bill Branan added a comment -
          This article http://www.theserverside.com/tt/articles/article.tss?l=AxisAxis2andCXF notes that CXF integrates well with Spring. As we are intending to move toward using Spring as part of the baseline this may be the distinguishing feature.
          Show
          Bill Branan added a comment - This article http://www.theserverside.com/tt/articles/article.tss?l=AxisAxis2andCXF notes that CXF integrates well with Spring. As we are intending to move toward using Spring as part of the baseline this may be the distinguishing feature.
          Hide
          A. Soroka added a comment - - edited
          I'd like very much to expose some of Fedora's API-M through JMS. It seems possible with Axis 1.x, but I'd rather not invest any time in that if (as is devoutly to be desired) Fedora is moving to a more modern library. I'm not able to commit any time to helping with that now, so for the moment, this is just a vote in favor and another reason to throw on the pile for a new WS library.
          Show
          A. Soroka added a comment - - edited I'd like very much to expose some of Fedora's API-M through JMS. It seems possible with Axis 1.x, but I'd rather not invest any time in that if (as is devoutly to be desired) Fedora is moving to a more modern library. I'm not able to commit any time to helping with that now, so for the moment, this is just a vote in favor and another reason to throw on the pile for a new WS library.
          Hide
          A. Soroka added a comment -
          An additional reason: CXF (and other similar frameworks) now permit of building out REST interfaces using JAX-RS or similar approaches. It would be lovely to imagine a unified model exposed in every architectural style wanted simply via annotations. Even if that level of unification isn't considered desirable, just using the same library for REST and SOAP exposure would lower the barrier to entry for contribution.
          Show
          A. Soroka added a comment - An additional reason: CXF (and other similar frameworks) now permit of building out REST interfaces using JAX-RS or similar approaches. It would be lovely to imagine a unified model exposed in every architectural style wanted simply via annotations. Even if that level of unification isn't considered desirable, just using the same library for REST and SOAP exposure would lower the barrier to entry for contribution.
          Hide
          Benjamin Armintor added a comment -
          CXF handles JAX-WS in master for 3.6
          Show
          Benjamin Armintor added a comment - CXF handles JAX-WS in master for 3.6

            People

            • Assignee:
              Asger Askov Blekinge
              Reporter:
              Chris Wilper
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: