Danny Waldmann schrieb:
Your authors can edit the website contents with Lenya, I don't think it
would be useful to add another Tapestry-based layer on top of the
authoring environment.
Thanks for your answer. Yes, we don't want to do that. A main problem that
I'm seeing right now is that Lenya is using it's own XML based Template
mechanism whereas Tapestry is using our HTML Templates. How, in this
scenario the author is going to see what the layout is look like? Because he
sees the content together with the Lenya XML based Templates right?
If you want WYSIWYG across multiple applications, I'd recommend the
following basic principles:
- Keep the templates as simple as possible.
- Avoid duplicating template logic. If you have to duplicate them, try
to generate them automatically from a single source (meta templates).
- Do everything you can in CSS. CSS can be shared.
In your specific case, I'd try to strip down the Tapestry templates to a
very basic XHTML structure, which can be duplicated in the Lenya
application with low maintainance costs.
Do you already know which editor you want to use? (BXE, Kupu, ...)
A central question is how to design
the interface between your application and Lenya. Do you want to use
something like HTTP to achieve a loose coupling, or do you want to
integrate the apps more tightly, e.g. using SAX to get the XML content?
At this point our wishes are very small. We only want to fetch content from
the Apache Lenya repository and want that a editor (our clients) can access
Apache Lenya and modify texts, pictures and the like on some websites. At
the moment we put that content in the apache web server and
access it from our tapestry web app. Now we have thought of using a web
content management system for that purpose. This will allow our clients to
edit the content directly.
Can you think of a possible solution for that scenario?
If you can implement a caching mechanism in your Tapestry application,
the easiest way would probably be to fetch XHTML snippets from Lenya
over HTTP and pass them through your final rendering steps. I'm not
familiar with the Tapestry rendering mechanism - if you need more
details about the integration, you'd have to give me a little introduction.
-- Andreas
Thanks in advance.
Hi Danny,
Danny Waldmann schrieb:
We want to integrate an Apache Tapestry 4 (similar to JSF) Web Application
with Apache Lenya. The goal is, that the Apache Tapestry 4 Web Application
is able to get content like pictures or text from the Apache Lenya
repository and that the author can edit a website and add and modify
content.
Tapestry uses HTML Templates.
My question is, do you see a way to do this with Apache Lenya and
When yes, how you would do this?
it's hard to answer your question without knowing some more details.
Your authors can edit the website contents with Lenya, I don't think it
would be useful to add another Tapestry-based layer on top of the
authoring environment.
As far as the Tapestry web application is concerned: You can fetch
content from the Lenya application in various formats, Lenya was
designed for this usage scenario. A central question is how to design
the interface between your application and Lenya. Do you want to use
something like HTTP to achieve a loose coupling, or do you want to
integrate the apps more tightly, e.g. using SAX to get the XML content?
Some aspects to keep in mind are performance/caching, flexibility,
reusability etc.
-- 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]
