[
https://issues.apache.org/jira/browse/PIVOT-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915882#comment-13915882
]
Labrosse Aurélien commented on PIVOT-936:
-----------------------------------------
Hi Sandro,
Thanks for your quick response. A schema generator could be a good solution.
Its invocation would be integrated into the Maven build process, providing a
schema that matches the source code as each rebuild/release.
It is the exact opposite way I usually do, a kind of automated reverse
engineering :)
I would be happy to contribute if I can, say, if we keep Pivot as part of our
process.
regards,
> Create a XML Schema for BXML
> ----------------------------
>
> Key: PIVOT-936
> URL: https://issues.apache.org/jira/browse/PIVOT-936
> Project: Pivot
> Issue Type: Improvement
> Components: core-xml
> Reporter: Labrosse Aurélien
>
> I saw an older bug that focuses on DTD, which was sadely closed.
> From my point of view using XML without schema is dangerous for project
> adoption : as a model driven architecture fan, i can't use a perfect mapping
> to produce BXML code without an ugly generator.
> The xml schema would suppress this limitation and leverage Pivot to a more
> professional level. It would allow its core syntax to be used in various
> existing model transformation tools available on the Open Source market.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
