Re : Re : File output with cocoon

[Roland <ro...@les-imaginaires.fr>]

Hi, Robin, Paul and others
Thanks for your answers here are some precisions about my problem

What I want to do is very simple, we wil create a intranet for a small
company. We will create DTD, and first xml for the content and xsl for
presentation. 
Standard users will see the page on their browsers, processed by cocoon, we
separate xml (content), xsp (process) and xsl for the appearance on screen
or elsewhere. 
We want some people of the company (authors) to be able to modify the
content (pure xml files) without using a database, just xml files on the
server. We want them to be able to achieve it simply because they have
authorisation to do it and with the same web interface as other users except
for an "edit" button they're the only ones to see. They will acces to a form
(cocoon-processed from the xml source file), be able to edit the "fields"
(elements or attribute) and see a preview and if they're happy with it just
push the save button and the site is up to date.

I hope this is more precise and I think the use of java.io.filewriter sounds
a good way to achieve it. I just can't figure out what to do with it.


        Roland



Roland Decaudin developper chez "Les Imaginaires"

RE: Re : Re : File output with cocoon

[Daniel Jones <da...@cs.utexas.edu>]

Why don't you use Servlets!

You can then use something like the following therein:

FileWriter fw = new FileWriter(new File("fileName.xml"));
String xmlOutput = getXMLOutput();
fw.write(xmlOutput);
fw.close();

-----Original Message-----
From: Roland [mailto:roland@les-imaginaires.fr]
Sent: Tuesday, May 02, 2000 6:23 AM
To: cocoon-users@xml.apache.org
Subject: Re : Re : File output with cocoon


Hi, Robin, Paul and others
Thanks for your answers here are some precisions about my problem

What I want to do is very simple, we wil create a intranet for a small
company. We will create DTD, and first xml for the content and xsl for
presentation.
Standard users will see the page on their browsers, processed by cocoon, we
separate xml (content), xsp (process) and xsl for the appearance on screen
or elsewhere.
We want some people of the company (authors) to be able to modify the
content (pure xml files) without using a database, just xml files on the
server. We want them to be able to achieve it simply because they have
authorisation to do it and with the same web interface as other users except
for an "edit" button they're the only ones to see. They will acces to a form
(cocoon-processed from the xml source file), be able to edit the "fields"
(elements or attribute) and see a preview and if they're happy with it just
push the save button and the site is up to date.

I hope this is more precise and I think the use of java.io.filewriter sounds
a good way to achieve it. I just can't figure out what to do with it.


        Roland



Roland Decaudin developper chez "Les Imaginaires"

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org