Title: Message
Assuming I want to do it anyway, what's the container configuration involved?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rupp, Heiko
Sent: Sunday, February 01, 2004 11:47 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Disallowing Local interface access from servlet tier

Hi,
 
what you want can be done through container configuration. But you will
loose much speed.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Craig Berry
Sent: Monday, January 12, 2004 8:16 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Disallowing Local interface access from servlet tier

I have noticed that in the default JBoss 3.22 + Tomcat deployment configuration, it is possible to obtain Local interfaces for EJBs from the Servlet tier.  In the interest of maintaining maximum portability (e.g., to enable us to later move to separate boxes for the two tiers), I would like to disallow Local access from the servlet tier.  Obviously, our design avoids using it, but I'm concerned that "leakage" might occur without our noticing it (e.g., an EJB returns an object to the servlet tier which, when accessed, does a Local lookup back to another EJB component).
 
Is there any way to make Local lookups from the servlet to the EJB container impossible at the configuration level?  Or would I have to run the two in separate JVMs to accomplish this?
 
--
Craig Berry
Principal Architect and Technical Manager
PortBlue
(310) 566-7546
 

Reply via email to