Portable should be ok m.n. to m.n+1 , but m+1 may be problematic. Tomcat to Jetty is not so much a problem, unless you get a m to m+1 issue at the same time.
Precompiling is a good thing, just that it is fragile. Some have argued that when we precompile, we should bundle the entire JSP engine into the WAR to avoid such issues. This might be a good idea, but not yet acted on. cheers On 21 September 2016 at 16:31, Marcel Stör <[email protected]> wrote: > On 21.09.16 01:13, Greg Wilkins wrote: > >> precompiled JSPs are highly dependent on the precise JSP impl used, so >> they are not going to be very portable. >> > > Do mean "portable" in the sense of porting an app from e.g. Tomcat to > Jetty or more in the sense of porting from Tomcat m.n. to m.n+1 or m+1? Or > do you generally feel that precompiling be a bad thing? > > > -- > Marcel Stör, http://frightanic.com > Couchsurfing: http://www.couchsurfing.com/people/marcelstoer > O< ascii ribbon campaign - stop html mail - http://j.mp/1OThh9L > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
