Webclient's native exception throwing mechanism half baked.

ASSIGNED
Assigned to

Status

P3
normal
ASSIGNED
19 years ago
7 years ago

People

(Reporter: edburns, Assigned: edburns)

Tracking

Trunk
All
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: suntrak-n6)

(Assignee)

Description

19 years ago
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.
(Assignee)

Comment 1

19 years ago
I accept.
Status: NEW → ASSIGNED
Target Milestone: --- → M4

Updated

18 years ago
Whiteboard: suntrak-n6

Updated

18 years ago
Target Milestone: M4 → ---

Comment 2

18 years ago
Changing QA contact
QA Contact: geetha.vaidyanaathan → avm

Comment 3

18 years ago
I reproduce this bug on NT & Linux SMP with nightly MOzilla & Webclient.
Component: Java APIs to WebShell → Java APIs to WebShell
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.