Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Solaris bug?

 
Burk Hufnagel
Ranch Hand
Posts: 814
3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Argh! I've got my "final" version all packed up and ready to upload and I just ran into a problem.

I did all my development and testing under Windows (95 and 2000) but figured I'd try my application (FBNS) under Solaris at work. Everything seemed fine until I tried to book a flight.

I entered a valid value into the JSpinner I'm using to hold the number of seats to reserve and clicked the button to book the flight. At that point, one of the following should happen:
1) If the flight has no available seats, a dialog box pops up saying there are no seats available for the selected flight.
2) If the number of seats requested is larger than the number of seats left, a dialog box pops up saying there's only X seats left - where X is the number of available seats.
3) If the number of seats requested is <= the number of seats left then a dialog box pops up giving the flight info and the number of seats requested and asks whether to go ahead and book, or cancel.

Well, I was expecting number 3 and got it. I cancelled the operation and entered too many seats. I expected result 2 but got 3 - and it showed the old number of seats.

In the log file I got this cryptic message "Couldn't find X Input Context".

I know that isn't one of my messages so I searched Sun's web site with no results - then I Googled for it and found one hit. I had to use Google's cache since the page has been removed. It appears to be in the native code for Solaris's awt input method.

I played with my applicaiton a bit and found that if I just typed a new value, the old one was used. But if I use the arrow keys to move the cursor within the field then the new value gets used - at least most of the time.

The error message seems to be tied to those times I enter a value but don't move the cursor.


OK. Bottom line is this, I don't know what to do about it. Should I document that this odd behavior happens in Solaris but not in Windows and upload my assignment solution? Or, since it doesn't happen on either of the Windows versions I used, should I just forget it and upload?

Sorry for the long post, but I've been trying to get this thing done and out for way too long and I'm feeling a bit frustrated.

Thanks for any ideas you can give me.
Burk
 
Jon Entwistle
Ranch Hand
Posts: 118
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Burk,

I developed my assignment on FreeBSD with the port of JDK 1.4_4. I found some serious bugs in the JDK such as writing to a non-existant file doesn't throw an exception to name just one.

I decided the best option was to switch to Linux were the bugs did not show and use this as the development platform in version.txt.

If I were you I would put windows in the version.txt, upload, and let Sun stress about their bugs

Regards,

Jon
[ July 28, 2004: Message edited by: Jon Entwistle ]
 
Burk Hufnagel
Ranch Hand
Posts: 814
3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, Jon.

Actually, I brought up the issue with one of the architects here (who's also an SCJD from several years ago) and he suggested much the same thing.

I suppose that as a good Java citizen I should also check out the bug parade and post it if it's not there.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic