| Re: [jakartaee-platform-dev] Core profile as its own top level org |
_______________________________________________I had outlined some options on an earlier thread. Just for reference they are essentially along these lines:
- See if it is possible to migrate (by value, not reference) MicroProfile JWT into Jakarta Security. During the “migration” one should take the opportunity to improve design if sensible.
- If this proves too cantankerous, simply define a way in Jakarta Security for multiple authentication/authorization mechanisms in the same application, including “third party” ones. Then hope that MicroProfile JWT choses to become one of these recognized “third parties”.
To be honest, I think these are the only two practical choices without getting into mind bending circular platform dependencies that we ask developers to try to understand.From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Kito D. Mann <kito.mann@xxxxxxxxxxx>
Sent: Tuesday, December 6, 2022 9:56 PM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Core profile as its own top level orgYou have a good point, Reza, and in general I agree. It's all somewhat confusing and we need to keep pushing forward. However, I think Arjun is trying to solve the specific problem of how to handle JWT with Jakarta EE Security without reinventing the wheel. And I still don't see a solution for that (unless I missed it).___Expert training and consulting: Cloud architecture, Java/Jakarta EE, Web Components, Angular* Enterprise development, front and back. Listen to Stackd Podcast.* Speak at conferences? Check out SpeakerTrax._______________________________________________This is generally the feedback we get from customers, old and new to the space. Truth be told, the Jakarta EE/MicroProfile segmentation is already cause for a lot of confusion. Core Profile is an obvious need in evolving the space. There is also no harm in having faster Core Profile only releases and independent specification releases. It’s best to not further segment unless there is truly a compelling need (which I currently honestly do not see). If anything, a path towards gradual brand convergence would be best (though that is clearly not pragmatic right now).I understand some folks believe Jakarta EE has a brand perception issue. I tend to think it’s an issue that can be mitigated through consistent delivery, jettisoning truly damaged brands like EJB, serious innovation in implementations beyond the specifications as well as persistent, high quality marketing/advocacy.At any rate, my main point is that maybe we should focus on delivering more high quality releases right now instead of more restructuring/reshuffling/renaming/regrouping that’s likely to get in the way of delivery and add to an already very confusing landscape that maybe actually helps no one.From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Vedran Smid <vedransmid@xxxxxxxxx>
Sent: Wednesday, November 30, 2022 4:52 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Core profile as its own top level orgHi,To an outsider and an end user all this sounds very confusing. Too much of everything usually makes management harder.Perhaps it is better not to mix MP and Jakarta. Keep MP what it is, an independent(aside APIs of course) extension to Jakarta.On Wed, 30 Nov 2022 at 10:40, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:_______________________________________________I would say another Working Group is a bad idea as it is another load of bureaucracy, charter, committee and fees. A separate project under Jakarta EE makes more sense to me i.e. splitting the current platform project.
Steve
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Rudy De Busscher <rdebusscher@xxxxxxxxx>
Sent: Wednesday, November 30, 2022 8:38:35 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Core profile as its own top level orgI really like the idea of a separate entity/working group for core profile.
That would also solve the ambiguity around CDI lite that exists today, and a separation of the CDI specs which is really needed. Since CDI lite is not a separate spec, nor has a separate API (which means you have one API where some classes/methods that don't need to be supported in the runtime) which will lead to confusion, exceptions during runtime (since methods might not be implemented), etc ...
I means we can also remove _expression_ language from the profile since that is only required for CDI full (not supported for CDI lite)
Rudy
On Tue, 29 Nov 2022 at 18:25, Werner Keil <werner.keil@xxxxxxx> wrote:
_______________________________________________Hi,
Sorry I missed the call today, but that diagram/idea for Core Profile would sound about right leaving aside the Core Profile now includes „CDI Light“.
Kind Regards,
Werner Keil
Von: arjan tijms
Gesendet: Dienstag, 29. November 2022 18:09
An: jakartaee-platform developer discussions
Betreff: [jakartaee-platform-dev] Core profile as its own top level org
Hi,
During the platform call we very briefly touched on the core profile being the intersection between Jakarta EE and MicroProfile, but since it's part of Jakarta EE that relation is somewhat unclear.
We had on the table at one point a discussion of making "core profile" (we didn't have the name back then) its own top level working group (org/entity):
Maybe we can revisit this idea again.
Kind regards,
Arjan Tijms
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
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
