[jboss-jira] [JBoss JIRA] (WFLY-3941) Provide a translator .xsd->parser+object model

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar closed WFLY-3941.
-----------------------------
    Resolution: Rejected


You are thinking too much in forms of XML.
XML is just current default persistent state of the model.
There are initiatives to support different formats like json for our persistent model. Based on that XSD --> model definition tooling would be just redundant extra work.

You can still make it as standalone tool and we can add it to Wildfly Extras https://github.com/wildfly-extras but I don't see any good reason to have this in main code base or a definitive go-to tool for writing subsystems.

> Provide a translator .xsd->parser+object model
> ----------------------------------------------
>
>                 Key: WFLY-3941
>                 URL: https://issues.jboss.org/browse/WFLY-3941
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>            Priority: Minor
>
> When writing a new subsystem, it would be good to have tooling that takes a .xsd for the <subsystem> element and translates its content in a rough first form of parser + matching object model (*Definition, *Add and so on).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)