New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature for future] Automatic generation of class hierarchy from xml schema #12
Comments
Of course it would be useful to add the reverse as well (schema from classes). That should be easier to achieve. I'll have to check the state of the code generator (when I have time). The API should support it at this moment, but it was the case that SerialInfo was not implemented completely. On XML Schema, I'd be happy for some to work, but it is likely that we would be limited to a subset of xml schema. The way it works isn't quite the way that Kotlin/Java type hierarchies work, but supporting a common part of it is certainly possible.. |
The just released version actually builds a full representation of the types. This should make the opposite case (schema from code) quite feasible. That is certainly the easier case, but I don't see why this could not also be used to generate kotlin classes for the schema. |
Schema from classes is also quite useful. |
Hi. Any news about this feature release date? It will be very useful to have alternative to Java XJC + Krasa plugin in Kotlin multi-platform, to have Kotlin classes with validations and text captions from XSD instead of JAXB + JSR303. |
I haven't started on this (work comes first, especially over adding features). Of course a good example would be helpful, but I don't think that I'll be able to put much time in it soon. |
This feature requires some additional work and external tool, but I am putting it here just to track it. It is possible to generate Kotlin class file compatible with
kotlinx.serialization
from xml schema. We should consider doing it in future. It will also help to cover different use-cases.The text was updated successfully, but these errors were encountered: