Scott Eade wrote: >I believe what you are suggesting is possible. Classes can be loaded from >jar files by default and turbine provides ClasspathResourceLoader for >retrieving templates from a jar file. If the classes and templates for a >module are provided in a jar file and a configuration file is added to >inform the main application about the module (so it knows how to integrate >it) then all that should be required is a restart of the webapp to kick the >new module off. Note that a new module might also need the resource loader >paths and module.packages to be updated in TR.props to work properly. > >HTH, > >Scott > > One problem I see with this is with intake.xml and like you said TR.props. If a template is using intake for form validation, you essentially need to "patch" the file in order for it to work. Is there anyway to get around this?
Will -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
