<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
SCJP, SCWCD
Can you explain the performance difference
between standard SQL and EJB-QL.
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
Hello Ted,
Can you tell me how can take part in Java Ranch Give Away Book pooling.
Regards
Awais Bajwa
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Originally posted by Rick Hightower:
I find code that get's generated from EJB QL can be really ineffecient SQL/JDBC code. But....
Most app servers will cache the entity beans so you don't hit the DB everytime you hit the site. We found that EJB CMP with caching turned on improved our performance.
I think you should look into EJB CMP. It is very productive. There is a link to serveral tutorials I wrote on EJB CMP included in my signature.
Gee... I hope I win a free copy of this book. It sounds really good.
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Originally posted by Rishi Singh:
...Well i would like you to lend some insight as to how to make an intelligent call when one need to decide out of the following :
1)Plain JDBC v/s Entity beans
2)BMP v/s CMP when in terms of development time.when would we go for BMP's
3)Using 3rd party Persistence v/s Writing portable EJB-QL's
4)What to use as a wrapper an MDB or a Session Bean over Entity Beans in Session Facade.
5)How do we test performance issues in case of BMP/CMP.
Rishi
SCJP,SCWCD
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Normal is in the eye of the beholder
After doing this project, I'm now a big fan of CMP/CMR.
This is not to say there aren't cases that warrant rolling your own, but if I had to generalize, I'd side with the container doing the heavy lifting.
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
- Bill -
2) The class dependencies in case of a Entity bean is five(home,remote,bean implementation + 2 superinterfaces ) whereas JDO needs only two class ( plain .java class, and one primary key class)
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
4) In case of Entity bean we cant have benefits of dynamic query as we need to write the EJB-QL in deployment descriptors, whereas JDO's can take the leverage of dynamic query .
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
1) Entity beans were never meant to be 'real' domain objects,
though we can use entity beans as references across the application still the benefits of inheritance is lost(infact there are many points where EJB violates pure OO concepts)
JDO can make use of inheritance to the best possible manner as they are plain java objets.
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
when we need to acess data involved in three or more tables it becomes pretty hard to do the mapping and write EJB-QL
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
Originally posted by Ramjet:
Good looking book...I had it in my hand just the other day. Did not look at it long enough to check if your tests included using Container Managed Relationships and showed how they effect performance.
Just curious.
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Originally posted by Rishi Singh:
Hi Ted,
I would like to compare entity bean and JDO over the following points:
1) Entity beans were never meant to be 'real' domain objects, though we can use entity beans as references across the application still the benefits of inheritance is lost(infact there are many points where EJB violates pure OO concepts)JDO can make use of inheritance to the best possible manner as they are plain java objets.
2) The class dependencies in case of a Entity bean is five(home,remote,bean implementation + 2 superinterfaces ) whereas JDO needs only two class ( plain .java class, and one primary key class)
3) The building and the deployment process is almost the same for both
4) In case of Entity bean we cant have benefits of dynamic query as we need to write the EJB-QL in deployment descriptors, whereas JDO's can take the leverage of dynamic query .
These are some of the points which i realised when taking a close look at both and i feel BMP/JTA/JDO is the way to go.would like to hear from
Ted about this....
Rishi
SCJP,SCWCD
A reason to use Entity beans to wrap JDO classes (using a BMP delegate strategy) is to allow the JDO classes to be remotely accessible directly, rather than through a session facade. This implies a higher degree of autonomy and functionality in the JDO classes.
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Originally posted by Rishi Singh:
1) Entity beans were never meant to be 'real' domain objects, though we can use entity beans as references across the application still the benefits of inheritance is lost(infact there are many points where EJB violates pure OO concepts)JDO can make use of inheritance to the best possible manner as they are plain java objets.
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Originally posted by EJB Testing:
Are you presenting at any other Java user's groups in the near future? A few of my colleages in San Jose would like to attend if you are out that way!
-jason
<a href="http://www.tedosborne.com" target="_blank" rel="nofollow">Ted Osborne</a><br />Co-author of <a href="http://www.amazon.com/exec/obidos/ASIN/1904284000//tedosbornecom-20" target="_blank" rel="nofollow">J2EE Performance Testing with BEA WebLogic Server</a> and <a href="http://www.amazon.com/exec/obidos/ASIN/1861005083//tedosbornecom-20" target="_blank" rel="nofollow">Professional EJB</a><p> <a href="mailto:[email protected]" rel="nofollow">[email protected]</a> <br /><a href="http://www.tedosborne.com" target="_blank" rel="nofollow">http://www.tedosborne.com</a></p>
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
I am going through your Xdoclet tutorials and it seems an intresting read, whether weblogic7.0 support this.?
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
Well what if the application depends upon alot of real time dynamic data,how can u restrict ur end-user the leverage of not getting real-time data.
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
it may not be a logical thing to instantiate 1000 or more entity beans if i have that number of rows and if the need be so, this is what i had explained in my earlier post.
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
Are you okay? You look a little big. Maybe this tiny ad will help:
New web page for Paul's Rocket Mass Heaters movies
https://coderanch.com/t/785239/web-page-Paul-Rocket-Mass
|