-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 
Author Message
 Post subject: added details for running Hibernate with an EJB in the WSAD5
PostPosted: Sat Mar 06, 2004 1:22 am 
Beginner
Beginner

Joined: Tue Mar 02, 2004 6:17 pm
Posts: 20
Added some details to the steps of running Hibernate with an EJB application in the WSAD 5.0.1 environment, originally posted at this link: http://www.hibernate.org/173.html.

I've added some details to make it easier for beginners like myself.

Note all test server configurations refer to the WSAD test environment

1.Create the EAR and EJB projects as you normally do, create the Session bean that normally used as transactional facade.

2.Import the following jar archives to the EAR project root directory from the file system:

cglib2.jar
commons-collections.jar
commons-logging.jar
dom4j.jar
hibernate2.jar
odmg.jar
xalan.jar

There may be warnings about the dependent Jar files not available for some of the JARs above. You can either ignore them or add them from WSAD


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 06, 2004 12:13 pm 
Hibernate Team
Hibernate Team

Joined: Sun Sep 14, 2003 3:54 am
Posts: 7256
Location: Paris, France
Please update the wiki page itself.

_________________
Emmanuel


Top
 Profile  
 
 Post subject:
PostPosted: Mon Mar 08, 2004 1:37 pm 
Newbie

Joined: Tue Feb 03, 2004 11:58 am
Posts: 11
Step #5:
"Configure a DataSource the normal way. (You may need to set up a JAASC Authentication entry on the Security tab of the server configuration, and then set the Container managed Authentication Alias for the DataSource to that entry)"

Question:
In setting a DataSource: in the "JDBC provider list:" I suppose I should select "Default DB2 JDBC Provider" with "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource" for the "Implementation class name" if dealing with DB2 database.
If that is correct, which version of the Data Source did you select in the
"Data source defined in the JDBC provider selected above:": version 4 or 5.

Step #6:
"Create a resource reference for the SLSB refering to the DataSource (EJB Deployment descriptor):


Top
 Profile  
 
 Post subject: Yes my steps are tested under EJB2.0 with WSAD5.
PostPosted: Tue Mar 09, 2004 12:33 am 
Beginner
Beginner

Joined: Tue Mar 02, 2004 6:17 pm
Posts: 20
As for dataSource, what I heard from others is user the one for Version 5 whenever possible.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 13, 2004 6:45 am 
Newbie

Joined: Tue Apr 13, 2004 2:36 am
Posts: 5
Hi

I tried apply your decision, but still have problem. My situation:
- I don't use Websphere devel. studio
- use Eclipse and XDoclet for build EJBs
- use Maven for build EAR/JAR

My EAR have structure:
root_dir
- META-INF
- app.jar
- hibernate-2.1.2.jar
- other jars when you wrote
- hibernate.cfg.xml

When I try read Configuration from EJB inside app.jar, I can't found hibernate.cfg.xml. I try put hibernate.cfg.xml to app.jar, but still can't read it, what's wrong?

MD


Top
 Profile  
 
 Post subject:
PostPosted: Wed Nov 02, 2005 9:31 pm 
Newbie

Joined: Wed Nov 02, 2005 5:33 am
Posts: 12
Dear All,

Did you succeed in deploying your Hibernate Application onto Websphere Application Server WAS v5.1.2? If yes, could you share your experience with the community? Thank you!


--------------------------
thanh.hoc@gmail.com
---------------------------


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.