Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jdwilliams@austin.rr.com
 designates 24.93.47.43 as permitted sender)
Message-ID: <4409B2D1.9030906@austin.rr.com>
Date: Sat, 04 Mar 2006 09:31:29 -0600
From: "J.D. Williams" <jdwilliams@austin.rr.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.2) Gecko/20040803
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Migrating Cocoon site for static presentation
References: <44087E49.70608@austin.rr.com> <4408C204.3040000@taube.de>
In-Reply-To: <4408C204.3040000@taube.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thanks, Fady.

I'll give this a try and let you know what happens.

Joe

Fady Albashiti wrote:
> Hi,
> i have the same problem/plan and after asking the list, martin has sent 
> this link (i ll try it tomorrow):
> 
> http://www.mail-archive.com/users@cocoon.apache.org/msg31015.html
> 
> if you find more, tell me please
> 
> Fady
> 
> J.D. Williams wrote:
> 
>> I have a Cocoon webapp that is nothing more than a way of presenting 
>> XML-based documentation based on an arbitrary DTD. I use Cocoon 
>> instead of another way of building the HTML output because it works 
>> better than any other method I have tried.
>>
>> The important thing is the DTD. It is required as a way of organizing 
>> the content, which is quite complex and which my client requires. This 
>> means we have developed XSL specifically for this content.
>>
>> All is good so far.
>>
>> However, a need has arisen to generate static Web sites for this 
>> content for delivery via a Web server; i.e., not Tomcat or other 
>> servlet container.
>>
>> Forrest looks like a good bet, and I have gotten the Forrest 
>> documentation and demo site to work. Diving into the documentation to 
>> determine how to migrate this particular project has proven a bit 
>> confusing. I think the section "Customizing Your Content" was written 
>> for a somewhat different scenario than the one I have in mind.
>>
>> I have also read that the Cocoon CLI is another option, but have not 
>> really "grokked" that one as yet.
>>
>> So, if anyone on the list has done something similar and has any tips 
>> on the best way to proceed, I would appreciate it. The directory 
>> structure of the existing webapp is way simple, as follows:
>>
>> |-- myproject
>> |   -- myxmlcontent
>> |   -- myxsl
>> |   -- mydtd
>> |   -- mycss
>> |   -- WEB-INF
>> |   -- META-INF
>> |       |-- sitemap.xmap
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org