Nasty ... I hadn't dug into the source yet on that issue, but I don't doubt you are correct.
All sub-application configurations are stored in application scope and a reference given to them in the request when appropriate (under the same key the default-app gets in the application scope, I believe). The key used ends in "config" for the default sub-app and "config/module" for each module (module being the actual name of the module :-) I would think this same strategy should be followed by the plugins. If a plugin does not follow this strategy, I would consider it a bug - and file a report in Bugzilla. Of course, if you happen to have the time to put your heel down firmly on this certain bug, feel free to do so (and submit a "cvs diff -u" as a patch, please!). Bugzilla can be reached at: http://issues.apache.org/bugzilla (I believe) phpsurf wrote: >Hi, > >looking at the code of the validator plugin (I needed an example to write a plugin), >I saw that the plugin stores the validation resources into the servletContext, using >the key 'org.apache.commons.validator.VALIDATOR_RESOURCES' > >the problem is that the validator configuration is specific to one module. >so you have to add a plugin in the struts-config.xml of every module. >but everytime the ValidatorPlugin.init() is called, it replaces the previous object >in the context, because it uses the same key ... > >so I guess the key should be module dependant ? >or is there a module-context where module-relative objects can be stored ? > -- Eddie Bush -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
