I think it's possible to specify/extend interfaces on the generated CT*
classes. So the un-/marshaller
would pick a version implementation and hopefully there is a common subset in
the properties.
I thought about lazy loading the fragments and only unmarshall them when needed.
Maybe we could also
If the schemas aren't backwards compatible and we have CT* classes in the
XSSF classes, then wouldn't that mean that we'd need to dynamically import
the CT classes and reload the XSSF classes with the correct schema at
runtime?
This sounds tricky.
On Oct 22, 2017 02:30, "Andreas Beeker" wrote:
Hi *,
I'm struggling with jaxb and the ecma v5 schemas for quite a while - maybe you
could have a look at [1].
My idea is to have several ecma version available in parallel and decide which
to use after some
introspection of a given ooxml file - AFAIK the versions are not downward
compatible.
