1 2 3 Previous Next 32 Replies Latest reply on May 8, 2007 10:37 AM by Jens Weintraut Go to original post
      • 30. Re: Seam 1.2 released
        tedgoddard Newbie

        ICEfaces 1.6 and Richfaces cannot currently be used on the same page. It may be possible with the right configuration to use ICEfaces and Richfaces on different pages within the same application.

        • 31. Re: Seam 1.2 released
          Leo Baschy Novice

          Can that be fixed in the future?

          What is it? Name conflicts?

          Sure, some combinations might be impossible or to too hard to work out.

          But some combinations should be possible.

          Components are supposed to be plug-and-play, as much as reasonably possible.

          • 32. Re: Seam 1.2 released
            Jens Weintraut Apprentice

             

            "petemuir" wrote:
            Post the exception :), see if it pins things down...

            If you submit a testcase to JIRA (needs to be simple and have just enough code to demonstrate the problem) I'll take a look at it. You could probably take the ui example and manipulate it...


            Hi Peter,

            I tested the ui exmaple. It works as expected.

            Today I tried to modify the ui example to work with ICEfaces. It's not complete, since the pages aren't rendered correctly. But there's rendered enough to see that the value of the noSelection-option is an empty string instead of "org.jboss.seam.ui.NoSelectionConverter.noSelectionValue".

            Here's the code of that page:
            <ui:composition xmlns="http://www.w3.org/1999/xhtml"
             xmlns:ui="http://java.sun.com/jsf/facelets"
             xmlns:f="http://java.sun.com/jsf/core"
             xmlns:h="http://java.sun.com/jsf/html"
             xmlns:s="http://jboss.com/products/seam/taglib"
             xmlns:ice="http://www.icesoft.com/icefaces/component"
             template="template.xhtml"
             >
             <ui:param name="tagName" value="s:selectItems" />
             <ui:define name="body">
             <p>This example shows example usage of the <code>s:selectItems</code> tag being used for CRUD on a <code>Person</code> entity.</p>
             <p>The example also uses:</p>
             <ul>
             <li><code>s:span</code></li>
             <li><code>s:convertEnum</code></li>
             <li><code>s:message</code></li>
             <li><code>s:decorate</code></li>
             <li><code>s:link</code></li>
             <li><code>s:conversationPropagation</code></li>
             <li><code>s:decorate</code></li>
             </ul>
            
             <ice:form>
             <s:decorate template="decorateField.xhtml">
             <ui:define name="label">Title</ui:define>
             <h:selectOneMenu value="#{person.honorific}">
             <s:selectItems value="#{honorifics}" var="honorific" label="#{honorific.label}" noSelectionLabel="Please select" />
             <s:convertEnum />
             </h:selectOneMenu>
             </s:decorate>
            
             <s:decorate template="decorateField.xhtml">
             <ui:define name="label">Name</ui:define>
             <ui:define name="description">Enter your name as it appears on your passport</ui:define>
             <h:inputText value="#{person.name}" required="true" />
             </s:decorate>
            
             <s:decorate template="decorateField.xhtml">
             <ui:define name="label">Continent of Birth</ui:define>
             <ice:selectOneMenu value="#{personHome.instance.continent}" required="true" id="continent">
             <s:selectItems value="#{continents.resultList}" var="continent" label="#{continent.name}" noSelectionLabel="Please Select..."/>
             <s:convertEntity />
             </ice:selectOneMenu>
             </s:decorate>


            If I had a smooth running example I would post it. Perhaps you've better luck switching from ajax4jsf to ICEfaces in the ui example.

            Thanks in advance
            Newlukai

            1 2 3 Previous Next