Hi Andreas,
I am having a similar problem as Steve. I am using Lenya 2.0 (SVN) and I
have created a resource type for the XML of the document that I am
trying to import by following the tutorials. At this stage though, I'm
not trying to import an entire site; I just want to display a single
page (the home page) via a XSLT pipeline.
The problem I have is that after the page is generated using the XSLT,
the default Lenya menus and tabs remain. Our page is displayed in a
'frame' beneath and to the side of the Lenya menus and tabs.
After searching various sources on the web over the course of a few
days, I have a few theories about why this is:
1. I need to overwrite some XSLTs in the default lenya publication so
that our own XSLT & CSS are the only ones used.
or
2. I need to remove the Lenya templet that was somehow inherited when I
created the publication and not use any templet at all.
The web site in question is available here:
http://www.illation.com.sg
We already have our RNGs and XSLTs & CSS defined.
Does anyone have any theories on why this is? A 'ground' up tutorial
that gives a simple example of a XML page being transformed and
displayed would be helpful.
I've read about the Coocoon pipeline, but just can't quite work out how
this is linked in or accessed through Lenya.
Cheers,
Jeremy Tan
Andreas Hartmann wrote:
Hi Steve,
Nunez Steve schrieb:
G'Day Gentlemen,
I have an existing website that is composed of XML
files, using a custom schema, that is styled by an
XSLT stylesheet into XHTML, and then finally presented
by way of external CSSs. The entire process is driven
by 'make', and the system works quite well.
It seemed upon first reading that importing this into
Lenya would be straightforward, however this has not
proven to be the case. I've been through all of the
documentation I can find, however I haven't read the
simplest use case:
1. Create an XML document instance & XSLT stylesheet
2. Apply the stylesheet to the XML document
3. Display the results in Lenya.
Can anyone point me to the simplest way to do this?
Given that we've already got the 'hard' part done --
created debugged XML/XSLT/CSS, it should be a matter
of using Lenya to manage this.
what you have to do is
1. create a resource type for your specific XML
2. find a way to import your existing content
For task 1, take a look at these tutorials, depending on
the Lenya version you want to use:
http://lenya.apache.org/docs/1_2_x/how-to/custom_resourcetype.html
http://lenya.apache.org/docs/2_0_x/tutorials/resourcetype/part1.html
For task 2, it depends on the Lenya version.
With 1.2.x it might make sense to write an Ant task which creates
the Lenya content directory structure and the workflow, revision
etc. files.
With 2.0 you should use the API - the Import usecase will probably
be a good starting point
(http://lenya.apache.org/apidocs/2.0/modules/export/index.html).
You will have to customize it and extend the Importer class to meet
your specific requirements.
HTH,
-- Andreas
--
Cheers,
Jeremy Tan
================================================================
"Most people make the mistake of thinking design is what it looks
like, that's not what we think design is. It's not just what it looks
like and feels like. Design is how it works."
-- Steve Jobs
================================================================
begin:vcard
fn:Jeremy Tan
n:Tan;Jeremy
org:Illation Pty Ltd
adr:140 William Street;;Level 40;Melbourne;VIC;3000;Australia
email;internet:[EMAIL PROTECTED]
title:Consultant
tel;cell:+61 04 3836 7393
x-mozilla-html:FALSE
url:http://www.illation.com.au
version:2.1
end:vcard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
