Indeed, it's not true. We do both client-side and server-side
state saving.
Also, there'll be some terminology confusion: ADF's default
client-side state saving only saves a token to the client,
and saves the real state in the HttpSession - so you don't
have the major performance and I/O drag
Adam,
(And we do support a client-side state saving mode
that pushes everything to the client for
HttpSessionophobes,
but it's not the default)
How do you turn on that? I haven't seen that ...
Frank Felix
From the configuration docs:
oracle.adf.view.faces.CLIENT_STATE_METHOD
Chooses the type of client-side state saving used when client-side
state saving is enabled (with the JSF standard javax.
faces.STATE_SAVING_METHOD parameter). Two values are accepted:
token: the default, which stores page
[EMAIL PROTECTED] schrieb:
I just released, that the InputSuggestAjax of the Sandbox doesn't work
together with Oracle ADF...
When I'm typing something into the SuggestBox, i just get the following
message on my console (but I don't get any suggestitems nor any
errorstack...)
2006-03-29
Looks like ADF enforces client side state saving.
Yes, seems to be.
Sorry, but the component doesn`t work with client side state saving at
the moment.
It`s on my opened-issues list, but I had less time to fix it.
If you switch to server side it should work fine.
cheers,
Gerald
On 3/29/06,
ADF enforces client-side state-saving? I can't believe that!
regards,
Martin
On 3/29/06, Gerald Müllan [EMAIL PROTECTED] wrote:
Looks like ADF enforces client side state saving.
Yes, seems to be.
Sorry, but the component doesn`t work with client side state saving at
the moment.
It`s on
6 matches
Mail list logo