Re: Looking for some work to do on Lenya

[Bob Harner <bo...@gmail.com>]

Michael,

Abeit a little late, here are some thoughts I had on static HTML
exporting, for your consideration as you design this:

1) Make sure it works when running Lenya under SSL.  I have had great
difficulties with this using Lenya 1.2.4 under WebLogic behind an
SSL-enabled web server, particularly since my site's SSL certificate's
root CA is not in the default trust store.

2) If the new design will be doing an http(s) connection to Lenya to
generate each page, maybe we can reuse the output of the http(s)
connection that ProxyGenerator makes during the publishing step.  Or
at the very least, both the publishing (ProxyGenerator.java) and the
export (Wget.java) should be refactored to use the same http(s)
connection code, same trust store location, etc.

3) Do we really have to make an http(s) connection to generate the
static HTML pages at all?   I know that the publishing process uses an
http(s) connection so that the "live" site can be on a different
server, but for those creating static HTML pages this is generally not
the case (I assume).  Or can we call a Cocoon API to send a desired
URI through the pipelines and save the result to a file (after
rewriting the URL's, of course), without needing to make a socket
connection at all?

4)  I may be showing my ignorance on this one, but it seems like an
obvious question:  Most people want the static HTML files because they
will be using a web server to serve up the site, rather than having
Lenya serve it up.  In those cases, why do we need a "live" copy of
the site at all?  Maybe instead of an export process, the Publish step
should optionally save HTML instead of XML.  I know, I know, too much
code to change on this one.

On 11/18/05, Michael Ralston <mi...@ralston.id.au> wrote:
> On Fri, 18 Nov 2005 07:13 pm, Andreas Hartmann wrote:
> > Michael Ralston wrote:
> > > I've used lenya for a couple of australian companies, I'm familiar with
> > > org.apache.lenya.ac and the StaticHTMLExporter (which seems to have
> > > disappeared in current SVN??)
> >
> > ... and is still in need of an appropriate replacement :)
> > A component for exporting a site to static HTML would be a nice addition
> > to 1.4. Some issues which could be improved in comparison to 1.2:
> >
> > - configurability
> > - reusability (command line?)
> > - functionality (proper downloading of images, CSS, etc.)
>
> Ok, so static export for 1.4 is a good candidate for something for me to work
> on then, (In addition to taking a look at the automated tests)
>
> In 1.2 there seemed to be two ways to do static export right? There was the
> publish task export, and there was also the ant task?
>
> I wasn't real fond of the ant task, how would a command line export be used in
> production? It would probably run via the operating system scheduler, eg
> cron? Anyway, not that much of an issue as long at the export class can be
> called from two different use-cases.
>
> In regards to configuration, it's something that just needs to be configured
> via a file somewhere, not via the web right?
>
> In addition to downloading images and processing the css properly, a problem I
> found with the 1.2 exporter was that when a page published/deactivated the
> pages which should have a navigation link appear/disappear were not updated.
> This could be difficult to solve without making some assumptions about how
> the site navigation has been configured.
>
> I'll get started on it and upload a patch to bugzilla when i have something :)
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org