The javadoc for the sample code is linked to source code. Just click
on the class or method at the appropriate link.
For example, the javadoc for the 'Samples' class is at:
https://glassfish.dev.java.net/nonav/javaee5/amx/samples/javadoc/
amxsamples/Samples.html
Clicking on the Samples classname yields:
https://glassfish.dev.java.net/nonav/javaee5/amx/samples/javadoc/
amxsamples/Samples.html#Samples(com.sun.appserv.management.DomainRoot)
Sample code may be found at glassfish/www/javaee5/amx/samples/amxsamples
I'll look at the layout of the page as far as news, etc.
Lloyd Chambers
Appserver team
Sun Microsystems
On Jul 20, 2006, at 1:39 PM, Kohsuke Kawaguchi wrote:
>
> I did a bit of experiment with AMX to see if I can use it for
> automating JAX-WS tests. I found a few things about AMX while this
> exercise, so I thought I'd send it here to see if the glassfish
> developers are interested in fixing those.
>
> 1. This webpage https://glassfish.dev.java.net/javaee5/amx/ is great,
> but it has a few things to be desired.
>
> - it has a link to the sample code javadoc, but it's more
> appropriate
> to link to the sample source code in FishEye, or better yet, a
> downloadable sample bundle. There really isn't much point in
> seeing
> the *javadoc* of the sample --- I want to see the code!
> (I still haven't found where the sample source files are in the
> repository.)
>
> - There are things that are only linked from the "news" section.
> I thought the way news works is that you add something to the main
> page (the rest of the page), and then *also* put that to the news
> section to highlight it. I find it confusing when something is
> only
> available in the news, because as the first-time visitor to the
> website, I thought I didn't need to read any news.