[ https://jira.terracotta.org/jira//browse/CDV-237?page=comments#action_22218 ] Fiona O'Shea commented on CDV-237: ----------------------------------
Do Taylor's idea. > Validate root definitions > ------------------------- > > Key: CDV-237 > URL: https://jira.terracotta.org/jira//browse/CDV-237 > Project: Community Development > Issue Type: New Feature > Components: DSO:L1 > Reporter: Steven Harris > Assigned To: Juris Galang > > From the forums: > If I mistype the field-name of a root declaration in my terracotta config, > running the application does not throw any error whatsoever. I tried enabled > root debugging in the config, but it still doesn't say anything about > incorrectly named roots. Is there a way to have terracotta output these > errors to the log? > --- > This is a bit tricky. Since java dynamically loads it's classes the question > is at what point does a root definition become invalid? One could even be > dynamically generating the class with the root. The way I currently deal with > this kind of thing is to turn on debugging and if the root isn't getting > created I go back and validate my config. > That said, we might be able to have some sort of validator that searches the > classpath for all roots and gives a warning if no variable matches the root > spec. While not perfect because of dynamically generated stuff I think it > would be helpful 99 percent of the time. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.terracotta.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
