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

        Hello,

        I have updated Seam + Maven integration to Seam 1.2.0

        See http://software.softeu.cz/seam/ .

        Petr Ferschmann

        • 16. Re: Seam 1.2 released

           

          "fers" wrote:
          I have updated Seam + Maven integration to Seam 1.2.0
          See http://software.softeu.cz/seam/

          Minor detail: the first bullet on the above URL states:
          - Provide all jboss-seam jars and poms for download (DO

          Is something missing after the "(DO", or is the "(DO" is some leftover?


          • 17. Re: Seam 1.2 released

            To avbentem: thank you. I was marking which parts were finished (DONE). But now all parts are at least partly implemented, so I have now page with issues (http://software.softeu.cz/seam/issues.html).

            Petr

            • 18. Re: Seam 1.2 released
              gavin.king
              • 19. Re: Seam 1.2 released
                monkeyden

                man, you guys are cranking. I'm glad I got on board early.

                • 20. Re: Seam 1.2 released
                  tony.herstell1

                  I only have 10Gb limit a month on my ISP Plan. ;)

                  These releases are coming thick and fast which is GREAT :).

                  MyEclipse download was getting out of control at over 150MB (which now includes the complete Stack including Eclipse and MyEclipse in an ALL-In-ONE!)... and they now use some UBER compression tool to squeeze it.

                  I wonder how much the 66MB could be squeezed into!

                  • 21. Re: Seam 1.2 released
                    mariuszs

                    pages.xml ending conversation is broken with 1.2, only works with plain navigation.xml!

                    • 22. Re: Seam 1.2 released

                      Hi,

                      don't know if it has been corrected or not. We just detected a problem in org.jboss.seam.ui.UISelectItems. There's a

                      private static final String NO_SELECTION_VALUE = null;

                      defined which should be replaced by

                      import static org.jboss.seam.ui.NoSelectionConverter.NO_SELECTION_VALUE;

                      Because:
                      SelectItems class always uses 'null' as value of NullableSelectItem. Therefore during conversion this is not recognized by the NoSelectionConverter.

                      Without this change the s:selectItems will not work with noSelectionLabel set.

                      • 23. Re: Seam 1.2 released
                        pmuir

                        No.

                        Render phase:
                        1) UISelectItems adds the NullableSelectItem to the list
                        2) NoSelectionConverter runs getAsString, the NullableSelectItem has a value null so NoSelectionConverter.NO_SELECTION_VALUE is returned

                        Submit phase:
                        1) NoSelectionConverter runs getAsObject, the value is NoSelectionConverter.NO_SELECTION_VALUE, so null is returned
                        2) Validators are run, if required=true, then, as the value is null, validation will fail
                        3) The model is updated with a null value.

                        I can't see a problem - the UI example has noSelectionLabel on both components with required=true and not and the behaviour I describe happens.

                        What problem are you seeing?

                        • 24. Re: Seam 1.2 released

                          Hi,

                          thanks for your answer. Here's some code:

                          Page:

                          <ice:selectOneMenu id="projectselection" value="#{projectControllingActions.selectedProject}"
                           valueChangeListener="#{projectControllingActions.projectSelectionChanged}"
                           partialSubmit="true" required="true">
                          
                           <s:selectItems value="#{projectControllingActions.projects}" var="project"
                           label="#{project.name}" noSelectionLabel="#{apc_messages.please_select}"/>
                           <s:convertEntity />
                          
                          </ice:selectOneMenu>
                          
                          <ice:selectOneMenu id="taskselection" value="#{projectControllingActions.selectedTask}">
                           <s:selectItems value="#{projectControllingActions.tasks}" var="task"
                           label="#{task.description}" noSelectionLabel="#{apc_messages.please_select}"/>
                           <s:convertEntity />
                          </ice:selectOneMenu>


                          When the page is rendered the first time both selectOneMenus show the noSelectionLabel. Then I change the value of "projectselection" and since there's a partial submit, the lifecycle is invoked. The "projectselection" value is converted correctly. But the conversion of the noSelectionLabel in "taskselection" throws an exception because "null" can't be converted to "Integer". Inspecting the HTML page source I saw that the noSelectionLabel of the selectOneMenus were represented by an empty string.

                          Perhaps it's a compatibility error with ICEfaces 1.5.3???

                          Thanks in advance
                          Newlukai

                          • 25. Re: Seam 1.2 released
                            pmuir

                            Quite possibly, I've never personally tested this with icefaces. The easiest way to check is just to swap in a normal h:selectOneMenu and see whether it works as expected. Perhaps ask over at icesfaces?

                            • 26. Re: Seam 1.2 released

                              We tried this with normal h:selectOneMenus. But it's the same exception ...

                              So we thought the bug has to be in Seam. And with the mentioned workaround this app works as it should.

                              Hmm. I'm wondering which framework delivers the converters, since the excpetion tells that a conversion from null to Integer failed.

                              • 27. Re: Seam 1.2 released
                                pmuir

                                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...

                                • 28. Re: Seam 1.2 released
                                  tedgoddard

                                  As of ICEfaces 1.6.0 DR#3, substantial progress has been made with Seam/ICEfaces integration. In general, it is enough to simply add the ICEfaces .jar files to turn your Seam application into an Ajax application. Please download the latest ICEfaces release here:

                                  http://icefaces.org/main/downloads/os-downloads.iface

                                  Of particular interest are Ajax Push and seam-gen. ICEfaces Ajax Push is now working with Seam applications (this allows you to update the browser page under application control; no interaction from the user is required). To generate an ICEfaces application with seam-gen, please download the recently added ICEfaces seam-gen bundle

                                  http://icefaces.org/main/downloads/project-downloads.iface

                                  and unzip it at the root of your Seam 1.2.1 installation. You will then be able to generate ICEfaces Seam applications from within the icefaces-seam-gen directory. Over time we will be enhancing these templates to take full advantage of ICEfaces, allowing you to automatically generate a full CRUD application with a single-page Ajax user interface.

                                  • 29. Re: Seam 1.2 released

                                    Can ICEfaces 1.6 and Richfaces be used in the same application?