Re: [wsrp] [wsrp-wsia] [change request #240] Remove Interface.UnsupportedLocalefault

Title: 

I agree with Mike's proposal of removing it from the spec and letting
the producer/portlet to fallback to the most appropiate Locale
available or throw an OperationFailed fault.

Alejandro

Rich Thompson wrote:

 

  Document: Spec

Section: 6.2.1 +

Page/Line: 43/21

Requested by: Michael Freedman

Old text: Interface.UnsupportedLocale

New text: remove this exception

Reasoning: Do we really want the producer/portlet to throw this
explicit 

exception if it can't match the requested locale?  Wouldn't it be
better 

if portlets thought of the consumers list as preferred locales and 

merely returned the markup with whatever locale it decided to use?  The 

consumer could then decide what it wanted to do.  This fits a little 

better in the world where the portlet is implemented in Java as 

parts/much of the content may come from resource bundles which always 

resolve to a default whether the requested locale exists or not.  In
the 

end, if a portlet wants to merely abort the render and return an 

exception it can always use Interface.OperationFailed.  I.e. as the 

consumer has the portlet meta data that indicates what locales its 

supports it seems that those consumers that want to ban inappropriate 

locales can choose to do so be not calling the render method based on 

this information.  Right now, a consumer that wants content no matter 

what is forced to explicitly pass * as the last entry in its list.