Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: domain of dmehrtash@gmail.com
 designates 64.233.170.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
        b=ZgbOAMSFUvoamxtRwUzRz6UaXnM13R9BLHsjxaeqJ/C8ESAtNTPm+NHI3hYs5iNCdibBAJOeDWY23SZ/dHjG95zfQgRkTAkMIcS9KShxJyDat609KA8mFf78MDnWlQKaM2JBi8MWwkGkM+KsXovfjOarPhlxyYYBVSLbNl78/38=
Message-ID: <e5b8e97905061613294a49e9a4@mail.gmail.com>
Date: Thu, 16 Jun 2005 13:29:28 -0700
From: Daryoush Mehrtash <dmehrtash@gmail.com>
Reply-To: Daryoush Mehrtash <dmehrtash@gmail.com>
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: .ser files in WSM
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_511_22175881.1118953768672"

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

Eddie in the previous thread you said:

 The .ser file is an artifact of the fact that the services are
deployed on Axis. Were the annotation processor targeting JAX-RPC
directly, the output of the annotation processor might not use the
.ser file.


=20
I am not sure I follow your point here. As I said in the previous thread on=
=20
the .ser file, the original of this was to solve the parameter name default=
.=20
We started off in WSM by deploying source and compile at runtime (similar t=
o=20
the drop in deployment model in Axis), then evolved into having seperate=20
build time and run time phases that deployed services by doing reflection o=
n=20
.class files, to the current iteration that uses the .ser file which means=
=20
all the work is done at build time..

You have looked at the .ser file more closely recently, but AFAIK, there is=
=20
nothing Axis specifc in it. It is essentially the 3rd itteration of the=20
model we are using to deploy services. It is true that our Axis=20
implementation understands the .ser file, but if we were say to port the WS=
M=20
to XYZ stack, our apprach would be to write an extension in the XYZ stack=
=20
that would understand the .ser file.

I don't follow what you mean when you say if we were "targeting JAX-RPC=20
directly....". Can you please be more specific here.


--=20
Daryoush

Weblog: http://perlustration.blogspot.com/

------=_Part_511_22175881.1118953768672--