Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [POLL] Would you support the as-is javax JAXB and JAX-WS in your implementation
+1 Mark
90% of the webservices that i know in the german insurance/financial industry are XML! And i'm almost sure that wont change in the next 5 years.

Am Do., 5. Dez. 2019 um 09:12 Uhr schrieb Tibor Digana <tibordigana@xxxxxxxxxx>:
>> Try establishing http+JSON between governmental organisations! You will sweat blood and badly miss the guaranteed structure which an XML Schema gives us.
Or try to access SAP or whatever 'established' system without SOAP. Good luck!

As Mark said, this is all true! These words should be written on the top of every wall wherever the young REST fans in DZone are looking!!!

On Thu, Dec 5, 2019 at 8:09 AM Mark Struberg <struberg@xxxxxxxxxx> wrote:
b.) move JAX-WS from javax to jakarta.*

Reason is that there are a TON of applications still using JAX-WS. And it makes perfect sense. Try establishing http+JSON between governmental organisations! You will sweat blood and badly miss the guaranteed structure which an XML Schema gives us.
Or try to access SAP or whatever 'established' system without SOAP. Good luck!

For _some_ use cases XML makes perfect sense. We should not ditch support for it easily.
I'm fine with making it optional. But I'd rather see us resurrecting the idea with the different profiles: micro/web/full. And in full profile JAX-WS should really be there.

Now why should we do the work moving from javax to jakarta packages? Because it's big bang. And thus relatively easy to do.
We probably don't need to change anything in the current release. But if there is any chance that we must add/tweak anything then we will start cursing a lot...

LieGrue,
strub


> Am 03.12.2019 um 10:59 schrieb David Blevins <dblevins@xxxxxxxxxxxxx>:
>
> An informal poll for the implementations.  I think we might be all saying the same thing differently.
>
> Let's say that Jakarta EE 9 doesn't "include" JAXB, JAX-WS or Activation, whatever "include" means.
>
> Will you then:
>
> a) leave the `javax` versions of JAXB, JAX-WS, Activation in your future Jakarta EE 9 implementation
> b) put the work into removing `javax` versions of JAXB, JAX-WS, Activation and ship your future Jakarta EE 9 implementation without them
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
> 310-633-3852
>
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top