Antonio -- 

Can you explain this using this example?

                <action name="course_*" method="{1}" class="course">
                        <result name="input" type="tiles">course.page</result>
                </action>

My class "course" is wired up in Spring.  The course.page tiles definition
cab be found below.  The course.jsp allows CRUD operations for a Course. 
All four methods in the class return INPUT.  An intial request of this page
via action=course_input invokes Spring and ultimately display my composite
page.  The problem is that as items are added and the save() method returns
INPUT, the beans are not renewed via Spring.  However, the other methods
returning INPUT do invoke Spring and renew the objects behind the page!  I
don't understand how each of the CRUD methods return INPUT, yet only the
save() method is skipping the Spring step.  I'll add that the save() Action
method is invoked through the form, while the other three methods are
invoked via links.  I have also included the course.jsp where you will find
this code.  There seems to be a different lifecycle that is based on the
invocation technique.


  <definition name="standard" template="/pages/base.jsp">
          <put name="title" value="Standard Title for base.jsp" />
          <put name="header" value="/pages/header.jsp" />
          <put name="navigation" value="/pages/navigation.jsp" />         
          <put name="body"   value="/pages/body.jsp" />
          <put name="footer" value="/pages/footer.jsp" />
  </definition>
  <definition name="course.page" extends="standard"
preparer="controller.CourseController">    
          <put name="title" value="Course" />     
          <put name="body"   value="/pages/course.jsp" />
  </definition>  

        <body>
                <s:form >
                        <s:textfield name="course.text" key="course.add.text" 
size="40" />
                        <s:submit key="label.save" action="course_save"/>
                </s:form>

                <table border="1">
                        <s:iterator value="#request.list">
                                <tr>
                                        <td>
                                                <s:property value="id" />
                                        </td>
                                        <td>
                                                <input type="text" 
name="course.text" size="40"
                                                        value="<s:property 
value="text"/>">
                                        </td>
                                        <td>
                                                <s:url id="url" 
action="course_remove">
                                                        <s:param 
name="course.id">
                                                                <s:property 
value="id" />
                                                        </s:param>
                                                </s:url>
                                                <s:a href="%{url}">Remove</s:a>
                                        </td>
                                </tr>

                        </s:iterator>
                </table>
        </body>
-- 
View this message in context: 
http://www.nabble.com/Tiles-2-Lifecycycle-tf3561248.html#a9981576
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to