This may be a feature of the multi-application support, but I wanted to make sure. And if it was I wanted to get a little more info on the reasoning for it. Basically I have a main config and a sub config. An action is processed using an action configured by the main application. The result of that request is a JSP with an <html:form> on it.
Due to the constraints on action attribute of the form, the action can only be an Action configured in the main configuration. I think there is a lot of potential in having sub application (as well as the main) share configurations - actions, forms, etc. Or at least reduce the constraints on the action so that a user of Struts can integrate applications with out modifying code. Any thoughts? Laine -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
