You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by st...@outerthought.org on 2003/02/04 10:00:05 UTC
[WIKI-UPDATE] CocoonCompetenceCenter BeginnerSimpleWebappTutorial BeginnerSWTutorial_01 Tue Feb 4 10:00:05 2003
Page: http://wiki.cocoondev.org/Wiki.jsp?page=CocoonCompetenceCenter, version: 13 on Tue Feb 4 08:58:39 2003 by Dabbous
- [setup cocoon in 15 minutes|beginnerInstallation]\\
+ [setup cocoon in 15 minutes|beginnerInstallation] (cookbook)\\
? +++++++++++
- [setup a cocoon application in 1 day|beginnerSimpleWebappTutorial]
+ [setup a cocoon application in 1 day|beginnerSimpleWebappTutorial] (tutorial under construction)
? ++++++++++++++++++++++++++++++
- [setup tomcat in 15 minutes(unix)|beginnerInstallTomcatUnix]\\
+ [setup tomcat in 15 minutes(unix)|beginnerInstallTomcatUnix] (cookbook)\\
? +++++++++++
- [setup tomcat in 15 minutes(windows)|beginnerInstallTomcatWindows]\\
+ [setup tomcat in 15 minutes(windows)|beginnerInstallTomcatWindows] (cookbook)\\
? +++++++++++
Page: http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappTutorial, version: 5 on Tue Feb 4 08:53:03 2003 by Dabbous
- !!The use case
+ You may now proceed to the [Tutorial|BeginnerSWTutorial_01] ...
+ ----
- We need to serve a hierarchically structured website.
- The website contains only one sort of documents. These
- documents are all written in XML notation using the
- same XSCHEMA (or DTD). Every page shall show where in the
- hierarchie the current document is laying, which documents
- are available in the same hierarchical depths and which #
- documents refer directly to the current document as
- "child documents". The whole website shall be separated
- into subhirarchies containing different languages.
- The layout and most of the used graphical material
- shall be kept in one common place and used all over the
- site.
-
- The whole application shall be easy maintainable,
- expandable and scalable. Special care shall
- be taken, that page layout can be modified with as
- little effort as possible. It shall further be
- possible to directly use XHTML fragments within the
- documentation. The editors may use any convenient
- XML editor for their authoring work.
-
- This "Pflichtenheft" (fixme) is complex enough to
- be of certain interest, but not too complex so that
- we can show you the nuts and bolts in detail.
-
- Let's start the tutorial.
-
- !! I. About the heart of cocoon "sitemap.xconf"
-
- The sitemap is the place where you specify, what
- Cocoon shall do when a particular URL has been typed
- in from a Webbrowser.
-
- !submounting
-
- {{{
- <!-- Basic Website pipeline -->
- <map:pipeline>
-
- <!--
- <map:match pattern="">
- <map:redirect-to session="false" uri="en/index.page"/>
- </map:match>
-
- <map:match pattern="en">
- <map:redirect-to session="false" uri="en/index.page"/>
- </map:match>
-
- <map:match pattern="en/">
- <map:redirect-to session="false" uri="en/index.page"/>
- </map:match>
-
- <map:match pattern="*/**">
- <map:mount check-reload="yes"
- reload-method="synchron"
- src="{1}/"
- uri-prefix="{1}"/>
- </map:match>
-
- </map:pipeline>
- }}}
-
Page: http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSWTutorial_01, version: 1 on Tue Feb 4 08:57:17 2003 by Dabbous
New page created:
+ !!Creating a simple Webapplication (Tutorial, part I)
+ - TARGET-AUDIENCE: __*beginner*__ advanced expert\\
+ - COCOON-RELEASES: __2.0.3__, __2.0.4__\\
+ - DOCUMENT-STATUS: __*draft*__ reviewed released\\
+ !!! NOTE: Im currently working on this tutorial. Please don't use.
+ ----
+ !!The use case
+
+ We need to serve a hierarchically structured website.
+ The website contains only one sort of documents. These
+ documents are all written in XML notation using the
+ same XSCHEMA (or DTD). Every page shall show where in the
+ hierarchie the current document is laying, which documents
+ are available in the same hierarchical depths and which #
+ documents refer directly to the current document as
+ "child documents". The whole website shall be separated
+ into subhirarchies containing different languages.
+ The layout and most of the used graphical material
+ shall be kept in one common place and used all over the
+ site.
+
+ The whole application shall be easy maintainable,
+ expandable and scalable. Special care shall
+ be taken, that page layout can be modified with as
+ little effort as possible. It shall further be
+ possible to directly use XHTML fragments within the
+ documentation. The editors may use any convenient
+ XML editor for their authoring work.
+
+ This "Pflichtenheft" (fixme) is complex enough to
+ be of certain interest, but not too complex so that
+ we can show you the nuts and bolts in detail.
+
+
+ !! I. About the heart of cocoon "sitemap.xconf"
+
+ The sitemap is the place where you specify, what
+ Cocoon shall do when a particular URL has been typed
+ in from a Webbrowser.
+
+ !submounting
+
+ {{{
+ <!-- Basic Website pipeline -->
+ <map:pipeline>
+
+ <!--
+ <map:match pattern="">
+ <map:redirect-to session="false" uri="en/index.page"/>
+ </map:match>
+
+ <map:match pattern="en">
+ <map:redirect-to session="false" uri="en/index.page"/>
+ </map:match>
+
+ <map:match pattern="en/">
+ <map:redirect-to session="false" uri="en/index.page"/>
+ </map:match>
+
+ <map:match pattern="*/**">
+ <map:mount check-reload="yes"
+ reload-method="synchron"
+ src="{1}/"
+ uri-prefix="{1}"/>
+ </map:match>
+
+ </map:pipeline>
+ }}}
+ ----
+ ! page metadata
+ - AUTHOR: Hussayn Dabbous\\
+ - AUTHOR-CONTACT: [hussayn.dabbous@saxess.com|mailto:hussayn.dabbous@saxess.com]\\
+ - REVIEWED-BY: \\
+ - REVIEWER-CONTACT:\\
+