• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problems in using RMS in WSDD

 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
author
Posts: 1436
6
Python TypeScript Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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.
 
reply
    Bookmark Topic Watch Topic
  • New Topic