Is anyone aware of any problems serializing the java.lang.reflection classes or using
reflection with EJBs?
In our application the EJBs return a data class containing a Hashtable which stored
java.lang.reflection classes (Fields as keys, Methods as objects). The class itself
also used reflection. Any clients making a call to the EJBs caused a
CORBA.MarshalException although the Hashtable and class were itself serializable.
What's odd is that in the IBM VisualAge IDE (for development) the application ran
fine, but when we migrated to IBM Websphere 3.0 (for deployment) this problem
occcurred. This would seem to indicate the presence of a bug, or perhaps the
serializing mechanism is somewhat different in Websphere. We eventually overcame the
problem by moving the reflection objects out of the return class and keeping it
strictly on the server side.
Thanks,
David Olivares
===========================================================================
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".
