Gary, I suggest this feature should be tranparant for developer like changes in JSP when developer have just save the file. Currently, We are able to change java code right in debug mode and those changes will apply immediately. >From this perspective, the requirement to reload the configuration file sounds like a big disadvantage. I think, the remote command might make sense for the production, but not for the design-time environment.
-- Sergey <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Sergey, > > > Now, I have to restart my servlet container each time I have even small > > changes in the clay configuration file. I have not to do it for java > > classes, bundles, jsps. Development the UI with Clay might be much more > > faster if clay config file will be updated on the fly. > > Does any plan to avoid restarting exist? > > > > Currently the clay configuration files are loaded by a context listener on application startup. The meta-data is cached in application scope. > > I don't see a reason why we couldn't reload it on the fly. It seems like struts had the same feature in the early releases allowing an action to reload the struts-confg files. I'm positive that someone listening here could tell us the history and why the decision was made to remove it. > > We might be able to do this with a Shale remote command. It would be kind of fun to return an XML representation of the component meta-data after all inheritances have been realized. > Gary > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
