Thank you, however, this is exactly what I have done in my code. However, this doesnt seem to work. I am implementing it over a portlet API in Liferay portal server. But as the underlying concept was the same of struts, posted it here. As we are using struts tiles, my code would look like -
<action path="/MyAction"
name="MyForm"
type="com.whatever.MyActionClass">
<forward name="portlet.tiles.url.success" path="portlet.tiles.url.success.definedInTilesdef"/>
<forward name="chainedAction" path="/ChainedAction/edit"/>
<!--
1. we dont have a *.do extension attached, when attached it didnt seem to work,hence added the portlet mode as an extension to the
servlet URL as /<servletname>/edit & /<servletname>/view.
2. All the paths are defined in tiles-def.xml which point to the correspdng
jsp files.
3. for a forward as defined in the chained action above, I presume that it tries to look into the tiles defs for the URL and not look at it as a new action defined in the struts-config.
-->
</action>
<action path="/ChainedAction"
name="MyForm"
scope="request"
type="com.whatever.MyChainedActionClass">
<forward name="portlet.tiles.url.success.chainedAction" path="portlet.tiles.url.success.chainedAction.definedInTilesDef"/>
</action>