If you set something at package level then it's implicit that those items are defaulted for actions within that package. So why is it necessary to have <default-interceptor-ref> at the package level when <interceptor-ref> at the package level would mean the same thing?
On Nov 30, 2003, at 7:14 PM, Jason Carreira wrote:
But they're fundamentally different... One is directly setting a reference into an Action... The other is setting a default for all Actions.
-----Original Message----- From: Robert Nicholson [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2003 6:13 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Referencing default stack from a package?
But doesn't the fact that I've even referencing something at package level do that?
and if I don't want what I referenced at package level then I'll override it in my action.
On Nov 30, 2003, at 4:29 PM, Jason Carreira wrote:
you createUmm.. So you realize you're setting the default for every action in the package?
-----Original Message----- From: Robert Nicholson [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2003 4:24 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Referencing default stack from a package?
Why is there a distinction made b/w how to you reference a interceptor stack within a package and stack or action reference?
Why for instance is it "default-interceptor-ref" instead of interceptor-ref.
If you define an interceptor-ref for the package isn't that implicitly the default for all actions in the package?
Why is there this "default-interceptor-ref?"
Ref: p 119 of the JOSP book.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it helpyou createbetter code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it helpbetter code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
