You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Woonsan Ko (JIRA)" <je...@portals.apache.org> on 2009/09/09 09:35:57 UTC

[jira] Created: (JS2-1061) Option to to allow empty namespace uri in portlet descirptor

Option to to allow empty namespace uri in portlet descirptor
------------------------------------------------------------

                 Key: JS2-1061
                 URL: https://issues.apache.org/jira/browse/JS2-1061
             Project: Jetspeed 2
          Issue Type: Improvement
          Components: Deployment
    Affects Versions: 2.2.0
            Reporter: Woonsan Ko
            Assignee: Woonsan Ko
            Priority: Minor
             Fix For: 2.2.1


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 (uri:"", local:"portlet-app"). Expected elements are <{http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd}portlet-app>,<{http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd}portlet-app>

The portlet.xml is like the following:

<?xml version="1.0" encoding="UTF-8"?>
<portlet-app id="charttest" version="1.0">
<snip/>
</portlet-app>

It's because PortletAppDescriptorServiceImpl of pluto-2.0 used by Jetspeed-2.2 is using strong validation with JAXB. I think that's fair for pluto-2.0.
However, how about having another option to ignore this kind of validation errors in Jetspeed-2.2? I mean we can allow empty namespace for portlet 1.0 PAs. (Also, I think this option should be the default.) It will help using the existing Portlet 1.0 based PAs.

To do this, with the new (default) option, I think we need to override the PortletAppDescriptorService for JetspeedDescriptorService to allow empty namespaced portlet descriptors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


[jira] Resolved: (JS2-1061) Option to to allow empty namespace uri in portlet descirptor

Posted by "Woonsan Ko (JIRA)" <je...@portals.apache.org>.
     [ https://issues.apache.org/jira/browse/JS2-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko resolved JS2-1061.
-----------------------------

    Resolution: Fixed

This problem has been fixed by PLUTO-580. So, just upgrades the pluto dependency.

> Option to to allow empty namespace uri in portlet descirptor
> ------------------------------------------------------------
>
>                 Key: JS2-1061
>                 URL: https://issues.apache.org/jira/browse/JS2-1061
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Deployment
>    Affects Versions: 2.2.0
>            Reporter: Woonsan Ko
>            Assignee: Woonsan Ko
>            Priority: Minor
>             Fix For: 2.2.1
>
>
> 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 (uri:"", local:"portlet-app"). Expected elements are <{http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd}portlet-app>,<{http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd}portlet-app>
> The portlet.xml is like the following:
> <?xml version="1.0" encoding="UTF-8"?>
> <portlet-app id="charttest" version="1.0">
> <snip/>
> </portlet-app>
> It's because PortletAppDescriptorServiceImpl of pluto-2.0 used by Jetspeed-2.2 is using strong validation with JAXB. I think that's fair for pluto-2.0.
> However, how about having another option to ignore this kind of validation errors in Jetspeed-2.2? I mean we can allow empty namespace for portlet 1.0 PAs. (Also, I think this option should be the default.) It will help using the existing Portlet 1.0 based PAs.
> To do this, with the new (default) option, I think we need to override the PortletAppDescriptorService for JetspeedDescriptorService to allow empty namespaced portlet descriptors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org