[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Jesper Pedersen commented on SHRINKDESC-92: ------------------------------------------- The use-case is that I need a tool that I can use to generate the files for the IronJacamar specific XSDs. That work isn't part of the SHRINKDESC project, so I need the tool as a Java app, that is deployed in the Nexus repo and that I can execute as part of my build. The generated files for the XSDs will be part of our IronJacamar/Embedded distribution - used in f.ex. Arquillian based environments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Jesper Pedersen commented on SHRINKDESC-92: ------------------------------------------- Our XSDs are here - http://docs.jboss.org/ironjacamar/schema/ The DTD one is filed under SHRINKDESC-91. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Ralf Battenfeld reassigned SHRINKDESC-92: ----------------------------------------- Assignee: Ralf Battenfeld -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Ralf Battenfeld commented on SHRINKDESC-92: ------------------------------------------- Except the connection_1_0.dtd, the others can be generated by the transformation now. I will now test the generated descriptors. Some little things are not correct related to the attributes. I think in few days, these descriptors are working well. Then, I will have a look about the dtd file. The good thing is, if you have in future xsd's following the same style, the generation works out of the box. Is for you also a static generation possible, e.g. generated once and you simple check-in the generated classes in your repo? That would be an alternative. Please note that Andrew told me that is is not sure that the xslt approach is coming into the final release. Regards, Ralf -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Ralf Battenfeld commented on SHRINKDESC-92: ------------------------------------------- I worked on this. The tool is ready but a little thing parsing the iconjacamar.xsd doesn't pass the test case. I think, during the next week this should be corrected and Andrew and you could review the tool. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SHRINKDESC-92?page=com.atlassian.jira.plu... ] Jesper Pedersen commented on SHRINKDESC-92: ------------------------------------------- Added some comments about the pull request - we need to extract the tool into a standalone thing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira