I'm of two minds. The world finally seems to be slowly getting past the
"just drop Java in and make services" mantra. However, many beginners
still start that way because they literally do no work to make services.
So I don't mind leaving it but we need to make some comments about the
limitations of the approach. Maybe the quick start should also have a
simple service that processes Axiom directly too?
Sanjiva.
Dennis Sosnoski wrote:
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
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
