http://book.mentaframework.org/posts/list/3.page JForum - http://www.jforum.net
As we have discussed in earlier chapters, sometimes there is no way out and you have to configure your actions. This chapter will show you how to do it.

[code]

public class ApplicationManager extends org.mentawai.core.ApplicationManager {

@Override
public void loadActions() {

// More verbose style...

addGlobalFilter(new AuthenticationFilter());

addGlobalConsequence(LOGIN, new Redirect("/login.jsp"));

ActionConfig ac = new ActionConfig("/User", UserAction.class);
ac.addFilter(new VOFilter("user", User.class);
ac.addConsequence(SUCCESS, new Forward("/ok.jsp"));
ac.addConsequence(JSP, new Redirect("/users.jsp"));

addActionConfig(ac);

// Less verbose style...

filter(new AuthenticationFIlter());

on(LOGIN, redir("/login.jsp"));

action("/User", UserAction.class)
.filter(new VOFilter("user", User.class))
.on(SUCCESS, fwd("/ok.jsp"))
.on(JSP, redir("/users.jsp"));
}

[/code]

Note that we are adding a global filter that will be applied to all actions. We are also adding a filter specific to the action ([i]VOFilter[/i]). Two consequences (one for [i]JSP [/i]and one for [i]SUCCESS[/i]) and a global consequence for the result [i]LOGIN[/i] are being added as well.

No inner action was specified, so by default this configuration will be considered for all inner actions inside UserAction.class. The following actions will be executed with the filters and consequences configured above:

http://www.mysite.com/User.mtw
http://www.mysite.com/User.add.mtw
http://www.mysite.com/User.del.mtw

Basically all inner actions inside the [i]UserAction [/i]class will have the configuration specified for the [i]UserAction[/i] class. Now let's get more specific.

You can add consequences and filters specific for a single inner action. Let's add a filter and a consequence specific for the [i]add [/i]inner action, in other words, for requests to http://www.mysite.com/User.add.mtw:

[code]
@Override
public void loadActions() {

// More verbose style...

addGlobalFilter(new AuthenticationFilter());

addGlobalConsequence(LOGIN, new Redirect("/login.jsp"));

ActionConfig ac = new ActionConfig("/User", UserAction.class);
ac.addFilter(new VOFilter("user", User.class);
ac.addConsequence(SUCCESS, new Forward("/ok.jsp"));
ac.addConsequence(JSP, new Redirect("/users.jsp"));

ac.addFilter(new AuthorizationFilter(new Permission("add")), "add");
ac.addConsequence(SUCCESS, "add", new Forward("/add.jsp"));

addActionConfig(ac);

// Less verbose style...

filter(new AuthenticationFIlter());

on(LOGIN, redir("/login.jsp"));

action("/User", UserAction.class)
.filter(new VOFilter("user", User.class))
.on(SUCCESS, fwd("/ok.jsp"))
.on(JSP, redir("/users.jsp"))

.filter(new AuthorizationFilter(new Permission("add")), "add")
.on(SUCESS, "add", fwd("/add.jsp"));
}
[/code]

So for our example, we will have the following filters being executed, in the following order:

AuthenticationFilter -> VOFilter -> AuthorizationFilter -> UserAction.add

Note that global filters are always executed first, then comes the action specific filters, then comes the inner action specific filters.

For consequences, the rule is simple:

First try to get a consequence specific to the inner action. If not found, try to get a consequence specific to the action. If not found, try to get a global consequence. If still not found, go by the Mentawai conventions: forward to /User/add.jsp.

You can get even more specific creating a whole [i]ActionConfig [/i]object just for the inner action you want to configure. The filters and consequences you define will be applied only for the inner action specified in the action config. Below is an example:

[code]

// More verbose style...

ActionConfig ac = new ActionConfig("/User", UserAction.class, "add");

ac.addFilter(new AuthorizationFilter(new Permission("add")));

ac.addConsequence(SUCCESS, new Forward("/add.jsp"));

// Less verbose style...

action("/User", UserAction.class, "add")
.filter(new AuthorizationFilter(new Permission("add")))
.on(SUCCESS, fwd("/add.jsp"));
[/code]

You can play with the order of the filters with some methods like [i]ActionConfig.addFilterFirst()[/i], that will add a filter to be executed BEFORE the global filters. You can also make your action implement the [i]GlobalFilterFree [/i]interface, to signal to the controller that it does not want any global filters. And you can also add a global filter that will be executed LAST, in other words, after all other filters have been executed. This will be rare cases, when for some very particular scenario you need to take more control in the invocation chain of filters.

Below are some examples of these rare methods:

[code]

// More verbose style...

ac.addFilterFirst(new TheFirstFilter()); // before global filters

addGlobalFilter(new TheLastFilter(), true); // true = LAST

// Less verbose style...

.filterFirst(new TheFirstFilter()) // before global filters...

filterLast(new TheLastFilter()); // after all other filters...

[/code]

[code]


public class UserAction extends BaseAction implements GlobalFilterFree {

public String add() {

// ...
}

public String execute() {

// ...
}

public boolean isGlobalFilterFree(String innerAction) {

if (innerActoin != null && innerAction.equals("add")) {

return true;
}

return false;
}
}
[/code]
]]> http://book.mentaframework.org/posts/preList/14/15.page http://book.mentaframework.org/posts/preList/14/15.page GMT