Rich Client Technologies

Still trying to find my way into the Rich client technologies, I just read those articles (in french):

• Quel client riche Java sur le poste de l’utilisateur?
• Client riche: l’inévitable fusion des architectures client-serveur et web

So fo me the main concurrent are:

• Linux Desktop
• SuSE Desktop
• Desktop System (JDS)
• xalm (Longhorn)
• WCTRE
• XUL de Mozilla
• Flex de Macromedia
• Acrobat Reader
• Java:
• SwiXML,
• Thinlet,
• SwingML,
• JellySwing,
• AUIML,
• xmlgui,
• Speed GJ,
• xWidglets,
• Ultrid,
• Altio
• Jndc

Now wich one do you choose ?! (take a bet...)

Craig McClanahan Presentation

I went to a presentation of Sun Java Studio Creator and JSF.
Nice demo. I hadn't tested Creator yet.
It's based on Netbeans and jsp, it take full use of them. (If you don't want to use jsf, not the right tool)
I already had a demo of Visual Studio and asp.net.
Sun created the equivalent of VS for Rapid developpement

It's a nice tool:

• start quickly J2EE developpement
• minimum requirement for the team
• develop J2EE webapp more like VB applications
• doesn't depend on Sun server (even if it's tightly coupled with creator)
• help newbies by providing places where they can put code without thinking to much
  

but with some restrictions:

• not enought thrid part products integration (they are working on it...)
  
• Sun make many choices for you (just has Microsoft do with VS)
• jsf
• 1 to 1 relation between a page and a bean representing the page
• validation process
  
• help you (to much) to copy/paste components (instead of making a service locator for example)
• doesn't prevent bad coding...
  

I would clearly consider Creator for small, rapid developpement project but eclipse is still my favorite IDE because of the plugin comunity.
But for a team of java newbies or corporate developpers that would clearly help to get started.
But once you've started with jsf, I will be hard to abandon it...

blog entry of craig presentation
An other vision of this presentation by sami Jabber - dotnetguru (I don't agree with him but I don't want to flame his blog ;))
A better blog entry in my opinion

Refactoring Unit Tests

I'm currently refactoring some of my unit tests I made when I first started using JUnit framework.

2 things stroke me at first sight:

• I make better unit tests now:

1. I test only usefull thing,
2. they depend less upon other things (ex: a file present in file system)
3. they are clearer

• Using Unit tests forced me to create new entries in my legacy classes, now unit testing is easier. I don't have to refactor a class before starting to unit test it.
  

Renaming JUnit Tests

Using JUnit as it advantages but also it drowbacks...
Actualy it's more wsad 5.0 that could be improve.

When I decide to Rename or Refactor a set of Classes, I have to take care of the classes but also the ClassesTests.

For Exemple, let say I have classe called Foo and a classe FooTest.
If I rename Foo using refactoring menu from wsad, I have to take care of renaming FooTest myself.
It seems obvious but during the first days of programming, when you create your classes from scratch I usually rename my classes often until I'm satisfy by the classes name.

I also refactor and rename often the methods names and the problem is the same I have to rename the testMethod() method in the Test classe... (It is not allways obvious when You only added an "s" to the method name...)
It would be great if refactor menu could also take care of the Tests classes...

I'll try with eclipse 3 to see if they improve that point.