ehearty / swadl Goto Github PK

Is there any chance you could add a license to this project?

I'm working with WADL generated by Jersey. I've come across a weird issue in chrome where it doesn't generate link to schema for complex elements correctly. I've tracked it down to the test for $ns-uri and starts-with($ns-uri, 'http://www.w3.org/XML/') = false inside the getHyperlinkedElement template. The weird thing is I can't reproduce this with test.wadl (and specifically application.wadl/xsd0.xsd) in the repo, even though they look the same (structure, elements, attributes).

Turns out boolean($ns-uri) is actually true when $ns-uri = '' in many XSLT engines including the one used in chrome (it is false in FF). See demonstration.

Based on info from stackoverflow I changed this test to not(normalize-space($ns-uri) = '') and starts-with($ns-uri, 'http://www.w3.org/XML/') = false which seems to work across browsers (at least FF and Chrome). I'll submit a PR with that change, not entirely sure why it's necessary though.

It seems like Swadl is not working in Google Chrome. It just shows a white page underneath the green bar.

When the grammar (i.e. application.wadl/xsd0.xsd) contains a class named "link" displayResult will enter infinite recursion when adding "active_schema_link" class. This is because the class name generated for schema for "link" class is "schema_link" which is the same as the internal class name used for anchors linking to result schema.

I am getting this error, any recommendations?

Unable to load wadl. Check cross-domain compatibility.

I am trying to use Artifactory's Jersey generated, which from the server is: http://server:port/artifactory/api/application.wadl. This is referenced https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API.

I downloaded the file, and edited the xmlDoc to point to a file I named at artifactory.wadl. And I get the following error:

Unable to load wadl. Check cross-domain compatibility.

I noticed the downloaded wadl references, has this:

<resources base="http://172.16.0.48:8081/artifactory/api/">

Is this the cause of the probelm. 172.16.0.48 is IP running from my vagrant box running artifactory.

Hi Elena,

Are there any plans to build a HTTP client into swadl? Swagger has one, which lets you try out the services you can document with it - it'd be great if swadl had something like this too; it would help with testing and my app devs would stop nagging me that "your APIs are so hard to call" ;-)

I'm no good with frontend webby stuff, but I can conribute some XSL if that helps.

Cheers,

Uwe