Question: cloning localized preferences.

[Michael Freedman <Michael.Freedman@oracle.com>]

Internally, we have been discussing how we can extend the basic 
preference model we have defined to support entity preferences stored in 
the locale of the creator.  JSR 168 allows a developer to define 
[default] localized preference values. Its possible to conceive that a 
producer would want to use the appropriate localized version of these 
values when cloning the entity for the first time [say when the 
user/page developer places the portlet on a page].  Unfortunately, our 
clonePortlet call doesn't pass any information regarding either the 
users preferred locale or the consumer's preferred locale for the clone. 
 Hence, at the moment, this behavior seemingly can only be accomplished 
by an extension.  Unfortunately, extensions will diminish use -- 
particularly in the JSR environment as you don't know what wsrp/jsr 
container you may be talking to.   Is syncing up with this JSR 168 
capability something anyone else thinks we should address in 1.0 during 
the Public review -- or are folks fine on having the JSR 168 concept of 
default localized preference values be essentially meaningless in the 
remote case?
     -Mike-