JSP Weaver interprets the JSP markup on-the-fly instead of producing and compiling Java code. This reduces JSP reload times in development from tens of seconds to milliseconds. Typical JSP containers are optimized for production speed, not development productivity. In some containers reloading just a single JSP involves multiple recompilations totaling tens of seconds. Since this latency is same for small and big changes it gets annoying very quickly. Following the ZeroTurnaround goal of bringing Java EE development on par with that of Ruby and PHP we are proud to announce JSP Weaver — a JSP container that reloads JSPs instantly. Instead of translating JSPs to Java code and then compiling that JSP Weaver interprets the markup on-the-fly. This sacrifices some performance, which is not noticeable in development, but wins up to 50 times faster JSP reloading. JSP Weaver supports full JSP specification from 1.0 to 2.1, but does not support Java 5 language changes like generics and enums in scriptlets at the moment. Installing JSP Weaver is as easy as dropping a JAR into WEB-INF/lib and registering the servlet in web.xml. Download it from ZeroTurnaround and give it a try. Disclaimer: JSP Weaver is commercial software with a free trial for 14 days and developer seat cost at 49$.
- Posted by: Jevgeni Kabanov
- Posted on: November 06 2007 12:41 EST
Hi JSPWeaver guys, Thanks, Sounds nice and useful utility. But one issue. I deployed as per the instructions in Websphere. I got the following exception:- java.lang.RuntimeException: java.lang.NullPointerException at com.zeroturnaround.jspweaver.support.TldLocationsCache.(TldLocationsCache.java:192) Any clue to get it up? Thanks
Hi The product has not been tested with Websphere but it should work. Can you provide the full stacktrace via support at zeroturnaround dot com or http://www.zeroturnaround.com/forum/ ? Thanks, Toomas
HiAh....It "should" work....EE "portability" don't you love it? -- Bill Burke http://bill.burkecentral.com
The product has not been tested with Websphere but it should work. Can you provide the full stacktrace via support at zeroturnaround dot com or http://www.zeroturnaround.com/forum/ ?
J2EE applications are mostly portable. JSP engines are not. For example you can't take Jasper and use it in Websphere when the application relies on the Websphere classloading mechanism to find TLD files in other places besides the application context. The same goes for taking BEA's Javelin and trying to use it in Jetty, OC4J or Resin.