|
Hi,
Jakarta EE is our
vision for the future of java enterprise development. I think we
have extensively discussed and decided this during the recent
months.
Microprofile becomes a more and more important part in this
area. But it is not the end of the world if we drive two
different namespaces. Even if Microprofile will be later merged
into Jakarta.
We at Imixs drive an open source project full based on Java EE
and Microprofile. I do not see that big problem if in a version
4.x Microprofile will change the namespaces later.
Ralph
On 27.09.19 05:02, Phillip Kruger
wrote:
Hi Reza
Not sure if I would call that fairly simple. Maybe rather
fairly messy. But that might just be me.
Again, if the rest of the community feel this is the
solution, then I'll support it. I think this topic need some
more discussion before we just start renaming ....
Cheers
A
fairly simple way to solve this is doing exactly what
needs to be done for javax.
*
Freeze mature MicroProfile APIs ready to move to Jakarta.
*
Move these APIs properly to Jakarta as-is.
* At
the runtime level, resolve org.eclipse.microprofile.* to
jakarta.*.
*
Make future changes under Jakarta.
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
9/26/2019 8:51 PM, Phillip Kruger wrote:
Hi Mike.
So are the Config that is proposed under Jakarta a
new Config API or the one from MicroProfile ?
* If it's a new one, we then have 2 Config APIs.
This is not good for us nor for the users.
* If it's the MicroProfile Config API that is
moving to Jakarta, my original concern is valid. This
means that everytime that an API move between these
communities it will cause a change, not only
internally for other MicroProfile APIs, but more
importantly our uses.
We have this one chance that our users needs to
change package names anyway due to javax, we should
make sure we do this correctly.
Either MicroProfile needs to become a sub brand of
Jakara and also make the change from org.eclipse.* to
Jakara now (so we still only effect users once) or we
need to find a brand (and org - so my initial
org.eclipse suggestion is bad) namespace to be used by
both (and future) communities.
This is what we had with javax.
On
2019-09-26 11:24 a.m., Thomas Andraschko wrote:
IMO independent of MicroProfile or
any other possible API which will be a part of
Jakarta in the future, all specs in Jakarta
needs the same "jakarta" namespace.
AFAIK, that is also the position of the Jakarta EE
Specification Committee. I don't believe this is in
any way a controversial statement. So just as Config
expected to switch to the javax
namespace when it was under the JCP, it
should expect to switch to the jakarta namespace if it re-hosted
there.
_______________________________________________
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
--
Imixs Software Solutions GmbH
Web: www.imixs.com Phone:
+49 (0)89-452136 16
Office: Agnes-Pockels-Bogen 1, 80992 München
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsführer: Gaby Heinle u. Ralph Soika
Imixs is an open source company, read more: www.imixs.org
|
