09Sep

OrientDB – Graph DB

mlindhout Java 0 comment

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…

26May

Reading highlight

mlindhout People 0 comment

I’m now reading Fearless Change.

12May

What motivates us?

mlindhout People 0 comment

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

11Oct

Into Grails (continued)

mlindhout Java 0 comment

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….

29Sep

Into Grails….

mlindhout Java 0 comment

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 then the others do in their area’s. Let’s see where it crashes…

17Aug

Seam, Flex and Facelets integration

mlindhout Flex, Java 0 comment

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!

17Aug

Think more, design less

mlindhout Design 0 comment
16Aug

Tracing the impact of a requirements change

mlindhout Java 0 comment

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:

...
<r:req xmlns:r="nl.jointeffort.analysis" id="REQ301"/>
...

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.

12Aug

A brand new start…

mlindhout Uncategorized 0 comment 
Thread mySite = new Thread() {
   public void run() {
      ...
   }
};
mySite.start();