> From: jim moore [mailto:[EMAIL PROTECTED]] > > Also, I think it would be useful when an xsl transform is run on > maverick.xml to write the resulting xml file to disk (maybe > maverick-processed.xml or something). This file would never be loaded or > used by maverick, but would be there mainly so the developer could look at > it to ensure its what they wanted or just to see what is really going on. > Particularly in cases where one developer inherits a maverick project from > another developer, I think it would be useful for the new developer to be > able to view this processed file to more easily understand what is going > on.
Is it really worth having Maverick do this rather than just running a command-line xslt processor? Ok, probably :-) Maybe instead of writing a file, it would be better to be able to specify a command (similar to reloadCommand) which dumps the current config as a page. That way it isn't necessary to worry about where you can write to the filesystem, should getRealPath() be used, etc. Jeff Schnitzer [EMAIL PROTECTED] _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
