Imagine the billions of user of castor, which are tired (I guess) to write a binding file from their XML Schema, while Castor can read the XML Schema, and create class (so, it can add "meaning" to the schema, in order to generate class).
>From a XML schema, an user (like me) take each type/element, and add the appropriate <XXXBinding> section so that 1) no conflicts occurs 2) if he's maniac like me, each generated class get it own package and name Wouldn't be nice if Castor does that for me the first time? If I have a very big schema - like XHML ( http://www.w3.org/TR/2004/WD-xhtml-modularization-20040218/schema_module_defs.html#a_schema_module_defs), then I suppose I will have to create each elementBinding for element that won't fit (cf. 1) 2)). I don't know if my "feature request" is clear enough, and maybe it's useless as it can certainly be done using a XSL Stylesheet, but that what's I was meaning as "a generator of binding file". 2008/5/13, Werner Guttmann <[EMAIL PROTECTED]>: > > > > Baldurien wrote: > > Werner Guttmann wrote: > >> I am not 100% sure, but - as per the warning - Castor will > >> (automatically) rename any XML name artefact that is in conflict with a > >> Java identifier to something meaningful: class --> clazz. Why the > >> binding is not used ... I will have to cross-check. > > Hum, > > > > It seems for me that this rules you're speaking is done before the > > binding, which would explain the error. > > > > Ow, I know something that could be friendly : a generator of binding > file. > > Which would be ... ;-) ? > > > Werner > -- http://www.bbnwn.eu
