We are good with Nokia Browser-Simulator/Gateway-Simulator combination. My team doing the requirement analysis, and I am specifically looking for J2EE-WAP related Reference Architectures / Design Templates. We are thinking of using the Struts framework for control/page navigation (rather Deck navigation), but when it comes to WAP, seems there are few differences like how to handle exception. To detail, if an action from a particular card generates exception at server, what is the best way to handle this? Is it like:
Redirect the same Deck with one more card detailing the exception message, with a link which will route the user to previous Deck-Card combination?
Do we have a "WAP Usability Guide" anywhere in the net or otherwise, which will list out 'best practices' for Good-Handheld-user-Experience?
|