Andreas,
> With the current Lenya 1.4, this would mean to implement a custom
> DocumentIdToPathMapper and a custom SiteManager.
>
In theory I agree. I would love to find the time and actually do it, and
it it was only for the fun. I'd like to find out if there are no hidden
assumptions somewhere that would break it.
> But - do we really want to allow editing a Forrest site?
> Or is it enough to provide an import/export interface?
I am not sure. Maybe an import/export interface will do. But does that
mean to export the entire site every time you changed a page and want to
publish it?
Also please don't forget:
- Editing a Forrest site is one topic.
- Editing a Forrest site in a SVN repository is another topic.
If you think of a partial export, are you sure you could always clearly
identify what needs to be exported?
Well, maybe we should just start and try.
Regards,
Torsten
Andreas Hartmann schrieb:
Torsten Schlabach wrote:
It is an example of that fact that the virtual directory / URI layout of
the site that is visible to the outside and the current Lenya internal
filesystem layout in pubs/<mypub>/content as well as
pubs/<mypub>/resources are different and not a 1:1 mapping. In fact,
there
is quite a complex relationship mapping a URI from the outside to an
actual storage location. Some of that mapping is done in Java, some is
done in the sitemap.
These are two structures. We are about to introduce another one for
JCR as
we had a discussion that it will probably not a good use of a JCR
repository to just mimic the filesystem 1:1 there. The structure that the
current Apache website update and publishing process requires is just
another structure, isn't it?
OK, I see what you mean.
Not yet, but it is a requirement of Doco, and people are interested
in implementing this feature in the near future (see thread by
Roos Gardler, "Finally creating Doco")
Can't they do this in form of a JCR backend? That way their work could
even be leveraged beyond Lenya.
Either this, or maybe import/export is sufficient (see below).
What I am concerned with for quite some time is our URI mangling magic
stuff. IMO he have way too much semantics and implicit contracts in our
URIs, especially when it comes to embedding (a page and pictures on the
page) or linking pieces (internal and external links) together.
OK, but this is not related to the storage mechanism, is it?
I think it is:
Whenever I link nodes of content I need a system of referencing them. To
say it very concrete: You have to put something into the href attribute.
And this something needs to make sense in any place where the document
shows up and the href needs to be deferenced. Therefore inside Lenya the
path from page A to picture B might be different than it will be in a
static export of the site to HTML than it might be in a static export of
the site in XDoc.
Am I wrong?
Another way of thinking about this is:
- Does Lenya own the storage repository and can dictate where it's
putting
what? This is what it is today.
Actually the mapping from documents to XML files is customizable
(DocumentIdToPathMapper).
Or:
- Can we teach Lenya to edit documents that it does not own and that are
sitting on some external storage with a given, predefined directory
layout
structure (i.e. the SVN of the Forrest source of Apache sites).
If you want to use Lenya to edit the content of an XDoc Apache website,
you need the latter, don't you? The structure is given and you would even
have to support a different way of handling the sitemap, which would no
longer be Lenya's sitemap.xml but Forrest's site.xml. (Which is sort of
pseudo-XML which will make it pretty funny IMO.) Ok, the Doco project
might have sorted that all out. Again, apologies for not keeping up with
the discussion here.
With the current Lenya 1.4, this would mean to implement a custom
DocumentIdToPathMapper and a custom SiteManager.
But - do we really want to allow editing a Forrest site?
Or is it enough to provide an import/export interface?
On a separate but related topic: How do they plan to edit XDoc in Lenya?
That should be no problem, at least with BXE.
BTW, the cocooncenter.org pub is based on xdoc (but without BXE
integration).
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
