You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/11/18 00:14:43 UTC
[jira] Created: (SLING-106) microsling should use the sling
namespace just like Sling
microsling should use the sling namespace just like Sling
---------------------------------------------------------
Key: SLING-106
URL: https://issues.apache.org/jira/browse/SLING-106
Project: Sling
Issue Type: Bug
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: 2.0.0
Currently microsling uses no namespace for the resourceType property. This makes data used for microsling not portable to Sling as Sling uses the sling prefix for this property.
microsling should therefore be enhanced to also use the sling prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-106) microsling should use the sling
namespace just like Sling
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-106.
-----------------------------------
Resolution: Fixed
Fixed in Rev. 596022 to use the name sling:resourceType and also adapted the content creation form. The MicroslingResourceResolver constructor verifies and ensures the correct mapping of the sling namespace prefix to
http://sling.apache.org/jcr/sling/1.0.
> microsling should use the sling namespace just like Sling
> ---------------------------------------------------------
>
> Key: SLING-106
> URL: https://issues.apache.org/jira/browse/SLING-106
> Project: Sling
> Issue Type: Bug
> Components: microsling
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently microsling uses no namespace for the resourceType property. This makes data used for microsling not portable to Sling as Sling uses the sling prefix for this property.
> microsling should therefore be enhanced to also use the sling prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-106) microsling should use the sling
namespace just like Sling
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-106:
------------------------------------
Component/s: microsling
> microsling should use the sling namespace just like Sling
> ---------------------------------------------------------
>
> Key: SLING-106
> URL: https://issues.apache.org/jira/browse/SLING-106
> Project: Sling
> Issue Type: Bug
> Components: microsling
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently microsling uses no namespace for the resourceType property. This makes data used for microsling not portable to Sling as Sling uses the sling prefix for this property.
> microsling should therefore be enhanced to also use the sling prefix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.