Re: admin webapp (was: [PATCH] make directory browsing ...)

[Christopher Lenz <cm...@gmx.de>]

25.07.2001 18:24:52, "Craig R. McClanahan" <cr...@apache.org> 
wrote:
>On Wed, 25 Jul 2001, Remy Maucherat wrote:

[snip]
 
>> IMO, the choice is between Struts and JSPTL.
>> 
>
>Or both :-).  They are not mutually exclusive.
>
>FWIW, the early access version of JSPTL (available at
><http://jakarta.apache.org/taglibs>) requires Servlet 2.3 and JSP 1.2
>support.  Struts 1.0 is 2.2/1.1 compliant.
>

Right.

Struts would be an excellent choice for the admin webapp I think, 
being a complete webapp framework rather than just a tag library. 

So I'll move dependancies on JSPTL into tag classes that extend basic 
tag classes, and add struts dependant tag classes. In both cases I'd 
like to have the tags collaborate with the tags provided by the 
framework, most importantly the iteration tags. In case of JSPTL, I 
really want to enable use of the expression language evaluator, it's 
just SO sweet ;o). If I'm the only one interested in a JSPTL version, 
we can also omit that of course.

Then we could start the admin webapp, using the tag and bean classes, 
and adding actions and stuff. So what should the responsibilities of 
the admin webapp be ? There comes to mind:
- User/Group management
- Change permissions
- Kill locks
Should the admin webapp be limited to a single namespace, or should it 
be possible to add/remove namespaces (effectively changing the config 
file(s)) ?

On a related note, it would be nice to add an example for a user web-
interface to Slide, also based on the taglib and Struts, complete with 
file upload etc. But that's lower priority of course.

-chris
________________________________________________________________
cmlenz at gmx.de