Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] EE4J Project Proposals
What Oracle has stated at least publicly so far is that existing technologies can continue to use whatever packages they have now. How exactly this squares with any consistent legal position with regards to branding and trademarks I have absolutely no idea. This is probably one of those compromises the sensible technical people were somehow able to make with Oracle legal. Or at least let's hope so. Otherwise this entire effort is dead in the water since it will have to break backwards compatibility and force migrations.

Such is the nature of dealing with a company that still grapples with understanding the value of openness to it's own technologies/business and only deals with it when it absolutely has to. Even Microsoft didn't have a problem fully granting C#/CLI to ECMA/ISO without strings attached. Hindsight is twenty/twenty but of course all of this would be a moot point if Sun had properly standardized Java via the ECMA/ISO like it should have in the first place.

On 11/25/2017 12:44 PM, Werner Keil wrote:
What's also weird about JAX-RS is, that it was seemingly "forgotten" when all of Java EE 8 (and earlier JSRs) moved to a new place under

What is not mentioned in the proposals of either, but seems far more important IMO than whether it's called "Eclipse RESTful Web Services API for Java", "JAX-RS" or something else is backward compatibility with the Java EE 8 or 7 versions of these APIs. Is the new follow-up API allowed to stay under "javax.ws.rs" or immediately forced to refactoring into something else? (like "ee4j.ws.rs", "ee.<something>.ws.rs" or e.g. "org.eclipse.ws.rs" just to mention some hypothetical examples)

Werner


On Sat, Nov 25, 2017 at 6:00 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to
        ee4j-community@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/mailman/listinfo/ee4j-community
or, via email, send a message with subject or body 'help' to
        ee4j-community-request@eclipse.org

You can reach the person managing the list at
        ee4j-community-owner@eclipse.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."


Today's Topics:

   1. Re: EE4J Project Proposals (Markus KARG)


----------------------------------------------------------------------

Message: 1
Date: Fri, 24 Nov 2017 18:07:49 +0100
From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
To: "'EE4J community discussions'" <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
Message-ID: <002a01d36546$c5179710$4f46c530$@eu>
Content-Type: text/plain; charset="utf-8"

I don't understand that new versions of the JAX-RS specification shall be done, but at the same time it would violate Oracle's naming rights if we call that new specification still "JAX-RS"??! That means, we have to rename the specification's name? BTW, a quick search in the WIPO Global Trademark Database did not bear any registration of the term "JAX-RS", neither by Oracle nor by others.

-Markus



From: ee4j-community-bounces@eclipse.org [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Donnerstag, 23. November 2017 18:25
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] EE4J Project Proposals



On 2017-11-23 11:58 AM, Markus KARG wrote:

What is "the corresponding spec project"? For JAX-RS for example, Jersey is "just" the RI, and it is just the *current* RI.


Exactly right.




In the JCP we could decide to have future release of JAX-RS with different RIs.


It is the intent of Oracle, IBM, Red Hat, and other participants that future versions of the JAX-RS specs will be done using a new spec process hosted at the Eclipse Foundation.




So does that mean that from now on the JCP must stick with Eclipse-provided *current* RIs forever?

Um. no. That would be dumb. And under the new spec process provisions will be made to allow new RIs to appear, as well as ensuring the creation of independent implementations.

Actually I do not understand why the API project is not simply named "JAX-RS API", the TCK project "JAX-RS TCK" and the RI simply "Jersey"?


Because those project names would violate Oracle's trademark rights in the "JAX-RS" name.

--
Mike Milinkovich
mike.milinkovich@eclipse-foundation.org
(m) +1.613.220.3223

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171124/1c92e2e0/attachment.html>

------------------------------

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


End of ee4j-community Digest, Vol 3, Issue 72
*********************************************



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


Back to the top