def host = new Ghost(“barman.byte-code.com“)
def result = host.ls()
println result

think about it carefully… do you think it’s possible in less then 10?
Let’s pull out a groovy solution!

The server:

1:import groovy.net.xmlrpc.*
2:import java.net.ServerSocket
3:
4:def server = new XMLRPCServer()
5:def socket = new ServerSocket(8080)
6:
7:server.executeShell = { commandArray ->
8: def p = commandArray.execute()
9: p.waitFor()
10: p.text
11:}
12:
13:server.startServer(socket)

And the client:

1:import groovy.net.xmlrpc.*
2:
3:class Ghost{
4:
5: def hostProxy
6:
7: Ghost(host){
8: hostProxy = new XMLRPCServerProxy(“http://${host}:8080“)
9: }
10:
11: def callCommand(methodName,params){
12: def commandArray = []
13: commandArray << methodName
14: params.each{ commandArray << it }
15: hostProxy.executeShell(commandArray)
16: }
17:
18: def methodMissing(String name , args){
19: callCommand name,args
20: }
21:
22:}

I’m just amazed… this is what I call next generation devlopemt: based on solid foundation of good java libs and move foward on top them.
I don’t think this a full “production-ready” implementation but..it works!
and they’re less the 10 line of code if you remove the “bloat”… half an hour work, a fullblown coffe break application!

Repeat… less then 10 line of code!

Happy groovin’ , keep DRY and write less code that do more;)

after the sunny Florida I drove up all the Interstate 95 and I reached Reston VA to attend to 2GX Groovy and Grails Experience!

It was absolutely great!

First I would like to compliments Jay and the NFJS team , because the organization was absolutely wonderful and professional, we arrived and find all that we need to enjoy the show(schedules, slides and so on…). I never attended to a NFJS event , because I’m european , but from now on I will be very happy if NFJS tours will reach the other side of the atlantic;)

All session I’ve attended showed up with great contents and interesting topics, from metaprogramming to ui mashup and testing… really good works folks!

I really believe that  we’ve found the in Groovy the new Java 2.0 ,as said many times during the conference, with the ability to reuse all the good stuff that the Java World has created(and there’s a lot of good stuff out there!) and in Grails a easy path to web application development. It was a long time that I felt so positive about a new technology… and that’s great! Moreover the community is growing fast and steady , and the community is THE base for any successful opensource project (maybe someone has forgot that…).

I will advise everyone that as the opportunity to not miss the next 2GX in San Jose coming in October…

so, when in Europe , or better in some beautiful place in Italy?

today Grails 1.0 was released, as usual I prepared the package for rpm-based systems.

Get it here , and congratulations to all the Grails&Groovy community.

Davide

given some requests I publish a classresolver for Wicket that enable groovy pages & components to be hot reloaded in development mode.
I suppose you have a project with maven and so let’s start…

1. Get the “mighty” GrovvyClassResolver
2. (fix up the package)
3. Open the WebApplication class and do something like that (remember that I use maven & jetty for dev, If u have a different project structure change the path of the BASE_SRC constant pointing to your source dirs)

   1. 
      
      /**
      
       *
      
       * @author Byte-Code Srl 2004-2007
      
       */
      
      public class GroovierWebApplication extends WebApplication {
      
      
      
          public static final String BASE_SRC = "src/main/java/";
      
      
      
      
      
          protected void init() {
      
              initSpringContext();
      
      
      
      
      
              getResourceSettings().setThrowExceptionOnMissingResource(false);
      
      
      
              String configurationType = getConfigurationType();
      
              if (configurationType.equals(DEVELOPMENT)) {
      
                  getResourceSettings().addResourceFolder(BASE_SRC);
      
      
      
                  getApplicationSettings().setClassResolver(new GroovyClassResolver(BASE_SRC));
      
              }
      
          } }

4. You’re done! Now you can develop in wicekt using groovy & hot reload pages and components.
5. As a side note remember to create a production profile so when you deploy the war the groovy class are compiled and you won’t loose any performances!
6. Ok, now you have to transfer some bucks to my account… or it won’t work!

Ok, that’s all folks, if u have problem just drop me an email!

D

I’m looking forward to give you a live coverage of the events form the states, so stay tuned between 10 & 24 feb !

Take it Grails-1.0-RC4