Hello Achim, I am using the following PAX modules:
pax-confman-propsloader-0.2.2.jar pax-url-classpath-1.3.4.jar pax-url-war-1.3.4.jar pax-url-wrap-1.3.4.jar pax-web-extender-war-1.1.1.jar pax-web-extender-whiteboard-1.1.1.jar pax-web-jetty-bundle-1.1.1.jar pax-web-jsp-1.1.1.jar I found my problem :). There were two issues: - I needed to explicity add my jstl libs to the classpath in the manifest. I need to do this because it is a wab (not a plain war)? I guess I got confused by this line in the ops4j web page "Tag libs are searched within this war and it's containing jars". My bad. - To verify the JSPs generated, I was setting the org.ops4j.pax.web.jsp.scratch.dir to actually see the generated code and compare it to what tomcat produced. When I first fixed the classpath, stopped and restarted my equinox OSGi container, Pax Web was not regenerating the JSP java code (I eventually realized I had to go and explicitly delete it). Is that expected behaviour? If I clear the "org.ops4j.pax.web.jsp.scratch.dir" and retries (i.e. run once with bad classpath, then run with good classpath), then PAX Web apparently does regenerate the JSP code as my wab worked correctly with the correct classpath. Where does the generated JSP code go if "org.ops4j.pax.web.jsp.scratch.dir" is set to ""? Thanks very much again for your help. Gareth On Wed, Aug 24, 2011 at 8:08 AM, Achim Nierbeck <[email protected]> wrote: > Hi Gareth, > > which bundles of Pax web do you use? > > actually it should work that you place your taglibs inside your wab's > lib directory. > Those libs are scanned for taglibs at the start of the webcontext. > > Could you also take a look at the integration tests of pax web. > I think I did something similar there for the JSF (1.2) tests so > it should work. > > If it still doesn't work for you, don't hesitate to open an issue and please > add a nice description (or even better a sample) so I can build a test for it. > > regards, Achim > > > 2011/8/24 Gareth Collins <[email protected]>: >> Hello, >> >> I am in the process of migrating some wars to be wabs to run in Pax >> Web (1.1.1 running currently in equinox in Eclipse Indigo). >> >> I am starting to test and I am noticing that Pax Web is not executing >> the c:out tag correctly. e.g.: >> >> if token = "FRED" >> >> and the JSP is: >> >> <string><c:out value="${token}"/></string> >> >> tomcat at runtime (which uses jasper) is converting this to be: >> >> <string>FRED</string> >> >> whilst PAX Web at runtime (which also uses jasper) is converting this to: >> >> <string><c:out value="FRED" /></string> >> >> Any idea what could cause this? PAX Web provides the tag libraries, >> doesn't it? Even adding >> the tag libraries to the war in the WEB-INF/lib dir (as is done for >> tomcat), doesn't appear to change the behaviour. >> >> I am sure I am missing something obvious. Any help/suggestions would >> be greatly appreciated. >> >> thanks in advance, >> Gareth >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general >> > > > > -- > -- > *Achim Nierbeck* > > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > blog <http://notizblog.nierbeck.de/> > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
