You are currently browsing the Philipp Meier's weblog blog archives for January, 2003api


Answers on WebWork vs. Struts

Andre writes in
Here is my shortlist of initial queries:

1. Is there a dynamic tempating framework similiar to Tiles? Whats the best practice used by most WW guys?
2. Is there a Valididator engine, other than rolling your own doValidation method? Do you guys use the Commons Validator?
3. Is there a html taglib engine similiar to struts-html ?

I try to give an answer below.
Continue reading →

Citation of the Day

Citation of the Day:

IT Trends Blog – Citation


Use a lightweight database

Charles Miller writes in
The Fishbowl: Databases, Part One:

I feel pretty confident saying that a significant number of people who are using a Relational Database, shouldn’t be.

Yes, most the times using a relational Database is overkill, even only because of the administrative overhead. But, wait, there is a nice solution at least for us java programmers: these nice little file based databases like: Hypersonic or InstantDB. I like them, I use them. They’re small, they’re fast.

Wer bin ich?

Hier kann jeder sein eigenes Phantombild erstellen. Ich hab mich allerdings selber nicht wiedererkannt:



Get notified of software errors by email

I recently set up an application at a customer’s site. To get notified of errors, I used log4j’s SMTPAppender to sent an email with the log message if the log level was ERROR. I watched my Mailbox for about a week, but then I noticed the incredible number of over 10.500 new messages in my inbox.

What had happened?

My application’s job is to parse emails sent to a certain mailbox and process them. Unfortunately the application would leave a message in the inbox of an error occured during import. Because the other system sent an email that my application would reject to parse, the message stayed in the inbox and my application tried to parse it again and again, every 15 minutes.

What do we learn?
  1. Do not use an active notification on error if the error is permanent.
  2. Do not report the same error again and again.
  3. Write some log4j appender that would filter or aggregate the messages in this case. ;-)