Hi Dennis, Yes I've been thinking about this too. it seems this is indeed a necessity since it is good to have seperate data binding templates for each of the frameworks. I can modify the resolver to pick up the correct databinding template according to the users input. I'm definitley +1 on the proposal and willing to go ahead if you want me to do it :)
Ajith On 6/1/06, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
Right now DatabindingTemplate.xsl consists of five separate <xsl:template match="[EMAIL PROTECTED]'name']"> blocks glommed together in one file (where 'name' is the name of each supported databinding framework, plus 'none"). This makes it difficult to extend data binding code generation, since the templates are specific to the <databinders> element. I'm currently working with this issue as part of the unwrapped support for JiBX, where I want to handle a new <wrapped> element in the input XML document. I can do this by just adding an <xsl:template match="wrapped"> to the template, but this is going to start getting very confusing if the different frameworks handle things in different ways. I'd like to split DatabindingTemplate.xsl into five separate files, one for each data binding framework, and derive the appropriate file name in AxisServiceBaseMultiLanguageEmitter by appending the framework name to the base name of the template (so there'd be DatabindingTemplate_xmlbeans.xsl, DatabindingTemplate_adb.xsl, DatabindingTemplate_jibx.xsl, etc.). Anyone object to this? - Dennis -- Dennis M. Sosnoski SOA, Web Services, and XML Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ajith Ranabahu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
