I have a Java EE application that takes XML and implements XSLT to generate HTML. This process is done in a custom service, it is usually used to create part of the content on some web pages. Since the actual data is already stored in XML, it was understandable to just change the servlet.
It is actually made up how this report prepares the servlet HTML by lifting the cost of change in the servlet every time. The DOM representing the XSL file is also cached in memory .
Currently XSLT has been deployed inside the war file. We want to support a default XSLT deployed in the WAR file, but there is also the ability to update XSLT only without reapplying the entire app. I am hoping that some people may have some good ideas to solve this kind of problem.
Update
I get the comment (comment) I know some servers are doing this way but I'm hoping to solve it in more normal way . I need to make sure that I am able to keep the following features ...
- Once a new XSLT is found, then cache XSLT (unless newer version Found)
- Keep cached versions of HTML generated when updating them when there is a new XSLT. Instead of putting XSLT inside the war file, I have a configuration outside of my war.
Comments
Post a Comment