| I can confirm this. I have never seen “actual use” of ACC in the wild. Remote EJB calls from Java SE / Swing / JavaFX - Definitely, but not ACC.
Thank you Arjan for clarifying this, I was also confused by this point.
+1 to deprecate ACC from EE. On Jan 9, 2025, at 7:44 AM, Reza Rahman via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
The reason for this is that vendor-specific remote JNDI lookup pre-dates the ACC. It’s just a very narrow set of customers that ever bothered with the ACC.
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Arjan Tijms via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx>
Sent: Thursday, January 9, 2025 1:57 AM
To: jan@xxxxxxxxxxx <jan@xxxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [DISCUSS] Mark Application Client as deprecated in Jakarta EE 11 Platform Profile?
As I understand it the appclient is what Swing uses to connect to the application server. I'm now mostly retired but I can refer to the last 20+ years of development in Java/JavaEE/JakartaEE.
My hunch is that quite a lot of people confuse "plain" remote JNDI access (using some client libs and InitialContext) with the application client container. All the Swing applications I ever saw in the same last 20+ years used remote JNDI access to talk to a J2EE/Java EE server.
The actual application client container does uses this technology under the hood, but is a rather distinct thing itself.
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
|
