Hi, >One way to experiment with this is to create a script that prints out >various request values (path, selectors, suffix, etc), and see how it >behaves when using the various sling:include attributes. Or debug the >source code, of course, which is the most precise way of finding >things out.
How can I debug the source code. Usually I look at the mvn output when there is an error and try to find the reason. janandith On Fri, Aug 8, 2008 at 7:54 PM, Bertrand Delacretaz <[EMAIL PROTECTED]>wrote: > Hi, > > On Tue, Aug 5, 2008 at 6:59 AM, janandith jayawardena > <[EMAIL PROTECTED]> wrote: > > ...When using replaceSuffix inside sling include tag like <sling::include > > replaceSuffix=test.pdf /> > > > > will it replace > > > > <a href="/content/mynode/file.bin/My Report.pdf">report</a> > > > > with "/content/mynode/file.bin/test.pdf" > > > > so I can use test.pdf file instead of My Report.pdf automatically.... > > No, replaceSuffix will not change anything to an href attribute. > > in <sling:include>, replaceSuffix replaces the suffix of the > *included* request, so that if you're currently processing a request > that has a /foo suffix and you use <sling:include > replaceSuffix="/bar"/>, the request that's executed by sling:include > will have /bar as its suffix instead of /foo. > > One way to experiment with this is to create a script that prints out > various request values (path, selectors, suffix, etc), and see how it > behaves when using the various sling:include attributes. Or debug the > source code, of course, which is the most precise way of finding > things out. > > -Bertrand >
