[
http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ]
Chris Laprun updated JBPORTAL-857:
----------------------------------
Fix Version/s: 2.6.6 Final
2.7 Final
(was: 2.8 Final)
Assignee: Chris Laprun (was: Julien Viet)
The description is slightly wrong... I will extend WSRP strict mode support to language
validation so that we can accept wrongly formatted language codes (en_US instead of en-US
for example).
Deal with non standard Locales better
-------------------------------------
Key: JBPORTAL-857
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-857
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal WSRP
Affects Versions: 2.4 Final
Reporter: Chris Laprun
Assigned To: Chris Laprun
Priority: Minor
Fix For: 2.7 Final, 2.6.6 Final
Original Estimate: 3 hours
Remaining Estimate: 3 hours
Per the WSRP Spec regarding UnsupportedLocale fault:
The Portlet does not support generating markup for the requested locale. Since the
Portlet is not required to generate markup in the requested locale, a Portlet returning
this fault message is indicating that it processes locales in a stricter manner and has no
markup for the requested locales. The Consumer can treat this as a specialization of the
OperationFailed fault message and does not have to retry getting the markup in other
locales.
Currently, LocaleInfo throws an IllegalArgumentException if the locale is not standard
which gets wrapped into an OperationFailedFault at the handler level. We should deal with
locale errors better and maybe be more lenient as to what we accept.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira