Scripting RAD tools such as Ruby on Rails and Grails can be really slow?

Tiago Fernandez in his blog reported some results about benchmarks using Java, JRuby, Groovy and Scala. I know: we can talk about benchmarks for days but in the Internet there are a lot of them and the performance problems of the scripting language is not a news.

Results show that Groovy is very slow in comparison to the pure Java and the Scala scripting language. This could be a serious reason to be worried when your application created with Grails or RoR goes in production...

So, why don't you use a real Java RAD tool like Roma Meta Framework? :-)

You can develop shortly without using a scripting language with the benefits of great refactoring support (Eclipse, Netbeans and IntelliJ are master on it) and performance and scalability!

The source: http://tiagofernandez.blogspot.com/2009/05/java-integration-with-groovy-jruby-and.html

Romulus at the Internet of Services 2009 conference

On June, 10th 2009 I will be in Brussels to present the Romulus demo at the "Internet of Services 2009" conference. Romulus project is scheduled in the afternoon. Below the agenda.

Group 2: June 10, 13:30 - 17:30

• Semantically enhanced SLA Negotiation (BREIN)
• Automated Service Level Agreement Management Framework - Adhoc Demonstrator (SLA@SOI)
• TEAM: Knowledge management in distributed software communities by applying semantic technologies (TEAM)
• Decentralized transactional collaborative drawing (SELFMAN)
• Romulus: your answer to improving productivity in Java Web Applications (ROMULUS)
• Edutain@Grid: A Service-Oriented Infrastructure for Future Real-Time Interactive Internet Applications (edutain@grid)

Luca in the first page of Google searching for "Java JSR"

Today Mara told me that searching "Java JSR" in Google (at least in the Italian version), in the first page compares my face and this blog... I've tried and is real! What nice thing :-)

Transparent DataNucleus enhancement at run-time

Today it has worked! In the last days I was working to avoid the enhancement phase in the building of Roma Framework projects. Yes. Until yesterday you needed to invoke the "persistence-compile" task in your Roma project and all the projects that contained persistent classes.

Furthermore pre-packaged modules such as ADMIN, USERS, MESSAGING and SCHEDULER-QUARTZ needed to self-execute the enhancement in order to put persistence capable classes inside the JAR. This was a mess if you needed to change the ORM binding since anything resided inside the JAR.

I have to check yet if run-time changes to the entity POJOs are auto-enhanced at the fly... If works the productivity would be speedup over and over again.

Thanks to Andy Jefferson of DataNucleus team in supporting my crazy requestes :-) The work tomorrow will be in changing all the wizards to support the new configuration. In few words the change consist in:

1. Let to the PersistenceAspect to invoke the Enhancer at startup
2. Create the file persistence.xml inside the src/META-INF folder.
   

Once everything works I'll commit in to the SVN trunk for the upcoming release 2.0.