J. Wolfgang Kaltz schrieb:
Andreas Hartmann schrieb:
(...)
Actually that was my first idea too (with a slightly different syntax):
> <component-instance name="admin.deleteGroup" logger="lenya.admin"
> class="org.apache.lenya.cms.ac.usecases.DeleteGroup">
> <view template="admin/deleteGroup" menu="true"
exit-usecase="admin.groups">
> <parameter name="tab" value="groups"/>
> </view>
> </component-instance>
But when I noticed that dynamic parameters have to be added in some
cases, I realized that we need a Java interface to this functionality
anyway.
Do you mean that the exit-usecase is sometimes a dynamic thing, or are
you referring to other types of parameters ?
Please give an example :)
OK, I should have read the commit mailing list first, sorry about that.
IIUC you meant that the knowledge of which usecase to go upon exit is
not always sufficient; in some cases you need to pass a parameter as
well so that the request can be built correctly. For example, after the
"add group usecase" we want to go to the "group profile" usecase, for
the group id we just added.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
