Problem refreshing UI after document deletion

[pibou_Bouvret]

Hi,

i'm trying to implement a permanent deletion feature : I created a document type that lists the deleted documents for a given user, so that he can permanently delete the selected ones.

Everything runs fine ... for the first deletion

It seems that the previsously selected documents are still cached somewhere in the UI (my "permanently delete" button is enabled although selection is empty), so that if i try to delete a second batch of docs, i get a "No such document" error.

I tried to use the Seam.Refresh operation, but it doesn't seem to work.

Any idea ?

[Laurent_Doguin]

quick question, does it work when you click on the refresh button from the UI?

[pibou_Bouvret]

No,

[Benjamin_Jalon1]

Can you give us your operation chain you used to implement the permanent deletion ?

[pibou_Bouvret]

That is simply

[pibou_Bouvret]

Same kind of problems with my new "validate button"

[Laurent_Doguin · Accepted solution]

Actually we're missing a 'Clear Selection' operation, a bit like 'Clear Clipboard' works.

The code of your operation would look like that:

@OperationMethod
public void run() {
    OperationHelper.getDocumentListManager().resetWorkingList(
            DocumentsListsManager.CURRENT_DOCUMENT_SELECTION);
}

This will empty the current selection. The refresh UI operation only invalidates queries cache.

[pibou_Bouvret]

Thx.

[pibou_Bouvret]

the 'Clear Selection' operation works fine : I can select documents after a deletion, nevertheless i still have to refresh the list with my "refresh" automation chain.