Hi Scott,
I agree “The burden is enormous on GlassFish to be the first impl”. I can’t remember the reason for that dependency but in the Jakarta EE 12
timeframe we should again look to remove it like the Core Profile is doing now.
I was wondering whether other implementations have problems with these specific tests. I will check internally where we are on these.
|
--
|
|
Steve
Millidge
Founder
&
CEO
|
From: Scott Marlow <smarlow@xxxxxxxxxx>
Sent: 27 November 2024 13:08
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>; Steve Butler <steve.butler@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [EXTERNAL] Re: [DISCUSS] Mark Application Client as deprecated in Jakarta EE 11 Platform Profile?
I would assume that marking something as deprecated doe not in itself remove the obligation for an implementation to test the deprecated api or am I wrong with that assumption?
Apologies for not being across all the discussions but are other implementations also failing the relevant tests or is this a GlassFish issue?
We know that the (TCK tests vehicle) ejb bean lookup returns null and some other hints but personally when I tried single stepping through the Glassfish EJB3 impl code (some orb/jndi code as well), I didn't get
lucky on finding the reason for the lookup to fail. Scott Stark got a standalone app client program to work with using @EJB but we haven't recreated the same to work with the TCK. David also found a possible workaround of using "lookup" in the app client
deployment descriptor which is another path but not a strong one (see recent comments in the GF issue for improving information shown during remote bean lookup).
Going forward, we should identify what we need for our teams to succeed in finishing the release. The burden is enormous on GlassFish to be the first impl as well as the pressure to complete the TCK tests on
those working on TCKs.
|
--
|
|
Steve
Millidge
Founder & CEO
|
Looks like even in Jakarta EE 11 platform, we could make App Client and Remote EJB optional. If we do that, the TCKs for these areas would be eliminated.
And, even if they were allowed, they would still need to be covered by the TCK and implemented by at least one implementation.
It is, however, possible to deprecate the app client, and by that (sort of) making the test coverage less relevant.
Anyway, as we learned in the Platform call yesterday, it is _not_ testing the app client itself that is the issue. Those tests pass and are fine.
The issue is the _usage_ of the app client in the TCK for testing other areas (such as JPA).
Thanks for confirming. This indicates another endorsement of being able to release Web Profile separately from Platform Profile.
The only references are in the CDI EE integration part of the specification that is now part of the platform spec.
Please do that and get back to us.
I believe that app client is entirely in the platform, but need to double check CDI for mentions.
At the 2024-11-26 Platform Project call, an idea was surfaced, I think originally by Ivar, to not wait until EE 12 to mark the Application Client as deprecated in the Platform Profile. This thread is intended to discuss and determine
the feasibility of this idea.
The most important questions seem to be:
·
Can this be done without making any changes to any of the component specifications?
·
Can this be done entirely and completely by making changes only to the Platform Profile specification text?
_______________________________________________
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
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation
Eclipse Foundation - Community. Code.
Collaboration.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|
