Figured it out - apparently the older versions of jboss and hibernate didnt
care that i had my DBO (Pojo) objects duplicated in my HAR file as well as in
my WAR file but the newer versions care. I just took out the duplicate files
from the war dir and used the ones in the HAR exclusively.
View
I recently upgraded my previously functional codebase to use hibernate 3.0.5
and jboss 4.0.3 from hibernate 3.0.1 and jboss 4.0.1sp1. Now when hibernate
hits the database with q.uniqueResult() it returns an Object which is of type
Client but when i try to cast it to client i get a classCastExcep
anonymous wrote : 2005-08-15 21:47:47,828 INFO
[org.jboss.deployment.EARDeployer] Undeploying J2EE application, destr
| oy step: file:/opt/jboss-4.0.2/server/all/farm/ServiceEnginePrincipal.ear
| 2005-08-15 21:47:47,892 WARN [org.jboss.mq.Connection] Connection failure,
use javax.jms.Connec
The EOFException could be getting thrown by not having your farmed out files
jarred up. In farm deployment you need to have your ear/har/sar etc... files
are jarred up or else when you distribute to your cluster you get exceptions
like those. It could be somthing else but i have run in to that p
I am deploying a HAR file with hibernate 3.0.3 and jboss 4.0.2
Everything seems to deploy ok but when i goto retrieve the SessionFactory from
the JNDI it feeds me back a null value.
This is the code to get the sessionfactory
| SessionFactory sf = null;
| try {
|
I have the same problem that is explained in the origional post. Anyone figure
out what the fix was?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878477#3878477
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878477
