On Mon, 2008-06-16 at 10:09 +0200, Paul Sandoz wrote:
> Martin Grotzke wrote:
> > A way to keep this flexible would be to create a specialized
> > DocumentedWadlGenerator, that extends WadlGenerator, so that clients can
> > use what is preferred. Of course WadlGenerator methods have to be
> > changed to instance methods then. I would prefer this solution.
> >
> > What do you think?
> >
>
> +1
>
> There are also two issues logged against WADL generation:
>
> https://jersey.dev.java.net/issues/show_bug.cgi?id=29
> https://jersey.dev.java.net/issues/show_bug.cgi?id=50
>
> For the latter issue formating could be optional, but i think the
> following is important:
>
> would be also good if there would be the a simple comment saying which
> jersey version has been used to generate the WADL at the beginning.
> Ie. sth like what JAX-WS has
>
> If you have time perhaps you could look at these as well?
Yes, I will.
Cheers,
Martin
>
> Paul.