axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Davis" <...@us.ibm.com>
Subject Re: setJavaClass
Date Thu, 10 Jan 2002 11:36:29 GMT
But that doesn't explain why the Class parameter was moved from the
getDeserializer() method to a completely new method.
-Dug


Sam Ruby/Raleigh/IBM@IBMUS on 01/09/2002 06:26:03 PM

Please respond to axis-dev@xml.apache.org

To:    axis-dev@xml.apache.org
cc:
Subject:    Re: setJavaClass



Doug Davis wrote:
>
> Can someone explain the purpose of setJavaClass and why its on the
factory
> and not on the deser itself?  The comments in the code don't really
explain
> the purpose (or need for) of this method.

Before this change, a significant percentage of the runtime for even a
simple "get stock quote" was in Class.getDeclaredConstructor.  The reason?
Every deserializer would have to look up the constructor themselves as the
intended class wasn't "known" until after the deserializer was constructed.
The improvement is even more dramatic where significant time was being
spent in determining whether the class was an enumerator or not - every
single time!

- Sam Ruby




Mime
View raw message