Skip to content
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.

Decide for JAX-WS implementation #29

Closed
hohwille opened this issue Aug 21, 2014 · 3 comments
Closed

Decide for JAX-WS implementation #29

hohwille opened this issue Aug 21, 2014 · 3 comments

Comments

@hohwille
Copy link
Member

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.

@hohwille hohwille added this to the oasp:0.2.0 milestone Aug 21, 2014
@hohwille hohwille self-assigned this Aug 21, 2014
@hohwille hohwille removed their assignment Aug 22, 2014
@sobkowiak
Copy link
Member

👍 for CXF

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.

@hohwille
Copy link
Member Author

hohwille commented Sep 8, 2014

@hohwille
Copy link
Member Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants