[EMAIL PROTECTED] schrieb:
You did not mention which version of Lenya is installed.  Assuming
2.x, someone else must provide specifics about importing.  My
experience is with Lenya 1.2 and 1.3.

"most of the files are xsp, xml, or xsl."
All versions of Lenya natively handle XSP, XML, and XSL files because
all versions of Lenya are based on Cocoon 2.1.  (Cocoon 2.2 has
difficulty with XSP.)

How best to import depends on your XML files:
1. The files might remain in their current location or be imported
into Lenya's data structure.
2.  A new resource type could read the files in their current format,
or you could transform the XML files into the Lenya's standard XHTML
format/resource type.
3. Lenya depends on a "sitetree" to translate URL document paths.
Lenya 1.2 can build a sitetree document from a hierarchical directory
structure.  Lenya 1.3 uses a flat data structure and dynamically
generates the sitetree from "indexes" describing the relationships.  I
believe Lenya 2.0 uses a static sitetree document to translate URL
paths to UUIDs for locating XML documents in a flat datastore.  As
mentioned, someone else needs to provide details about sitetrees in
Lenya 2.0.

What solprovider wrote about 2.0 is correct. A major difference to 1.2 is that 2.0 doesn't support custom content paths. To integrate external content, you have to implement a Lenya repository (Node, NodeFactory etc.) that operates on this content.


The first decision is whether you are converting the website to Lenya
or just using Lenya for its WYSIWYG editing.  You can "link between
Lenya and our website," but that likely requires more work to setup
than a one-time conversion.

I strongly support this argument. The implementation of connectors (i.e., custom back-ends) tends to be very expensive.

-- Andreas



--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to