[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
MSc Electronics, ICT
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Originally posted by Roland Barcia:
Calling an EJB with the local interface from the Web Container is possible.
I recomend it. It is a matter of performance versus location transperency. I would choose performence since you will have the EJB and Web in the same layer most of the time anyway.
Kishore
SCJP, blog
Originally posted by Kishore Dandu:
I am curious how EJB and Servlet can be in the same layer(in the sense of clustered environment). They may look like that since they are both on the server side, but they both can be on two different virtual machines. But for a user they may seem virtually on the same layer(server side) but on two different JVMs. Only in small scale J2EE systems they are sitting on the same box, I would say.
Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Originally posted by Kishore Dandu:
Only in small scale J2EE systems they are sitting on the same box, I would say.
Originally posted by Chris Mathews:
Absolutely wrong. Most large-scale J2EE deployments co-locate the EJB and Web tiers in the same JVM in the form of an Enterprise Application. This is the main motivation for standardizing EAR deployments in the J2EE 1.3 Specification. When large systems need to scale horizontally then the application is replicated across all nodes in the cluster.
Kishore
SCJP, blog
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Regards,
Pho
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Originally posted by Roland Barcia:
I never liked the idea of having the Remote/Local interfaces being a programmatic decision, I think this made the spec more complex for the client. Using some type of smart delegate is defintley that hides the details of weather it is local or remote is definitely adivisable. The spec should have made this a deployment decision and not a programmatic one.
Kishore
SCJP, blog
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
Regards,
Pho
Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services