In Relation To

One of my favorite feature in JBoss Tools is the Project Archives which provides automatic and incremental archiving of arbitrary directories into a zipped archive (jar,zip,war,etc) or into an exploded directory. Usable for any development that wants hot and/or exploded deployment.

Stephan Schmidt says that people don’t get the difference between business and UI logic:

Gavin pointed out that he did not get the separation between business logic and UI. Which leads to the question of why are we layering in the first place? I have heard many many bad reasons to justify layering. Actually, this is one of my favorite questions when I give a training. It's always fun to see the people sweating over a justification.

Someone asked on Slashdot what NAS he should buy. As usual, the clowns have a field day on the comments (even at threshold 5). The usual You should not need one if you do foo, Why add a single point of failure, and other Funny comments. I actually happen to have a NAS at home for more than a year. Here is what I wrote a year ago:

I've just installed Fedora 8 on my ThinkPad X60, and as it comes with packages for Iced Tea (Red Hat's version of OpenJDK), I thought I would take the Seam Booking Example out for a spin.

The release candidate of JBoss Tools is now available at sourceforge for Linux, Windows and Mac.

To celebrate the new release of JBoss Tools, I'm going to walk through some of the features of JBoss Tools that are interesting to Seam developers.

While there are many things I like about the Java language, the lack of unsigned types has always bothered me.

Matt Raible lists his picks of the top web frameworks for deploying on the JVM:

So, I've been following this discussion with interest. I'm still confused. All I'm really getting out of the comments on this thread is: there's some other objects in the system that aren't DAOs or entities. But I knew that already. Clearly, I need to actually read the damn book for myself. Still, it really doesn't fill me with confidence that people who /have/ read the book don't seem to be able to explain (in words or code) the Repository notion coherently. And it looks like everyone has their own private take on what exactly a Repository is all about. This gives me a hint that the idea is not especially well-defined.