2012/8/20 Paul Benedict <pbened...@apache.org>:
> Are you familiar with index actions in HTTP servers? It's the page
> that loads when a directory is specified. It's the default when no
> specific resource is requested. That's different than the "default
> action" in S2 which runs if no suitable action can be found.
>
> Pretend there is a default package called "checkout" with "viewCart"
> set to the default action. Here are some example actions in that
> package:
> /checkout/addToCart.action = Adds item to cart
> /checkout/viewCart.action = Views items in cart
> /checkout/ = runs default action
> /checkout/zzzzzz = runs default action too
> /checkout/qwerty = runs default action too
>
> As you can see, S2 interprets the default action to mean "I can't find
> anything so let's execute the default." I am saying, we should allow a
> more narrow configuration that says run the default action only if NO
> specific resource in the package is being requested.
But isn't the same as default action per package ? Where you can
specify the index action:
<package name="default" namespace="/" extends="struts-default">
<default-action-ref name="index" />
<action name="index">
<result>index.jsp</result>
</action>
</package>
Or would you have a more sophisticated mechanism which will
automagically discover index action instead of specifying default
action for each package ?
The case is that there can be more than one class used to implement
actions for given namespace.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
