OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [wsrp] [wsrp-wsia] [change request #240] Remove Interface.UnsupportedLocale fault

We don't require this fault to be thrown? All the fault says is that "the portlet does not support generating markup for the request locale". That could be taken to mean it is ok to generate markup (or a gif), even if the portlet can't localize to one of the requested locales, and not raise this fault. I would keep the fault but point out that it is optional (e.g. a contract would need to be in the right locale).
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 20 March 2003 13:05
To: wsrp@lists.oasis-open.org
Subject: [wsrp] [wsrp-wsia] [change request #240] Remove Interface.UnsupportedLocale fault

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.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]