Thanks for the reply. I was looking to find some time to investigate myself too. So far all I noticed by looking at the bundles, as Justin suggested me, is that org.apache.felix.http.bridge bundle is listed in JBoss while in Sling it's not listed, and org.apache.felix.http.jetty is listed in Sling, and it's not listed in JBoss.
Other than that, all the bundles are Active. Thanks, Dragos On Wed, May 9, 2012 at 8:25 AM, Felix Meschberger <[email protected]>wrote: > Hi > > Sorry for the delay. I can unfortunately confirm that JSPs don't work even > though ESPs (JavaScript) do work. Will have to further investigate what's > going on. > > Regards > Felix > > Am 07.05.2012 um 10:53 schrieb Dascalita Dragos: > > > Hi, > > > > Thanks to a patch on Apache Felix, committed by Felix Meschberger a few > > days ago( with the patch from David Jencks ) I was able to build Apache > > Sling launchpad with org.apache.felix.framework version > > 4.1.0-SNAPSHOTinstead of > > 3.0.8. > > With than, Apache Sling runs on JBoss 7.1.1. Kudos to everyone involved. > > Really cool to see this happening. > > > > Most of the things I've tried work fine in JBoss, except one thing, > Servlet > > Resolution. > > > > Having a resource X, with resourceType 'foo/bar' and a jsp located at ' > > apps/foo/bar/html.jsp', the request to > > sling-launchpad-7.0-SNAPSHOT/path/to/X.html is not getting resolved with > > the JSP, but with the org.apache.sling.servlets.get.DefaultGetServlet > > > > Do yo have any hints as to how to make this work, and if it's possible to > > do so in JBoss 7.1 ? > > > > Thanks, > > Dragos Dascalita Haut > >
