This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I built my application using JDK 1.4.02, using Windows XP and 98. I have just tested my application on Solaris 10, and Linux 7.2 Red Hat. I had some unexpected results.
The Solaris 10 box was running JDK 1.5. Everything came up ok, but at first there was a focus issue. Upon initial launching of my standalone or network client, I could not type in any of the text fields. I could select rows in my JTable, but could not give focus to a text field. Also I could not select rows in the JTable with the up and down arrow keys. So the application seemed unresponsive to the keyboard. Then I switched focus to another window altogether and then went back to my application window. At that point everthing seemed to work fine. I cannot imagine anything in my code that would have caused this. So that's problem number 1.
The Linux 7.2 box was running JDK 1.4.001, a previous version of the JDK than what I used to build my application. My application ran fine in standalone mode, and the server started ok as well. But when trying to run the network client, it seemed unable to make a network connection to the server. My network client startup dialog just froze up and hung, so I was hosed at that point. That's problem number 2.
Aside from those issues it seemed to work fine. My question is this: how thorough must we be in our testing on other operating systems? I imagine the examiner will try it out on Solaris (since we're talking about Sun here) and Windows. Are these issues I should be concerned about?
I think that problem number 2 (Linux problem) could be due to running my application with a previous version of the JDK than what I built the application with. In that case, I would think that you should only test your application with the same JDK that you used to build with, or a later one (not a previous one). Otherwise, it seems that it would be an invalid test.
Has anyone had similar problems? Do you think I should be concerned about these issues?
that should not be a problem, just make sure it works well if you run your client and server applications on different Windows (XP, 98) machines and for the JDK version you are using. Then document the JDK and OS versions in your version.txt. I think your assignment documentation mentions that in the deliverables section.
I had something like:
Java version: 1.5.0_02 Platform: Windows XP Service Pack 2, Debian GNU/Linux (testing)
(both did run without changes though...)
"The UrlyBird catches the certificate. And he's gonna FlyByNight"<br /> <br />SCJP 1.2/5.0, SCJD, SCBCD, SCWCD, SCEA
what if I don't Solaris or Linux to test my application?? I have mention in version.txt about JDK version and platform (win 2k & XP)..
I know it should run on any platform since it is java but nothing mention (must condition) about platform in URLbird assignment.
SCJP, SCWCD, SCBCD, SCJD, BB Java2 and JSP1.1
Joined: Feb 16, 2005
writing an application in Java does not mean that it your platform will automatically run on any platform. For example, file separators could be different, a platform might put less restrictions on the usage of ports, one system might have different security settings....
You should be fine if you list Windows XP as your only host platform in version.txt (at least my assignment said so in the "Deliverables" section), but make sure you have another Windows box available so you can run the server and client on a separate machine (for a long time the Windows version of Java has been the best one in terms of quality and performance anyways...).
Joined: Dec 10, 2003
I do understand about file system different from on platform to other but valid argument can be drawn (result in point cuts) but not failure for sure.
I am not going to test on other platform for sure (as I don't have it) and mention that in versions.txt.