Thanks very much for taking the time to respond.
I have tried unchecking the Namespace Mangling option of the Resource Resolver
Factory. I have a few observations. Unfortunately it did not fix the problem.
Rendering of the link still was still rewritten removing the colon (:) and
surrounding
This really depends on what you mean by 'calling directly'
if you put a jsp file under the /apps directory. You are putting a file there.
You can access that file directly as a file. If you are looking at accessing
the functionality that the jsp provides, the servlet, you need to point to
This is the namespace mangling feature in the Sling Resource Resolver
Factory configuration:
Namespace Mangling
Defines whether namespace prefixes of resource names inside the path
(e.g. "jcr:" in "/home/path/jcr:content") are mangled or not. Mangling
means that any namespace prefix contained
Hi Jason,
Thanks for you reply.
By "calling directly" I mean to be processed as it was being called in a
web container. So the scriptlets and tags would be processed.
As I understood it correctly, I would need to have a servlet or component
that would be responsible for calling that JSP, right?
Hi all.
I’m having trouble with outbound links within AEM containing colons (:) within
the URL hash. The problem seems to stem from Sling URL mangling. I created a
Stackoverflow question with the details- see link below. I’m hoping folks on
the list can take a look and provide some
Hi,
Is there any way to call a JSP directly on Apache Sling?
I'd like to call a JSP that is deployed on Apache Sling.
Any tips are welcome.
Thanks
--
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
