Hi, IIRC the behaviour where the resource resolver iterates up the tree is normal resource resolver behaviour but the recursion is not. Neither is the integration test failure.
The resource resolver may be looking for the sling:resourceSuperType, but that is just a hunch. Either, the implementation of the ResourceProvider wiring inside the ResourceResolver is buggy, or the Properties of the resource you are sending back are incorrect, which is triggering the behaviour. I would suggest you look carefully at what a standard JcrResource looks like when you make a simular request. Its listed at [1]. Ian 1 http://localhost:8080/system/console/recentRequests On 21 August 2013 08:59, Dishara Wijewardana <[email protected]> wrote: > Hi > Since I am doing something similar to PlanetResource, I ran the integration > test of PlanetResource to verify it works in trunk. But that also got > failed and started a thread on that also. > > > On Wed, Aug 21, 2013 at 8:50 AM, Dishara Wijewardana < > [email protected]> wrote: > >> Hi, >> As per Ian's request I tried calling a resource URL ends with .json to get >> a json rendered page. >> There I just noticed that, the response I am getting was which I claimed >> earlier a blank page, is not actually a blank page. Sorry for the >> inconvenience. >> >> In the browser there is a message as follows. So then I debug it again. I >> put a debug pointer only inside CassandraProvider.getResource(), and >> observed that it is getting hit continuously. I also noticed that if I hit >> for http://localhost:8080/content/cassandra/pnode1/cnode1 , >> it continuously calls CassandraProvider.getResource with following paths >> over and over again. Appreciate any input on this ? Why the request is >> getting looped ? Because in the code I see no reason to call getResource in >> a loop. >> >> - /content/cassandra/pnode1/cnode1 >> - /content/cassandra/pnode1 >> - /content/cassandra >> >> This webpage has a redirect loop >> The webpage at *http://localhost:8080/cassandra/pnode1/cnode1/* has >> resulted in too many redirects. Clearing your cookies for this site or >> allowing third-party cookies may fix the problem. If not, it is possibly a >> server configuration issue and not a problem with your computer. >> >> -- >> Thanks >> /Dishara >> > > > > -- > Thanks > /Dishara
