This is the idea relative to why userContext is passed to a variety of
operations ... while it does not impact the state (either runtime or
persistent) of the entity, it may impact the accessibility of that state
(both read and write) regardless of whether the state is opaque or
transparent to the Consumer.
"Tamari, Yossi"
<yossi.tamari@sap To:
.com> cc:
Subject: RE: [wsrp-wsia] [I#99] Interface Issue: Entity property
09/24/2002 10:20 customiza tion and user context
AM
I think the idea behind passing the user context is that the properties the
user is allowed to see/change depends on his role. There is only one set of
properties, but the permissions on them are dependent on the use context.
Yossi.
-----Original Message-----
From: Gil Tayar [mailto:]
Sent: Monday, September 23, 2002 7:17 AM
To:
Subject: [wsrp-wsia] [I#99] Interface Issue: Entity property
customization and user co ntext
Topic: interface
Class: Minor Technical
Title: Entity property customization and user context
Document Section: 7 Published State Interfaces
Description:
The current signature of setProperties and getPropeties takes a usercontext
as an argument implying that the properties returned by an entity may be
dependent on the user. This in turn implies that an entity is potentially
maintaining multiple property models, one per user. Such a concept seems to
conflict with the notion that an entity exposes a single set of persistent
properties for configuration.
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
