I'e been facing this problem in implementing the Solution I've been
working on.
I've faced this issue in driver policies while integrating with other
components in the system(i.e. IDV, workflows, drivers, etc)
Here's the issue in brief:
The issues mainly have to do with the transaction management of the
Novell framework, and I am listing some of them here.

1) A local variable used in a driver policy must draw its state from
the current user object in the current transaction. However, if multiple
requests(for multiple user objects) are raised, the variable commonly
used in the policies are mixed up. Fo e.g. if there's a delete request
for user1 and create request for user2, we've encountered scenarios
wherein status values for user2 object are set in values for user1
For e.g. an attribute which triggered an event (transaction) when used
to set a local variable, returned null thus causing an exception ..
because variable was set to null in some other user object's

Is there a configuration problem somewhere?

2) For one user object, a local variable value (driver scope) is
persisted across multiple transactions. Say a variable being used in a
policy is initialized conditionally, and checked thereafter; the
variable’s value if not set in the current transaction gets set to its
previous value in a processed transaction.

All these problems have been observed at fairly low transaction density
say 2 simultaneous transactions.

I believe that data sanity is something which is usually taken into
account while developing a framework.

Please guide what Iam missing here??

varunece's Profile: http://forums.novell.com/member.php?userid=42999
View this thread: http://forums.novell.com/showthread.php?t=373886