They aren't different purposes... you're just referencing them in different places?
The scope is simply broader when referencing at a higher level.
I thought the whole point of packages was to use inheritance ie. anything defined at the package level was available within actions but also could be overridden within the actions as well and so therefore I don't look at interceptor-ref has having a different purpose. I see the default-interceptor-ref as an additional element that's unnecessary. As I was reading the JOSP book it was unclear to me what default-interceptor-ref was having already mentioned packages and seeing how interceptor-ref works. I believe that anybody who understands the concept of inheritance can appreciate that default-interceptor-ref is unnecessary.
On Nov 30, 2003, at 7:49 PM, Jason Carreira wrote:
Because it is not valid according to the DTD, for one.
I understand what you're saying. I'm explaining why it's designed this way. The DTD is designed to be simple yet easy to understand, and it's too confusing and error-prone to have the interceptor-ref used for multiple different purposes.
-----Original Message----- From: Robert Nicholson [mailto:[EMAIL PROTECTED] Sent: Sunday, November 30, 2003 8:44 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Referencing default stack from a package?
I don't think you're understanding me.
If I put an interceptor-ref outside of an action at the package level why isn't that the same as setting a default?
On Nov 30, 2003, at 7:14 PM, Jason Carreira wrote:
at packageBut 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 somethingaction inlevel 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:
Umm.. So you realize you're setting the default for everyyou createthe package?you create
-----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 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
