I have some session beans which, for some of their methods, take an interface. This interface is made available to the client code through our client jar. The client has written a class that implements this interface and is passing an instance of that class in to the session bean. The session bean then blows up with a ClassNotFoundException, because it cannot find the defination of the client's class. It also says RMI Class Loader disabled.
Is there anyway of fixing this whilst maintaining a client-facing API declared in terms of interfaces? Is enabling the RMI Class Loader the answer? What are the security implications of executing client-defined classes on the server? ============================================================================== This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. All information is the view of the individual and not necessarily the company. If you are not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication and its attachments is strictly prohibited. If you have received this email in error please notify: [EMAIL PROTECTED] ============================================================================== =========================================================================== 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".
