Hi Woonsan,
+1
But be aware that because of the XSD validation currently applied the Pluto based loading of the portlet.xml might assume certain structures
to be already ensured, e.g. required elements to be available. As result the internal "error" handling might not be as good as expected whe
On Sep 2, 2009, at 9:37 AM, Woonsan Ko wrote:
Hi there,
During testing RPAD with some useful PAs from jp.sf.pal repository,
I found that the current deployment component failed to deploy a PA
because the descriptor of the PA does not have any namespace uri
definition with the following e
+1
Randy
Woonsan Ko wrote:
Hi there,
During testing RPAD with some useful PAs from jp.sf.pal repository, I found
that the current deployment component failed to deploy a PA because the
descriptor of the PA does not have any namespace uri definition with the
following exceptions:
java.io.IO
Hi there,
During testing RPAD with some useful PAs from jp.sf.pal repository, I found
that the current deployment component failed to deploy a PA because the
descriptor of the PA does not have any namespace uri definition with the
following exceptions:
java.io.IOException: unexpected element (
[
https://issues.apache.org/jira/browse/JS2-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko resolved JS2-1058.
-
Resolution: Fixed
Write JS_PORTLET_HEAD_ELEMENTS only when any head element is contributed.
I have just app
Author: woonsan
Date: Wed Sep 2 09:59:36 2009
New Revision: 810442
URL: http://svn.apache.org/viewvc?rev=810442&view=rev
Log:
JS2-1058: Write JS_PORTLET_HEAD_ELEMENTS only when any head element is
contributed.
Just applied the suggestion by Lance Zhang. Thank you so much!
Modified:
portals
