Werner Punz schrieb: > Jan-Kees van Andel schrieb: >> Can't wait to finish my Bean Validation stuff and try the Groovy example. >> >> I think Grant is right and it is indeed a very good thing for MyFaces >> to have Goovy support. >> Yes indeed, while I personally think it is not suitable for big systems due to Groovys speed problems, it definitely is heavens sent if you want to program something small, or if you want to script parts of your application, it really helps to be able not to restart the server for every change.
The beauty of groovy more than other scripting languages is that it delivers its own classloader therefore blends itself perfectly into java. From what I have seen the other scripting languages either just use JSR 233 or in case of jruby just can deliver objects, but not classes you can instantiate (I have to do some testing to confirm that) So in the end with good groovy bindings you can get seamless scripting integration on the groovy side and you can blend it with java both ways (calling java from groovy and calling groovy objects and classes from java) >> Thanks for making the time! >> > Thanks a lot as I said i am not fully there yet, the code needs > some overhaul which I will do the next weeks. > > A lot of code will be dropped soon, because the original classloader > stuff is not needed anymore. > > So if you look into the code, it still is somewhat dirty and rough > around the edges, my bigger priority was to get the codebase in a > working condition into the repo, and then move on from then. > Ok I did the code dump, now the code is clearer again. I had checked in while I was in the middle of a refactoring process, which basically was done to eliminate the custom classloader. So there was a load of legacy code which now is removed and replaced by the new plugin infrastructure added to myfaces 1.2 (Which is still not finished yet it is just for now hacked in to enable the bindings)
