You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2008/03/06 03:22:58 UTC

[jira] Assigned: (PLUTO-473) XML Schema Location for pluto-portal-driver-config.xsd points to obsolete schema definition

     [ https://issues.apache.org/jira/browse/PLUTO-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliot Metsger reassigned PLUTO-473:
------------------------------------

    Assignee: Elliot Metsger

> XML Schema Location for pluto-portal-driver-config.xsd points to obsolete schema definition
> -------------------------------------------------------------------------------------------
>
>                 Key: PLUTO-473
>                 URL: https://issues.apache.org/jira/browse/PLUTO-473
>             Project: Pluto
>          Issue Type: Bug
>          Components: portal driver
>    Affects Versions: 2.0.0, 1.1.4, 1.1.5
>            Reporter: Benjamin Gould
>            Assignee: Elliot Metsger
>             Fix For: 2.0.0, 1.1.5
>
>
> In http://svn.apache.org/repos/asf/portals/pluto/trunk/pluto-portal/src/main/resources/pluto-portal-driver-config.xml, the schema location is:
> xsi:schemaLocation="http://portals.apache.org/pluto/xsd/pluto-portal-driver-config.xsd
>                         http://portals.apache.org/pluto/xsd/pluto-portal-driver-config.xsd"
> The file at that URL is not correct schema definition.  The correct schema definition for this version of the config exists in SVN at: 
> http://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.4/pluto-portal-driver/src/main/resources/pluto-portal-driver-config.xsd, or
> http://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.1.x/pluto-portal-driver/src/main/resources/pluto-portal-driver-config.xsd
> (The one in trunk is not correct)
> I'm not sure what the fix is... I guess the newer definition should be given a unique URI and the configuration files in 1.1.x and trunk should be updated in order to maintain backwards compatibility?
> Hopefully we can get this fixed in time for 1.1.5

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