On reflection, if I were to alter the default behaviour I would then have to make the current default behaviour relatively easy, so I would have to do something like add a new switch or a different special schemaNamespace tag, and I can't think of an intuitive one that is better than "all". So I'm have stuck with current proposal in that patch, leaving the default behaviour as it was. -- Kelvin.
On 31/05/07, Daniel Peter <[EMAIL PROTECTED]> wrote:
Important to me is, that the option not to generate all is still supported (not necessarily the default). Regards, Daniel. ----- Ursprüngliche Mail ---- Von: kelvin goodson < [EMAIL PROTECTED]> An: Tuscany Users <[email protected]> Gesendet: Mittwoch, den 30. Mai 2007, 18:23:05 Uhr Betreff: [SDO Java] behaviour of generator with multiple namespaces I'm applying a patch attached to [1] to the java generator which allows it to generate classes for multiple namespaces in a single run. The current fix is adopting the safe policy of not changing the default behaviour, which only exports classes for a single namespace. So as it stands, one new functional aspect of the fix allows you to use the newly reserved "all" value for the existing -schemaNamespace argument XSD2JavaGenerator -schemaNamespace all <schemafile> to generate classes for all namespaces I can see that it would be attractive to alter the default behaviour to always generate for all namespaces encountered unless directed otherwise with the -schemaNamespace or -namespaceInfo arguments (the latter being another new feature supplied by the patch). That way we could also do away with reserving the "all" tag. Would this be a problem at this stage of development? [1] http://issues.apache.org/jira/browse/TUSCANY-1233 __________________________________ Yahoo! Clever - Der einfachste Weg, Fragen zu stellen und Wissenswertes mit Anderen zu teilen. www.yahoo.de/clever
