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=20032>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20032 InvalidClassException and AxisFault ------- Additional Comments From [EMAIL PROTECTED] 2003-05-29 02:49 ------- Weird. Your unit testing is calling the method directly, I take it, not as a web service... can you include a little test application that demonstrates the problem (i.e. your bean class, the exception, WSDD file, and test client)? Is there perhaps another version of Axis in your classpath somewhere? If there's only one AxisFault.class (presumably inside axis.jar) which both the client and the EJB server are using, then there shouldn't be any SUID problems - though perhaps as you mention the code doing the serialization (in your EJB server) is built with a different JDK version than the client.... If that's the case, I don't see any harm in putting a SUID in AxisFault. It's not a major change (since the dynamic version was changing all the time anyway), we'll just have to be careful about updating it if we make incompatible changes to the class in the future.
