If you’re looking for a library and don’t know where it is check this search engine

Mike Thomas has developed SpringGraph a stylesheet to generate a graph from Spring beans in application context.
I took it and developed the maven-springgraph-plugin, check the sample output. I think spring users will find it useful.
The main drawback is the need to install Graphviz, so if anyone knows a Java implementation to make graphs, please tell me.

I don’t know why but the comments on this weblog are not emailed to me altough I checked the “E-Mail Comments” checkbox in settings.

Also I don’t know why comments are disabled for posts older than seven days.

Update: This happened when using a tool to post the entry such as w.bloggar

Another bug I’ve just discovered happened when logged in I added a comment in other weblog, the result page was MY weblog with the other weblog entry and comment added!

I think roller needs a bit more testing.

I found many blame Maven for many things that are not right, they just have not found the way to solve them.

Here it goes some of them:

• The learning curve is as steep as it can get, the documentation is rudimentary and limited and public domain is not much help either
  
  Almost all questions in the user list are answered, Maven has a growing community with lots of users. And once you are used to a Maven project you are used to all Maven projects all over the world.
• Limited Utilities to Integrate with existing IDEs like WSAD (eclipse 2.1 platform based)
  – mevenide is improving with time, anyway I don’t really need to use it, I prefer doing by hand.
• Tedious process of creating XDoc files
  – Use html2xdoc plugin
• Dependency management is a pain
  – Dependency management is one of the best things of Maven. You can’t blame maven because your alternatives are: doing it by hand writing lots of xml lines!
• Limited Integration facilities with SCM tools like Sub-Version, Serena etc.
  
  – It’s already done for next versions

I have just implemented a tiles controller that sets css styles based on user-agent header automatically.

The layout of the webapps can be easily customised without touching any jsp code nor creating new jsp files, CSS stylesheets are profusely used, no annoying tables, no need for typing different urls according to the browser you’re using, you can check that most of sites in the net are using different urls for pdas and other browsers, e.g. in Google you need to go to www.google.com/palm to see the palm site.

Here you can find the controller documentation
http://oness.sourceforge.net/multiproject/oness-common-webapp-controller/

And here some snapshots and the view documentation and tiles configuration file with a sample of setting a custom layout to a Palm pda.
http://oness.sourceforge.net/multiproject/oness-common-webapp-view

Today I’ve made major changes to the model layer. Hibernate is soooo complicated… Maybe it’s a good thing for simple applications but in a layered one there are many issues you have to deal with.

My idea is now:

• All collections are lazy to avoid sql queries
• Everytime you need a collection you have to call the DAO to get it, this way you also ensure independency of the persistence mechanism used
• When the DAO is called to get a collection it’s filtered to return only values not deleted (transactionTime.end is null)
• findById should return a clone of the object returned by Hibernate because it’s cached, so next modifications in facades don’t affect persisted instances.

Hope this works when rerunning test cases tomorrow morning. Then I’ll commit the changes.