config-browser doesn't deserve to be exposed to the binary mess I have created! I have refactored this Struts 2 application into oblivion. If package D extends packages A, B, and C and package A has a custom default-interceptor defined, shouldn't package D inherit this stack? I am having to duplicate the stack creation from package A inside package D! I think the only way to stop the decline of this application is to close the lid on my laptop and focus on the Kansas v. Texas Tech game. Have you ever "improved" code so much that you ended up where you began?
Peace, Scott On Mon, Mar 3, 2008 at 7:40 PM, Wes Wannemacher <[EMAIL PROTECTED]> wrote: > Scott, > > Would it help if you dropped the config-browser into the app and saw how > badly you have it mangled ;) > > -Wes > > On Mon, 2008-03-03 at 18:58 -0600, [EMAIL PROTECTED] wrote: > > I am knee deep in a problem where I have looked at it so long that I am > > nearly wrapped around the axle. Before I get into the gory details, > what > > does a package extend when it specifies the extends attribute followed > by > > multiple coma separated packages? I am chiefly interested in a > > default-interceptor-ref that might have been established in only one > > "parent." Should this be the stack the child adopts? I'll stop here > before > > blathering on about my mess. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Scott [EMAIL PROTECTED]
