When a project is created following the (excellent)
flash tutorial at
http://nbxdoclet.sourceforge.net/FirstHibernate.htm,
the user ends up with a project which has no logging at
all, because a log4j.properties file is missing at the
class path. This is especially frustrating for newbie
users because they cannot easily determine why their
application is failing, unless they learn about log4j,
commons-logging and where to put the missing property file.
My proposal is to modify the extension so that an
appropriate log4j.properties file gets generated and
added to project directory when the HibernateUtil.java
class is created. If that is not possible or too
complicated, I would suggest to add at least an
ex.printStackTrace() to the catch() clause in the
generated getSessionFactory() method. Then the
exception would appear in the log regardless of whether
log4j is configured or not.
Logged In: YES
user_id=885974
Thanks for report. I am not expert on log4j. Can you attach
your log4j. properties?