Closed Bug 46471 Opened 26 years ago Closed 7 years ago

Webclient's native exception throwing mechanism half baked.

Categories

(Core Graveyard :: Java APIs to WebShell, defect, P3)

All
Solaris
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: edburns, Assigned: edburns)

Details

(Whiteboard: suntrak-n6)

In some cases the native implementation of some method can throw Exception over JNI. And this exception isn't described in documentation and method isn't declared throwable. For example when we try to invoke History.getURLForIndex(i) within i in out of current History bounds then native implementation of getURLForIndex throw: << java.lang.Exception: raptorWebShellGetURL Exception: getURL() returned nsnull >> due to internal error(internal method return nsnull). Of course, exception is the good way to report to the end-api-user about internal troubles, but these exceptions should be described in documentation. Now we are assume that in such logical cases(e.g illegal parameters) tests must pass, if webclient isn't crash. And all exceptions are just catched and ignored. But for clear testing documentation is preferred. Thank in advance, Alexei.
I accept.
Status: NEW → ASSIGNED
Target Milestone: --- → M4
Whiteboard: suntrak-n6
Target Milestone: M4 → ---
Changing QA contact
QA Contact: geetha.vaidyanaathan → avm
I reproduce this bug on NT & Linux SMP with nightly MOzilla & Webclient.
Product: Core → Core Graveyard
Java APIs to WebShell isn't a thing anymore. Closing.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.