One thing I'm not using, but if I did, I'd be worried about, is resources. Form what I can tell, the message resources for a module are set into a request attribute by the RequestUtil.selectModule() method. But this is only done in an action servlet. So, if I've intended a JSP to rely on resources defined in a particular module, I must forward through an action in that module in order to have the right resources set.
Of course, I could use global resources. Second, I've been forced into doing a very bad thing and have to inspect information in ModuleConfig relating for the form for a mapping outside of the action handling that (extended RequestProcessor). Regards, Brian. >Brian, >don't take it as ridicule but what are doing with your JSPs that make >them module-aware? I don't think they are. Modularisation of struts >concerns the configuration of multiple struts-config.xml, tiles-defs.xml >and validation.xml files. > >I am 90% sure that JSPs are blind to the module they are in. True, you >can put them in a directory with the module name, but that has no effect. > >What module info are you refering to? > > >Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
