Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of danieldestro@gmail.com
 designates 66.249.92.203 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=fYBzMprLt5vCI95vxBKs9y6V65nyF484e9ZhkTNff69t9C575fJFa6Ce5uH2m7U4rnmmVhQa1ajvOaQvMGSA5ITHBa9Xj9NjMQUwc8qYgDS6ayXdQGF3mI2mhztC6e0eyBmbK0yDtwrM7ncsfbulDDsQUdadeVXifjz+Yc9QvsI=
Message-ID: <99ddef2f0604050931r6c556076lf02f0076159e615e@mail.gmail.com>
Date: Wed, 5 Apr 2006 13:31:17 -0300
From: "Daniel Destro" <danieldestro@gmail.com>
To: axis-user@ws.apache.org
Subject: Re: Generating Web Service with Axis 1.3
In-Reply-To: <022e01c658c4$d5833d20$c002a8c0@KALIO>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22758_2639973.1144254677607"
References: <99ddef2f0604050715t66a9929csd1c230c27b9a5fed@mail.gmail.com>
	 <022e01c658c4$d5833d20$c002a8c0@KALIO>

------=_Part_22758_2639973.1144254677607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Chris,

Thanks for your answer.

But, IMO, tools should work for us as much as possible. I don=B4t want to
write WSDD files myself, I want some tool to make that for me. Axis can do
that, but still there is some job to be done.

Regards
Daniel


On 4/5/06, Chris Smith <cdsmith@twu.net> wrote:
>
> Daniel Destro wrote:
> > Axis code generation process seems to be a little bit cumbersome,
> > because, first of all, I have to create the WSDL, then the
> > server-side classes are generated from the WSDL. It would be much
> > easier if we could do it with only one single step and it could also
> > use my original business class instead of make me add code to
> > delegate the calls from the XXXImpl class to the business class.
>
> If you already have both the WSDL and the implementation classes, then yo=
u
> don't need to use WSDL2Java at all.  Instead, you would just write a WSDD
> file pointing to your existing WSDL and Java code.  You would need to
> include type mappings in that file, potentially using bean serializers or
> even custom serializers if your data classes are not beans.  This will no=
t
> be a trivial process, since you need to match your existing code to the
> existing WSDL interface, and there may be problems on either side.
>
> WSDL2Java is meant to generate Java code, if it doesn't already exist...
> for
> example, if you've built the interface specification first as a WSDL file
> and a set of related XSDs, and then you want to build an implementation
> from
> there.
>
> --
> www.designacourse.com
> The Easiest Way To Train Anyone... Anywhere.
>
> Chris Smith - Lead Software Developer/Technical Trainer
> MindIQ Corporation
>
>

------=_Part_22758_2639973.1144254677607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Chris,<br><br>Thanks for your answer.<br><br>But, IMO, tools should work=
 for us as much as possible. I don=B4t want to write WSDD files myself, I w=
ant some tool to make that for me. Axis can do that, but still there is som=
e job to be done.
<br><br>Regards<br>Daniel<br><br><br><div><span class=3D"gmail_quote">On 4/=
5/06, <b class=3D"gmail_sendername">Chris Smith</b> &lt;<a href=3D"mailto:c=
dsmith@twu.net">cdsmith@twu.net</a>&gt; wrote:</span><blockquote class=3D"g=
mail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
 0pt 0pt 0.8ex; padding-left: 1ex;">
Daniel Destro wrote:<br>&gt; Axis code generation process seems to be a lit=
tle bit cumbersome,<br>&gt; because, first of all, I have to create the WSD=
L, then the<br>&gt; server-side classes are generated from the WSDL. It wou=
ld be much
<br>&gt; easier if we could do it with only one single step and it could al=
so<br>&gt; use my original business class instead of make me add code to<br=
>&gt; delegate the calls from the XXXImpl class to the business class.<br>
<br>If you already have both the WSDL and the implementation classes, then =
you<br>don't need to use WSDL2Java at all.&nbsp;&nbsp;Instead, you would ju=
st write a WSDD<br>file pointing to your existing WSDL and Java code.&nbsp;=
&nbsp;You would need to
<br>include type mappings in that file, potentially using bean serializers =
or<br>even custom serializers if your data classes are not beans.&nbsp;&nbs=
p;This will not<br>be a trivial process, since you need to match your exist=
ing code to the
<br>existing WSDL interface, and there may be problems on either side.<br><=
br>WSDL2Java is meant to generate Java code, if it doesn't already exist...=
 for<br>example, if you've built the interface specification first as a WSD=
L file
<br>and a set of related XSDs, and then you want to build an implementation=
 from<br>there.<br><br>--<br><a href=3D"http://www.designacourse.com">www.d=
esignacourse.com</a><br>The Easiest Way To Train Anyone... Anywhere.<br><br=
>
Chris Smith - Lead Software Developer/Technical Trainer<br>MindIQ Corporati=
on<br><br></blockquote></div><br>

------=_Part_22758_2639973.1144254677607--