Hi Tom,
> I'm puzzled.
> (a) the pop3.jar I have, dated June 4th, does seem to have such
> a class in it. (just use grep, or ^F on the windows dir containing
> the jar, to search for the actual string
> com/ibm/network/mail/pop3/event/MessageListener
> because that's in the jar, uncompressed.)
jar -tf don't find it, I am certain. IMO the fact that you have it points
towards the likelyhood of long term devs having the correct jar for some
historical reason, but the public tarball not having it...
> (b) you said
> java -classpath C:/src/.../soap.jar ...SMTP2HTTPBridge
> so how can pop3.jar be in your classpath?
Eh. It was a cleaned up command line to make the email more readable. I
doublechecked those jars carefully, including doing
"find -name "*.jar" -exec jar \-tf {} \; | grep MessageListener" on every jar on
this box.
Hang loose a minute for the full solution. Richard's call on the developerworks
origin of the jar was correct, but leads to another developerworks jar
dependency, this time for smtp.jar. ...I'll post the full suite of workarounds
in a couple minutes.
yours,
Lucas
