Correct. Do
not assume that just because we have to change javax to "jakarta"
that it applies to all projects that might someday be associated with Jakarta
EE. The javax rename is a special case due to Oracle requirements.
As Dmitry points out this whole area needs further discussion.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
"dmitry.kornilov"
<dmitry.kornilov@xxxxxxxxxx>To:
JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>Date:
09/18/2019
12:31 PMSubject:
[EXTERNAL]
Re: [jakartaee-spec-project-leads] Jakarta NoSQL and Eclipse MicroProfile
ConfigurationSent
by: jakartaee-spec-project-leads-bounces@xxxxxxxxxxx
It doesn't mean it. Where is an option
to keep microprofile.io namespace. We need to discuss it.- Dmitry-------- Исходное сообщение
--------От: Otavio Santana <otaviopolianasantana@xxxxxxxxx>
Дата: 18.09.2019 10:56 (GMT-08:00)
Кому: JakartaEE Spec Project Leadership
discussions <jakartaee-spec-project-leads@xxxxxxxxxxx> Тема: Re: [jakartaee-spec-project-leads]
Jakarta NoSQL and Eclipse MicroProfile Configuration If move Eclipse MicroProfile into Jakarta
EE process means a new package name such as jakarta.config.
I don't think that is a good idea, because several people use Eclipse MicroProfile
in production. So, we are going to have two projects to the same thing
(one as MicroProfile and a second one as Jakarta), and sometimes it might
mean copy/paste from/to projects. Therefore, smell code on both projects.On Wed, Sep 18, 2019 at 10:36 AM Dmitry
Kornilov <dmitry.kornilov@xxxxxxxxxx>
wrote:Emily,I have a better idea. Let's make MP Config
the first spec which follows Jakarta EE spec process. It will make it a
full Jakarta EE citizen and open doors to other specs to use it. :)Thanks,DmitryOn 18 Sep 2019, at 05:38, Emily Jiang
<emijiang6@xxxxxxxxxxxxxx>
wrote:Hi Otavio,As promised via our chat, I would share
my view here.I totally agree that Configuration is
very important for developing cloud-native microservices. It is a best
practice in 12-Factor App to make microservice configurable. MicroProfile
Config exists for exactly that reason. I strongly recommend to use it.As for your question of whether it is
ok for Jakarta EE to depend on Eclipse MicroProfile Config, I think it
is a good idea. Since many people including Adam Bien, myself, etc, seriously
think Jakarta EE + MicroProfile are very powerful together and most of
time they are needed at the same time, I strongly think it makes sense
for Jakarta EE specs also utlising MicroProfile specs such as MicroProfile
Config, etc. MicroProfile specs already pull in Jakarta EE specs, such
as CDI, JAX-RS, JSON-B and JSON-P. Technically Jakarta EE should be able
to pull in MicroProfile specs.If a lightweight onboarding process is
needed to enable MicroProfile specs to be used in Jakarta Specs, I am ok
with that. It is very important that MicroProfile and Jakarta continue
complementing with each other not competing with each other.My 2cents.EmilyOn Sun, Sep 15, 2019 at 9:07 PM Otavio
Santana <otaviopolianasantana@xxxxxxxxx>
wrote:
Hello everyone, I have one question about the integration between Jakarta
and Eclipse MicroProfile.
As you know, Jakarta EE has the goal of the cloud-native application, so
we tend to use good practices on that.
There
is the twelve-factor of an Appthat has the good practices of delivery your application in the cloud,
and the third
item there is the configuration.My whole point here is that need to have
one API to all Jakarta EE project to use related to configuration. We might
use this API on several projects such as JPA, JMS, and so on. Right now,
we're
facing this discussion on Jakarta NoSQL.
My question is: Do we have plans to integrate Jakarta EE with Eclipse
MicroProfile Configuration?
I'm not happy with a copy/paste approach from a feature that already exists,
because that means two points to maintain; furthermore, that is not good
code practices.In the cloud, the perspective configuration
will be like CDI, because several specifications are going to use it. Right
now, my best shot to Jakarta NoSQL is to use only in the Reference implementation
and put it as optional.-- Otávio Santanatwitter: http://twitter.com/otaviojavasite: http://about.me/otaviojava_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
-- Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
-- Otávio Santanatwitter: http://twitter.com/otaviojavasite: http://about.me/otaviojava_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads