Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As to the concrete question, just split the bean in 2 separate beans. As you're apparently managing beans by Spring instead of by JSF or CDI for some unclear reason, you can use <code>@Autowired</code> to inject the one bean as a property of the other bean. </p> <pre><code>@Named @Scope("request") public class Login implements Serializable { private List&lt;Role&gt; roles; @AutoWired private User user; public String submit() { UserTable userTable = user.getTable(); // ... } // ... } </code></pre> <pre class="lang-java prettyprint-override"><code>@Named @Scope("session") public class User implements Serializable { private UserTable table; // ... } </code></pre> <p>If you were managing the beans by JSF <code>@ManagedBean</code>, you could use <code>@ManagedProperty</code> for that. If you were managing the beans by CDI <code>@Named</code>, you could use <code>@Inject</code> for that.</p> <hr> <p>Coming back to the concrete functional requirement,</p> <blockquote> <p>And I feel like roleList should not be in session scope, since it will be populated in a combo box during registration page only. I guess request scope is enough.</p> </blockquote> <p>That's a pretty weak reason. If it were me, I'd have placed it in the application scope. The role list is the same for every single request/session anyway, right? You don't need to reload/repopulate it on every request then, unless you've a really, really low memory footprint.</p> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/7031885/how-to-choose-the-right-bean-scope/7031941#7031941">How to choose the right bean scope?</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POJSF managedbean has variables with different scope
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJSF managedbean has variables with different scope
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThat is a very good answer. So I should split the beans. Is it possible to have instance variables with different scope in a single ManagedBean? I used to think that login, register, logout functions are related to User, thats why I should put all these functions in a single UserManagedBean. Is there any good practices to split the functions and managed beans? Absolutely roleList should be in application scope for my case. Thanks much.
      singulars
      1. PO
      1. USSasue Nie
    2. COThat's tight coupling. For starters, use a separate request/view scoped bean per `<h:form>`. It'll automagically end up in clean code. Note that I've updated my answer with a link "How to choose the right bean scope?", I recommend to give it a read.
      singulars
      1. PO
      1. USBalusC
    3. COI read somewhere that by using JSR330 in Spring, I could reuse that managedbean in another CDI environment. Thats why I am mixing Spring with JSR330. Do you have any comment on that?
      singulars
      1. PO
      1. USSasue Nie
 

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