Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: pass (hermes.apache.org: domain of peter.dykstra@donovandata.com
 designates 168.238.130.5 as permitted sender)
In-Reply-To: <4189698E.8030003@brondsema.net>
To: user@forrest.apache.org
Cc: user@forrest.apache.org
Subject: Re: two general questions
MIME-Version: 1.0
Message-ID: 
 <OF55660254.2C730E8A-ON85256F42.004FCE13-85256F42.00512778@donovandata.com>
From: peter.dykstra@donovandata.com
Date: Thu, 4 Nov 2004 09:46:25 -0500
Content-Type: multipart/alternative;
 boundary="=_alternative 0051276E85256F42_="

This is a multipart message in MIME format.
--=_alternative 0051276E85256F42_=
Content-Type: text/plain; charset="US-ASCII"

Thanks Dave, notes below.

Dave Brondsema <dave@brondsema.net> wrote on 11/03/2004 06:28:14 PM:

> peter.dykstra@donovandata.com wrote:
> > 
> > 1) I just mean there's a mapped drive from the Tomcat server (a mount 
> > point actually) which I can specify so that so apps running under 
Tomcat 
> > can read files from the other server.
> 
> Ok, so you just want to pull content from a different location, not a 
> different format.  IIUC, IMSManifest is about having your sources in a 
> different format, not a different location.

OK, thanks. IMSManifest looks interesting, but I hadn't gotten very far 
with it, but that puts it in context.

> 
> > 2) yes, forrest.properties lets me change directories, but only (as 
far 
> > as I can tell) within the current Forrest project.  If I put an 
absolute 
> > path to an xdocs directory on another server, Forrest appends it to 
the 
> > current context path and I get an error.
> 
> I think it is a required part of webapps that they cannot access things 
> outside their context path.  You can try using ../../../path/to/files 
> though.
> 
If this is a restriction, it is a Forrest restriction, not a general 
Webapps restriction. To test this, I went into the underlying cocoon.xconf 
file (within the deployed webapp on Tomcat) and hard coded the xdocs 
directory to point to a separate server. This worked fine. The problem is 
that since this bypasses the Forrest variables, any other Forrest 
functions that depend on these to determine the xdocs location (like 
search and sitemap linking) are probably broken. (The ../../../ format 
doesn't work.)  It looks like if I want to do this while waiting for 0.8 
to arrive, I'll just have to attempt to trace the variable settings back 
within Forrest to reset the pointers and then test all the functions. In 
the process I may discover that there are inherent webapp restrictions, 
but that would surprise me.
> 
> -- 
> Dave Brondsema : dave@brondsema.net
> http://www.splike.com : programming
> http://csx.calvin.edu : student org
> http://www.brondsema.net : personal
> [attachment "signature.asc" deleted by Peter Dykstra/USA/DDS] 
--=_alternative 0051276E85256F42_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Thanks Dave, notes below.</font>
<br>
<br><font size=2><tt>Dave Brondsema &lt;dave@brondsema.net&gt; wrote on
11/03/2004 06:28:14 PM:<br>
<br>
&gt; peter.dykstra@donovandata.com wrote:<br>
&gt; &gt; <br>
&gt; &gt; 1) I just mean there's a mapped drive from the Tomcat server
(a mount <br>
&gt; &gt; point actually) which I can specify so that so apps running under
Tomcat <br>
&gt; &gt; can read files from the other server.<br>
&gt; <br>
&gt; Ok, so you just want to pull content from a different location, not
a <br>
&gt; different format. &nbsp;IIUC, IMSManifest is about having your sources
in a <br>
&gt; different format, not a different location.</tt></font>
<br>
<br><font size=2><tt>OK, thanks. IMSManifest looks interesting, but I hadn't
gotten very far with it, but that puts it in context.</tt></font>
<br><font size=2><tt><br>
&gt; <br>
&gt; &gt; 2) yes, forrest.properties lets me change directories, but only
(as far <br>
&gt; &gt; as I can tell) within the current Forrest project. &nbsp;If I
put an absolute <br>
&gt; &gt; path to an xdocs directory on another server, Forrest appends
it to the <br>
&gt; &gt; current context path and I get an error.<br>
&gt; <br>
&gt; I think it is a required part of webapps that they cannot access things
<br>
&gt; outside their context path. &nbsp;You can try using ../../../path/to/files
<br>
&gt; though.<br>
&gt; </tt></font>
<br><font size=2><tt>If this is a restriction, it is a Forrest restriction,
not a general Webapps restriction. To test this, I went into the underlying
cocoon.xconf file (within the deployed webapp on Tomcat) and hard coded
the xdocs directory to point to a separate server. This worked fine. The
problem is that since this bypasses the Forrest variables, any other Forrest
functions that depend on these to determine the xdocs location (like search
and sitemap linking) are probably broken. (The ../../../ format doesn't
work.) &nbsp;It looks like if I want to do this while waiting for 0.8 to
arrive, I'll just have to attempt to trace the variable settings back within
Forrest to reset the pointers and then test all the functions. In the process
I may discover that there are inherent webapp restrictions, but that would
surprise me.<br>
&gt; <br>
&gt; -- <br>
&gt; Dave Brondsema : dave@brondsema.net<br>
&gt; http://www.splike.com : programming<br>
&gt; http://csx.calvin.edu : student org<br>
&gt; http://www.brondsema.net : personal<br>
&gt; [attachment &quot;signature.asc&quot; deleted by Peter Dykstra/USA/DDS]
</tt></font>
--=_alternative 0051276E85256F42_=--