Scheduling for "Dev" for now...

I'm not sure hiding column would work because you might have two different
sesions, say a jpda and a CND native debugger and you want the column to be
present for the sake of the CND debugger.
My original suggestion was to have the concept of "N/A" (Not Applicable)
instead of UnknownTypeExceptions. The cell could either render "N/A",
or stay blank or show a "shrug" glyph :-)

I'm working around the problem as follows.
It should work regardless of who gets to be the original model and who
gets to be the filter.

    private Object fallbackGetValueAt(TableModel original,
                                      Object node,
                                      String columnID)
                                  throws UnknownTypeException {
        try {
            return original.getValueAt(node, columnID);
        } catch (UnknownTypeException x) {
            if (isOurProperty(columnID))
                return "";
            else
                throw x;
        }
    }

    // interface TableModelFilter
    public Object getValueAt(TableModel original, Object node, String columnID)
        throws UnknownTypeException {

        if (! (node instanceof Session))
            return fallbackGetValueAt(original, node, columnID);

        NativeSession ds = NativeSession.map((Session) node);
        if (ds != null) {
            if (columnID == X) {
                return X
            } else if (columnID == Y ) {
                return Y
            } else {
                return original.getValueAt(node, columnID);
            }
        } else {
            return fallbackGetValueAt(original, node, columnID);
        }
    }

IMHO this will be solved by the fix of issue #61319, this is a duplicale of that
in my point of view.
I'll set this as a duplicate after we have a fix of issue #61319.

This should be resolved by the fix of issue #61319. Therefore resolving as a
duplicate.

*** This issue has been marked as a duplicate of 61319 ***

Removing MARS keyword. The already fixed issue 61319 will be considered for
porting to 5.5.1.

verified duplicate of much more active issue