Thanks for the update. I am actually working on a Java RAML Parser Java SDK generator… (e.g. using the Java RAML parser project to parse RAML into Java, then sifting through the object to generate java SDK).
I suspect I am not alone among the RAML users that would want a single project that could handle building SDKs, server side and documentation, and possibly automation test code as well… from RAML documents. That said, there are some things that may still need to be added to the 1.0 spec (assuming it’s not too late… still waiting on some sort of status update on that project) such that we can utilize XSD/JSON Schemas that refer to multiple types in the documents, including those that import/include other schema files into the same namespace. Right now, there doesn’t appear to be a good way to identify individually defined types inside an XSD schema for example, within the RAML document. I’ve opened an issue around that here (https://github.com/raml-org/raml-spec/issues/137) if you’d like to understand a little bit more about that.