> Well, I would like to have just one graph instance (probably a BMP > Entity Bean as you suggested), because it can be very heavy in > consumption of memory, and I cannot permit that the container create > more than one instance like stateless session beans instances.
Rule 1 about EJB introductions - dont try to do the container's job. The answer to your question is "it depends". It you're running a default JBoss configuration then yes, there will only be one instance of the bean. > So I > would like that session beans make requests to the initialized graph > data of the entity bean (always the same). And, I can tell that the > initialize time of a graph would be a long and not acceptable to answer > a request in real time. So besides the large amount of memory a graph > (~entity bean) would need, the initialize time would be not satisfactory > to handle requests each time a entity bean would be created. is it _really_ that much data? what is it, 2 meg? Anyway, yes - caching is one of the many features that an EJB container will provide. Be sure to select cache-option "A" (assuming you have exclusive access to the database). > Probably, I would map my graph data to the session beans which would run > the Dijkstra algorithm. > > So, can you point me some topics to configure a BMP Entity Bean to be > just instance bean? I'm using JBOSS 3.x. default config should do what you want. Have a look at the JBoss beginners guide, and then buy the JBoss docs (they're cheap, and worthwhile). hth dim =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
