You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Sandor Spruit <sa...@cs.uu.nl> on 2003/11/13 14:03:40 UTC
Cocoon 2.1.x beginner needs guidance to resolve specific key issues
[Context: cocoon-2.1.2-src.zip as of 10/1/2003, 4:42:00 PM]
Hello all,
I'm considering the use of Cocoon 2.1.x as the primary engine for a new
students' lab environment. Though I've quite some experience with Cocoon
1.x, I'm overwhelmed by the sheer size of recent versions. Frustration
is coming up. There are multiple elegant ways to do almost anything, but
I'm wading through docs and Java files: close but not quite there :)
I've built Cocoon 2.1.2 from the source and copied relevant parts to a
separate directory to act as the base for my own web application. I've
experimented with sitemap features. No problem there. But now I'm stuck.
I need three features to work orthogonally across my web application,
and have as yet not been able to get anything working:
1. Uploading files
I think a custom Action provides the best way to implement uploading
files. I can introduce a FileUploadAction in the main sitemap, then
reference it in subsitemaps to match a URI at my convenience. Right?
2. Authentification
What I need is a basic mechanism to handle restricted access to my
web application. Something like the JDBCRealm with users and roles
cf. Tomcat, plus user groups. Specific groups of users, with full
sub-site access - i.e. anything below some point in the hierarchy.
3. Webdav access
It would be very nice if people could upload files to my Cocoon site
through webdav, because of the increasing support for webdav in XML
editing software. At present, the only way to get read/write access
is to bypass Cocoon and use the Tomcat webdav functionality. Cocoon
for publishing, a Tomcat backdoor to edit - both servlets accessing
the same datasource (filesystem, database etc.). Right?
Any comments on these three issues will be much appreciated,
Sandor
--
Information and Computing Sciences, Utrecht University
Contact information, see: http://www.cs.uu.nl/people/sandor/
"Our minds are harnessed by knowledge, by the hill and the will
to succeed". From: Fish, "Vigil in a wilderness of mirrors"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.1.x beginner needs guidance to resolve specific key
issues
Posted by Sandor Spruit <sa...@cs.uu.nl>.
gounis@osmosis.gr wrote:
>
> they are samples for authentication and webdav in "samples" area
> for uploading they are several threads in this list
Yup. You are right, but I've read most of the "several threads" and
looked at examples - as any long-time mailing list user should do :)
They do not resolve the *specific* issues as described, in particular:
- I have as yet been unable to find out how the "webdav" example is
exposed to the outside world. Where is the mapping? What is it that
allows me to connect "network places" (Windows Explorer) to the "repo"
directory, but not to other directories?
(Tomcat is quite clear in this respect: stuff gets routed through the
webdav servlet that comes with it)
- The stuff that comes with the webdav example states that it allows for
*read-only* access, which is obviously insufficient for XML editing;
(Tomcat allows for read/write access, I've tested this using MS Word)
- The authentification is done through actions, too. Just like the file
upload. Suppose I want part of my site to be protected. Suppose this
site consists of many, say 100, subsites. One for each student. There
has to be an elegant solution here. Not 100 subsitemaps with dozens of
map:act elements to cover every document. That won't do - especially
because I'd like students to edit their own sitemap as an exercise :)
Regards,
Sandor
--
Information and Computing Sciences, Utrecht University
Contact information, see: http://www.cs.uu.nl/people/sandor/
"Our minds are harnessed by knowledge, by the hill and the will
to succeed". From: Fish, "Vigil in a wilderness of mirrors"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Cocoon 2.1.x beginner needs guidance to resolve specific key
issues
Posted by go...@osmosis.gr.
they are samples for authentication and webdav in "samples" area
for uploading they are several threads in this list
--stavros
On Thu, 13 Nov 2003, Sandor Spruit wrote:
> [Context: cocoon-2.1.2-src.zip as of 10/1/2003, 4:42:00 PM]
>
> Hello all,
>
> I'm considering the use of Cocoon 2.1.x as the primary engine for a new
> students' lab environment. Though I've quite some experience with Cocoon
> 1.x, I'm overwhelmed by the sheer size of recent versions. Frustration
> is coming up. There are multiple elegant ways to do almost anything, but
> I'm wading through docs and Java files: close but not quite there :)
>
> I've built Cocoon 2.1.2 from the source and copied relevant parts to a
> separate directory to act as the base for my own web application. I've
> experimented with sitemap features. No problem there. But now I'm stuck.
>
> I need three features to work orthogonally across my web application,
> and have as yet not been able to get anything working:
>
> 1. Uploading files
>
> I think a custom Action provides the best way to implement uploading
> files. I can introduce a FileUploadAction in the main sitemap, then
> reference it in subsitemaps to match a URI at my convenience. Right?
>
> 2. Authentification
>
> What I need is a basic mechanism to handle restricted access to my
> web application. Something like the JDBCRealm with users and roles
> cf. Tomcat, plus user groups. Specific groups of users, with full
> sub-site access - i.e. anything below some point in the hierarchy.
>
>
> 3. Webdav access
>
> It would be very nice if people could upload files to my Cocoon site
> through webdav, because of the increasing support for webdav in XML
> editing software. At present, the only way to get read/write access
> is to bypass Cocoon and use the Tomcat webdav functionality. Cocoon
> for publishing, a Tomcat backdoor to edit - both servlets accessing
> the same datasource (filesystem, database etc.). Right?
>
> Any comments on these three issues will be much appreciated,
> Sandor
>
> --
> Information and Computing Sciences, Utrecht University
> Contact information, see: http://www.cs.uu.nl/people/sandor/
> "Our minds are harnessed by knowledge, by the hill and the will
> to succeed". From: Fish, "Vigil in a wilderness of mirrors"
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org