> This is normal then. Class foo loaded by class > loader A is not castable to class foo loaded > by class loader B (if they are really independent, > of course - if A is the parent of B and B > delegates, it will work). You have to > put the class in a spot shared by both > webapps (that means the shared class loader. > > Remy
Then how does this work in a general client- server relationship such as RMI servers, EJB servers, etc. Don't they usually just give you a jar with the classes that you add to your client? Having to use the exact same file seems excessive???! Isn't there some way to allow use of a copy of the class? -- Frank -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
