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 :)


I didn't add the configuration option, because I thought that a
mixture might be confusing.

Hmm, maybe. The usecase configuration we have so far is used in the flowscript, not in the Java code IIUC. Is this what you mean by a confusing mixture, if the configuration were also used in the Java code ?

> But maybe it would make sense to configure
the exit usecase name in cocoon.xconf (which would mean that all usecase
names are configured there) and the parameters in the Java code
(parameters are generally declared in the code)?

I guess it depends what the function of the parameters is.
So far the usecase configuration says something about how this usecase is composed within the CMS (for example, is it part of a group of usecases). I think the knowledge of "where to go when this usecase is finished" should also be in the usecase configuration.

(At least, IMO it shouldn't be within the Java implementation, maybe it should be within a separate "usecase manager configuration file", where all usecases, how they are assembled, and how they may refer to each other might be configured; independently of the cocoon.xconf. I don't think we absolutely need this at this time but maybe a thing to consider for the future ?)


--
Wolfgang

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

Reply via email to