[xsd-users] naming issue w/serialization and parsing

[Boris Kolpackov]

Hi Ray,

Rizzuto, Raymond <Raymond.Rizzuto at sig.com> writes:

> Thanks for the detailed answers.  I think part of the problem I have is
> in understanding the mapping from the schema to the object model that
> XSD generates.

This is documented in detail in the C++/Tree Mapping User Manual:

http://www.codesynthesis.com/projects/xsd/documentation/cxx/tree/manual/


> - possibly allow finer granularity to specify the style.  I.e.
> --accessor-type java

Our general philosophy in matters like this is to provide an easy
to use, high-level mechanism for commonly used cases as well as the
powerful, low-level one for situations where people want to do their
own thing. Providing mechanisms in between these two extremes is
generally not worth the effort since only a handful of people will
ever use them.


> - document the entire set of base regex's for knr, java, etc. to make it
> easier to create a mix and match version

We thought about this but decided against it since it would take up
way too much space. You can always find the exact expressions in the
source code (see xsd/cxx/tree/name-processor.cxx).


> - allow a style to be defined in a file and referenced.  i.e.
> --load-style myStyle.def.  This would also help with corporate coding
> conventions.

You can already do this using the more generic mechanism offered by
the --options-file option.

Boris