yes, and have another Persistence Framework like Hibernate as
Hibernate isn't the only framework available for mapping objects to persistent data stores. I encourage you to evaluate each of them and choose the best one for your needs. Some alternative frameworks, listed in no particular order, are:
1. OJB. "ObjectRelationalBridge (OJB) is an Object/Relational mapping tool that allows transparent persistence for Java Objects against relational databases." Apache license. http://db.apache.org/ojb/
2. Castor. "Castor is an open source data binding framework for Java[tm]." BSD-like license. http://castor.exolab.org/
3. CocoBase. "CocoBase� offers a simple to use, powerful Dynamic Object to Relational Mapping� tool for Java developers writing applications on the J2EE, J2SE and J2ME platforms." Commercial. http://www.thoughtinc.com/cber_index.html
Instance pooling is a misfeature, actually. Your JVM can pool memory much more effectively than your application server can, and you shouldn't acquire references to heavyweight resources in entity objects.
(The original EJB specs were written when Java garbage collection was much more expensive than it is today.)
Originally posted by Gavin King: Instance pooling is a misfeature, actually. Your JVM can pool memory much more effectively than your application server can, and you shouldn't acquire references to heavyweight resources in entity objects.
(The original EJB specs were written when Java garbage collection was much more expensive than it is today.)
Ok, The server can be acquired memmory when run server , So
Can i see detail of environment was acquired? How to config about memmory size for server ?
AS Gavin said it is about the JVM configuration. Every available virtual machine can offer its set of parameters to configure (for example see Sun JVM - Tuning Garbage Collection articles).
Originally posted by Ali Pope: AS Gavin said it is about the JVM configuration. Every available virtual machine can offer its set of parameters to configure (for example see Sun JVM - Tuning Garbage Collection articles).
./pope
Is n't it easier to configure the container than JVM?
I tend to prefer Hibernate simplicity when mapping domain objects than focusing into performance issues.
POJOs and a bit of xml are FAR simpler to code and mantain than ejb's home/local/remote interfaces and architecture. You've to add the complexity of the container, too.
The memory acquired by your domain model objects is just a tiny fraction of the total memory usage of the server. Your JDBC driver, JSP engine, etc, are spewing out way more garbage than Hibernate is. So trying to control memory allocation by adjusting pool size for domain objects is unlikely to be very successful in real applications.
If it is difficult to get it working with some major application servers(like Weblogic), what is the point in using Hibernate??
From where is this coming? Hibernate fully integrates with JBoss, WebSphere (there are also documents on this) and WebLogic (underwork if I am not wrong) - so the major AS. Check the wiki part of Hibernate site and you will get all the info needed to make it work.
From where is this coming? Hibernate fully integrates with JBoss, WebSphere (there are also documents on this) and WebLogic (underwork if I am not wrong) - so the major AS. Check the wiki part of Hibernate site and you will get all the info needed to make it work.
./pope
One of the other posts in the forum says that it is not easy and there are problems while working with weblogic(ie about 20% of app server market right)
From where is this coming? Hibernate fully integrates with JBoss, WebSphere (there are also documents on this) and WebLogic (underwork if I am not wrong) - so the major AS.
We are using Jboss app server and Hibernate works smoothly. Does Jboss entity beans use Hibernate as persistent layer for entity beans? I am not clear what do they mean by usinh Hibernate as persistent layer.
We are using Jboss app server and Hibernate works smoothly. Does Jboss entity beans use Hibernate as persistent layer for entity beans? I am not clear what do they mean by usinh Hibernate as persistent layer.
Yes, entity can use Hibernate BUT it's bad performance.(More overhead).
I'm use session bean(SEssion Facade) to call/manage hibernate persistent.
BUT in web application such as E-commerce website.. etc , i'm use Hibernate instead DAO.
Post by:autobot
You will always be treated with dignity. Now, strip naked, get on the probulator and hold this tiny ad:
a bit of art, as a gift, the permaculture playing cards