RE: Form accessing a JSP Action
Apparently this solution may work, but found that my hello.jsp which should invoke the method doUpdate in MyJSPAction does not work, well doUpdate() is invoked but buildNormalContext() as well getting into an infinite loop. In fact, doUpdate is invoked even if i do not call it myself from a JSP. If I change doUpdate to any other name it does not even get invoked. Is doUpdate a method in JspPortletAction? Cannot i use any other method name and invoke it from a JSP template? Many thanks. -Mensaje original- De: Oscar Ruiz [mailto:[EMAIL PROTECTED] Enviado el: martes, 04 de mayo de 2004 17:57 Para: 'Jetspeed Users List' Asunto: RE: Form accessing a JSP Action Many thanks, i'll test that. -Mensaje original- De: Raphaël Luta [mailto:[EMAIL PROTECTED] Enviado el: martes, 04 de mayo de 2004 17:36 Para: Jetspeed Users List Asunto: Re: Form accessing a JSP Action Le 4 mai 04, à 13:12, Oscar Ruiz a écrit : Hi all, I've got a problem while calling a JSP action from a JSP template. I've got a JSP Portlet identified by: Action: portlet.MyJSPAction Template: test.jsp Another JSP Porlet identified by: Action: none Template: hello.jsp In fact what I want to do (do not know if possible) is execute hello.jsp, from there invoke MyJSPAction and return test.jsp as a result of the invocation. That's to complete a JSP flow. View Controller Hello.jsp - MyJSPAction Test.jsp - Is that possible?, shall I use the same JSP with different action method calls? You should probably only define 1 portlet: Name: MyJSPPortlet Action: portlets.MyJSpAction Template: hello.jsp ResultTemplate: test.jsp In your Action processing code, set manually the template you want to display based on your portlet state using setTemplate(). Jetspeed does not automate anything in flow processing so your controller code needs to explicitely set the next template to use based on its current state. -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterprise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form accessing a JSP Action
Le 4 mai 04, à 13:12, Oscar Ruiz a écrit : Hi all, I've got a problem while calling a JSP action from a JSP template. I've got a JSP Portlet identified by: Action: portlet.MyJSPAction Template: test.jsp Another JSP Porlet identified by: Action: none Template: hello.jsp In fact what I want to do (do not know if possible) is execute hello.jsp, from there invoke MyJSPAction and return test.jsp as a result of the invocation. That's to complete a JSP flow. View Controller Hello.jsp - MyJSPAction Test.jsp - Is that possible?, shall I use the same JSP with different action method calls? You should probably only define 1 portlet: Name: MyJSPPortlet Action: portlets.MyJSpAction Template: hello.jsp ResultTemplate: test.jsp In your Action processing code, set manually the template you want to display based on your portlet state using setTemplate(). Jetspeed does not automate anything in flow processing so your controller code needs to explicitely set the next template to use based on its current state. -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterprise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Form accessing a JSP Action
Many thanks, i'll test that. -Mensaje original- De: Raphaël Luta [mailto:[EMAIL PROTECTED] Enviado el: martes, 04 de mayo de 2004 17:36 Para: Jetspeed Users List Asunto: Re: Form accessing a JSP Action Le 4 mai 04, à 13:12, Oscar Ruiz a écrit : Hi all, I've got a problem while calling a JSP action from a JSP template. I've got a JSP Portlet identified by: Action: portlet.MyJSPAction Template: test.jsp Another JSP Porlet identified by: Action: none Template: hello.jsp In fact what I want to do (do not know if possible) is execute hello.jsp, from there invoke MyJSPAction and return test.jsp as a result of the invocation. That's to complete a JSP flow. View Controller Hello.jsp - MyJSPAction Test.jsp - Is that possible?, shall I use the same JSP with different action method calls? You should probably only define 1 portlet: Name: MyJSPPortlet Action: portlets.MyJSpAction Template: hello.jsp ResultTemplate: test.jsp In your Action processing code, set manually the template you want to display based on your portlet state using setTemplate(). Jetspeed does not automate anything in flow processing so your controller code needs to explicitely set the next template to use based on its current state. -- Raphaël Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterprise Portal in Java http://portals.apache.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
