Hi Dishara,
Excellent, well done. The ResourceResolver is quite picky about whats
in the Resource and is also sensitive to trailing / on paths. I expect
you now know a lot more about how it works... which will be a good
thing for the tasks to come.
Well done.
Ian
On 22 August 2013 04:25, Dishara W
Hi Ian,
Found it finally :-). You are quite right. I am missing the
resolutionPathInfo property to send back and hence going to a wrong
servlet. I set it to json and it gave me a json rendered page. Awesome !!.
On Thu, Aug 22, 2013 at 7:57 AM, Dishara Wijewardana <
ddwijeward...@gmail.com> wrote
Hi Ian,
I found the place which redirects and causing the loop in debugging. This
is for a similar request on
http://localhost:8080/content/cassandra/pnode1/cnode1.
The class is StreamRendererServlet. My request always falls inside the else
block that specified in BOLD and it redirects the respon
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 implementati
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 <
ddwijeward...@gmail.com> wrote:
> Hi,
> As per Ian
Hi,
If I do a log just inside the Provider.getResource method as following gets
printed. This seems a weird behavior
System.out.println("+Reource GET " + s);
+Reource GET /content/cassandra/pnode1/cnode1
+Reource GET /content/cassandra/pnode1/cnode1
+Reourc
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 follow
