Databases
StackOverflow2013
Postsdbo
POHow many Beans should be enough?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow many Beans should be enough?
    primarykey
    data
    text
    <p>I'm a undergrad Student at a German University.<br> I have a team Programming Course .. where we have to use JavaEE/JSF to make a social networking site .. like LinkedIn.<br> Anyway my group has created a lot of beans. Which IMHO is too much .</p> <pre><code> &lt;?xml version='1.0' encoding='UTF-8'?&gt; &lt;!-- =========== FULL CONFIGURATION FILE ================================== --&gt; &lt;faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;SessionBean1&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.SessionBean1&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;session&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;ApplicationBean1&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.ApplicationBean1&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;application&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;RequestBean1&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.RequestBean1&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Hauptseite&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.Hauptseite&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;PasswordVergessen&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.PasswordVergessen&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;registery&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.registery&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Page1&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.Page1&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;validator&gt; &lt;validator-id&gt;login.EmailValidator&lt;/validator-id&gt; &lt;validator-class&gt;Login.EmailValidator&lt;/validator-class&gt; &lt;/validator&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Bewertung&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;group52.infoholders.Bewertung&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Mitarbeiter&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;group52.infoholders.Mitarbeiter&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Nachrichten&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;group52.infoholders.Nachrichten&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;Benutrzer&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;group52.infoholders.Benutzer&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;application&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$MainPage&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.MainPage&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$NavigationBar&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.NavigationBar&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$PartnerProfilePage&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.PartnerProfilePage&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$PartnerProfileChange&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.PartnerProfileChange&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$ProfilePage&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.ProfilePage&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;navigation-rule&gt; &lt;from-view-id&gt;/Page1.jsp&lt;/from-view-id&gt; &lt;navigation-case&gt; &lt;from-outcome&gt;case1&lt;/from-outcome&gt; &lt;to-view-id&gt;/view/MainPage.jsp&lt;/to-view-id&gt; &lt;/navigation-case&gt; &lt;/navigation-rule&gt; &lt;navigation-rule&gt; &lt;from-view-id&gt;/view/MainPage.jsp&lt;/from-view-id&gt; &lt;navigation-case&gt; &lt;from-outcome&gt;case1&lt;/from-outcome&gt; &lt;to-view-id&gt;/view/ProfilePage.jsp&lt;/to-view-id&gt; &lt;/navigation-case&gt; &lt;/navigation-rule&gt; &lt;managed-bean&gt; &lt;managed-bean-name&gt;view$ProfileChange&lt;/managed-bean-name&gt; &lt;managed-bean-class&gt;egispartnerprofile.view.ProfileChange&lt;/managed-bean-class&gt; &lt;managed-bean-scope&gt;request&lt;/managed-bean-scope&gt; &lt;/managed-bean&gt; &lt;/faces-config&gt; </code></pre> <p>Actually : </p> <ul> <li>Ever Site is a Bean</li> <li>We have 3 Application Beans</li> <li>I just use 1 Session Bean</li> </ul> <p>I think they missunderstood the purpose of Beans.(did they? or am I wrong ?!)<br> How can i make them clear ... that 1 Session Bean is ( or could be) enough?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdarkrain
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow many Beans should be enough?
      1. USMike Spross
      1. VTFavorite
    2. VO
      singulars
      1. POHow many Beans should be enough?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSomeones going to have some serious gas problems with all them beans
      singulars
      1. POHow many Beans should be enough?
      1. USJason Watts
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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