JSP into JAR package support

The so-called business unit is the ability to put a variety of execution resources in the jar package to be placed according to the business sub-module.
General resources, configuration are not too large part, but for the JSP has a problem, this is due to the implementation of JSP mechanism.
Although it may have become more and more inappropriate to use JSP as an engine of presentation, as far as I was concerned, there is a need to consider support as a platform for the use of JSP in historical legacy projects.
People familiar with the JSP execution mechanism know that JSP is to be processed by the container into Java code, and then compiled to generate the class file, and then executed.
But consider a variety of implementation mechanisms, different containers on the solution is not the same, especially WebLogic and websp here, there is an interface to the implementation of the strong transfer of the class, resulting in the implementation of the package can not be achieved, resulting in technical problems can not be resolved, the scheme is shelved. In the one months of use, think twice about this problem, and finally suddenly the idea of an existing point, test it is successful--and then add detailed implementation plan.
The effect is now achieved:

• can support various containers such as tomcat,jetty,glassfish,weblogic,websphere.
• You do not need to hack the implementation class of the container.
• All kinds of JSP technology such as: FORWARD,REDIRECT,INCLUDE,JSTL, etc. are perfectly supported, that is, the JSP specification is fully supported.

Perfect integration with the tiny framework.
JSP files can be freely placed in the jar package, and from then on, the War project can no longer contain business content.

JSP into JAR package support