Hi! Ajit, I am a junior -junior-junior level prog,maybe should not even consider myself as a programmer as yet,haven't done a single project as yet. Preparing for any interview that MIGHT come up. I read this q on the web . I couldn't get the answer so i asked. Have i done something wrong Sir!. --Praveen
Praveen, No you have not committed a crime. It's just that your question was not very clear to me. In general the number of types of entity beans or the number of entity bean instances is not constrained by anything. Through to the magic of instance pooling, activation and passivation the container is required to juggle any number of entity beans. It is quite obvious though, the more number of bean instances you bring to life, the memory management becomes a challenge. There are several well documented design patterns that teach you how not to map every table to a new entity bean type. By making use of what is known as "coarse grained entity beans" you can reduce the number of bean types. I cannot imagine someone asking such a question in a technical interview. If they do, you now know what to answer Cheers,
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).