Solved

Entity EJB Design question

Posted on 2004-08-29
8
251 Views
Last Modified: 2013-11-24
I'm creating an Entity EJB using Bean Managed Persistence, which could be fairly complex.  It's would represent an object whose data spans multiple DB tables and the fields consist of some potentially large objects (input streams). The cost of storing and loading this info to and from the DB would be fairly high.  This object is essentially representing a program whose code and associated include files are stored in the DB. There are certain attributes that will be used quite a bit more often than others, for example the name, description etc. will be looked up often to generate a list of these programs available to the end-user. Where as the large program files and include files will be used less often only when a user chooses to run the program.  All the attributes will need to be modifiable. I want to avoid having to do the expensive reads and writes of the large attributes every time the ejbLoad and ejbStore methods are called, and only do them when needed. I have a few ideas but I wanted expert input:

1. Create two Entity Beans to model the object. One will contain the commonly used display attributes and the other will contain the less commonly used functional attributes. This will give an easy separation of the object and allow the expensive read/write calls to be used only when needed.  I’m not sure if this will lead to integrity issues since a remove of one will necessitate a removal of the other, and this might cause problems.

2. Use only one Entity EJB and instead of having all the fields in the DB be instance variables of the EJB and be loaded and stored with each call of the ejbStore or ejbLoad. For the large and expensive fields I would create methods that pull and load those fields only when explicitly asked for or changed. To me this seems like the best solution but it doesn’t seem to fit in with the idea of Entity Beans but I’m not too sure, I’m very new to EJBs.

I’m sure there are other possible approaches too. Any input is greatly appreciated.

Thanks
David
0
Comment
Question by:NHBFighter
8 Comments
 
LVL 35

Expert Comment

by:girionis
Comment Utility
We had a similar problem though not using EJBs but Hibernate. We did something similar to your first approach, we had one bean represent the commonest/less expensive data and a second bean representing the *all* data. Then it was matter of what we needed to load. The whole data represented binary stuff which was expensive to load up and most of the time we did not need to load it. So we were mainly calling the less expensive bean (the one that represented mainly primitive type data) and only called the "expensive" bean when we really had to. This was a good approach and saved us processing power and memory. The only drawback was that we had to write a separate class and a separate XML mapping for the "less expensive" bean, which was not a big deal if you think about it.

With regards to your approach two, you could do that but indeed it does break the concept of entity beans. If you want to strictly follow the EJB specification better avoid it, but if you really think it is the solution then you might as well go for it.
0
 
LVL 30

Expert Comment

by:mayankeagle
Comment Utility
Even I would say that the first approach sounds good to me. The idea of dividing the roles amongst two beans is more acceptible, mainly because:

>> allow the expensive read/write calls to be used only when needed

Do have a good hands-on with EJBs or do you also want some links to the EJB specification, tutorials, etc?
0
 
LVL 4

Author Comment

by:NHBFighter
Comment Utility
Thankks for the input, I'm just learning EJBs but I'm getting a fairly good handle on it and I've done lots of reading on them but any links would help.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 35

Accepted Solution

by:
girionis earned 84 total points
Comment Utility
I'd say the best place is this one: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/
0
 
LVL 30

Assisted Solution

by:mayankeagle
mayankeagle earned 83 total points
Comment Utility
You can also try: http://www.ejbtut.com
0
 
LVL 6

Assisted Solution

by:valipotor
valipotor earned 83 total points
Comment Utility

The best book on ejbs i'v ever read is Mastering EJB, now second edition, available here
http://www.theserverside.com/

valipotor
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

An old method to applying the Singleton pattern in your Java code is to check if a static instance, defined in the same class that needs to be instantiated once and only once, is null and then create a new instance; otherwise, the pre-existing insta…
Introduction This article is the last of three articles that explain why and how the Experts Exchange QA Team does test automation for our web site. This article covers our test design approach and then goes through a simple test case example, how …
Viewers learn about the third conditional statement “else if” and use it in an example program. Then additional information about conditional statements is provided, covering the topic thoroughly. Viewers learn about the third conditional statement …
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now