Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] [jakartaee-platform-dev] Removing Jakarta Enterprise Web Services, JSR 109 from GlassFish or not?
Hi,

Indeed, this just concerned 109 which is not JAX-WS. Removing it from the GlassFish code would, in my opinion, not be deleting the code but moving it to its own project.

That way it could still be tested (and GlassFish could still be used for that), but it just would not be included in the downloadable and certified GF disto

Anyway, maybe we can consider this for a future GF version.

Kind regards,
Arjan



On Tue, May 12, 2020 at 8:21 PM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

Hi Tibor,

 

We are not discussing specs here just whether GlassFish 6 needs to have it and it does as it is optional and we need an implementation of all optional specifications in GlassFish for now.

 

GlassFish isn’t the reference implementation of anything in Jakarta EE 9.

 

JSR109 isn’t JAX-WS it predates JAX-WS.

 

Steve

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Tibor Digana
Sent: 12 May 2020 18:49
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Removing Jakarta Enterprise Web Services, JSR 109 from GlassFish or not?

 

If GlassFish is the reference implementation of WS then you cannot remove it and the TCK tests have to support it.

I would be really happy if Jakarta synchronized the work with the group at IETF.

If the SOAP RFC is updated then Jakarta has to support WS and keep updating Jakarta spec.

 

Removing this spec kills the banks and government systems.

 

Finally, Jakarta EE must have this spec forever.

The application server may implement it or not. And this is what I understand by "Optional" except for the reference implementation.

 

Back to the API. JAX-WS and JAX-RS have different philosophy.

The RS is only a subset of WS, where WS can be used to e.g. transfer money over the bank accounts but RS works only with "data" as a resouce. Not everything is a resource.

 

Feel free to propose a new RFC at IETF and a new API over JSON and miscellaneous implementations over JMS, HTTP, ...

Removing it is simple but creating a new one is difficult...

 

On Tue, May 12, 2020 at 5:36 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

 

With JSR 109 being optional for Jakarta EE 9, is it the intention for this one to be removed from GlassFish?

 

Kind regards,

Arjan

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top