On Saturday, November 2, 2002, at 05:40 AM, Craig R. McClanahan wrote:
On Fri, 1 Nov 2002, robert burrell donkin wrote:
snip
but that sounds like the right way to write the API. one of the
weaknesses
of MethodUtil's is that the API grew rather than being designed.
I have a very strong piece
I agree, with Craig's position. So far I have looked only at the FieldUtils.
What I found was that 1.3 reflection was badly broken, and 1.4 still had a
few oddities. The problem lay with the getField() method. getDecleredField()
was fine.
Thus the only way I can see to replicate hard coded method
invokeMethod, invokeExactMethod are poorly defined. the java doc comments
are very loose about their expected behaviour.
i think that methods should be replaced by a single series of methods that
work as if it were they were compiled ie. use the rules in the JLS.
for example invoke('method',
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13771.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Saturday, November 2, 2002, at 01:41 PM, Stephen Colebourne wrote:
snip
my main issue with the current MethodUtils API is that it not precise in
it's definition of expected behaviour. the API does not say 'this methods
finds conforms to the JLS spec'. since these methods can be called
On Saturday, November 2, 2002, at 01:53 PM, Stephen Colebourne wrote:
snip
I want to keep the same naming pattern accross the three classes, and
although I'm not wedded to these precice names, they do seem to work quite
well.
using the word 'exact' would cause confusion with the existing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9226.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Friday, November 1, 2002, at 12:05 AM, Scott Sanders wrote:
snip
#3893 multiple element body parts problem
-
i think that in this case the method gets called more than once. so, i'd
say the behaviour is reasonable. the comment from emmanual berg
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7135.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7135.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
10 matches
Mail list logo