Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

struts tags on tomcat server  RSS feed

 
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On my WSAD development environment the jsp page works. However when my error page was moved to production it started telling me

org.apache.jasper.JasperException: /jsp/LoginError.jsp(27,0) Unterminated <html:html> tag



I have struts.jar in the lib directory of my web app. Are there any tomcat configuration parameters that can disable the execution of taglibs???


 
pie sneak
Sheriff
Posts: 4727
Mac Ruby VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You could leave out the <html:html> tag. You're not using it for any functionality, so why waste the processing time?
 
peter cooke
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
as a short term work around we did go simply with <html>

However this indicates there could be a bigger problem.
This is the first evolutionary prototype to be displayed on a demo production basis. The JSP's currently all embed lots of scriptlets(until functional requirements stabalize). The next version was supposed to take all that scriptleting and convert it to custom tag libraries.


It appears to me that all tag library work will now fail. If I cannot get the tag library infrastructure will not work as is supposed to. I would then be forced to handle all jsp content presentation maintenace for every jsp page. I would much prefer tag libaries, and to train my HTML content providers on how to use JSTL and the STRUTS tags, and let them modify the JSP pages.


I may be tooo naive in the world of programming. But I thought one of the goals of JSP's converting scriptlets to custom tags was to have html content providers maintain JSP pages instead of java developers.
Am I wrong???
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!