| Key: |
COR-710
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Patrick Roemer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
Not Specified
|
|
|
Remaining Estimate:
|
0h
|
|
|
Time Spent:
|
2h
|
|
|
|
| Resolution Date: |
22/Aug/07 07:44 PM
|
| Labels: |
|
| Participants: |
Patrick Roemer
|
| Number of Attachments: |
0
|
| Number of Comments: |
0
|
|
Calling ObjectSet#get() for an invalid ID in C/S mode is expected to trigger an IOOBE on the client. But the exception is not caught on the server (and consequently there is no client notification) - the application hangs. (This may not be the only case where valid use of the List API triggers (runtime!) exceptions that should be transmitted to the client.)
For this specific case, the exception occurs in MObjectSetGetId#processAtServer().
|
|
Description
|
Calling ObjectSet#get() for an invalid ID in C/S mode is expected to trigger an IOOBE on the client. But the exception is not caught on the server (and consequently there is no client notification) - the application hangs. (This may not be the only case where valid use of the List API triggers (runtime!) exceptions that should be transmitted to the client.)
For this specific case, the exception occurs in MObjectSetGetId#processAtServer(). |
Show » |
| There are no comments yet on this issue.
|
|
IndexOutOfBoundException triggered by ObjectSet#get() is not caught on the server