Jakarta EE Platform deployments can still call remote EJBs remotely on other server instances as well as locally (hopefully the local call is optimized).
Then there would be some effort required to update the platform TCK to replace use
of the application client with either server to server or co-located remote EJB calls; otherwise, I expect almost all remote EJB testing would be eliminated.
Tracy Burroughs
(tkb@xxxxxxxxxx)
WebSphere Application Server Development
IBM Rochester, Dept AAW, Bldg H315/050-2
2800 37th Street NW, Rochester MN 55901-4441
From: Scott Marlow <smarlow@xxxxxxxxxx>
Sent: Tuesday, November 26, 2024 3:28 PM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Tracy Burroughs <tkb@xxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] [DISCUSS] Mark Application Client as deprecated in Jakarta EE 11 Platform Profile?
Without the application client, there would be no required client making Enterprise Beans Remote interfaces effectively unusable? Jakarta EE Platform deployments
can still call remote EJBs remotely on other server instances as well as locally
Without the application client, there would be no required client making Enterprise
Beans Remote interfaces effectively unusable?
Jakarta EE Platform deployments can still call remote EJBs remotely on other server instances as well as locally (hopefully the local call is optimized).