Why does WL7 restrict security deployment descriptors?

Question

Hi,
WL7 has nice role based features - I can create a role based on
username/groupname and time.
However, when you define a role for a web application say, in a BEA specific
file weblogic.xml,
then I can only do this:
<security-role-assignment>
<role-name>RoleA</role-name>
<principal-name>SomeName</principal-name>
</security-role-assignment>
Why is this so restrictive? How can I add a time based component to this
role for instance?
Do I have to use the Admin Console? If I do use the console, then I can't
persist my changes, so in effect I can't use all the role features.....
I expected to find something like:
<security-role-assignment>
<role-name>RoleA</role-name>
<constraints>
<and>
<principal-name>SomeName</principal-name>
<group-name> Foobar </group-name>
</and>
<or>
<time> xxxyyxxx</time>
</or>
</constraints>
</security-role-assignment>
or something similar :-)
Regards,
Jon

Answer 1

The iAS registry is stored in a flat file (reg.dat) on UNIX platforms.
David
Raymond Brandon wrote:
And probably now a stupid question:
I'm wondering why IAS needs the GUIDs (global unique identifiers) to
register EJB's when it uses JNDI to look them up?
I'm using windows NT and can see the GUIDs in the registry under iPlanet
Application Server, but I wonder how this is done on platforms that don't
have a registry like Unix?
Raymond