Open avinashpaul opened 9 years ago
Hi, @avinashpaul. Sorry for late response. We had a lot to do for the "Connect" conference.
Right now we do not support such manner of including chemes. We support only standard. According to it, the element
attribute must contain "qualified name of the root element as described within the grammars
section".
So, could you, please tell more about the syntax you use. Is it a common practice?
Regards, Konstantin
@KonstantinSviridov thank you for the reply , so you mean to say only the below case is handled
<grammars>
<schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<element name="Customer">
<complexType>
<sequence>
<element name="id" type="string" />
</sequence>
</complexType>
</element>
</grammars>
....
....
....
<representation mediaType="application/xml" element="Customer" />
I would say, it would work like this:
<grammars>
<include href="http://www.example.com/Schema_where_Customer_element_is_defined.xsd"/>
</grammars>
<representation mediaType="application/xml" element="Customer" />
The resulting schema will be just the same as Schema_where_Customer_element_is_defined.xsd
.
Hi @KonstantinSviridov , I try out this project. It does a great job of converting WADL to RAML , It is missing a common feature , the below WADL request element
is mapped in raml as below
But the Schemas section does not have any reference to Customer , the below part is missing from generated RAML file