Modern Development: May 2011

Tuesday, May 31, 2011

Home - Gilead

Gilead stands for Generic Light Entity Adapter

It permits you to send Persistent entities (and especially the partially loaded ones) outside the JVM (GWT, Flex, Web-Services, Google AppEngine ...) without pain.

No LazyInitialisationException. No DTO mapping. Just POJO and Domain Driven Design :) !

The complete features list is available here.

Creating Application using Spring Roo and Deploying on Google App Engine | Javalobby

Spring Roo is an Rapid Application Development tool which helps you in rapidly building spring based enterprise applications in the Java programming language. Google App Engine is a Cloud Computing Technology which lets you run your application on Google's infrastructure. Using Spring Roo, you can develop applications which can be deployed on Google App Engine. In this tutorial, we will develop a simple application which can run on Google App Engine.

This, however, is a dealbreaker:

Spring Roo on app engine does not support enum and references yet which means that you can't define one-one or one-to-many relationships between entities yet.

Google App Engine Java Persistence: The Truth About Joins

Whenever I get the opportunity to talk to my peers about the coolness of App Engine it always pains me to have to say "...but you can't do joins." I know how useful joins are because I spent many many years using them before I started working on App Engine. Lately I've been thinking that there has to be a way to make it work. The App Engine datastore offers a guarantee that query performance scales with the size of the result set, not the size of the data set, so a query that returns 100 results should take the same amount of time whether you have a thousand rows or a million. That means we can't compute a full cross-product at time-of-query because that would require looking at all the data in the n tables we're joining, and if we look at all the data our performance is now tied to the size of the data set. Still, it feels like we ought to be able to do something here.

Google App Engine Tutorial for Java

GAE/J supports JPA (Java Persistence API) 1.0 for persisting data. As all data on the GAE/J are stored in Bigtable some features of JPA are not supported. See JPA on GAE/J for details. Alternatively to JPA you can also use JDO or the low-level API of the App Engine. The datastorage facility is described in Datastore Java API Overview .

The following will create a small "Todo" application using servlets and JSP's. The persistence will be handled by JPA . For an introduction into servlet and JSP programming please see Servlet and JSP development - Tutorial.

Tuesday, May 24, 2011

Free Java hosting with the Google App Engine « JTeam Blog / JTeam: Enterprise Java, Open Source, software solutions, Amsterdam

Lately I have been looking into and playing around with the Google App Engine. In this post I want to give a little introduction to the Google App Engine, why it can be interesting and how to work with it.

Wednesday, May 11, 2011

GWT Sushi: Create a GWT Contact Application in 10 easy steps.

Google GWT and Spring Source have joined forces to make it easier to develop web applications by developing a tool which creates your data models, your web gui interface and all the web-server communication code in a few easy command line statements. This was demo’d at Google IO 2010 and I aim to replicate the steps required here, including any pitfalls to help you jump start your GWT development.

Building a GAE+GWT application using the best practices (Index) « Reminiscential: of or pertaining to remembrance

Part 1 – Introduction
Part 2 – Project setup and server side wiring

Part 3 – Writing the web service with command pattern

Part 4 – client side wiring

Part 5 – UI coding

Monday, May 9, 2011

Why the New Guy Can't Code - Slashdot

theodp writes "'We've all lived the nightmare,' writes Jon Evans. 'A new developer shows up at work, and you try to be welcoming, but he can't seem to get up to speed; the questions he asks reveal basic ignorance; and his work, when it finally emerges, is so kludgey that it ultimately must be rewritten from scratch by more competent people.' Evans takes a stab at explaining why the new guy can't code when his interviewers and HR swear that they only hire above-average/A-level/top-1% people. Evans fingers the technical interview as the culprit, saying the skills required to pass today's industry-standard software interview are not those required to be a good software developer. Instead, Evans suggests: 'Don't interview anyone who hasn't accomplished anything. Ever. Certificates and degrees are not accomplishments; I mean real-world projects with real-world users. There is no excuse for software developers who don't have a site, app, or service they can point to and say, 'I did this, all by myself!' in a world where Google App Engine and Amazon Web Services have free service tiers, and it costs all of $25 to register as an Android developer and publish an app on the Android Market."

Wednesday, May 4, 2011

Marlinspike's Droid Firewall Kills Tracking - Slashdot

mask.of.sanity writes "The first dynamic Android firewall, dubbed WhisperMonitor, has been released by respected security researcher Moxie Marlinspike. The firewall will allow users to stop location-tracking apps and restrict connection attempts by applications. Marlinspike, whose company created the application, designed WhisperMonitor in response to the incidence of location tracking and malware on Android platforms. It monitors all outbound connection attempts by applications and the operating system, and asks users to permit or block any URLs and port numbers that are accessed."

Monday, May 2, 2011

Developing Android Apps Visually, In 3 parts - Slashdot

"Dr. Dobb's has a three-part blog (all three parts are up; this is part 1) about using App Inventor. The focus isn't so much on the technology but rather the discussion of 'can visual development let anyone program?' If so, is App Inventor really visual development? And should we be teaching real programmers about visual development. Most of the conclusions are in part 3. As a byproduct, they show you how to put App Inventor output on the Market and there are two games on the market (free) that resulted from the articles."