Re: [Webwork-devel] DefaultActionFactory change

[Matt B. <ma...@sm...>]

----- Original Message -----
From: "Rickard" <ri...@mi...>
To: "Matt Baldree" <ma...@sm...>
Cc: "Webwork-Developer" <web...@li...>
Sent: Thursday, January 03, 2002 2:12 AM
Subject: Re: [Webwork-devel] DefaultActionFactory change


> Matt Baldree wrote:
>
> > Well, I don't think this is a good idea. The problem is several.
> >
> > 1. Multiple Alias proxies. This could be a problem with two caches.
>
>
> Why? Example?
>

Can't think of a good example.

>
> > 2. Major problem is a possible circular relationship of having an alias
with
> > a command and an Action with a command.
>
>
> Example?
>

A) If you surround CommandFactory with AliasFactory

Example:
<A href="testfoo!foo.action">Misc. tests</A>

views.properties with alias
testfoo.action=Test!foo

In this scenario, the first alias would not find testfoo!foo.action, then
the command would be stripped and the second alias would find testfoo
returning Test!foo as an action. This action won't be found. I realize this
is an odd case and we could just say it will not support this scenario.

B) If you leave the default factory as it is now, then this example will
fail.

Example:
<A href="testfoo.action">Misc. tests</A>

views.properties with alias
testfoo.action=Test!foo

In this scenario, the command would see "testfoo.action" and would see that
it is not a command then alias would find and return Test!foo as the
action.. This action won't be found.

> /Rickard
>
> --
> Rickard Öberg
>
>
>