problems getting setup

2005-09-09 Thread Jorg Heymans
Hi,

I am trying to update the cocoon website, following roughly the
instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate. I've
got forrest 0.6 installed, updated path and FORREST_HOME accordingly.


When doing forrest from the root site directory i get :

d:\src\cocoon-siteforrest

Apache Forrest.  Run 'forrest -projecthelp' to list options


Buildfile: d:\tools\apache-forrest-0.6\src\core\forrest.build.xml

init-props:
 [echo] Loading project specific properties from
D:\src\cocoon-site\forrest.
properties
 [echo] Loading user specific properties from C:\Documents and
Settings\heymjo\forrest.properties
 [echo] Loading default properties from
d:\tools\apache-forrest-0.6\src\core
 -emacs -logger
org.apache.tools.ant.NoBannerLogger\context\default-forrest.pro
perties
[mkdir] Created dir: D:\src\cocoon-site\${project.temp-dir}
 [echo]
 [echo] -- Warning --
 [echo] Using skin forrest-site which is deprecated.
 [echo] Please migrate to one of the new skins listed in
forrest.properties.
 [echo] The skin that most likely resembles these ones is called 'pelt'.

echo-settings:

check-skin:

fetch-skins-descriptors:

BUILD FAILED
D:\tools\apache-forrest-0.6\src\core\targets\skins.xml:88:
D:\tools\apache-forrest-0.6\src\core -emacs -logger
org.apache.tools.ant.NoBannerLogger\context\skins not found.

Total time: 2 seconds


Any pointers ?

Jorg



Re: problems getting setup

2005-09-09 Thread David Crossley
Jorg Heymans wrote:
 Hi,
 
 I am trying to update the cocoon website, following roughly the
 instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate. I've
 got forrest 0.6 installed, updated path and FORREST_HOME accordingly.

Hmmm, no idea sorry. I can build cocoon-site no problems.

Would you try this test please:

cd somewhere
mkdir my-test; cd my-test
forrest seed
forrest

... that will determine that your forrest installation
is okay.

-David


Re: directory listing batch file invocation

2005-09-09 Thread Louis . Masters

OK, after looking at the examples and
the Coccon wiki page for the DirectoryGenerator, I got my directory listing
to somewhat work. Here is the my basic sitemap.xmap entry:

   map:pipeline
internal->
map:match
pattern=**/defaultbuilddir.html

map:generate type=directory src="">

map:parameter name=depth value=2/

/map:generate

   map:transform
src="" /

map:serialize type=xml/
/map:match
   /map:pipeline

The xsl is basically the stylesheet
from the Cocoon wiki. It converts the directory listings to html
tags. The problems I am having with it are:

1. The raw html tags are being
displayed. I thought I saw a FAQ on this somewhere, but I could not
find it again. I also tried the html serializer, but I got a DTD
error.
2. I am losing the rest of the
Forrest site (tabs, menus, etc.). I think I have to aggregate this,
correct? Any pointers?

Also, I'm still working on implementing
the full Jetty server.

Thanks,
Lou


David Crossley [EMAIL PROTECTED] wrote on
09/02/2005 10:10:32 AM:

 [EMAIL PROTECTED] wrote:
  I'm using Forrest 0.6 to migrate off of a plain old apache server.
I have
  most of the site replicated. The only remaining issues
are:
 
 Any reason for 0.6 ? You would be better of start a new
 application with 0.7 version. Anyway ...
 
  1. I need a directory listing of a path outside of the
web app. I tried
  using the Directory Generator, but quite honestly, I have no
idea how to
  implement it. Anyone have it set up already and can send
me some snips?
 
 http://cocoon.apache.org/2.1/userdocs/generators/directory-generator.html
 and you can probably find other stuff at wiki.apache.org/cocoon
 
 There are a couple of examples in Forrest
 cd forrest_06_branch/src/core/context
 grep directory *.xmap
 
  2. I need to call a batch file from a link. I was
using cgi-bin to do
  this, but I can't find a similar function in Forrest (I don't
think there
  is one). I saw a post about redirecting to an apache web
server, but I
  can't do that as I am removing the plain apache server. The
batch file
  only created a zip of a couple of directories so I was trying
to use the
  Zip serializer, but again, I'm having some issues.
 
 Are you using a full Jetty as the servlet container
 for your forrest webapp. It can run cgi programs,
 so probably can Tomcat.
 
 I have never used the Cocoon ZipArchiveSerializer,
 http://cocoon.apache.org/2.1/userdocs/serializers/ziparchive-serializer.html
 but i gather that you would construct a pipeline in
 your project sitemap that generates an xml document
 in the format shown, then finish that with the serializer.
 
 -David


Re: directory listing batch file invocation

2005-09-09 Thread Louis . Masters

Just an update. I got the html
serializer working (the html was malformed) and the html now renders. I
believe the rest of the issues relate to my not understanding xmaps.

Now on to understanding aggregates...

-Lou

[EMAIL PROTECTED] wrote on 09/09/2005 12:14:42
PM:

 
 OK, after looking at the examples and the Coccon wiki page for the

 DirectoryGenerator, I got my directory listing to somewhat work. 
 Here is the my basic sitemap.xmap entry: 
 
map:pipeline internal-

 map:match pattern=**/defaultbuilddir.html

  map:generate type=directory
src="" 
  map:parameter name=depth
value=2/ 
  /map:generate 
  
  map:transform src="">
 stylesheets}/dir2html.xsl / 
  map:serialize type=xml/

 /map:match 
/map:pipeline 
 
 The xsl is basically the stylesheet from the Cocoon wiki. It

 converts the directory listings to html tags. The problems I
am 
 having with it are: 
 
 1. The raw html tags are being displayed. I thought I
saw a FAQ on
 this somewhere, but I could not find it again. I also tried
the 
 html serializer, but I got a DTD error. 
 2. I am losing the rest of the Forrest site (tabs, menus, etc.).
I
 think I have to aggregate this, correct? Any pointers? 
 
 Also, I'm still working on implementing the full Jetty server. 
 
 Thanks, 
 Lou 
 
 
 David Crossley [EMAIL PROTECTED] wrote on 09/02/2005 10:10:32
AM:
 
  [EMAIL PROTECTED] wrote:
   I'm using Forrest 0.6 to migrate off of a plain old apache
server. I have
   most of the site replicated. The only remaining issues
are:
  
  Any reason for 0.6 ? You would be better of start a new
  application with 0.7 version. Anyway ...
  
   1. I need a directory listing of a path outside of
the web app. I tried
   using the Directory Generator, but quite honestly, I have
no idea how to
   implement it. Anyone have it set up already and can
send me some snips?
  
  http://cocoon.apache.org/2.1/userdocs/generators/directory-generator.html
  and you can probably find other stuff at wiki.apache.org/cocoon
  
  There are a couple of examples in Forrest
  cd forrest_06_branch/src/core/context
  grep directory *.xmap
  
   2. I need to call a batch file from a link. I
was using cgi-bin to do
   this, but I can't find a similar function in Forrest (I
don't think there
   is one). I saw a post about redirecting to an apache
web server, but I
   can't do that as I am removing the plain apache server.
The batch file
   only created a zip of a couple of directories so I was trying
to use the
   Zip serializer, but again, I'm having some issues.
  
  Are you using a full Jetty as the servlet container
  for your forrest webapp. It can run cgi programs,
  so probably can Tomcat.
  
  I have never used the Cocoon ZipArchiveSerializer,
  http://cocoon.apache.org/2.1/userdocs/serializers/ziparchive-serializer.html
  but i gather that you would construct a pipeline in
  your project sitemap that generates an xml document
  in the format shown, then finish that with the serializer.
  
  -David

Re: problems getting setup

2005-09-09 Thread Jorg Heymans

David Crossley wrote:

 That last 1.5 lines are remnants of the forrest.bat
 shell script that invokes forrest. I wonder if the
 parameters for the call are getting corrupted on
 your system. Sorry, someone else might have ideas.
 

I just found out what was wrong :

i had FORREST_HOME set to d:\tools\forrest\scr\core\ , removing the
trailing backslash made everything work.

I've been bitten by trailing slashes in env variables a few times
before, it always amazes me how they are able to completely wreck good
software and make it display errors nobody has ever seen before.

oh well :(
Jorg