you can do two types of service development with Axis2.
1. Contract first
This is what you currently doing. you start with a wsdl file (contract)
and generate the java code for this.
2. Code first approach
you first write the service classes and then generates the wsdl and
service from those classes.
So I think what you ask for the second option. This article may help you
http://www.developer.com/services/article.php/3726461
And also see the Axis2 documentation.
thanks,
Amila.
On Feb 14, 2008 8:17 AM, Kraus, David <[EMAIL PROTECTED]> wrote:
> Currently our web service generates server-side logic automatically using
> wsdl2java with the "–ss" parameter. The resulting classes handle the
> serialization of complex objects, created on the server-side, to xml to be
> transported back to the client (and vice-versa).
>
>
>
> My question is: Is this the required approach? Can the Axis2 core
> (provided in the binary distribution) also provide serialization, if the
> targeted complex objects (used as API parameters, and return objects) adhere
> to JavaBean requirements? Or must the web service developer provide
> serialization/deserialization for all complex objects introduced into a web
> service API?
>
>
>
> Thanks, Dave
>
--
Amila Suriarachchi,
WSO2 Inc.
