Andreas Hartmann schrieb:
Campbell, Joe schrieb:
-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Hartmann
Sent: Wednesday, March 26, 2008 5:59 PM
To: user@lenya.apache.org
Subject: Re: Let me see if I can be more precise
Campbell, Joe schrieb:
I currently have a website that is developed using Spring
MVC and uses
velocity as the presentation technology. I am interested
in using a
CMS to provide my business with the capability to edit the Velocity
pages with some work flow tied to it such that they do not need to
have access to the code base on which the pages will be run. This
translates for me into the following: I would like to have the
Velocity content pages managed by a CMS (in this case
Lenya) while the
overall code base is the pervue of the development
organization. In
order to accomplish this I would have to have the CMS have
the capability to:
1) Serve Velocity pages
2) Allow the server with the dynamic back end calls be capable of
using this CMS and the velocity pages within to make the
application complete.
Just for my understanding: Do you want to import your (XML?) pages
into the standard Lenya repository, or do you want to implement a
Lenya repository which operates directly on your pages? If the latter
is the case, which interface would this repository implementation use
(web service, file system, database, ...)?
Are there specific drawbacks or limitations to using any of the
implementations that you list? File system is prob the easiest to allow
an outside 'source code' builder to pull in the latest 'authorized'
version of the pages, but assuming there are not any glaring advantages
or disadvantages I would not be specifically picky about FS, Database,
or other.
If you want to implement your own repository, here's the package
containing the required interfaces:
http://lenya.apache.org/apidocs/2.0/org/apache/lenya/cms/repository/package-frame.html),
But I guess it would be easer to import the pages into the standard
Lenya repository and provide an interface for your Velocity application
to access them. HTTP is probably the most straightforward option.
Another option would be to automatically save the pages (after each
change or periodically) to the file system. The RepositoryListener
allows to react immediately to any content changes.
Alternatively, you can export the pages when they are published.
-- 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]
