Well, like I said, that URL just demonstrates the _IDEA_, not the actual
implementation (I think using that exact config would suck as well). But a
config can be simple and still support all those extra options as well.

As for parsing whether the result is an action or a view, it's not that it's
non-trivial, it's that it's impossible, since the user might want either
behavior!

I really think it would be possible to maintain the simplicity of
views.properties (I've never used actions.xml) while still offering much
more power.

-Pat

----- Original Message -----
From: "Maurice Parker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 04, 2002 10:26 AM
Subject: Re: Configuration (was RE: [OS-webwork] Webwork Security
Requirements)


>
>
> Patrick Lightbody wrote:
>
> >http://radio.weblogs.com/0108886/2002/09/15.html
> >
> >
> Sheesh, this looks like a usability nightmare.  Have I not been clear on
> my feelings about complicating the Action configuration?
>
> I get the impression that you are forcing more configuration on the
> enduser because you found that parsing the view URL to determine if it
> is a view or an action proved non-trivial.
>
> -Maurice
>
> >-Pat
> >----- Original Message -----
> >From: "Jason Carreira" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Sent: Monday, November 04, 2002 9:30 AM
> >Subject: Configuration (was RE: [OS-webwork] Webwork Security
Requirements)
> >
> >
> >
> >
> >>What are the current thoughts on moving to one form of configuration
> >>(i.e. getting rid of views.properties and just using actions.xml)?
> >>
> >>-----Original Message-----
> >>From: Patrick Lightbody [mailto:plightbo@;cisco.com]
> >>Sent: Monday, November 04, 2002 12:24 PM
> >>To: [EMAIL PROTECTED]
> >>Subject: Re: [OS-webwork] Webwork Security Requirements
> >>
> >>
> >>Oh, good! I just thought two different ServletDispatchers would be nice
> >>to offer flexibility, but maybe only one is needed. Either way, doing it
> >>this way is nice also because internal actions are now not exposed at
> >>all. One of these days we might want to rename views.properties, since
> >>it's not views at all anyone, but action definitions. In fact, I'd be
> >>all for requiring an action to be aliased before it can be used (not
> >>more looking in the package). I alias all my actions before using them.
> >>This sorta goes back to my original hope that configuration be
> >>simplified and make much more sense in version 2.0.
> >>
> >>-Pat
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: ApacheCon, November 18-21 in
> >>Las Vegas (supported by COMDEX), the only Apache event to be
> >>fully supported by the ASF. http://www.apachecon.com
> >>_______________________________________________
> >>Opensymphony-webwork mailing list
> >>[EMAIL PROTECTED]
> >>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >>
> >>
> >
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: ApacheCon, November 18-21 in
> >Las Vegas (supported by COMDEX), the only Apache event to be
> >fully supported by the ASF. http://www.apachecon.com
> >_______________________________________________
> >Opensymphony-webwork mailing list
> >[EMAIL PROTECTED]
> >https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> >
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to