+1 regards, gerhard
http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2009/12/9 Werner Punz <[email protected]> > Hello everyone I just wanted to give a small report regarding > ext-scripting. > > The status looks very good, I am getting very close to a possible alpha > release, I have two big open things (and a handful of minor ones, like > dropping qdox and and class rewriting, and finally fixing the dreaded > windows issues) > > The one I am working now on is concurrency/aka multiuser handling, that is > being worked on currently, the other is JSF2 Groovy annotation support, that > will be the next task. > > After that bugfixing and then I will make a vote for an alpha release. > I will start to work on the documentation post alpha! > > So I am right in time to get it at least up to beta status for the JSF > days. > > Anyway here is what you will get for 1.0 > > Groovy Support: > JSF Artefacts, Bean reloading (also session and application beans), > JSF2 dynamic annotation support > > Java Support: > > JSP like dynamic recompilation and reloading für all JSF artefacts, > dynamic Bean reloading, also for session and application scoped beans. > > JSP like dynamic recompilation also for annotated JSF2 artefacts! > (most of you probably have seen my youtube video) > > > Currently all this works as a simple plugin to myfaces with a few > parameters in the web.xml and for now I could avoid any javaagents to be > set! > > I guess with all this we will be way ahead of what Mojarra currently can > deliver. > > Post 1.0: My plan is once the core is stable enough to integrate > as many scripting languages as possible. Currently we can support > pretty much every scripting language which can compile against the VM. > So possible candidates are Scala, JRuby and Jython. > > Also Kito asked me for portlet support, currently not supported, but this > one is also an important post 1.0 target to aim for. > > Theoretically it would be possible also to support the Java scripting API > but from what I have seen the API is very limiting. > > I dont think I will ever try to integrate it at least I dont have any plans > to do it for now, I also dont think it will be needed in the forseeable > future since more and more scripting languages seem to > target the VM directly with their compilers. > > > Werner > >
