[
https://issues.apache.org/jira/browse/CAUSEWAY-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18027998#comment-18027998
]
Andi Huber commented on CAUSEWAY-3858:
--------------------------------------
Need to investigate this, but disabling Wicket's serialization entirely might
just work for us.
ViewModels encode their state in the URL. Why would we need to serialize their
associated page's component object graph?
Entities fetch their state from the persistence layer on rendering.
For Ajax requests the relevant state is held client side (browser). Are there
exceptions?
> [Wicket Viewer] When server is still busy serializing the page, keep
> indicating busy state to the end-user
> ----------------------------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3858
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3858
> Project: Causeway
> Issue Type: Wish
> Components: Viewer Wicket
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> When page is fully rendered server-side and transferred to the client, the
> is-busy indicator disappears, but the server may still hold on to the
> response stream, when it is busy serializing the page. (Might take many
> seconds in case of large tables that use viewmodels as rows.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
