Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The original getFishTicketNumbers() registered your request associated with a operation id and then returned the same list of numbers at every request. As a result users had to scan the list and remove any numbers that had previously been used. The getFishTicketNumbers002() behaves very similarly to getFishTicketNumbers(), in that it reserves numbers and assocates them with a give operation id and will return the same list of numbers on subsequent requests. However, unlike getFishTicketNumbers(), the getFishTicketNumbers002() removes any numbers that have been used on unsubmitted reports, deleted reports or submitted reports.

The getFishTicketNumbers002() takes five arguments:

  1. String Userid – i.e "amarx"
  2. String password – i.e. "A_marx"
  3. String schemaVersionNumber – i.e. "2.1"
  4. String operationId - i.e. "1"
  5. String numberOfNumbersRequested - i.e. "10" or null

Each user is associated with one or more operation ID's. You can find a legal operation ID for a user by calling the web service getUserInfo() and examining the list of returned operations associated with the user profile.

If we pass in a numberOfNumbersRequested=10, we are asking for 10 new fish_ticket_numbers from the database that have never been used and will be reserved for our use. If null is passed in for numberOfNumbersRequested, the system will return all previously reserved tickets without adding new numbers to the list.

String xml = svc.getFishTicketNumbers002("amarx", "A_marx", "2.3", "1", null);

...