-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We have been doing option 2b for over 1+ years. There have been some anomalies, like pages not reloading... but these were several versions of Forrest ago.
For high-traffic sites, we also cron/schedule a "forrest site" and a maven task to deploy it. The schedule varies depending on the site. Some are done every 15 minutes.. some nightly. At an estimate, we have over 20+ sites on about 10 different disconnected servers (inside firewalls, outside, etc..) Kind Regards, Michael L. Conneen Information Integrators, Inc. http://www.infointegrators.com PGP Key: http://mconneen.infointegrators.net/mconneen.asc Mobile: (219)201-6192 On Mar 2, 2006, at 04:36, Johannes Schaefer wrote: > So, there are some options to run Forrest in live mode: > > 1. 'forrest run': runs Jetty in a console window (stays open in > Windows) > 2. 'forrest war': creates a web application to deploy e.g. in tomcat > a) use the webapp directory > b) use "context descriptors" to use another webapp directory > c) use the location map to place the XML files somewhere else > 3. Service-Wrapper (Windows only) to do 'forrest run' as a > service (e.g. firedeamon) > > In case (1) and (3) one can use the Forrest directory structure > directly and edit the XML files in place. > > In case (2c) this may be possible as well --> anyone tried it? > > In case (2a) and (2b) one edits the XML files in the deployed webapp > directory or one may "watch" the source repository (CVS, svn) and > automatically deploy changed files to the webapp. > > I would like to know about the experiences with these options, > if there are other options and some details about them. > > Maybe I'll be able to put the information together into a how-to > (or the forrest documentation). > > Thanks to all! > Johannes > > > > Michael Conneen wrote: >> 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 >>>> >>> >> >> > > > -- > User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg > Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 > Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * > D-81825 München > www.uidesign.de > > Buch "User Interface Tuning" von Joachim Machate & Michael Burmester > www.user-interface-tuning.de > -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.5 (Build 5050) iQA/AwUBRAbvwY96tm6MluGvEQKWPQCfT/iWpLRHOjHorknB8S5sk9v5ObEAoIMJ J5FFCvBVqUh0LrXRG19fy3e+ =UjRa -----END PGP SIGNATURE-----
