We implemented this as an Interceptor... We implement any cross-functional infrastructure as Interceptors.
Application specific cross-action behavior can also be implemented in application specific Interceptors. > -----Original Message----- > From: Florian Weber [mailto:[EMAIL PROTECTED] > Sent: Friday, December 19, 2003 3:46 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] using interceptors > > > > hi! > > this message might be a slightly off-topic, but its still > somewhat related to webwork/xwork. > > im currently writing a mvc framework for php, which is > inspired in alot of parts by webwork/xwork. now im wondering > how much usage of interceptors is recommended or better: > which usage is recommended? > > for example would it be considered good-design to make a > interceptor for the storing the request data in the model or > should this be directly implemented in the action class or > another class, but NOT in an interceptor? > > any feedback is appreciated =) > > ciao! > florian > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign > up for IBM's Free Linux Tutorials. Learn everything from the > bash shell to sys admin. Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371> &op=click > > _______________________________________________ > > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork