Wicket vs. Tapestry4

Last couple of days I've been tossed between Tapestry 4b3 and Wicket 1.1b3. Both of which integration with Spring is quite problematic.


Things I like about Tapestry(4):

   
• Full control over pages/components

   
• Once Spring is integrated, full IOC is possible.

   
• Nice components available (eg. Tacos)

Things I don't like about Tapestry:

   
• Quite a lot of dependencies (Here less is beter)

   
• Hivemind.. (way to beta to do some actual work). Try integrating it with hibernate for example..

   
• Directory structure. HTML pages fload around in the classpath without the possibility to have them

But comparing them with Wicket...

Good things:

   
• Strong typed

   
• Real components (class+html) possible (just drag a jar in the lib folder)

   
• Good I18n possibilities

   
• Good templating possibilities (both HTML and class)

   
• very few dependencies

   
• Spring can be integrated by encapsulating it in the Application class

Things I don't like about Wicket

   
• Everything needs to be defined in java, no pull possible

   
• Getting the HTML right is hell, tags aren't replaced they are filled

   
• Components require the right tags

   
• No real IOC

Israeli technology

I just found a whole lot of interesting new technology articles on the Isracast site. Really quite interesting. Some samples:

• PEN-LIKE INSTRUMENT WILL SNIFF OUT EXPLOSIVES


• ISRAELI COMPANY DRIVES THE LARGEST SOLAR PLANT IN THE WORLD


• LIKE A FISH - REVOLUTIONARY UNDERWATER BREATHING SYSTEM


• CELL PHONE RADIATION MAY CAUSE VISUAL DAMAGE

Boycott IE7

Paul Thurrott, a journalist that usually writes about all things windows related (and sometimes about Apple affairs too), made a call in a recent article to boycott Internet Explorer, due to Microsoft's approach (continued in IE7) of not supporting web standards

It's a cancer on the Web that must be stopped. IE isn't secure and isn't standards-compliant, which makes it unworkable both for end users and Web content creators. Because of their user bases, however, Web developers are hamstrung into developing for IE at the expense of established standards that work well in all other browsers. You can turn the tide by demanding more from Microsoft and by using a better alternative Web browser. I recommend and use Mozilla Firefox, but Apple Safari (Macintosh only) and Opera 8 are both worth considering as well.

Read the complete article

Stupid servlet problems

Been chasing my tail here for half an hour. Got a 404 when trying to format an EDI message through my EdiFormatter application which helps me reading those formats. No matter what I did it gave me a 404 till I tried it locally and saw it couldn't find the class. Ahhrrrr.....changed package but forgot to update the web.xml. Ok well, if you've searched long enough for a stupid problem then you'll figure them out easier and faster next time you'll encounter them.