Return-Path: Delivered-To: apmail-lenya-user-archive@www.apache.org Received: (qmail 85581 invoked from network); 2 Apr 2008 13:47:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Apr 2008 13:47:33 -0000 Received: (qmail 336 invoked by uid 500); 2 Apr 2008 13:47:32 -0000 Delivered-To: apmail-lenya-user-archive@lenya.apache.org Received: (qmail 176 invoked by uid 500); 2 Apr 2008 13:47:32 -0000 Mailing-List: contact user-help@lenya.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@lenya.apache.org Delivered-To: mailing list user@lenya.apache.org Received: (qmail 161 invoked by uid 99); 2 Apr 2008 13:47:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 06:47:32 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jcampbell@ingdirect.com designates 63.113.210.15 as permitted sender) Received: from [63.113.210.15] (HELO ingdesmtpps.ingdirect.com) (63.113.210.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 13:46:51 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Re: Let me see if I can be more precise Date: Wed, 2 Apr 2008 09:46:58 -0400 Message-ID: <324634B71B159D469BCEB616678A6B9408199B16@ingdexs1.ingdirect.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Let me see if I can be more precise thread-index: AciQEar/Zq1KNeBYQDanrsViXjBikwEtf8uA References: <324634B71B159D469BCEB616678A6B94080211B4@ingdexs1.ingdirect.com> <324634B71B159D469BCEB616678A6B940802157F@ingdexs1.ingdirect.com> From: "Campbell, Joe" To: X-OriginalArrivalTime: 02 Apr 2008 13:46:58.0851 (UTC) FILETIME=[059B8F30:01C894C8] X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: news [mailto:news@ger.gmane.org] On Behalf Of Andreas Hartmann > Sent: Thursday, March 27, 2008 9:48 AM > To: user@lenya.apache.org > Subject: Re: Let me see if I can be more precise >=20 > Andreas Hartmann schrieb: > > Campbell, Joe schrieb: > >>> -----Original Message----- > >>> From: news [mailto:news@ger.gmane.org] On Behalf Of=20 > 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=20 > the Velocity=20 > >>>> pages with some work flow tied to it such that they do=20 > not need to=20 > >>>> have access to the code base on which the pages will be=20 > run. This=20 > >>>> translates for me into the following: I would like to have the=20 > >>>> 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=20 > capable of=20 > >>>> using this CMS and the velocity pages within to make the > >>> application complete. > >>> > >>> Just for my understanding: Do you want to import your=20 > (XML?) pages=20 > >>> into the standard Lenya repository, or do you want to implement a=20 > >>> Lenya repository which operates directly on your pages? If the=20 > >>> latter is the case, which interface would this repository=20 > >>> implementation use (web service, file system, database, ...)? > >> > >> Are there specific drawbacks or limitations to using any of the=20 > >> implementations that you list? File system is prob the easiest to=20 > >> allow an outside 'source code' builder to pull in the=20 > latest 'authorized' > >> version of the pages, but assuming there are not any glaring=20 > >> advantages or disadvantages I would not be specifically=20 > picky about=20 > >> FS, Database, or other. > >=20 > > If you want to implement your own repository, here's the package=20 > > containing the required interfaces: > >=20 > http://lenya.apache.org/apidocs/2.0/org/apache/lenya/cms/repository/pa > > ckage-frame.html), > >=20 > >=20 > > But I guess it would be easer to import the pages into the standard=20 > > Lenya repository and provide an interface for your Velocity=20 > > application to access them. HTTP is probably the most=20 > straightforward option. > > Another option would be to automatically save the pages (after each=20 > > change or periodically) to the file system. The RepositoryListener=20 > > allows to react immediately to any content changes. >=20 > Alternatively, you can export the pages when they are published. >=20 > -- Andreas This tells me some about the 'tail' end integration I may have to do - but it doesn't tell me anything about setting up lenya to allow the management of, and writing of Velocity pages/macros from its GUI interface. Maybe that would have been a better wording for the original question, How can I configure lenya to allow a user to utilize the lenya tooling to manage velocity content? The follow up question is then, how can I 'publish' that content in either a push mechanism (i.e. when changed push out to a location) or a pull mech allowing the server with the 'need' for the content to pull the content on some sort of approved schedule. Thanks, Joe ***************************************************************************= ** This email may contain confidential or privileged information. If you belie= ve you have received the message in error, please notify the sender and delet= e=20 the message without copying or disclosing it. ***************************************************************************= ** --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org For additional commands, e-mail: user-help@lenya.apache.org