This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
You could leave out the <html:html> tag. You're not using it for any functionality, so why waste the processing time?
A good workman is known by his tools.
Joined: Mar 16, 2004
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???