So next iteration,

again a new exception...


Upayavira wrote:


(3) it works in "normal" cocoon mode fine as ever.


As a servlet, you mean?

yes, precisely.



t's hope so, or maybe the docs could be extended. - the person who knows something best isn't always the best person to write user docs!

so, as a naive user, I tried to add some clarifications to the documentation; please be so kind and look at the file in the attachment, hopefully this is useful for you (it contains a part of the cli.xconf).





Just remove all blocks, and add them back as you need them.

I removed the authentication now, and all "unstable blocks". (If it is helpful, I could also send my build.properties)



so, now I can provide again a new exception:


Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at Loader.invokeMain(Unknown Source)
at Loader.run(Unknown Source)
at Loader.main(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletConfig




(to be honest, I would have given up already since yesterday; but we have the cocoon-day in austria, with one complete day of cocoon tutorials, and I really would want to present the resulta of the "offline-cocoon"... but Cocoon currently tries to do everything to avoid my presentation *g*)


Alex
   <!--+
       |  Specifies a user agent string to the sitemap when
       |  generating the site.
       |  A user-agent in the "normal" web-application is e.g., the 
       |  Web-browser. This feature is useful if the webapplication
       |  to be "spidered" has some assumptions about a specific
       |  client application/browser = user agent.
       +-->
   <!--
   <user-agent>xxx</user-agent>
   -->

   <!--+
       |  Specifies an accept string to the sitemap when generating
       |  the site.
       |  This feature is connected to the user agent.
       |  Cocoon might distinguish between different user agents (see above)
       |  in providing certain informations like images.
       
       ** I still do not understand how this works **
       
       +-->
   <accept>*/*</accept>
   
   <!--+
       | Specifies which URIs should be included or excluded, according
       | to wildcard patterns.
       |
       | These includes/excludes might solve problems, that occur when using
       | "follow-links=true" settings. The user might not want the Cocoon
       | CLI to follow certain links, allthough they are "part of" the URL
       | like references to the api-documentation.
       | 
       | By default, all URIs are included. If both include and exclude
       | patterns are specified, a URI is first checked against the 
       | include patterns, and then against the exclude patterns.
       | 
       | Multiple patterns can be given, using muliple include or exclude
       | nodes. 
       | 
       | The order of the elements is not significant, as only the first 
       | successful match of each category is used.
       | 
       | Currently, only the complete source URI can be matched (including
       | any URI prefix). Future plans include destination URI matching 
       | and regexp matching. If you have requirements for these, contact
       | [EMAIL PROTECTED]
       +-->
   <include pattern="**"/>
   <exclude pattern="docs/apidocs/**"/>

   <!--+
       |  <uri> nodes specify the URIs that should be generated, and 
       |  where required, what should be done with the generated pages.
       |
       +----------------------------------------------------------------
       |
       |  APPEND: append the generated page's URI to the end of the 
       |  source URI:
       |
       |   <uri type="append" src-prefix="documents/" src="index.html"
       |   dest="build/dest/"/>
       |
       |  This means that 
       |   (1) the "documents/index.html" site is "spidered"
       |   (2) the results are written to the "build/dest" directory
       |   (3) in the "build/dest" directory the path of the website is appended like 
this:
       |       "build/dest/documents/index.html
       |
       +----------------------------------------------------------------
       |
       |  REPLACE: Completely ignore the generated page's URI - just 
       |  use the destination URI:
       |
       |   <uri type="replace" src-prefix="documents/" src="index.html" 
       |   dest="build/dest/docs.html"/>
       |  
       |  This means that 
       |   (1) the "documents/index.html" site is "spidered"
       |   (2) the result is written to "build/dest/docs.html"
       |   (3) this works only for "singular" files, not for hierarchies
       |
       +----------------------------------------------------------------
       |  INSERT: Insert generated page's URI into the destination 
       |  URI at the point marked with a * (example uses fictional 
       |  zip protocol)
       |
       |   <uri type="insert" src-prefix="documents/" src="index.html" 
       |   dest="zip://*.zip/page.html"/>
       |
       |  This means that 
       |     *** no idea ***
       |
       |  If in any of these scenarios, the dest attribute is omitted,
       |  the value provided globally using the <dest-dir> node will 
       |  be used.
       +-->

   <uri type="replace" 
        src-prefix="samples/" 
        src="hello-world/hello.html"
        dest="build/dest/hello-world.html"/>
   

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

Reply via email to