Axis 2 looks good, quick to pick up. All the doc definitely helped and
seemed quite comprehensive for an m1 release - I think its important that
its kept up to step as the code develops. The only issue I can think of was
I needed somewhere to stash away the Rhino compiled script object so the
compile only happens on the first request to a service. I ended up adding
it with a unique key to the map of operations on the AxisService which
isn't very nice. Maybe the AxisService should have a bag of general
properties. (I used the M1 release)
I do agree with some of Glen's comments on the spelling in the code, but I
can't see how that will get fixed unless native speakers like me start
posting corrections to this list.
...ant
Anthony Elder
[EMAIL PROTECTED]
Web Services + ESB Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
Sanjiva Weerawarana <[EMAIL PROTECTED]> on 27/04/2005 10:35:47
Please respond to [email protected]
To: [email protected]
cc:
Subject: Re: [Axis2]Article on E4X
Anthony Elder wrote:
>
>
>I've already written an E4X provider for AXIS2 for a subsequent article in
>this dW series. I'll see if I can post the code here before the article
>comes out.
>
Excellent. Can you comment on your experience in writing a provider for
Axis1
vs. Axis2? Any other comments that you think may help improve Axis2 would
be very welcome.
Thanks,
Sanjiva.
