JointEffort

OrientDB – Graph DB

mlindhout — Fri, 09 Sep 2011 08:13:38 +0000

I’m converting my never ending ‘financial app’ to use OrientDB, a small, fast and powerful NoSQL document database with support for directly storing and retrieving Java object. Seems promising…

Reading highlight

mlindhout — Thu, 26 May 2011 08:59:16 +0000

I’m now reading Fearless Change.

What motivates us?

mlindhout — Thu, 12 May 2011 06:41:10 +0000

I just saw the (pretty old) video from Daniel Pink about The Surprising science of motivation [TED].

Into Grails (continued)

mlindhout — Mon, 11 Oct 2010 06:55:19 +0000

So far, so good, Grails development is pretty easy and nice. I had to switch to IntelliJ’s IDEA environment, but anyway, everything went well until now. First pages of the app I built for a customer are converted. While digging through the Grails plugins, I found the Grails AppEngine Plugin. Guess what’s the next exercise? Right! Deploying my Grails app on the Google App Engine. To be continued….

Into Grails….

mlindhout — Wed, 29 Sep 2010 08:47:02 +0000

I just dived into Grails, giving it a try by duplicating an existing system for a customer I built in Java. I know about Ruby, Groovy and the like, but Grails seams to realized more speed in Java application development …

Seam, Flex and Facelets integration

mlindhout — Tue, 17 Aug 2010 20:18:07 +0000

I just achieved a ‘seamless’ (what’s in a name) integration between JBoss Seam (backend) and Adobe Flex (frontend). The backend consists of a set of Seam components, exposed as REST services via RESTEasy, while the (Swiz-based) Adobe Flex application calls this services using the simple HTTPService object. The backend generates DOM4J based XML responses. The Flex application is embedded in a dynamically generated Facelets-based page. The Flex app allows customers to design a poster, and add them to their basket for later checkout. Once in the basket, an earlier designed poster can be re-opened by the Flex ‘designer’ by passing the poster identifier using the FlashVars variable. Works like a charm!

Think more, design less

mlindhout — Tue, 17 Aug 2010 07:32:59 +0000

Tracing the impact of a requirements change

mlindhout — Mon, 16 Aug 2010 14:09:11 +0000

Wouldn’t it be nice if we easily could trace the impact of a change in a requirement? Lately I was faced this question, and spent some thoughts on it. For example, regarding Java code, we might use an annotation like this:

@Requirement(id = "REQ0206", version="1.0")
public class CustomerAssignment {
...
}

But Java code is only part of the job. For XML (or XSD’s, XHTML’s and other XML-like formats), we could use someting like this:

...

...

And last but not least, we may write a simple Maven plugin that generates a report of code artifacts that will be affected by a change in a requirement.

Would you use this? Please let me know.

A brand new start…

mlindhout — Thu, 12 Aug 2010 11:38:30 +0000

Thread mySite = new Thread() {
   public void run() {
      ...
   }
};
mySite.start();