is it what the browser shows ? Can you select a Page source and check ?
Sergey On 26/01/15 14:42, MayBee wrote:
Ok, that are the normal semantics of a xml prefix I know. But then, the prefixes are currently unbound for the WADL. See, I get the following generated WADL with linked XSDs: <application> <grammars> <schema elementFormDefault="qualified" targetNamespace="http://host/myNamespace"; version="1.0"> ... </schema> <schema elementFormDefault="qualified" targetNamespace="http://host/myNamespace"; version="1.0"> ... </schema> </grammars> <resources base="http://localhost:8080/app/rest/service";> <resource path="/"> <resource path="myService"> <method name="POST"> <request> <representation mediaType="application/xml" element="prefix1:typeFromXsd"/> <representation mediaType="text/xml" element="prefix1:typeFromXsd"/> </request> <response> <representation mediaType="application/xml"/> </response> </method> </resource> </resources> </application> 1. 'prefix1' is not bound anywhere. So how can it refer to any of the xsd types? 2. includes of the referenced xsd schemas seems to be not resolved. I do not know whether this is necesssary, but I would suggest so. I currently only added the root schemas to the list of schemaLocations. Nevertheless, if I also add the XSDs referenced by the root XSDs into the list (at the end), I again do not get the original XSDs into my generated WADL, but the generated XSDs -- View this message in context: http://cxf.547215.n5.nabble.com/included-xsd-s-are-not-resolved-for-wadl-generation-tp5753451p5753546.html Sent from the cxf-user mailing list archive at Nabble.com.
