Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by GregorRothfuss: http://wiki.apache.org/lenya/LenyaUsecases The comment on the change is: moved to lenya docs ------------------------------------------------------------------------------ - = Introduction = + deleted - == Links == - - In Lenya 1.4, there is a [http://lenya.apache.org/1_4/concepts/usecase-framework/index.html Usecase Framework] to implement usecases based on flow, JX templates, and Java classes for business logic. - - == Where the term usecase comes from == - - == How usecases are implemented in Lenya == - - * matcher - * steps - - = Usecase Sitemap Structure = - - == Publication Specific Usecases == - - A publication can ''extend'' the ''core'' usecases provided by the Lenya core by introducing additional usecases. The {{{lenya/usecase.xmap}}} file is prepared to mount publication specific usecases from files called {{{usecase-xxxx.xmap}}} in the publication root directory. - - Remark: - - Make sure you understand that inside a publication specific usecase all pathes are relative to the publication, not to the Lenya core anymore. If in the core usecase.xmap you had to write - - {{{ - <map:match pattern="*/authoring/**.txt"> - }}} - - the same matcher in a local, publication specific usecase would have to be - - {{{ - <map:match pattern="authoring/**.txt"> - }}} - - Please also note that because there is one less wildcard, {{{ {2} }}} in the global usecase.xmap becomes {{{ {1} }}} in the local, publication specific sitemap. - - == Usecases versus FlowScript == - - The usecase concept in Lenya 1.2 is inferior to FlowScript. - Lenya 1.4-dev contains a simple [http://lenya.apache.org/1_4/concepts/usecase-framework/index.html Usecase Framework] for writing usecases using Flow. - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
