> Any thoughts on the viability of this approach? Any alternative approaches?
Sounds complicated. But if you want to preserve the markup of your source file, using xsl might be the way to go. An alternative or additional tech is to create custom wicket tag handles (e.g. to handle <wicket:interaction>) that dynamically inserts (auto)components in those spots. Look at the existing ones for ideas. Or you could just use a factory for building your form dynamically using the XML file as input. But that would only work well if you don't want to preserve your markup (e.g when you'd only have 'interaction' regions and maybe a very limited set of primitives for defining layout such as <block>, <list> etc) Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
