Hey, folks!
I just committed the auto-compiling javaflow into trunk.
Since it's quite a big change I thought I go for trunk
first. (although it was initially developed with/for 2.1)
I changed the default Servlet to the ParanoidServlet
inside the web.xml. Feel free to change that ...but
I thought it might be better for people who want to
give it a quick try.
Due to the big change the GroovyFlow in scratchpad
had to go. But it should be quite easy to re-add this
through a jci compiler implementation. Sorry, I did
not have the time to do that yet.
Both javaflow and jci are now external maven projects.
If it's ok for the folks at jakarta both projects will
find their home inside the jakarta sandbox. (At least
that's what we agreed on at the ApacheCon). For now I
added the source distribution to our repo as well.
I've put them into the javaflow block as zip-archives.
Does anyone know ...do I just propose the projects
for the sandbox? AFAIU every apache committer can
get commit access. What's the process for that?
Or do I need some jakarta committer to sponsor the
projects?
There is quite a TODO list for all three projects,
jci, javaflow and the cocoon integration. (still need
to write down some of that) So if anyone would like to
help out - that would be great.
It's important that this does not end up in a one man
show. That being said: javaflow is no black magic!
there are quite some things to improve even without
touching the byte code rewriting. IMO the general flow
(also javascript) integration also needs some polishing.
There are some areas we could benefit from those two
projects. Some potentially usecases:
* auto-compilation of components
* simplification of the XSP infrastructure
I promise to do the TODOs ASAP but currently I am
awfully busy.
Glad I finally made it to commit the stuff :o)
Enjoy!
cheers
--
Torsten
PS: For those who tried it: yeah - I know ...the logging
is the first thing on the TODO list ;-)
