Comments on the schema/spec changes from last week

[Subbu Allamaraju <subbu@bea.com>]

1. My understanding of the use case brought up for state changes during 
markup/resource request was to let the consumer/producer allow state 
changes provided such a change does not require the producer to 
implicitly clone the portlet and return new portletContext.

But the schema changes now allow state changes to happen regardless of 
cloning. In the updated schema, the producer can return portletContext 
with markup/resource responses. What is the use case for this?

2. On pbia and handleEvents, portletStateChangeRequired flag is 
duplicated. Since RuntimeContext is always present, we don't 
portletStateChangeRequired elements in InteractionParams and EventParams.

3. On a related note, the position of the "events" element was changed 
in UpdateResponse. Any reason for this change?

Subbu
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.