Sean,
Ejipt 1.1.1 (due out in a week or so) provides support for "local" or
"private" beans. This provision (fully compliant with the spec) is designed
to solve the problem of sharing server resident data while not exposing all
deployed beans to clients.
All private beans are otherwise standard beans. The only difference between
private and public beans is that the server:
1) does not make the homes available in the JNDI contexts
2) does not export the stubs to RMI classloaders and
3) is able to optimize calls to the private bean's objects.
Imre Kifor
Valto Systems
-----Original Message-----
From: Sean C Sullivan <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, May 21, 1999 4:54 PM
Subject: Deny remote clients access to Entity bean methods
>I've got two EJB's:
>
> EJBA - a stateful session bean
> EJBB - an Entity bean
>
>I implemented home and remote interfaces for both beans.
>
>I want to setup the following:
> 1) allow remote clients to call methods on EJBA
> 2) deny remote clients access to methods on EJBB
> 3) allow EJBA to call methods on EJBB
>
>#1 is easy to do.
>
>I'm looking for the best way to satisfy requirements #2 and #3.
>
>Thoughts?
>
>-Sean
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
