469,572 Members | 1,206 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,572 developers. It's quick & easy.

EJPPC0005E: portlet.xml validation caught a SAXException on Websphere 6.1

Hi All,

I am trying to deploy one of the portal applications on websphere 6.1.
During the course of deployment, I get the following error:

EJPPC0005E: portlet.xml validation caught a SAXException. The Message
was: 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_1_0.xsd":supported-locale,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":resource-bundle,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":portlet-info}'
is expected.

The best part here is same application is deployed properly on 6.0, but
gives a SAXException when deployed on 6.1. The header of my portlet.xml
looks like this:

<?xml version="1.0"?>
<portlet-app
xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
id="hrapplication" version="1.0"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd">

Any help will be greatly appreciated.

Thanks All.

Nov 13 '06 #1
2 3841
ma***********@gmail.com wrote:
EJPPC0005E: portlet.xml validation caught a SAXException. The Message
was: 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_1_0.xsd":supported-locale,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":resource-bundle,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":portlet-info}'
is expected.
This is telling you that the schema is expecting one of three very
specific elements but that isn't what you provided. This is either an
error in your input document, or an error in your schema, or a bug in
the processor -- and without seeing the input doc we have no way of
telling you which.

I'd bet on the input doc being wrong and simply not having been detected
before -- perhaps a bug in 6.0 that was fixed in 6.1, or perhaps you've
stepped on this copy of the input.

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
Nov 13 '06 #2
Hi Joe,

Thanks a lot for your response.

I was able to fix the problem. The issue was, that the 6.1 parser
accepts the portlet.xml in well defined format. By which I mean, inside
the portlet tag the description should come first followed by name then
value etc..

bye.

Joe Kesselman wrote:
ma***********@gmail.com wrote:
EJPPC0005E: portlet.xml validation caught a SAXException. The Message
was: 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_1_0.xsd":supported-locale,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":resource-bundle,
"http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd":portlet-info}'
is expected.

This is telling you that the schema is expecting one of three very
specific elements but that isn't what you provided. This is either an
error in your input document, or an error in your schema, or a bug in
the processor -- and without seeing the input doc we have no way of
telling you which.

I'd bet on the input doc being wrong and simply not having been detected
before -- perhaps a bug in 6.0 that was fixed in 6.1, or perhaps you've
stepped on this copy of the input.

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
Nov 17 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by allerhed | last post: by
reply views Thread by Brian | last post: by
reply views Thread by motoman | last post: by
reply views Thread by Mario | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.