Sure, but is it all about what you can do and not about how? I certainly see your point, but that calls into question why there are two mechanisms at all, much less how the mechanisms are invoked. Why not have one mechanism that does it all? (I know that while my vote doesn't count for much in WW, I'd rebel against losing views.properties. It's my friend. It keeps me warm at night. It fights off the trolls.)
--------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant On Mon, 4 Nov 2002, Maurice Parker wrote: > > Joseph Ottinger wrote: > > >No, actually I see his point: We add a configuration option that tells > >webwork how to configure views. That enables people like me, who are > >addicted to the raw simplicity of views.properties, to be happy... while > >it allows him to have his custom frobnigator that nobody ELSE will ever > >use or care about just as well. I think that's probably a justifiable > >change. > > > Go reread my reply to Pat. His custom frobnigator doesn't do anything > that I couldn't do with even views.properties. > > Check out this example from view.properties: > > jasperTest.action=jasperreports.OrderList > jasperTest.success=orderList.jasper?dataSource=orders > > Last I checked you could also do this with Actions. Maybe a param tag > in actions.xml would make this more elegant, but that's about it. > > -Maurice > > > > >--------------------------------------------------------- > >Joseph B. Ottinger [EMAIL PROTECTED] > >http://enigmastation.com IT Consultant > > > >On Mon, 4 Nov 2002, Maurice Parker wrote: > > > > > > > >>Joseph Ottinger wrote: > >> > >> > >> > >>>+1! Pat is a god! (He told me to say that so I'm blindly worshipping him.) > >>> > >>>Actually... I still vote +1, and Pat's just another frood in > >>>PsychoDelusionLand. > >>> > >>> > >>> > >>Well I say he's on something that's harming his short term memory. I > >>rail on how complicated the webwork.properties file is and he proposes > >>yet another configuration option. > >> > >>Pat, put down the pipe! :-) > >> > >>-Maurice > >> > >> > >> > >>> > >>> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: ApacheCon, November 18-21 in > >>Las Vegas (supported by COMDEX), the only Apache event to be > >>fully supported by the ASF. http://www.apachecon.com > >>_______________________________________________ > >>Opensymphony-webwork mailing list > >>[EMAIL PROTECTED] > >>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >> > >> > >> > > > > > > > >------------------------------------------------------- > >This SF.net email is sponsored by: ApacheCon, November 18-21 in > >Las Vegas (supported by COMDEX), the only Apache event to be > >fully supported by the ASF. http://www.apachecon.com > >_______________________________________________ > >Opensymphony-webwork mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
