we too had the same performance concerns for reflection.
so we did an elementary test using both approaches ( the ordinary 'casting'
method that impedes polymorphism & the reflection method)
inside a for loop of a local client app
{
...
code that gets a reference to the RemoteObject starting from naming.lookup
}
we found that the code that used reflection ran slightly faster !!
one plausible reason could be that the cost of casting is higher than using
constructs like -
homeObject.getClass().getMethods(); //where homeObject is of type
java.lang.Object not EJBHome
what do u people feel about this?
am i doing something fundamentally wrong here?
-sriram
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
