I'd suggest you take a look around in [1] and more specifically [2]. Even so, I think you're not getting a direct answer because you "url is the same" requirement is not exactly in line with the fundamentals of sling. Specifically Sling is like a "RESTful" web service, and by definition if you want something different, then you use a different url. The focus is on content, so you have /content/stuff/myEntry, and if you want to view it on a normal browser you go to .../myEntry.html, if you want it for mobile, you go to myEntry.mobile, and if you want a summary, you go to myEntry.summary (plus using whatever url constructs). Saying that "the url can't change" pretty much breaks a lot of the power of sling and forces you to put "if...else if..." somewhere to process other inputs like get parmeters. Also check out [3] since I think it does a decent job of utilizing sling to do the job rather than writing custom code.
[1] http://sling.apache.org/site/the-sling-engine.html [2] http://sling.apache.org/site/dispatching-requests.html [3] http://sling.apache.org/site/46-line-blog.html -- View this message in context: http://apache-sling.73963.n3.nabble.com/Using-Filter-and-RequestDispatcher-to-substitute-responses-tp3918391p3919064.html Sent from the Sling - Users mailing list archive at Nabble.com.
