StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I don't do ICEFaces, but you're encountering basically <a href="https://stackoverflow.com/questions/4022193/is-there-a-way-to-create-dynamically-richtab-elements">the same problem</a> as RichFaces has with its <code><rich:tab></code>. As there exist no hypothetical <code><rich:tabs></code> (like as <code><rich:columns></code> which would be the dynamic variant of <code><rich:column></code>/<code><h:column></code>), one would have to use the view build time JSTL <code><c:forEach></code> tag to prepare the JSF view with those tags. You could apply the same on your ICEFaces page:</p> <pre><code><ace:tabSet clientSide="true"> <c:forEach items="#{bean.tabs}" var="tab"> <ace:tabPane> <f:facet name="label">#{tab.label}</f:facet> <h:outputText value="#{tab.name}"></h:outputText> </ace:tabPane> </c:forEach> </ace:tabSet> </code></pre> <p>Note that this will only fail if <code>#{bean}</code> is not a real managed bean, but an expression which in turn depends on an evaluation of another JSF component, such as <code><h:dataTable var="bean"></code>.</p> <p>The <code><ui:repeat></code> won't work as it's a render-time tag. It won't dynamically generate multiple JSF components before the JSF component tree is been built.</p> <h3>See also:</h3> <ul> <li><a href="http://jira.icefaces.org/browse/ICE-6527" rel="nofollow noreferrer">ICEFaces issue 6527 - Dynamically adding/removing <code>ace:tabPane</code> Results in <code>ace:tabset</code> Retrieving Entire Tabset Content</a></li> <li><a href="http://jira.icefaces.org/browse/ICE-6560;jsessionid=927D82111E1B79775EF7785D2A682A85?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel" rel="nofollow noreferrer">ICEFaces issue 6560 - New <code>ace:tabs</code> dynamic tabset component</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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