> but theYou have different pros and cons about both implementations. Some users do not want to use javascrpt because of it's interpreted nature and some political issues (you cannot make your work closed source if you want to sell it).
Java needs to be compiled, the container restarted for each change,
Not if we integrate the CompilingClassloader as it is on the TODO list. But we need that eclipse license issue solved first!
development cycle could shorten when using an advanced java ide (like eclipse) - so you do not make such great number if stupid typos you cannot predict. It could be faster than javascript and more attractive to commercial vendors.
Even though commercial issues are the last thing that matters here on this list it is something that should not be forgotten as if the commerce gets interest in cocoon it could provide additional resources for the project.
Who knows :)
cheers -- Torsten
