Maybe you did this and I missed it, but it would have been good to see the original clone of Jasper checked in first, and then your changes checked in over that. That way, we would all be able to see the baseline from which you started, not to mention be able to track back to Tomcat sources and port ongoing updates / bug fixes from over there.
-- Martin Cooper On Fri, Jul 31, 2009 at 11:18 AM, Musachy Barroso <musa...@gmail.com> wrote: > You might have noticed I just committed the code of Jasper compiler > under the sandox/struts2-jsp-plugin. I modified jasper (unable to > extend as most of the code is private) to read JSPs from the classpath > and compile them into java in memory (no intermediate file required), > and then I am using the java compiler API to compile the java code and > keep a cache of the generated servlets. > > The end result is that I can use JSPs from the classpath now. TLDs and > includes do not work currently, but they will soon, I hope. Then I > will make it work from an OSGi bundle. I know some people want to be > able to package JSPs in jars, so this might work out, eventually. > > musachy > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
