Diana Shannon wrote:
>
> On Wednesday, May 15, 2002, at 05:20 AM, Stephan Michels wrote:
>
>> The best way to do this, is to implement the CVS support in cocoon.
>
>
> But you still need some form of webapp front-end to address all CMS
> concerns. CVS versioning is insufficient, IMO.
>
>>
>> I were glad to see a CVSSource and a CVSSourceFactory, but if it too
>> difficult to map the parameters like revision, cvs repository, and file
>> into an URI, we could implement this into a generator and transformer?!
>>
>> Something like this
>>
>> <generator src="src/documentation/xdocs/overview.xml">
>> <parameter name="cvsroot"
>> value=":pserver:****@cvs.apache.org:/home/cvspublic"/>
>> <parameter name="password" value="****"/>
>> <parameter name="revision" value="1.2"/>
>> </generator>
>
What about a 2-sided configuration :
- in cocoon.xconf, declare a new source-handler specific to a particular
CVS repository
<source-handler>
<protocol name="cocoon-cvs" class="...CVSSourceFactory">
<cvsroot>:pserver:****@cvs.apache.org:/home/cvspublic</cvsroot>
<password>****</password>
<branch>cocoon_2_0_3_branch</branch>
</protorol>
</source-handler>
- in the sitemap, use only the path inside the repository, with
additional optional parameters if a particular version/branch is required
<map:generate
src="cocoon-cvs:/src/documentation/xdocs/overview.xml?revision=1.2">
This way, you have a single URL for any file (and revision) in the
repository, which can be used as a regular Source, or better,
WriteableSource.
>>
>> And the combination with slash-edit were ultimative ;-)
>
Having a WriteableSource is the key to slash-edit (see
SourceWritingTransformer).
> I agree. The sooner Forrest has a community-based CMS component, the
> better. Just think how wonderful it would be, to build in community
> contributions at the moment software is released (or before). Perhaps
> you might consider joining Forrest to work on building this dream ;).
>
> Diana
Could you elaborate more on how you see such a community CMS ? A big
problem for such a beast is that we currently don't have a servlet
engine running on Apache servers. And even if we had one, having a
webapp allowing to edit the Apache CVS directly from the web leads to
important security issues, and so it would have to be read-only.
Sylvain
--
Sylvain Wallez
Anyware Technologies Apache Cocoon
http://www.anyware-tech.com mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
