Hi all,
I'm not new to Java, but I am to EJB's and Orion's server. And I have a few
questions concerning both of those.
First, assuming a web client, what maps a particular client to a Statefull
Session Bean, particularly on subsequent pages? As a web developer, I've
used cookies to preserve state, I've used client-side JavaScript variable,
I've even had a server that designated certain pages to start a session and
certain ones to end it, but I don't see how state is being preserved in
this case. I understand the concept of one JSP creating a Statefull Session
Bean, but I'm unclear on what's going on behind the scenes when the user
invokes a second JSP and the Statefull Session Bean is still there having
retained the information from the first call. What starts and stops a
session? What happens if another user invokes the same JSP page? What if
they're both behind a firewall and both appear to the server as having the
same IP?
Second, does inheritance of Session Beans, work the same as other
inheritance in Java? The answer is probably yes, but I've never seen this
covered. Every EJB I've seen has extended EjbObject. Can I still have
abstract super classes?
Third, what's the deal with user authorization being contained in a flat
file (principals.xml)? Who has a static set of users? In my web
application, application users are defined in a login table within our
database. How would I express this in Orion/EJB (that user authentication
needs to occur through custom routines in the database)? Am I
misunderstanding the intent of the principals.xml file? Is it just a place
to handle system logins to the database, such that further authentication
can occur?
Thanks in advance,
-adam winter
