jQuery in Action, 2nd edition*
The moose likes Java Micro Edition and the fly likes Problems in using RMS in WSDD Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Mobile » Java Micro Edition
Bookmark "Problems in using RMS in WSDD" Watch "Problems in using RMS in WSDD" New topic
Author

Problems in using RMS in WSDD

Kelly Adams
Greenhorn

Joined: Feb 15, 2003
Posts: 13
Hi,
I had problems in using the record store/bouncy castle in WebSphere Studio Device Developer( WSDD). I set up a password, hash it, and store it in record store. And later, when asked the password again, the correct password is entered,and hashed. The hash value is compared with the hash value in the record store. In Sun's Toolkit 2.0, it works fine. When I transfer the code to WSDD, however, I can never get the password right (although the correct password was entered). Does anybody have similar problems? What can go wrong?
Thanks,
Kelly
Kelly Adams
Greenhorn

Joined: Feb 15, 2003
Posts: 13
Hi,
Never mind. I found the problem. Basically there is a problem in Sun's ToolKit 2.0: when you call nextRecordID() for RecordStore, it starts from the high index and moves to low index (1), while IBM's WSDD starts from the low index(1), moves to high index. That causes a big confusion.
Michael Yuan
author
Ranch Hand

Joined: Mar 07, 2002
Posts: 1427
Originally posted by Kelly Adams:
Hi,
Never mind. I found the problem. Basically there is a problem in Sun's ToolKit 2.0: when you call nextRecordID() for RecordStore, it starts from the high index and moves to low index (1), while IBM's WSDD starts from the low index(1), moves to high index. That causes a big confusion.

I do not think it is a "problem" in WTK. If I remember correctly, the specification says that you should not assume any particular order for the "nextRecordID()" or other similar methods to tranverse a record store. It is all implementation dependent. It could start from the middle and goes to both ends or give you odd number IDs first.


Seam Framework: http://www.amazon.com/exec/obidos/ASIN/0137129394/mobileenterpr-20/
Ringful: http://www.ringful.com/
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Problems in using RMS in WSDD