[JBoss JIRA] Resolved: (JBPORTAL-821) Find out to properly bind property descriptions to schemas
by Chris Laprun (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-821?page=all ]
Chris Laprun resolved JBPORTAL-821.
-----------------------------------
Resolution: Partially Completed
This is fixed when using JBoss WS bundled with 4.0.5. Question is what do we do for 4.0.4?
> Find out to properly bind property descriptions to schemas
> ----------------------------------------------------------
>
> Key: JBPORTAL-821
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-821
> Project: JBoss Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Portal WSRP
> Affects Versions: 2.6 Final
> Reporter: Chris Laprun
> Assigned To: Chris Laprun
> Priority: Minor
> Fix For: 2.6.Alpha1
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> In RegistrationTestCase:
> PropertyDescription regProp = new PropertyDescription("regProp", new QName("ns1:LocalizedString"),
> new LocalizedString("en", null, "Registration Property"), null, null);
> The second parameter of the PropertyDescription constructor is a QName indicating the XSD type of the property. However, the namespace prefix must be bound to a URN somehow. Right now, we're using a hack: ns1:LocalizedString is used since it is a WSRP-defined type. We also use ns1 as the namespace prefix since this is the prefix assigned to the WSRP type namespace which allows the WS stack to find the type. However, this is obvious that this is not the correct way to do it and this will have to be addressed for 2.6.
--
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
17 years, 9 months
[JBoss JIRA] Updated: (JBPORTAL-857) Deal with non standard Locales better
by Chris Laprun (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ]
Chris Laprun updated JBPORTAL-857:
----------------------------------
Fix Version/s: 2.6.CR1
(was: 2.6.Alpha1)
Decision must be taken on this so that we can close this issue.
> 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.6.CR1
>
> 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
17 years, 9 months