You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
According to issue #1 we decided for CXF as JAX-RS implementation. CXF also implements JAX-WS so it would be an option to use it for both JAX-RS and JAX-WS. However we have the greater experience with Metro2 what is also the reference implementation. We finally have to make a decision here.
The text was updated successfully, but these errors were encountered:
As already discussed in #1 we should use CXF for for JAX-WS too. We should use one implementation for both JAX-RS and JAX-WS.
Indeed, we have probably more experience with Metro but we have experience with CXF too. We should provide a platform which is easy and good manageable. Mixing 2 web services stacks only because we have more experience with Metro is a bad idea.
As mentioned in #1 Metro has some issues while integrating with Spring.
It seems that the entire OASP community votes for CXF. I did not get any other feedback.
I close this. If the lead architects come up with a problem or whatever, we can still re-open.
According to issue #1 we decided for CXF as JAX-RS implementation. CXF also implements JAX-WS so it would be an option to use it for both JAX-RS and JAX-WS. However we have the greater experience with Metro2 what is also the reference implementation. We finally have to make a decision here.
The text was updated successfully, but these errors were encountered: