The best place for taglibs is the war itself, you should place your tablibs jar inside the war. The JSP classloader is enhance to find those inside the bundles libraries.
Actually the fragment Idea is not bad but that bundle isn't checked :-) I guess I might introduce that in the future maybe, but we still have an open issue for TLDs scanning for all bundles inside the container. Either way I know that JSPs and taglibs are not easy and believe me it's not easy to get the stuff working around it since there is always some classloader stuff to take care of :-) 2011/8/24 bitec <[email protected]>: > I think org.ops4j.pax.web.pax-web-jsp bundle is responsible for: > 1. expression language libraries (they are 2.1 and don't allow methodx > expressions) > 2. tag libraries. Though in this case I cannot understand, why JSF tag > libraries were loaded, but PF - not. > > I tried to use the PF bundle as the fragment to > org.ops4j.pax.web.pax-web-jsp, but this didn't help... > > Any thoughts? > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/JSF-and-apache-servicemix-4-4-0-fuse-00-43-problems-tp3277669p3280706.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- -- *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/>
