On Mon, 2008-04-21 at 19:16 -0700, Andy Clark wrote: > Notice that the JSP/tag files that compose the > response are a mixture of the default ones and the > custom ones that the skin overrides. Skin authors > should not have to make complete copies of the > default skin tree in order to edit only a handful > of files; the system should make that transparent > to them.
How about using XSL to pregenerate the JSPs? (I do this but output to the JSP XML syntax.) Your users build up a skin config in your gui(?) which can be used as the main source in the transformation. With this approach you could pretty much do away with the tag files and stick them in through the transformation. You could still use the tag files and bring them in with the document function when indicated as necessary by the config or a wrapping tag. (oh, and since the tag files are not well-formed XML there might be a handy tool out there that can well-form them for you :) ). best, -Rob --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
