Document: Overview of Lenya Sitemaps
URL: 
https://lenya.zones.apache.org/cms/docu/authoring/docu20/reference/sitemaps14.html
Changed by user: Andreas Hartmann (andreas)


----
Removed: /document/body/section[1]/p[1]/text()
Lenya is based on Apache Cocoon. To understand how Lenya works, you should have 
at least some basic                     Cocoon knowlege. Make sure you know 
what a Cocoon sitemap is and you understand matchers, generators,               
    transformers and serializers at least.
----
Added: /document/body/section[1]/p[1]/text()[1]
Lenya is based on 
----
Added: /document/body/section[1]/p[1]/a
<a> (null)
----
Added: /document/body/section[1]/p[1]/a/@href
[attr] href=http://cocoon.apache.org (null)
----
Added: /document/body/section[1]/p[1]/a/text()
Apache Cocoon
----
Added: /document/body/section[1]/p[1]/text()[3]
. To understand how Lenya works, you should have at least some basic            
        Cocoon knowlege. Make sure you know what a Cocoon sitemap is and you 
understand matchers, generators,                   transformers and serializers 
at least.
----
Removed: /document/body/section[1]/p[2]/text()
Lenya uses some more Cocoon components, but if you can spot the matchers, 
generators, transformers and                  serizalizers, you will be able to 
get a good first overview of the Lenya sitemaps.
----
Added: /document/body/section[1]/p[2]/text()
Lenya uses some more Cocoon components, but if you can spot the matchers, 
generators, transformers and                  serializers, you will be able to 
get a good first overview of the Lenya sitemaps.
----
Removed: /document/body/section[1]/p[3]/text()
But Lenya is much more than just a collection of sitemaps and some XSLT 
stylesheets. Lenya builds on                    the Cocoon foundation and 
extends the Cocoon framework with custom
----
Added: /document/body/section[1]/p[3]/text()
But Lenya is much more than just a collection of sitemaps and some XSLT 
stylesheets. Lenya builds on                    the Cocoon foundation and 
extends the Cocoon framework with custom components.
----
Removed: /document/body/section[1]/ul
<ul> (null)
----
Removed: /document/body/section[1]/ul/li[1]
<li> (null)
----
Removed: /document/body/section[1]/ul/li[1]/text()
Matchers
----
Removed: /document/body/section[1]/ul/li[2]
<li> (null)
----
Removed: /document/body/section[1]/ul/li[2]/text()
Actions
----
Removed: /document/body/section[1]/p[4]/text()[3]
.
----
Added: /document/body/section[1]/p[4]/text()[3]
. These protocols are linked to a custom input module that comes with Lenya, 
the PageEnvelope input module.
----
Removed: /document/body/section[1]/p[5]
<p> (null)
----
Removed: /document/body/section[1]/p[5]/text()
These protocols are linked to a custom input module that comes with Lenya, the 
PageEnvelope input module.
----
Removed: /document/body/section[3]/p[2]/text()
In case you deployed lenya into a non-root context of any servlet container, 
the first                          part of the URI will be handled by the 
container itself to match the responsible webapp.
----
Added: /document/body/section[3]/p[2]/text()
In case you deployed lenya into a non-root context of any servlet container, 
the first                          part of the URI will be handled by the 
container itself to match the responsible web application.
----
Removed: /document/body/section[3]/p[3]/text()
If you deployed lenya.war into Tomcat for example, you will most likely have to 
use                             http://localhost:8080/lenya/ to get into the 
Lenya root sitemap.
----
Added: /document/body/section[3]/p[3]/text()[1]
If you deployed 
----
Added: /document/body/section[3]/p[3]/code[1]
<code> (null)
----
Added: /document/body/section[3]/p[3]/code[1]/text()
lenya.war
----
Added: /document/body/section[3]/p[3]/text()[3]
 into Tomcat for example, you will most likely have to use the URI 
----
Added: /document/body/section[3]/p[3]/code[2]
<code> (null)
----
Added: /document/body/section[3]/p[3]/code[2]/text()
http://localhost:8080/lenya/
----
Added: /document/body/section[3]/p[3]/text()[5]
 to get into the Lenya root sitemap.
----
Removed: /document/body/section[3]/p[4]/text()
For the rest of this document, we pretend Lenya is the root webapp in your 
container                            as this is the case with the built-in 
Jetty. Let's examine , what Lenya does in order to                              
  render the document you see when you enter this URL:                          
  
----
Added: /document/body/section[3]/p[4]/text()
For the rest of this document, we pretend Lenya is the root webapp in your 
container                            as this is the case with the built-in 
Jetty. Let's examine what Lenya does in order to                          
render the document you see when you enter this URL:                            
----
Removed: /document/body/section[3]/section[1]/title/text()
Part 1: The publication ID
----
Added: /document/body/section[3]/section[1]/title/text()
Part 1: The Publication ID
----
Removed: /document/body/section[3]/section[1]/p[1]/text()[1]
The first part is the publication id 
----
Added: /document/body/section[3]/section[1]/p[1]/text()[1]
The first part is the publication ID 
----
Removed: /document/body/section[3]/section[1]/p[1]/em/text()
Default                                 Publication
----
Added: /document/body/section[3]/section[1]/p[1]/em/text()
Default Publication
----
Removed: /document/body/section[3]/section[1]/p[1]/text()[5]
. There is a difference between the publication ID and the name of the 
publication.                                     The ID should be compatible to 
both the filesystem implementation as well as the URI encoding                  
                 because it will become both the name of the publication 
directory and a part of the URL. Therefore                                      
it is good practice to stick to 7-bit ASCII with no spaces or special 
characters.
----
Added: /document/body/section[3]/section[1]/p[1]/text()[5]
. There is a difference between the publication ID and the name of the 
publication. The ID should be compatible to both the filesystem implementation 
as well as the URI encoding because it will become both the name of the 
publication directory and a part of the URL. Therefore it is good practice to 
stick to 7-bit ASCII with no spaces or special characters.
----
Removed: /document/body/section[3]/section[1]/p[2]/text()
In contrast, the display name of the publication (which will show up in the 
list of publications                                        on the main Lenya 
entry screen) can be longer and it can contain spaces as well as any            
                      Unicode characters.
----
Added: /document/body/section[3]/section[1]/p[2]/text()
In contrast, the display name of the publication (which will show up in the 
list of publications on the main Lenya entry screen) can be longer and it can 
contain spaces as well as any Unicode characters.
----
Removed: /document/body/section[3]/section[1]/p[3]/text()[1]
The publication ID is used to mount the publication specific sitemap.xmap from  
                                
----
Added: /document/body/section[3]/section[1]/p[3]/text()[1]
The publication ID is used to mount the publication specific sitemap.xmap from 
----
Removed: /document/body/section[3]/section[1]/p[3]/text()[5]
 will strip the publication ID                                  from the URL, 
so the publication sitemap will just see the                                    
  
----
Added: /document/body/section[3]/section[1]/p[3]/text()[5]
 will strip the publication ID from the URL, so the publication sitemap will 
just see the 
----
Removed: /document/body/section[3]/section[1]/p[3]/text()[7]
 portion. Nevertheless a publication has its ID                                 
available through the page envelope. More on that later as we're not yet really 
inside the publication's                                        content.
----
Added: /document/body/section[3]/section[1]/p[3]/text()[7]
 portion. Nevertheless a publication has its ID available through the page 
envelope. More on that later as we're not yet really inside the publication's 
content.
----
Removed: /document/body/section[3]/section[2]/title/text()
Part 2: The area
----
Added: /document/body/section[3]/section[2]/title/text()
Part 2: The Area
----
Removed: /document/body/section[3]/section[2]/p[1]/text()
There are two possible areas.
----
Added: /document/body/section[3]/section[2]/p[1]/text()
By default, a Lenya application supports two different areas.
----
Removed: /document/body/section[3]/section[2]/p[2]/text()
You can think of areas as of modes, as in "live mode" and "authoring mode". 
Live mode is                                        the view of the publication 
as it is supposed to be displayed on the website to the site                    
                    visitor. The authoring mode is used by editors and 
reviewers to edit the publication's content.
----
Added: /document/body/section[3]/section[2]/p[2]/text()
You can think of areas as of modes, as in "live mode" and "authoring mode". 
Live mode is the view of the publication as it is supposed to be displayed on 
the website to the site visitor. The authoring mode is used by editors and 
reviewers to edit the publication's content.
----
Removed: /document/body/section[3]/section[2]/p[3]/text()
Technically speaking, the first major difference between the authoring area and 
the live area is just                                   that in authoring mode 
the CMS menus are displayed. Following the WYSIWYG principle of Lenya,          
                         the publication content is rendered the same way in 
authoring mode as it would be in live mode.
----
Added: /document/body/section[3]/section[2]/p[3]/text()
Technically speaking, the first major difference between the authoring area and 
the live area is just that in authoring mode the CMS menus are displayed. 
Following the WYSIWYG principle of Lenya, the publication content is rendered 
the same way in authoring mode as it would be in live mode.
----
Removed: /document/body/section[3]/section[2]/p[4]/text()
Besides displaying the CMS menus or not, there are different copies of the 
underlying content                                   repository for the 
authoring and live areas. This allows the editors to edit a working copy        
                             without affecting the live site. When a document 
is published after it was reviewed, it is                                      
just beeing copied over to the live repository.
----
Added: /document/body/section[3]/section[2]/p[4]/text()
Besides displaying the CMS menus or not, there are different copies of the 
underlying content repository for the authoring and live areas. This allows the 
editors to edit a working copy without affecting the live site. When a document 
is published after it was reviewed, it is just beeing copied over to the live 
repository.
----
Removed: /document/body/section[3]/section[2]/p[5]/text()[1]
If you're using the default filesystem repository of Lenya, you will find the 
two different                                     repositories under 
----
Added: /document/body/section[3]/section[2]/p[5]/text()[1]
If you're using the default filesystem repository of Lenya, you will find the 
two different repositories under 
----
Removed: /document/body/section[3]/section[2]/p[5]/text()[3]
 and                                    
----
Added: /document/body/section[3]/section[2]/p[5]/text()[3]
 and 
----
Removed: /document/body/section[3]/section[2]/p[6]/text()
As well as the publication ID the area is also stored in the page envelope. 
This will make                                      the actual area available 
to both the sitemap through the page envelope input module as well as           
                      to the components in the Java layer of Lenya.
----
Added: /document/body/section[3]/section[2]/p[6]/text()
As well as the publication ID the area is also stored in the page envelope. 
This will make the actual area available to both the sitemap through the page 
envelope input module as well as to the components in the Java layer of Lenya.
----

  

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

Reply via email to