I think the param in the config file may be too black and white. I kind of
like the direction Gerald is thinking.
You could have something like:
<views>
<group name="global>
<view id="error" path="/error.jsp"/>
</group>
<group name="protected">
<view id="loginInRequired" path="/login.jsp"/>
<!-- include "someotherview" in this group"-->
<view id ="someotherview" ref="someotherview"/>
</group>
<view id="someotherview" path="/foo.jsp"/>
</view>
<command name="admin" controller="com.foo.Admin">
<!-- this will include all views grouped in protected -->
<view group="protected">
<view id="success" path="/admin.jsp">
</command>
<command name="welcome" controller="com.foo.Welcome">
<view id="success" ref="someotherview">
</command>
Group global could be a standard group--anything in there gets automagically
included in every command (though you are free not to use it if you want to
keep the commands self contained). Views in group "protected" get included
in a command if they specifically include that group (<view
group="protected">) under the command. The example above also shows a way to
allow multiple groups to share the same view by including it by ref.
This was obviously put together pretty quickly, so it deserves some debate,
but its just what I was thinking right now...
--jim
_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user
