5:54 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-1730?page=com.atlassian.jira.pl...
]
Antoine Herzog updated GTNPORTAL-1730:
--------------------------------------
Description:
In many of the samples, such as jsfhellouser, the portlet.xml, that have the
<init-param> element, cannot validate against the schema :
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd.
In eclipse, you can see it directly with a validation error.
The error message is :
cvc-complex-type.2.4.a: Invalid content was found starting with element
'init-param'. One of
'{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":portlet-preferences,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}'
is expected.
The turnaround is simple : move the <init-param> element(s) after the
<portlet-class> element, and before the <supports> element.
Simple, but it would be more clean if the file can directly be validated.
was:
In many of the samples, such as jsfhellouser, the portlet.xml, that have the
<init-param> element, cannot validate against the schema :
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd.
In eclipse, you can see it directly with a validation error.
The error message is :
cvc-complex-type.2.4.a: Invalid content was found starting with element
'init-param'. One of
'{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":portlet-preferences,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}'
is expected.
The turnaround is simple : move the <init-param> element(s) after the
<portlet-class> element, and before the <supports> element.
Simple, but it would be more clean if the file directly with that.
samples portlet.xml : cannot validate against portlet-app_2_0.xsd -
element init-param at wrong place.
------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1730
URL: https://issues.jboss.org/browse/GTNPORTAL-1730
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation, QA
Affects Versions: 3.1.0-GA
Reporter: Antoine Herzog
Assignee: Luc Texier
Priority: Trivial
In many of the samples, such as jsfhellouser, the portlet.xml, that have the
<init-param> element, cannot validate against the schema :
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd.
In eclipse, you can see it directly with a validation error.
The error message is :
cvc-complex-type.2.4.a: Invalid content was found starting with element
'init-param'. One of
'{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":portlet-preferences,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter,
"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}'
is expected.
The turnaround is simple : move the <init-param> element(s) after the
<portlet-class> element, and before the <supports> element.
Simple, but it would be more clean if the file can directly be validated.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira