Looks like someone else had same issue... surely this cant be true..
Websphere does not apply tag library directives defined in included JSP. Before I had a file taglibs.jsp which has definitions of all required tag libraries <%@ taglib uri="... " prefix="... " %> ... , and taglibs.jsp was included on all required pages at first line. <%@ include file="taglibs.jsp"%> It does not work for Websphere. It requires to define all tag library directives on all pages. It really reduces maintenance of application http://www.jroller.com/agrebnev/entry/resin_websphere_jetty_fails_jsp2 reddeagle9 wrote: > > Hi Guys, > > Strange problem!. i was developing my code on tomcat. everything working > great and have just moved my project over to deploy on Websphere 6. > > The framework of the project works fine. goes in and out of the db etc but > i am having huge problems on the jsp side of things. > > within my default.jsp (for sitemesh) <%@ include > file="/common/taglibs.jsp"%> seems to be having no effect. When i run the > application, none of the taglibs are working. but when i move the code > from taglibs into default.jsp some of them work. > > I am really banging my head on this one, can anyone shed any websphere > expertise on this.. > > All files, taglibs etc are there, its nothing as simple as that. The jsp > pages are compiling, i can see the .class files. > > > -- View this message in context: http://www.nabble.com/Taglibs-include-on-Websphere-6-tf4635432s2369.html#a13254947 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
