Community
Participate
Working Groups
Build Identifier: 7.5.2, 7.5.3, 7.5.4 jetty-all-server MANIFEST contains wrong import: org.apache.jasper;version="[7.5,8}" Reproducible: Always
This is a regression introduced when we upgraded to the latest jsp-impl-2.1 We ended up re-distributing ourselves the classes missing from jasper-glassfish build. We need to force BND to export the version 2.1 for those packages.
Ok fixing the version export is easy. but the problem remains. The problem is that the aggregate contains classes that should have been inside the jsp-impl jar itself: the glassfish build of jsp-impl does not contain the ECJ compiler and instead rely on the java-compiler JSR99 inside jdk6... which absolutely does not work in OSGi. To workaround the lack of JDK5 support Jan stuffed the missing classes in the jetty-jsp-21 bundle and made it an osgi fragment. We don't use it in the p2-osgi build. Instead we made sure that the orbit build does contain the classes that the glassfish build does not have. Unfortunately the jetty-all-server does contain jetty-jsp-2.1 which pretty much prevents it from working in OSGi: in OSGi, the jetty-jsp-2.1 needs to be a fragment to the jsp-impl bundle. It can't be part of jetty's aggregate bundle At this point I think we have 2 choices: - convince Jan to remove jetty-jsp-2.1 from the aggregate so that it has a chance to work in OSGi. - make a new aggregate specifically for OSGi. Jan, Dmytro; comments welcome.
Is it possible to make jetty-jsp-2.1 as a fragment for jetty-all-server to enable JSP support? in this case jetty-all-server bundle will not contain JSP functionality by default. If user wants to add JSP support he adds jetty-osgi-boot-jsp and jetty-jsp-2.1 bundles.
Dmytro, I've checked the most recent jetty-all-server manifest (jetty-7.6.2), and the org.apache.jasper import no longer exists. Can you confirm that this issue can be closed? thanks Jan
Hello Jan, I've tested with 7.6.2. It works. Dmytro (In reply to comment #4) > Dmytro, > > I've checked the most recent jetty-all-server manifest (jetty-7.6.2), and the > org.apache.jasper import no longer exists. > > Can you confirm that this issue can be closed? > > thanks > Jan
Fixed for 7.6.2/8.1.2