•JSR168 has cloning as container functionality
•WSRP semantics may involve the entity in the clone
semantics
•The current clone-on-write semantics are an example for JSR168 where the portlet may be involved as the clone happens during the portlet invoking an operation on the container. The portlet would have to be prepared for the configuration record having been marked as read-only such
that the invocation throws an exception.
•JSR168 does not anticipate the configuration being
read-only.
•Also note that the container would have to manage an indirection for the configuration record in order to deal
with the case of cloning because a write
occurred. It has also been pointed out to the JSR
leads that a portlet may store a portion of
its persistent state somewhere other than the container managed properties and therefore a mechanism for it to be
involved in the cloning operation should be available.