|
From: <jue...@we...> - 2004-07-24 19:31:26
|
Sure - I still recommend to specify a brief "requestContextAttribute" = name like "rc" for custom usage, though. =20 The "springMacroRequestContext" should rather be considered an = implementation detail of the Spring-provided macros, to be activated by = the "exposeSpringMacroHelpers" flag. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Matt Raible Gesendet: Sa 24.07.2004 20:46 An: spr...@li... Betreff: Re: [Springframework-developer] Final preparations for 1.1 RC1 On Jul 24, 2004, at 7:12 AM, j=FCrgen h=F6ller [werk3AT] wrote: > Note that the "springMacroRequestContext" is not really meant to be > accessed directly; it is mainly meant to be used by Spring-provided > macros. If you want to use a RequestContext in your own expressions, > always specify the "requestContextAttribute" accordingly. We should > highlight that in the docs. > Right, but it actually does work if you use it. To me, setting the requestContextAttribute value seems to simply provide an alias for it.=20 Is it doing more than that? >> I would make sure and document that the name >> "springMacroRequestContext" >> can be overridden by specifying a "requestContextAttribute" property. >> It's much easier to write $rc.getMessage() than >> $springMacroRequestContext.getMessage(). ;-) > ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |