My scenario is that I've wrapped the ActiveMQ web console and added an OSGi
manifest. When I load this into Sling, I get the source codeof the jsp.
I added the Pax Web JSP bundle but was still unsuccessful. It did attempt to
compile the jsp but it has a problem using its own version of Jasper. The
problem is that Sling passes along an ELContextImpl that is not of the same
package as unmodified Jasper
("org.apache.sling.scripting.jsp.jasper.el.ELContextImpl cannot be cast to
org.apache.jasper.el.ELContextImpl").
I changed up my bundle to import more from the Sling JSP bundle but ran into an
issue of finding a config file in a sitemesh jar of my bundle. Also, the Sling
JSP bundle doesn't export jasper.
I can deploy this with JCR data to setup resource types but would I need to do
that for every JSP in the ActiveMQ web console? WOuld it be possible to setup
a Servlet to compile *.jsp resources?
----- "Bertrand Delacretaz" <[email protected]> wrote:
> Hi,
>
> On Tue, Oct 20, 2009 at 1:34 PM, <[email protected]> wrote:
> > I have managed to get the ActiveMQ web console wedged into
> OSGi/Sling but can't get the JSPs to compile. When I access index.jsp
> of the webapp, I get back the source to the page. Is there something
> I need to enable to get this to work?
>
> What's the exact failure scenario?
>
> Accessing a jsp page directly from Sling returns the JSP source code,
> by design. To execute the JSP, you need a resource type that points
> to
> it. Or use the FAQ trick at
> http://cwiki.apache.org/SLING/faq.html#FAQ-Howtoexecutescriptsdirectly%253F
>
> -Bertrand
