[oslc-core] Issue with Compact Rendering of a deleted (410) resource

[Michael A Jaworski]

Hi all,

I'm seeing a problem with the widget that controls the compact rendering of
a resource (rich hover), specifically after the resource has been deleted.
There are two scenarios that I've encountered that exhibit different
behavior:

1) Acceptable case: If the resource is deleted before the compact document
is fetched, the widget properly recognizes the 410 code returned by the
server and disables the rich hover on any following attempts, also
displaying a message which says, "More information is not available". (See
Image1.jpg attached)
(See attached file: Image1.jpg)
2) Failing case: If the resource is deleted after a compact document has
been previously fetched, the widget appears to ignore the 410 status
returned by the server and attempts to render the compact document again
(which instead just displays a nasty 410 exception in plain text). (See
Image2.jpg attached)
(See attached file: Image2.jpg)

>From a server standpoint, our best course of action is to display this
nasty exception with as pretty language as possible, but I don't think
that's going to be acceptable in the long run. Is this a problem with the
current spec? I would appreciate any insight as to why this happens, and
whether or not a defect should be filed for this.

Thanks,

Mike Jaworski
Rational Requirements Composer - Server Development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110923/494ae68c/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image1.jpg
Type: image/jpeg
Size: 7324 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110923/494ae68c/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image2.jpg
Type: image/jpeg
Size: 50151 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110923/494ae68c/attachment-0001.jpg>