Howdy, >Obviously I can't tell which methods are there via this technique. I'm just >trying to show the dates on the different classes to show that they are >from >the late-June version of the commons fileupload jar, as opposed to one of >the betas or RC* releases which had earlier dates. I'm taking it on faith >that the method I want is in there. Frankly, I'm not really sure how to >tell what methods are in a given class in a jar file.
Using the dates is not conclusive. One way to tell what methods are (or more importantly for this case, aren't) in the fileupload jar is to compile your classes against it. Not compile them someplace else and then deploy, assuming it's the same jar file. >I'm not sure I understand your advice. I did the compile in Eclipse on my >Windows machine. All I'm doing on the Linux box is importing a WAR file >that contains the already compiled class files from Windows. Either include the fileupload jar against which you compiled in the WAR file, or compile against the fileupload jar that's on your linux machine. >| Tomcat 4.1.26, which is looking like the next stable release at the >moment, have the fileupload 1.0 | final. Feel free to download and use it. > >Do I really need to do this? Tomcat 4.1.24 and commons-fileupload-1.0.jar >seem to work fine on my Windows machine. Shouldn't they also work fine on >the Linux box? They should work fine, but they aren't because somewhere along the way from your windows setup to your linux setup is a different fileupload jar. The reason I mentioned it is that tomcat 4.1.24 and 4.1.26 use different versions of fileupload, that are inconsistent as far as the API goes. >I'm still relatively new to Tomcat and Linux so I may be asking stupid >questions; if so, I don't mean to be. I'm just trying to understand what's >going wrong. It's very possible that I've made some kind of newbie mistake; >I'm just trying to understand what it is and how to fix it. This is more of a general issue: make sure you're compiling against the same libraries that you will deploy to. No question is stupid, but this is a common error. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
