I'm personally not convinced that this is a good approach, since it
starts users off on the wrong path. The whole POJO approach, while great
for demos, is fundamentally limited and certainly not a good approach to
use in real web services. So should it be the first thing users see?
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Ajith Ranabahu wrote:
Hi,
I've sent this as a reply to one of the conversations yesterday but
this seems worth more interaction from the community. So here is our
discussion on user documentation
We were discussing the user guide during the hackathon .The general
consensus was that the current documentation lacks a 'quick starter
guide'. Right now one has
to scan through at least 4 pages to get to the first code block which
will be annoying if you are looking to use Axis2 quickly [Which is the
majority case]. Most of the OSS projects (and even products!) tend to
have a quick starter guide
which is a one page guide of doing the most common tasks. This is
lacking in Axis2 and we ended up outlining this quick starter guide.
After all the quality matters more than the quantity in this case.
The outline for this quick starter guide is at
http://wiki.apache.org/ws/FrontPage/Axis2/userguide. All o you are
welcome to let us know what you think about it. The goal is to create
a 10 minute one page guide to Axis2 (which explains the basics ) and
we suppose that will be the most used (and probably the most needed at
this point) piece of documentation for Axis2.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
