Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Use a view scoped bean. It should work. The problems which you describe there suggests that you're binding it to JSTL tags or <code>id</code> or <code>binding</code> attributes. You should not do that on a view scoped bean. See also <a href="http://balusc.blogspot.com/2011/09/communication-in-jsf-20.html#ViewScopedFailsInTagHandlers" rel="nofollow"><code>@ViewScoped</code> fails in tag handlers</a>. Another possible cause is that you're using CDI's <code>@Named</code> to manage the bean instead of JSF's <code>@ManagedBean</code>. That would also explain why <code>@ManagedProperty</code> doesn't work in one of your attempts as it also requires the bean to be managed by JSF's <code>@ManagedBean</code>.</p> <p>As to the master-detail page approach, use a <code>&lt;h:link&gt;</code> with <code>&lt;f:param&gt;</code> in the table page to create view/edit links in the master page.</p> <p>E.g. <code>user/list.xhtml</code></p> <pre class="lang-html prettyprint-override"><code>&lt;h:dataTable value="#{userList.users}" var="user"&gt; &lt;h:column&gt;#{user.id}&lt;/h:column&gt; &lt;h:column&gt;#{user.name}&lt;/h:column&gt; &lt;h:column&gt; &lt;h:link value="Edit" outcome="edit"&gt; &lt;f:param name="id" value="#{user.id}" /&gt; &lt;/h:link&gt; &lt;/h:column&gt; &lt;/h:dataTable&gt; </code></pre> <p>The bean can be just request scoped.</p> <p>Then, in the defail page, which is in this case an edit page, use <code>&lt;f:viewParam&gt;</code> to convert, validate and set the <code>id</code> as <code>User</code>.</p> <p>E.g. <code>user/edit.xhtml</code></p> <pre class="lang-html prettyprint-override"><code>&lt;f:metadata&gt; &lt;f:viewParam name="id" value="#{userEdit.user}" converter="#{userConverter}" converterMessage="Bad request. Unknown user." required="true" requiredMessage="Bad request. Please use a link from within the system." /&gt; &lt;/f:metadata&gt; &lt;h:messages /&gt; &lt;h:link value="Back to all users" outcome="users" /&gt; &lt;h:form id="user" rendered="#{not empty userEdit.user}"&gt; &lt;h:inputText value="#{userEdit.user.name}" required="true" /&gt; ... &lt;h:commandButton value="Save" action="#{userEdit.save}"&gt; &lt;f:ajax execute="@form" render="@form" /&gt; &lt;/h:commandButton&gt; &lt;/h:form&gt; </code></pre> <p>Use a <code>@ViewScoped</code> bean to hold the data, service and action methods:</p> <pre><code>@ManagedBean @ViewScoped public class UserEdit { private User user; @EJB private UserService service; public String save() { service.save(user); return "users"; } // Getter+setter. } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POElegant handling of attributes without a session bean
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBalusC
    1. USBalusC
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POElegant handling of attributes without a session bean
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COEven in this case, is `@ViewScoped` really a good solution? Though it takes a little more work, I've typically favored `@ConversationScoped` to avoid problems with back-button use, multiple tabs/windows, and view-scoped data expiring. I need to write a proper blog post about my thoughts, but for now I'll reference a [previous answer](http://stackoverflow.com/questions/10098528/jsf-2-0-viewscoped-redirect-navigation-to-target-blank/10108609#10108609) of mine.
      singulars
      1. PO
      1. USBrian
    2. COThanks for your post @BalusC! Always a pleasure to read your answers. As for the options, we're not doing any binding to the specific tags that the link on your blog states, nor are we binding tags directly to a bean. can the problem be caused by using some EL expressions on "rendered" attributes? We do it to adjust the form depending on the case.
      singulars
      1. PO
      1. USGamb
    3. CODoes the `@ViewScoped` also fail on a basic hello world page with a single submit button wherein the action method returns `null` or `void`?
      singulars
      1. PO
      1. USBalusC
 

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