You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@sling.apache.org by Markus Joschko <ma...@gmail.com> on 2011/02/24 14:50:46 UTC

Reuse of JcrNodeResource possible?

Hi,

we have to implement two slightly opposing sets of requirements:

1a) Create notification e-mails with links to resources
1b) Allow external systems to store references to resources and to
retrieve resource data through that reference at a later date

and

2) Moving resources within the tree based on business processes

By moving a resource, the path would naturally change, which would
render any e-mail URL or external reference useless. For this reason,
it would be desirable to be able to use the node's UUID or, in cases
where the node was created by an external system, an immutable
property of the node which contains an externally created Id. Any URL
or reference based on this information would therefore remain valid
regardless of where the node is in the tree.

Our proposed solution is to implement a new ResourceProvider, mounted
in the virtual tree (under /uuid for example), which would process
URLs such as /uuid/e07a566f-9099-4859-bcdb-aadf76275bf2.tidy.json and
invoke the javax.jcr.Session.getItem method with [<uuid>] (e.g.
[e07a566f-9099-4859-bcdb-aadf76275bf2]) as the argument.

This works and it is possible to retrieve a JCR node with this
implemention. However, it is not currently possible to reuse
JcrNodeResource, as this class is a package private class in a private
package (bundle: org.apache.sling.jcr.resource). We do not wish to
implement our own JcrNodeResource.

Would it be possible to make these classes (namely JcrItemResource,
JcrPropertyResource and JcrNodeResource) available to other bundles,
either directly or through a public factory class?

Thanks in advance

Re: Reuse of JcrNodeResource possible?

Posted by Julian Sedding <js...@gmail.com>.

Hi Markus

You might get what you want by delegating your requests to the
ResourceResolver. I.e. you look up your node by UUID (or using search)
via the JCR API. Then you retrieve Node's path and call
resolver.getResource() using this path. Here you have a
JcrNodeResource, which you can return directly. In case you need the
resource's getPath() method to return the originally requested path,
you can wrap it before returning.

I used a similar approach for implementing SLING-1778[0], so you may
get inspiration from the attached patch.

Regards
Julian

[0] https://issues.apache.org/jira/browse/SLING-1778

On Thu, Feb 24, 2011 at 7:18 PM, Alexander Klimetschek
<ak...@adobe.com> wrote:
> On 24.02.11 17:15, "Markus Joschko" <ma...@gmail.com> wrote:
>>would prefer direct POSTs instead of having to deal with a redirect.
>
> But you can easily have internal redirects. I think writing a separate
> resource resolver (et. al.) for that seems overkill.
>
> The servlet would look up the real resource depending on ID/UUID/etc., and
> do a request dispatch (aka sling:include) on the new resource. The actual
> request, incl. POST method, parameters, etc., can be passed through.
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> Developer // Adobe (Day) // Berlin - Basel
>
>
>
>
>

Re: Reuse of JcrNodeResource possible?

Posted by Alexander Klimetschek <ak...@adobe.com>.

On 24.02.11 17:15, "Markus Joschko" <ma...@gmail.com> wrote:
>would prefer direct POSTs instead of having to deal with a redirect.

But you can easily have internal redirects. I think writing a separate
resource resolver (et. al.) for that seems overkill.

The servlet would look up the real resource depending on ID/UUID/etc., and
do a request dispatch (aka sling:include) on the new resource. The actual
request, incl. POST method, parameters, etc., can be passed through.

Regards,
Alex

-- 
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel