Check out the xwork.xml that's in the xwork/src/test... It's used to test out a lot of the features of the configuration.
> -----Original Message----- > From: Robert Nicholson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2003 3:29 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Referencing default stack from a package? > > > Do you have any non trivial xwork.xml that I could take a look at and > then provide > my thoughts on how I'd prefer it to look? I haven't done much > development > with xwork/webwork so I'd like to study some non trivial > examples first. > > Cheers > > On Dec 2, 2003, at 9:43 PM, Patrick Lightbody wrote: > > > Hey Robert, > > I am so sorry, my head wasn't working quite right. I see > now what you > > are saying (or at least, I see it much clearer than I did before): > > > > In packages, you define stacks with <interceptor-stack> but you set > > the default stack with <default-interceptor-ref/>. > > > > In actions you set the default (only 1 can exist) stack with > > <interceptor-ref/>. > > > > Why aren't they the same? I'm not really sure. In fact, the way we > > handle inheritance is quite non-standard: > > > > Package vs. Action (# means attr): > > * default-interceptor-ref vs. interceptor-ref > > * result-types#default=true vs. result#type=foo > > * global-result vs result > > > > I suppose that global-result could be renamed, though that > might get > > confused when standing next to <result-types> in the package. Also, > > default-interceptor-ref could be renamed, but likewise it > will become > > less clear as to what it is. > > > > Not really sure if it's a big enough issue to change. I > can't imagine > > it'll get out in 2.0, but please open an issue about how > you'd like to > > see your ideal xwork.xml layout and we'll get to it once > WebWork 2.0 > > is out. > > > > Thanks for the suggestions! > > > > -Pat > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > On Behalf Of > > Robert Nicholson > > Sent: Sunday, November 30, 2003 10:53 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [OS-webwork] Referencing default stack from a package? > > > > What does it mean to be a "default?" > > > > Am I confusing default with inheritance? > > > > My understanding is that a defaulted definition can be inherited. > > Therefore anything you define at the package level can be > inherited by > > the actions and subpackages of that package. I just don't > understand > > why it is necessary to have a specific element to define > something as > > "default" when it seemed as though the scope within which the > > reference was located determined the defaultness of a definition or > > reference. > > > > p 119 of the JOSP book. > > > > Instead of > > > > <default-interceptor-ref name="defaultStack"/> > > > > why not simply > > > > <interceptor-ref name="defaultStack"/> > > > > Does that have the same meaning? Or more precisely is there > a need to > > make a reference at the package level that is not implicit for > > subpackages and actions within that package? Isn't any reference I > > make at this level implicit for everything underneath and therefore > > "default"? > > > > On Nov 30, 2003, at 11:00 PM, Patrick Lightbody wrote: > > > >> Hi Robert :) > >> > >> I think the core reason for this is because you define multiple > >> interceptor-refs at the package level, so assuming it is > the default > >> wouldn't always be the case. The real question is: is this > is a good > >> idea? > >> > >> Personally, I've had situations where I've needed the defaultStack > >> and other times I've needed the defaultWorkflowStack -- all in the > >> same package. > >> > >> Examples work best. How would you ideally like to see the XML? > >> > >> -Pat > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] > On Behalf > >> Of Robert Nicholson > >> Sent: Sunday, November 30, 2003 5:47 PM > >> To: [EMAIL PROTECTED] > >> Subject: Re: [OS-webwork] Referencing default stack from a package? > >> > >> I'll be even more specific just in case you're still not > > understanding. > >> > >> 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: > >>>> > >>>>> Umm.. 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 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 > >>>> > >>> > >>> > >>> ------------------------------------------------------- > >>> 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 > > > > > > > > ------------------------------------------------------- > > 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 > ------------------------------------------------------- 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
