Help

Hibernate Core 4.0.1 has just been released. It mainly contains bug fixes and minor improvements. Check out the release notes for details.

The artifacts have all been published to the JBoss Nexus repository under the org.hibernate groupId. Or if you prefer, the download bundles are available from SourceForge in both ZIP and TGZ formats.

14 comments:
 
24. Jan 2012, 19:30 CET | Link
Sad Hibernate User

Please get rid of the requirements for JBOSS logging because it is making it very hard to adopt Hibernate. Here are the problems with JBOSS Logging.

1) There is no web page for the project, maybe I am blind but 10 minutes of googeling and I can't locate a place where I can find the documentation for JBoss Logging, Slf4j, log4j, jdk logging are documented to death

2) Putting together an enterprise java stack now requires log4j,slf4j,commons-logging, and now jboss logging this is just insane, I was hopping that frameworks like hibernate being low level foundational frameworks will do the right thing and not require any dependecies on other frameworks for logging, just use the jdk logging.

3) I don't care about the JBOSS family of projects, the only thing I use from JBOSS is hibernate I don't care about the app server, I use tomcat, why are you making me dependent on other JBOSS projects.

so please find a way to get rid of jboss logging asap otherwise you will find that many users will be very unhappy.

ReplyQuote
 
24. Jan 2012, 23:30 CET | Link

You do realize that Tomcat is largely developed by Red Hat and JBoss right?

 
24. Jan 2012, 23:33 CET | Link

I do agree though there should be a page or two about setting JBoss Logging up to log to various backends.

 
24. Jan 2012, 23:50 CET | Link

All you need to do is add jboss-logging.jar to the class path. There's no configuration necessary. The fact is that everyone wants something different for logging. It's you saying Just use JDK logging, or someone else saying Why are you using JDK logging, you should use log4j or someone else saying I can't use Logback because you didn't use slf4j. Using jboss-logging.jar means that all these backends will just work. Yes you have to add one small JAR but really this is the best solution possible, and trust me, this problem has been analyzed with a fine-tooth comb for many years by many many people.

 
24. Jan 2012, 23:57 CET | Link

BTW, jboss-logging is already an exported dependency of Hibernate itself. So if you use Maven, Gradle, Ivy, etc and pull in hibernate-core you already get jboss-logging. From there you just drop in the actual logging backend you want to use and jboss-logging picks it up

 
25. Jan 2012, 00:20 CET | Link
Sad Hibernate User

I don't have anything against red hat and JBOSS I just want a very lightweight framework with minimal dependencies this is why I have stuck it out with tomcat. I think JBOSS and Red Hat do great work but I want the choice to be a minimalist and I suspect others do too.

 
25. Jan 2012, 00:26 CET | Link
Sad Hibernate User

I actually don't use maven, gradel, or ivy because I don't want to pull in the public repos meta data files, and I want to check digital signatures on all downloaded files before I add them to an authorized internal runtime directory structure. For me keeping things really simple is very very important, it allows me be super productive compared to other JEE developers.

 
25. Jan 2012, 00:29 CET | Link
Sad Hibernate User

Please point me to where I can download the sources and jar of jboss logging and documentation explaining how to configure it with slf4j? I I would really appreciate that.

 
25. Jan 2012, 01:17 CET | Link

You don't configure anything in JBoss Logging as David already pointed out. It simply sees what logging backends are available on your system and uses (one of) them. slf4j is not a backend itself. For example, take a normal slf4j use case where you are using slf4j to route to log4j. In this case you'd have (1) slf4j-api.jar, (2) sl4fj-log4j12.jar and finally (3) log4j.jar. jboss-logging.jar would see log4j.jar and route logging through log4j.

You can see the order of preference for back-ends in jboss-logging in : https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/org/jboss/logging/LoggerProviders.java#L29 You can also see its configuration parameter if you absolutely want it to do something odd.

Anyway, you can gets its jars in both the JBoss Maven repository and the Central Maven repository. Its source jar also get published to each. Or you can get the project git repo at https://github.com/jboss-logging/jboss-logging

 
28. Feb 2012, 09:10 CET | Link
Christophe | cle(AT)mobiletoken.com

I totally agree with you !

 
04. Apr 2012, 20:03 CET | Link

And I do have to point out that both Gradle and Ivy allow you to define dependencies via directory paths, even project directory paths. Your choice of build tool (or lack thereof) is obviously totally up to you, but at least know what you are talking about when you say I dont use X because of Y.

 
18. May 2012, 11:25 CET | Link
Morten Knudsen | goatbrain(AT)gmail.com
I totally agree with the first poster.
Apparently jboss-logging does exactly the same stupid thing (run time discovery of logging backend) that made everybody hate commons-logging so much.
And why why why create a new logging framwork, when you could've just created an I18N and whatever framework on top of slf4j?
Logging in java is such a pain already, due to the many (and broken) frameworks.
There is actually a special place in hell for those who create new frameworks for no good reason.
 
18. May 2012, 11:28 CET | Link
Morten Knudsen | goatbrain(AT)gmail.com
BTW, the runtime discovery thing of course doesn't work in an OSGi environment, not that the hibernate team care about OSGi anyway.
 
09. Aug 2012, 16:04 CET | Link
Maximiliano Carrioz | mcarrizo(AT)gmail.com

Guys, if you were working outside Red Hat, you would agree with Sad Hibernate User. I think it's okay to be loyal with your current employer, but that not mean you should support every stupid decision. You are basically saying the rest of us should create a logging framework for each new framework we create. Because Hibernate belongs to Red Hat and JBoss, you are saying you will add everything from them, because you are the owner ... Very mature comment !

Come on !! Adding jboss-logging to Hibernate is useless and very stupid. Sorry, guys, its my opinion.

Post Comment