1. The principals.xml is used by the xmlusermanager, the parent of all of
the built-in usermanagers (and custom, unless you change the parent). As has
been said many times before, use the roleManager to add a user dynamically.
IF you do not declare a usermanager in your orion-application.xml (or the
default application.xml), only the xmlusermanager is used. If you use
ejbusermanager or datasourceusermanager, you can persist your users in a
database. A custom user manager could persist your users in cheese, if there
was a suitible cheese driver for java ;)...but more likely, you would use a
custom user manager to modify the in-built usermanagers (say the xml or ejb
or datasource...or use ldap, biometrics, etc.)
2. autodeploy in 1.5.2 is very useful, but many have experienced problems
with their specific files. The problems can often be traced back to some
esoteric deployment descriptor issue or using autoupdate to create the
1.5.2. Clean installations with proper deployment descriptors should work
with autodeploy.
regards,
the elephatnwalker
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rishi Kumar
Srivastava
Sent: Monday, August 27, 2001 10:25 PM
To: Orion-Interest
Subject: Can I implement security declaratively in the Principals.xml
and add users Dynamically into the file??
Hi Folks,
I was wondering if I could add users Dynamically into the principals.xml
so that the security in my application is implemented declaratively. I
Looked into the EJBUserBean also ...but it had empty ejbLoad and
ejbStore.. So obviuosly they are not persisting it into the
principals.xml. Then What are they doing with it is my confusion.
Would it b fine if I extend that class and add my own ejbStore and
ejbLoad which will persist the User data into the principals.xml.
How stable is the AutoRedeploy feature in Orion. Can an application b
designed based on the assumption that the AutoRedployment feature is
stable.
Warm Regards
Rishi
