[EMAIL PROTECTED] schrieb:
+ /**
+ * Sets the exit usecase of this usecase, i.e. the usecase that should be
entered when this
+ * usecase is finished.
+ * @param usecaseName The name of the exit usecase.
+ * @param parameters Parameters to pass to the usecase or
<code>null</code> if no parameters
+ * should be passed.
+ */
protected void setExitUsecase(String usecaseName, Map parameters) {
Regarding the exit usecase :
would it be possible to configure the exit usecase within the usecase
configuration, instead of the source code ?
For example, the delete group usecase has this code
setExitUsecase("admin.groups", null);
So this means the source code is dependant on the usecase name as
defined in cocoon.xconf. If we can avoid that, I think we should.
If we could configure it instead in the usecase configuration, for
example something like
<component-instance name="admin.deleteGroup" logger="lenya.admin"
class="org.apache.lenya.cms.ac.usecases.DeleteGroup">
<view template="admin/deleteGroup" menu="true">
<parameter name="tab" value="groups"/>
</view>
<exit name="admin.groups"/>
</component-instance>
that would avoid the Java code hard-wiring the name of the exit usecase.
That does make sense or am I missing something ?
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
