[
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?
|
+1. Very much agree. I have seen the ACC in use, but it is very,
very rare. Just JNDI (on Java SE or the server) is far more common
(and "common" is relative even here - I have not seen a new EJB
remote application in 15+ years).
On 11/26/2024 5:53 PM, Arjan Tijms via
jakartaee-platform-dev wrote:
Hi,
Personally I've been a fan of remote EJBs for a long time,
but realistically it's time to let them go, too.
Practically speaking, I've never in ~24 years used remote
EJBs from an application client. Nor did I ever see anyone
doing that. I've only ever seen remote EJBs being used from
plain Java SE (using JNDI lookups and client libraries), and
server to server (where those servers where the same brand and
version)
I'd say we can deprecate the application client
container already and don't necessarily have to deprecate
remote EJB too. Of course, if someone would still want to
deprecate remote EJB for Jakarta EE 11 I would be okay
with that. Just saying IMHO it's not strictly needed.
Kind regards,
Arjan Tijms
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).
_______________________________________________
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