was contained not in a java class, but in a aspect. And the part that appears in bold were in a dao java class, but not linked to Hibernate, and was high level, so the code could be reusable for the save, update or delete of the object.

By the way, he also shows how to encapsulate all HibernateException into DAOException (required by his virtual architecht), and also how to preserve people to directly call Hibernate oriented methods appearing in your DAO class after compilation by AspectJ.

As a demo, It was really incredible.

Many Thanks, Mr Colyer.

Now, I really hope that somes next version of NetBeans will include a module to manage aspects like the eclipse one.