Hi there,
it’s important to note that the `WOContext` object in WebObjects ends with the
lifecycle of the request and response. This means that simply storing the
`WOContext` object is not feasible as it will no longer be available after the
request is completed.
### Possibility of Implementat
I no longer use WO but I recall this framework in wonder:
ERPersistentSessionStorage
Amedeo
> On 17 May 2024, at 22:01, Martino Limido via Webobjects-dev
> wrote:
>
> Hi there,
>
> it’s important to note that the `WOContext` object in WebObjects ends with
> the lifecycle of the request and
Your best bet is likely to store the entire WOComponent as an ivar in the
session. You can get it from context().page()
That way wen they return and the session is still alive you can return that
ivar to render where they were and what they were doing.
So you’ll need to store it in the session
On 18 May 2024, at 6:26 am, Amedeo Mantica via Webobjects-dev
wrote:
> I no longer use WO but I recall this framework in wonder:
> ERPersistentSessionStorage
That framework is a fantastic proof of concept, but in practice the approach
can be quite brittle. It works by Java-serializing the obj
