I will be out of the office from 10-Sep-2001 to 03-Oct-2001, with limited email and voice mail access. For business matters, please click on the link below to contact the relevant person.
PetStore eXtreme matters :James H. Brooks
Other business matters, my manager : David L. Johnson
Thank you.
Hellu,
How can I configure Orion and my J2EE application such that client
applications are only able to call the get methods of the entity beans ?
I want that all modification are done throw the Session Manager. The
Session manager functiones as an intermediate to the entity beans.
I am using
Eddie,
Use your slsb or sfsb (the session manager) as your facade to the ejb for
all access. In your web.xml or client.xml, only refer to the slsb or sfsb as
an ejb reference. This means that your container will not allow you to get
the context for your entity ejb, so you won't be able to call
Elephantwalker,
Thanks (see below)
an ejb reference. This means that your container will not allow you to get
the context for your entity ejb, so you won't be able to call any methods
from the client.
But then I also can't call the entity get methods ??, or can I ?. Which is
what I want.
*This message was transferred with a trial version of CommuniGate(tm) Pro*
I've sent unsubscribe requests to both this list and the
orion-interest-request, and I'm still on here
Please get me off this *#$$# list! :)
PLEASE!
Jordan
The point was to use the facade pattern. Only access the entity bean in the
slsb, and use slsb methods from the servlet or client to mutate date AND get
data. You can also use authentication role's on your slsb methods to
restrict or prevent access.
This is what we on our www.elephantwalker.com