Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This construct works fine for me.</p> <p>As mentioned in among others <a href="http://showcase.omnifaces.org/converters/SelectItemsConverter" rel="nofollow">the showcase page</a>, the <code>omnifaces.SelectItemsConverter</code> uses by default the <code>toString()</code> representation of the complex object as converted item value. So if you didn't override the <code>toString()</code> method (so that it still defaults to <code>com.example.SomeClass@hashcode</code> which changes on every instantiation) and the <code>#{item}</code> managed bean is request scoped, then the list would basically be changing on every HTTP request. This would cause a "Validation Error: Value is not valid" error. </p> <p>If you add</p> <pre><code>&lt;p:messages autoUpdate="true" /&gt; </code></pre> <p>or</p> <pre><code>&lt;p:growl autoUpdate="true" /&gt; </code></pre> <p>so that you get all (missing) validation/conversion messages in the UI, then you should have noticed it.</p> <p>In order to utilize the <code>omnifaces.SelectItemsConverter</code> at its best, you should override the <code>toString()</code> method accordingly so that it returns a fixed and unique representation of the complex object. E.g.</p> <pre><code>@Override public String toString() { return "Extra[id=" + id + "]"; } </code></pre> <p>Alternatively, you could put the <code>#{item}</code> managed bean in a broader scope, such as the view scope.</p> <hr> <p><strong>Update</strong> as to your update, you're binding the selected values of <em>all</em> checkboxgroups to <strong>one and same</strong> bean property <code>#{cartBean.selectedExtras}</code>. This way every iteration overrides the property with the values from the current iteration round as long as until you end up with the values of the last iteration. If you've placed a debug breakpoint on the setter, you'd have noticed that.</p> <p>This is not right. They should each point to a different bean property. Technically, you should have a <code>#{item.selectedExtras}</code> as property. But I think that this makes no sense in your current design. Better would be to make the <code>#{cartBean.selectedExtras}</code> an <code>List&lt;Item[]&gt;</code> or <code>Item[][]</code>. This way you can get them to set based on the iteration index as follows:</p> <pre><code>&lt;ui:repeat var="item" value="#{category.items}" varStatus="iteration"&gt; &lt;p:selectManyCheckbox id="extraCheckbox" value="#{cartBean.selectedExtras[iteration.index]}" layout="pageDirection" converter="omnifaces.SelectItemsConverter"&gt; &lt;f:selectItems value="#{item.items5}" var="extra" itemLabel="#{extra.name}"/&gt; &lt;/p:selectManyCheckbox&gt; &lt;/ui:repeat&gt; </code></pre> <p>In case of <code>List&lt;Item[]&gt;</code> you only need to make sure that you preinitialize <code>selectedExtras</code> with nulls as many times as there are <code>#{category.items}</code> in bean's (post)constructor.</p> <pre><code>for (Item item : category.getItems()) { selectedExtras.add(null); } </code></pre> <p>In case of <code>Item[][]</code>, you can suffice with </p> <pre><code>selectedExtras = new Item[category.getItems().size()]; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPrimefaces ManyCheckbox inside ui:repeat calls setter method only for last loop
      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. POPrimefaces ManyCheckbox inside ui:repeat calls setter method only for last loop
      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
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for your efforts. Probably I really did post to little code. Actually the `#{item}` in this case is a variable from a higher `<ui:repeat>` - there do not seem to be any scope related issues. And I noticed, that the problem is not really about many checkboxes but just about my first two entries having checkboxes: The setter methods just aren't called on the first two entries. The other (also) `<ui:repeat>`-created entries and their checkboxes work fine (setter methods called).
      singulars
      1. PO
      1. USLester
    2. COHmm... it's not the first two `<ui:repeat>`-created entries for which the setter not called: It's only the last entry for which the setter method is called. That's a hint... but I still didn't find the problem.
      singulars
      1. PO
      1. USLester
    3. COI edited my question. I'm really sorry for requiring your time without providing enough information. I was not clear about the context of the problem and I am always worried to post masses of unrelated code.
      singulars
      1. PO
      1. USLester
 

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