Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would say that simon has answered very aptly to your question and leaves little ground to cover up. In addition to all the said things; I would just say that focus should be on OO design as that should really control the number of beans and not a rudimentary figure in head.</p> <p>A tightly coupled 3 bean code is as bad as a code containing 2000 beans with no real purpose. It's the design that must guide you. </p> <p>I may deviate from point; but if you'd really like to see how your beans should be controlled then read "<a href="http://java.dzone.com/reviews/draf-book-review-the-thoughtwo" rel="nofollow noreferrer">The Thoughtworks Anthalogy</a>" chapter "Object Calisthenics" essay written by Jeff Bay. The simple rules for programming is (Some of them even unbelieveable) :) 1. Use only one level of indentation per method 2. Don't use the else keyword 3. Wrap all primitives and String 4. Use only one dot per line 5. Don't abbreviate 6. Keep entities small 7. Don't use any classes with more than 2 instance variables 8. Use first class collection 9. Don't use any getter setter properties. (I know it won't work JSF way)</p> <p>But with these rules you'll be posed with some real challenges. But you'll see that even though number of beans is huge, you have perfectly well designed code. :)</p> <p>In short, I agree that you should move away from anti-pattern but most of the time one session bean is enough and it's good to have all beans with request scope. Number of beans is immaterial as long as you have well designed and flexible code. Cheers.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload