Anthony Elder wrote:
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.
Great!
The only issue I can think of wasAh we solved this at the 2nd f2f. There's going to be a very clean hierarchy of
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)
contexts scoped at the different levels of the lifecycle. This will give you a perfect
solution for this problem.
I do agree with some of Glen's comments on the spelling in the code, but II agree 100% the code and comments should be in good (Queen's? :-)) English. I
can't see how that will get fixed unless native speakers like me start
posting corrections to this list.
too will soon be getting into the code and will fix minor stuff as I see it. Your
contributions would be most welcome!
I didn't reply to Glen's note because I felt it was going too farand so wanted to write
a more detailed reply .. which means I never got to it :-(. While I would like the Sri
Lankan guys to write in perfect English, I'd rather have them having verbal
diarrorhea (sp?) on the mailing list than not writing because of worrying about
the English. The more you write the better you get right?
The same for the docs; let's write something down and keep improving them, rather than clamming up and not writing.
Sanjiva.
