[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] [DISCUSS] Mark Application Client as deprecated in Jakarta EE 11 Platform Profile?
|
What Arjan says is true. There’s a difference between calling EJBs remotely and calling them from an appclient container.
Appclient is a proxy that pretends that the client runs in an appserver, injects EJBs and calls them locally. Then it intercepts the calls and forwards them to remote EJBs running on the server. This is not used often, and if it is, it would still be possible to rewrite to use plain remote EJB calls.
Another things is that removing appclient from Jakarta EE doesn’t remove it from appservers. Most appservers that have will continue supporting it. It’s an old technology, no need to add new features, and old apps that use it will not need new features nor will need to be migrated to an appserver that doesn’t support appclient (in most cases).
So, by removing appclient from Jakarta EE, there will still be appservers that can run apps that need it, and it’s also possible to migrate them to plain remote EJB calls.
Ondro
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
