Hi, I'm sorry if this doesn't help you.
I went trough exactly the same stuggle trying to use a hibernate persistence
unit and JPA. Hence my reply. It IS possible to get the configuration right
(I did) but I never expected it to be so difficult and consume so much of my
time. I spend 1.5 weeks to overcome all issue, then when I finally had
hibernate talking to my sql server XADatasource, it turned out not the
driver but the hibernate libraries were having problems with that
XADatasource. After 2 weeks I got tiered of all hibernate's problems with
glassfish and netbeans, and since we were still deciding on architecture, we
did a test with oracle toplink. This took us one hour to do the following ;
Configure it
Generate model
Use persistence unit
Deploy to glassfish.
Do all required modifications to jpa annotations.
So congrets to the toplink team. They made me loose hibernate for now, as it
is NOT cleanly intergrated with glassfish OR netbeans, it doesn't matter
what them claim to be, it isn't.
So we're using toplink now. There's a rumour this would be much slower then
hibernate, but I get a reponse in below 0.01 secs. So we decided to put that
in production, to relieve our dev team from all the hibernate problems.
Aside from the common logging problem, expect to run into a lot of other
sheiss, f.e. we had to implement our own HibernateDialect just to get
timestamps and blob/clobs right. (sorry to the hibernate team but it's
reality). Using toplink everyting was perfectly generated from the first
time (we only had to modify 2 or 3 annotations).
In the past I would surely have recommended hibernate over toplink, but for
the time being, this has changed.
wim
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: vrijdag 13 juni 2008 15:05
To: users_at_glassfish.dev.java.net
Subject: Re: RE: RE: RE: Glassfish throws Commons logging error during
Configuration
Ive tried that as well and im still gettting the same error. I created a
simple Stripes project that has commons-logging bundled with it and deployed
it and received the same error. I would think that for an app server not to
be able to deploy an app that contains commons-logging is a pretty big deal.
Anyone else ever had this problem?
[Message sent by forum member 'kenbarnesjr' (kenbarnesjr)]
http://forums.java.net/jive/thread.jspa?messageID=280159
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net