Before I go into a discussion of the why... Let me ask this: Should there be an option to have global views work they used to? (I was thinking along the lines of a param for the config file to switch modes)
----------------- Jeff and I spent a good amount of time discussing this since the 1.0 release. What we wanted to provide was a way to define global views, like we already had, but not always to copy them into each command. We basically wanted to be able to guarantee that a command could be self-contained. If you looked at the command def, you would see all view paths out. This led us down the road of global views with local command refs. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of jim moore Sent: Thursday, February 14, 2002 9:41 AM To: [EMAIL PROTECTED] Subject: [Mav-user] global views I've finally ported both maverick projects I'm working on to mav 2, and so far I think it is great. The one small detail I don't quite get is the reasoning behind the way the global views are set up. In mav 1, a global view was truly global--every command got it by default. Now in mav 2, I need to explicitly declare a reference to the global view in each command: <command name="main" controller="com.foo.foo"> <view name="loginRequired" ref="loginRequired"/> <view name="success" path="/main.jsp" /> </command> Why is this? I have 20 or so commands and 4 global views so far. That means I have to add 80 seemingly unncessary lines to my maverick.xml file. Is this to support shunting or something else that I haven't come across yet (so far I have just done the basic port from mav 1 to mav 2--haven't used any new functionality)? _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
