Ahh, my mistake. I thought you were talking about servlet authentication
(per the Servlet 2.2 spec). You are obviously talking about EJB
authentication, which is a different ball game. Scott's previous comments
are correct; the bean (and thus the user info) is not reloaded, as far as I
know.
Sorry for the confusion!
Karl.
-----Original Message-----
From: Marcelo Bellezo
To: Karl Moss; '[EMAIL PROTECTED] '; Scott Stirling
Sent: 7/6/00 3:41 PM
Subject: RE: Reloading User Information for Authentication
Karl,
actualy I did my custom authentication retrieving authentication
information from a database, with
the following code based on sample1b:
private static final HashMap users = new HashMap();
static
{
try{
Database db = new Database();
CachedRowSet crs = new CachedRowSet();
db.setUsr("web");
db.setPwd("web");
crs = db.select("select CDUSER, PASSWD from USER");
while (crs.next()){
users.put(crs.getString("CDUSER"),
crs.getString("PASSWD"));
}
}
catch (SQLException e){
System.out.println(e);
}
catch (Exception ex){
System.out.println(ex);
}
}
I know this piece of code is static and it's run once at the UserBean
call, I already transfer this
code to setEntityContext but it doesn't made any effect. Tracing the
default-event.log I realized
that the UserBean was charged once by Ejb application.
So, after all these conclusions, I don't know how to charge the user
information from database
when JRun is running. I've been reading the JRun API, most the
UserManager API, but I didn't
taken any conclusions.
If you have a tip, I'll be very thankful.
Marcelo
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
