NetBeans Google App Engine Plugin - Changing Deployment Settings

The current Google App Engine plugin for NetBeans does not have a UI interface to change the username and password that it has saved. It also does not display its properties in Preferences tab. The only way to change the stored username and password is to modify the deployment.properties file located in .netbeans/6.9/config/Preferences/org/netbeans/modules/j2ee/appengine

You simply need to change the email address and password in this file. Hopefully, the development will continue on this plugin to add this functionality in the future.

NetBeans 6.9.1 and Google App Engine

A couple of weeks ago David Chandler from Google gave a talk at the Greenville Java Users Group (GreenJUG) about Google App Engine. I was very impressed with the presentation and demo. I decided to explore a little with NetBeans and a plugin for GAE.

The NetBeans support for Google App Engine Plugin is a quick install and works on NetBeans 6.9.1. Once it is installed create a sample Guestbook application to enable the App Engine features. The complete functionality is not enabled until you use it like a number of other NetBeans plugins.

After you create the project you must modify the appengine-web.xml to point to a registered project on appengine for example guestbook and set the version.

Finally we deploy it by selecting the project and deploying it using the context menu. The first time you deploy an application it will prompt you for your login and password. It retains the values for future deployments.

That was easy! Once you get your first application deployed, you have opened the way for future development.

Dynamic Languages on the JVM... Growth or Demise

TIOBE Index January 2011

Like most of you I saw the TIOBE Index this week. Java still holds the top slot, but the press is grinding out our slow inevitable demise.  My question to them is what language is replacing Java? I am not going to be such a zealot to assume that some day, hopefully in the distant future, Java will become COBOL. That day is not here.

One of the interesting observations was around dynamic languages. There was an overall decline, or stasis in dynamic languages. The exception being Python. My interest though is not in general languages like Python, or Ruby, but in their JVM compatible equivalents: Jython and JRuby. The press seems to group them in the "general" demise along with everything else.

I don't agree.

JRuby just released 1.6.0 RC1 on January 10th, 2011 and it will match pace with its parent Ruby when released. Jython has a new release candidate too: RC3 from January 11th, 2011.

I guess it is like a bumble bee, nobody told it: "You can't fly!" So it goes about its merry business like these projects. Nobody told them them of their imminent demise.

I believe that the decline of dynamic languages is real EXCEPT on the JVM. JRuby combined with Java has real staying power. It combines the ease of use in Ruby with the power and multitude of frameworks available in Java. I see growth here not decline.

It will be very interesting when JDK 7 is released later this year. The completion of JSR-292 Supporting Dynamic Languages on the JVM (InvokeDynamic) will breathe a new life into dynamic languages. If you are interested, it is already available. Just download OpenJDK to try it out.

Those are my thoughts. What are yours?

Related articles

• The Rise And Fall of Languages in 2010 (drdobbs.com)
• JRuby upgrade called biggest release ever (infoworld.com)
• Using JRuby by Charles Nutter released (oreilly.com)
• Dynamic Language Support on the JVM (artima.com)