Am 08.03.2010 um 21:46 schrieb Mike Schrag:
> for non-D2W you have to implement that interface for every single component
> you could ever use, though ... and deal with the fact that you could have
> pages with uncommitted EO's, etc. for D2W you might be able to do a rough
> impl, but you still
for non-D2W you have to implement that interface for every single component you
could ever use, though ... and deal with the fact that you could have pages
with uncommitted EO's, etc. for D2W you might be able to do a rough impl, but
you still can't general case it if people use custom component
It's way less complicated and can be solved on a case-by-case basis (AKA do I
really need this stuff?). For one, you could almost trivially implement it in
ERD2W.
Cheers, Anjo
Am 08.03.2010 um 21:24 schrieb Mike Schrag:
> you say that like it's trivial :) if that was easy, we wouldn't need
Yeah -- I got storing these things out of process working one time, but you
have to be very very careful about what you allow in the Session. (Essentially,
nothing. Or close enough it might as well be.)
tb
___
Do not post admin requests to the list.
you say that like it's trivial :) if that was easy, we wouldn't need a sweet
stateful web framework
ms
On Mar 8, 2010, at 3:09 PM, Anjo Krank wrote:
> Bah. You don't really need to store the pages. You only need to store how
> they can be reconstructed...
>
> Cheers, Anjo
>
>
>
> Am
Bah. You don't really need to store the pages. You only need to store how they
can be reconstructed...
Cheers, Anjo
Am 08.03.2010 um 18:07 schrieb Mike Schrag:
> Even within Apple, I would suspect that worked under VERY specific
> restrictions about what can be in your session at any point i
Greetings all,
Evidently, my problem was that I believed the javadoc when it said that
filteredObjects() would return allObjects() if the displayGroup was batching.
Or perhaps I failed to consider that we may have our own implementation of
batching. In any event, filteredObjects() is what I n
John,
I am guessing that somewhere along the line the byte count is being used to
calculate the width rather than the UTF8 width.
What does your jdbc connection URL look like?
What does the 'SHOW CREATE TABLE ;' output for that table look like?
Regards, Kieran
On Mar 8, 2010, at 11:22 AM, Jo
Greetings all,
I have a component using Wonder's ExcelGenerator framework, which is based on
another component which is also using batching display groups. I have a button
which is supposed to generate an excel document version of the displayGroup. I
also am adding a row at the bottom of the
Even within Apple, I would suspect that worked under VERY specific restrictions
about what can be in your session at any point in time ... As soon as you start
persisting the backtrack cache, it's going to get crazy complicated.
On Mar 8, 2010, at 11:40 AM, Pascal Robert wrote:
> So nobody outs
Out of curiosity, what sort of data are you trying to restore with
PDsession?
Ramsey
On Mar 8, 2010, at 11:13 AM, Johan Henselmans wrote:
I store a persistent PDsession EO (not related to WOSession): if a
user is timed out in a WOSessions, the next time the user logs in,
the information f
So nobody outside Apple have been able to do this? :-(
when you're done implementing persistent session, let me know ...
ms
On Mar 8, 2010, at 11:13 AM, Johan Henselmans wrote:
I store a persistent PDsession EO (not related to WOSession): if a
user is timed out in a WOSessions, the next tim
Probably OT, but, is there a simple fix for the problem when saving some text
that contains special characters where the error misleadingly says the column
is too long when it isn't (using mysql mysql-standard-5.0.18-osx10.4-i686):
Next exception:SQL Warning:01004 -- error code: 0 -- msg: Dat
when you're done implementing persistent session, let me know ...
ms
On Mar 8, 2010, at 11:13 AM, Johan Henselmans wrote:
> I store a persistent PDsession EO (not related to WOSession): if a user is
> timed out in a WOSessions, the next time the user logs in, the information
> from the PDsessi
I store a persistent PDsession EO (not related to WOSession): if a user is
timed out in a WOSessions, the next time the user logs in, the information from
the PDsession is restored unless they explicitely close it.
The problem that occurs is that sometimes a user logs itself in twice, so the
i
15 matches
Mail list logo
