You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "christian (JIRA)" <ji...@apache.org> on 2007/10/15 14:09:51 UTC
[jira] Created: (SLING-48) wrong content classname in componen-nt
definition
wrong content classname in componen-nt definition
-------------------------------------------------
Key: SLING-48
URL: https://issues.apache.org/jira/browse/SLING-48
Project: Sling
Issue Type: Bug
Components: Core
Reporter: christian
Priority: Trivial
The cnd containes an inexisting class name in its contentClassNames default-value.
Have a patch fixing it attached.
But, would suggest to remove it, as it mandates any sub-class to write the property if it wants to use a different content class(-name).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-48) wrong content classname in componen-nt
definition
Posted by "christian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
christian updated SLING-48:
---------------------------
Attachment: sling-core-component-nt.patch
patch containing a suggested fix
> wrong content classname in componen-nt definition
> -------------------------------------------------
>
> Key: SLING-48
> URL: https://issues.apache.org/jira/browse/SLING-48
> Project: Sling
> Issue Type: Bug
> Components: Core
> Reporter: christian
> Priority: Trivial
> Attachments: sling-core-component-nt.patch
>
>
> The cnd containes an inexisting class name in its contentClassNames default-value.
> Have a patch fixing it attached.
> But, would suggest to remove it, as it mandates any sub-class to write the property if it wants to use a different content class(-name).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-48) wrong content classname in componen-nt
definition
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534848 ]
Felix Meschberger commented on SLING-48:
----------------------------------------
Thanks for reporting.
We are currently investigating a major modification of the API which would involve dropping the Component interface. In this case then this issue would not be relevant anymore.
We will reconsider as soon as the API discussion has been settled.
> wrong content classname in componen-nt definition
> -------------------------------------------------
>
> Key: SLING-48
> URL: https://issues.apache.org/jira/browse/SLING-48
> Project: Sling
> Issue Type: Bug
> Components: Core
> Reporter: christian
> Priority: Trivial
> Attachments: sling-core-component-nt.patch
>
>
> The cnd containes an inexisting class name in its contentClassNames default-value.
> Have a patch fixing it attached.
> But, would suggest to remove it, as it mandates any sub-class to write the property if it wants to use a different content class(-name).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-48) wrong content classname in componen-nt
definition
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-48.
----------------------------------
Resolution: Won't Fix
Issue pertains to former Component API and has no correspondence with the new Sling API. Closing.
> wrong content classname in componen-nt definition
> -------------------------------------------------
>
> Key: SLING-48
> URL: https://issues.apache.org/jira/browse/SLING-48
> Project: Sling
> Issue Type: Bug
> Components: Core
> Reporter: christian
> Priority: Trivial
> Attachments: sling-core-component-nt.patch
>
>
> The cnd containes an inexisting class name in its contentClassNames default-value.
> Have a patch fixing it attached.
> But, would suggest to remove it, as it mandates any sub-class to write the property if it wants to use a different content class(-name).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.