raml-for-jax-rs How to handle XSD imports

How to handle XSD imports

Open justjacksonn opened this issue 10 years ago • 3 comments

Hi all,

I may be doing something wrong, but I have an XSD in path1/name.xsd that uses the xsd:import feature to import a relative path XSD ../path2/name2.xsd. The import is used due to the path2/name2.xsd having a different target namespace. When using the java code to run jax-rs generation, it seems that the use of the imported xsd fails due to what I assume is not able to find/load the relative path imported xsd.. which makes me wonder if this is an issue with how the jax-rs is using the jackson library (I think it's using jackson) to generate pojos from xsds. Anyone have any insight on this?

Mind you.. we can't change the use of ../path2 in our XSD import statement as it would break our build system and how it finds the XSDs to build things. I am looking in to converting this to Json Schema as well to see if that will solve the problem, but would like to understand better how the JAX-RS generator works with XSDs importing other XSDs.