Thank you Dave and Adam. I;'ve tried both suggestions. 1) Changing away from annotations, works an "proved" that my interceptors do work outside of their unit tests and actually in the system.
2) Trying the ParentPackage Annotation, works. I had read about this annotation, but convinced myself it wasn't what I was needing... Since I thought I needed to set the XWork Package for my action, not the Parent Package of the XWork Package... though given the way package inheritence works, I should have realized it would work. Now, I really want to use annotations instead of xml where possible, but the ParentPackage approach doesn't feel as clean/DRY as i would like. Configuring the interceptor stack (and global results) in XML is acceptable, since the only other options would tend to require place holder do-nothing classes to annotate. However having to annotate every action with a ParentPackage is very wrong. It feels like something like one of the following options would be needed and I can't tell if anything like this exists yet: 1) Provide some way for a default package to be declared in the struts.xml file 2) Make the actionPackages auto-detection set the XWork package based on the java package in some predictable fashion. (Not just the namespace as currently documented. ParentPackage could still override this default when needed for flexibility. 3) Move towards the "do-nothing" class to hold annotations -- some sort of ActionPackage interface... Might be able to make it slightly less useless by allowing anonymous interceptors to be defined/configured here if they don't need to be re-used in other packages? Is there some other appraoch to linking all "Zero Configuration" actions to a specified package without repeating it in every action? What could also be useful -- extend the config-browser plugin to expose an action's XWork package. It would definitely help with debugging/checking what XWork package an auto detected actionPackage is using. Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
