forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Conneen <mconn...@infointegrators.com>
Subject Re: Forrest as Windows-Service: Solution Firedeamon
Date Wed, 01 Mar 2006 20:27:49 GMT
What we do is watch a Forrest/Maven source directory in CVS... upon 
check in .. we simply copy the content to the deployed webapp.. and 
yes.. we used context descriptors as well. ;)

mc

On Mar 1, 2006, at 14:24, Gunther Sablon wrote:

> Hi
> > You edit the files in the webapp directory, I suppose?
> Actually the webapp (i.e., the web application)  is not located in the 
> "webapp" directory of Tomcat:
> we use a context descriptor file so that the webapp can be located 
> elsewhere.
> But indeed: the editable content is physically part of the webapp.
> Regards
> Gunther
>
>
> Thorsten Scherler wrote:
>
>> El mié, 01-03-2006 a las 17:19 +0100, Johannes Schaefer escribió:
>>
>>> Gunther Sablon wrote:
>>>
>>>> Hi again,
>>>> I am not the commercial guy, so I won't put any advertisments... ;-)
>>>>
>>> me neither, the ad was for forrest :-)
>>>
>>>
>>>> We used the command  'forrest webapp'. We deployed the generated 
>>>> webapp
>>>> under Tomcat only once.
>>>> We don't have to recreate any webapp when changing the XML sources; 
>>>> all
>>>> changes are immediately visible.
>>>>
>>> How do you do this?
>>> You edit the files in the webapp directory, I suppose?
>>>
>>
>> That would be one possibility but with 0.8-dev and the locationmap you
>> can determine where the content and anything else actually is coming
>> from.
>>
>> So you can have the "content" coming from any place (do not have to be
>> on the same server either).
>>
>> salu2
>>
>


Mime
View raw message