Hi David,
I tried with the latest bits, and it works for me, for example:
<ns2:resources base="
http://localhost:8080/extended-wadl-webapp/">
<ns2:resource path="items">
<ns2:doc>This is the root resource for managing items.</
ns2:doc>
<ns2:method name="POST" id="createItem">
<ns2:doc>Add a new item to the list of managed items.
The item will get assigned an id,
the resource where the item is available will be returned in the
location header.</ns2:doc>
<ns2:request>
<ns2:representation xmlns:ns3="
http://www.example.com
" mediaType="application/xml" element="ns3:item">
<ns2:doc>
<ns4:p xmlns:ns4="
http://www.w3.org/1999/xhtml
">
<ns4:h6>Example</ns4:h6>
<ns4:pre>
<ns4:code><?xml version="1.0"
encoding="UTF-8" standalone="yes"?>
<item xmlns="
http://www.example.com">foo</item>
</ns4:code>
</ns4:pre>
I do not recall any code in this area changing so i am guessing it
should also work for 1.0.3 as well.
How did you build the example? what version of maven are you using?
Paul.
On May 5, 2009, at 11:34 PM, Woodbury David-R28558 wrote:
> Hello:
>
> How can I trouble-shoot the @link tag with respect to dynamic content?
>
> I built the extended WADL sample application, included in Jersey
> 1.0.3, and the resulting WADL file did not include content
> associated with the {_at_link Examples#SAMPLE_ITEM} tag.
>
> The information was also missing from the resourcedoc.xml file.
>
> Static content associated with an @link tag does get picked up and
> displayed in the application.wadl.
>
> Thank you for any pointers on this.
>
> David Woodbury
>
>