Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

All the frameworks support JAX-WS specification so that it is easier to migrate from one to another. There exist two frameworks which are not mentioned in the following text, as they do not support JAX-WS standard and the community behind those product is not as big as behind the four frameworks mentioned above. The two frameworks:

...

 

1

2

3

4

5

6

7

8

9

10

Axis2

0

-

1

0.5

1

1

1

1

1

1

CXF

1

1

1

1

1

2

1

1

1

1

Metro

1

0

1

0.5 75

1

2

1

1

1

1

JBoss WS

0

-

0

0

0*

-

1

1

1

0

*only java2wsdl

Info

...

Performance comparison is taken from http://www.ibm.com/developerworks/webservices/library/j-jws14/index.html where large responses are taken into account.

Info

"Spring integration" comparison is based on tutorials posted on here (Axis2)here (CXF) and here (Metro), and on sample applications attached to the WS stack. For instance, sample application distributed with CXF for wsdl-first approach is well documented, there is support for both Maven and Ant, the Spring integration is also done and the example of using MTOM is also present. Samples from Axis2 sometimes support Maven, sometimes Ant, there is an MTOM example, but "Spring integration" and "wsdl-first" examples are missing. All sample applications from Metro use Ant for building, there is an example of wsdl-first approach and MTOM, but Spring integration showcase is missing.

Community Support

It is hard to measure this aspect, so I put here links to the issue trackers or, where it is present, the mailing lists with commits. I forgot to mention that CXF and Axis2 are both supported by Apache Foundations and Metro by Oracle. If fcrepo is going to migrate to Java EE 6 (with Context Dependency Injection, JAX-RS, etc.) in the future, Metro or JBoss WS stacks are better prepared to this migration, in my opinion.

...