1. SOAP should stay. I don't use it for anything new, but we use it when ever it comes to third party systems integration.
2. Maybe I still don't fully understand this relationship : I thought Oracle gave JavaEE to Eclipse so the community will drive it. From the last couple of messages on this mailing list, it looks and feels like Oracle is calling the shots and telling us what they want to do. (Just that we agree with majority of their proposals)
IMO we should add JAX-WS (SOAP) - and as carlos said - try to evolve it.
Its still widely used for some industry standards like in the financial/insurance area (at least in germany).
Am Do., 10. Okt. 2019 um 10:27 Uhr schrieb carlos andres de la rosa <kusanagi12002@xxxxxxxxx>:
Thanks bill for that great summary and as a committer, I'm still believing that the SOAP support must be included and try to evolve this spec for future releases
Reza Rahman
Principal Program Manager
Java on Azure
Please note that views here are my own as an individual community
member and do not represent the views of my employer.
On 10/9/2019 7:54 PM, Bill Shannon
wrote:
Thanks for all the input on, and support of, Oracle's proposed plan for
Jakarta EE 9. Given the widespread overall support, I've recast this as
the proposed plan from the Jakarta EE platform project. After further
review and feedback, I'll ask the platform committers to vote on this
plan.
I made the following significant changes to the plan:
- pruned Jakarta Management
- backwards compatibility NOT included
- no new profiles
- Microprofile APIs NOT included
- release in 12 months or less
Some of the changes above were motivated by the desire to release sooner
rather than later, which seemed to be the consensus.
The most feedback was probably around the removal of SOAP support.
I think we've adequately explained that products can continue to
provide SOAP support based on the Jakarta versions of the corresponding
specifications, which will have no changes to their APIs and will
continue to use the javax namespace. If platform project committers
believe SOAP support MUST be included, now is the time to speak up.
Note that this would have a significant impact on the amount of work
to be done for Jakarta EE 9.
Every detail in the plan will have someone who objects. What I'm trying
to achieve is consensus on a plan that most people can support, even if
no one thinks it's perfect. As usual, I'm looking forward to your
continued feedback, especially if you think I'm moving in the wrong direction.
Thanks.
--
Reza Rahman
Principal Program Manager
Java on Azure
Please note that views here are my own as an individual community member and do not represent the views of my employer.
