> -----Original Message-----
> From: Sergey Beryozkin [mailto:[email protected]]
> Sent: Friday, April 15, 2011 2:05 AM
> To: [email protected]
> Subject: Re: Generate human-readable documentation from WADL?
> 
> Hi
> 
> On Thu, Apr 14, 2011 at 10:56 PM, KARR, DAVID (ATTSI)
> <[email protected]>wrote:
> 
> > > -----Original Message-----it
> > > From: Sergey Beryozkin [mailto:[email protected]]
> > > Sent: Thursday, April 14, 2011 2:26 PM
> > > To: [email protected]
> > > Subject: Re: Generate human-readable documentation from WADL?
> > >
> > > Yes, I can see this link too:
> > > https://github.com/mnot/wadl_stylesheets
> >
> > I was able to get this one to work, with a few caveats:
> > * I tried several XSLT processors, and all of them failed except for
> the
> > "xsltproc" in my Cygwin installation.  XMLSpy, Perl XML::XSLT, and
> free
> > Saxon didn't work, for different reasons.
> > * I still have "/" prefixes on my @Path annotations, which is fine
> with
> > CXF, but the stylesheet output resulted in "//" prefixes.
> >
> 
> I think that works for SOAPUi which I believe concatenates the resource
> path
> values, but may be the Mark's stylesheet assumes values have no '/'
> prefixes
> and adds '/' itself. I think I'll just need to add  a property to
> WADLGenerator  (report leading '/' or not) to ensure various clients
> can
> consume it
> 
> 
> > * The output of schemas was confusing and didn't make much sense.  I
> might
> > have to have someone manually merge this output with the schema docs
> > generated by XMLSPy.
> >
> > Does the generated WADL have a proper grammar section generated ?

It has a grammars section with the schema, and the file appears to be valid.  
The HTML it generated had information about the schema, but it was hard to 
follow.

> > >
> > > However we will try to ship our own stylesheet, it's on the map,
> WADL
> > > work
> > > is one the map from now on
> > >
> > > Sergey
> > >
> > > On Thu, Apr 14, 2011 at 8:17 PM, KARR, DAVID (ATTSI)
> <[email protected]>
> > > wrote:
> > >
> > > > I'm looking for options for generating human-readable
> documentation
> > > from
> > > > WADL.  I found one stylesheet that uses obscure XSLT features
> (and
> > > uses an
> > > > apparently old WADL namespace), so that's not very practical.
> Are
> > > there
> > > > workable solutions for this out there?
> > > >
> >
> 
> 
> 
> --
> Sergey Beryozkin
> 
> Application Integration Division of Talend <http://www.talend.com>
> http://sberyozkin.blogspot.com

Reply via email to