<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>Corsin, Christian -</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>The approach I was thinking of was
this:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>- use the handler404/on demand approach for all resources
to be exported</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>- on module start-up, register a listener to
CmsEvents</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>- include in the module a class which uses intimate
knowledge of my templating approach to be able to return for any given
module-controlled VFS resource a list of resources affected by a
change</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>- handle CmsEvents to delete the RFS copies of all relevant
resources so determined</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>But as Christian says, it takes time...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2>Jon</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937040608-28022006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> opencms-dev-bounces@opencms.org
[mailto:opencms-dev-bounces@opencms.org] <B>On Behalf Of </B>Corsin
Camichel<BR><B>Sent:</B> 28 February 2006 07:04<BR><B>To:</B> The OpenCms
mailing list<BR><B>Subject:</B> Re: [opencms-dev] Static export
problems<BR></FONT><BR></DIV>
<DIV></DIV>Hi Christian<BR><BR>Thank you for your response.<BR>The "publishing
all" is no option for me, we have to export more than 5'000 files every
time.<BR>Another solution I see, is to create an OpenCms Cronjob/Scheduled Job
with the " org.opencms.scheduler.jobs.CmsStaticExportJob" class.<BR>If that is
not satisfying, I have to deactivate the static export and keep everything in
the database.<BR><BR>Thank you again<BR><BR>Regards<BR>-- Corsin<BR><BR>
<DIV><SPAN class=gmail_quote>On 2/27/06, <B class=gmail_sendername>Christian
Steinert</B> <<A
href="mailto:christian_steinert@web.de">christian_steinert@web.de</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>The
OpenCms mailing list <<A
href="mailto:opencms-dev@opencms.org">opencms-dev@opencms.org</A>> schrieb
am 27.02.06 19:01:16:<BR>> Thank you Hari for your setting<BR>><BR>>
I have set mine up the same, but the problem is now, that it exports ALL my
files each time somebody publishes something. <BR>> Do you (or anybody else
in this list) know how to avoid this? This takes a long time and needs some
resources.<BR>><BR>> Hope that you can help me.<BR><BR>Dear
Corsin<BR><BR>well... It's not a bug, it's a feature.... <BR><BR>As far as I
have understood it, you can roughly control which resources are exported by
using the <resourcesToRender> directives in the export
configuration.<BR>But as there is no mechanism for detecting, which pages will
be affected by a certain content change, so OpenCms will export everything
that should be rendered for your resource set. <BR><BR>The old strategy, from
Version 5, where only changed resources where exported, doesn't exist anymore,
it seems.<BR>There are only two publish strategies in version 6:<BR>- publish
everything<BR>or<BR>- publish each individual page upon "file not found". Then
you need a chronjob or something to remove the rendered files from time to
time, so that changes from the database will eventually get through to the
audience. I really find this a bit - well - uncommon to work like that, but
anyway, that's the way it currently is. <BR><BR><BR>To do it more effectively,
would be possible by writing an own exporter. The best approach for this, I
think would be if each template calls a method "addDependentResource", or
something similar, for each resource that depends UPON the current resource.
<BR>Then the system would precisely know, which resources to re-publish for
each changed resource, because the templates of each resource could provide
this information.<BR><BR>But I sadly don't have the time to implement it.
<BR><BR>-------------<BR>If I ever use static export, I think I just try to
sychronize two "independent" cms instances.<BR>- One instance exports all
changed resources upon export.<BR>- The other instance imports anything that
comes into a configured directory, checking repeatedly by using a chronjob and
then publishes all the stuff. <BR>Like that, no user would have to wait for
the whole publishing process to finish.<BR><BR>But currently its only an idea.
I don't know if I ever manage to implement that at some
point.<BR><BR>Regards<BR>Christian<BR><BR>__________________________________________________________________________<BR>Erweitern
Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach!<BR>Mehr Infos
unter <A
href="http://freemail.web.de/home/landingpad/?mc=021131">http://freemail.web.de/home/landingpad/?mc=021131</A><BR><BR><BR>_______________________________________________<BR>This
mail is sent to you from the opencms-dev mailing list<BR>To change your list
options, or to unsubscribe from the list, please visit <BR><A
href="http://lists.opencms.org/mailman/listinfo/opencms-dev">http://lists.opencms.org/mailman/listinfo/opencms-dev</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Corsin Camichel<BR><A
href="mailto:cocaman@gmail.com">cocaman@gmail.com</A> </BODY></HTML>