|Re: [jakartaee-platform-dev] [glassfish-dev] Removing Jakarta Enterprise Web Services, JSR 109 from GlassFish or not?|
Hi, On 5/12/20 10:04 PM, arjan tijms wrote:
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.
I've done part of this move years ago when I tried to move it to metro-jax-ws project but never found time to finish it as other priorities were showing up, so that work actually never left my hard drive. Not sure I still have it somewhere... Anyway for the move to be possible, tests (TCKs and others) should be in place and working to avoid breaking stuff.
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 distoAnyway, maybe we can consider this for a future GF version.
...count with ~2 weeks should you want my ETA for this :-) thanks, --lukas
Kind regards, ArjanOn 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 <mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx> <jakartaee-platform-dev-bounces@xxxxxxxxxxx <mailto: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 <mailto:jakartaee-platform-dev@xxxxxxxxxxx>> *Cc:* glassfish developer discussions <glassfish-dev@xxxxxxxxxxx <mailto: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 <mailto: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 <mailto: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 <mailto:jakartaee-platform-dev@xxxxxxxxxxx> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev _______________________________________________ glassfish-dev mailing list glassfish-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
Back to the top