[jira] Closed: (SLING-133) microsling Resource resolver and default renderers do not support Properties

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger closed SLING-133.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0
         Assignee: Bertrand Delacretaz

This issue is fixed.

> microsling Resource resolver and default renderers do not support Properties
> ----------------------------------------------------------------------------
>
>                 Key: SLING-133
>                 URL: https://issues.apache.org/jira/browse/SLING-133
>             Project: Sling
>          Issue Type: Improvement
>          Components: microsling
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Currently, assuming the /content/testing/foo Node exists and has a "text" property, requesting /content/testing/foo/text.txt (or any other extension) fails with a ClassCastException, as the resolution and rendering chain supports Nodes only.
> It should be fairly easy to use a JcrPropertyResource when the MicroslingResourceResolver finds an Item that is a Property, and let the default renderers handle it.
> One use case, is, when working with client-side forms, to fill a <textarea>, for example, with the value of a property, based on a relative URL.
> I don't think we need to handle POSTs to Properties for now, but GETs are useful in the above case, and for testing as well.

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