Sam and I, apparently, are the only ones who ever saw the exception: ClassNotFoundException:  test.wsdl.interop3.import1.step6.definition. <someLongName>Impl.  The stack trace implied that this was occurring during deployment, but we both were well past deployment when we got this exception.  That class did, indeed, not exist, so this change forces it to exist, even though it's never used.  I don't know why other folks don't see this problem and we do.
Sam and I, apparently, are the only ones who ever saw the exception:
ClassNotFoundException:  test.wsdl.interop3.import1.step6.definition.
<someLongName>Impl.  The stack trace implied that this was occurring
during deployment, but we both were well past deployment when we
got this exception.  That class did, indeed, not exist, so this change forces
it to exist, even though it's never used.  I don't know why other folks
don't see this problem and we do.

In my case, this exception was masking another problem.  It was as if this
exception were hanging around since deployment, waiting for some other
exception to occur, then it moved in as a doppelganger of the true
exception.


git-svn-id: 8699849808240b02471d01f5aaa03ec0c1cb68ee@254798 13f79535-47bb-0310-9956-ffa450edef68

apache/axis1-java,apache/axis1-java,apache/axis1-java,apache/axis1-java