Andri,
I don't what exactly you want do, but have a look on API Session :
restorePageForConextID, savePage, savePageInPermanentCache.
You can start to override this API and just log, to understand how
WebObjects works with pages and contextIDs.
HTH,
Stephane
Le
Hi Stephane,
The reason for not using the WO caching mechanism was, that I'm maintaining a
application which has pageWithName methods ad infinitum and this method does
always create a new instance of a page (please do correct me, if this is not
true), which is not the behaviour I want it to
Can you explain this more in terms of the end result you're trying to
achieve rather the approach you're trying at the moment?
On Oct 14, 2009, at 4:03 AM, Andri vonAllmen wrote:
Hi Stephane,
The reason for not using the WO caching mechanism was, that I'm
maintaining a application which
The end result:
A user navigates from page A to page B to page C.
Page C has a hyperlink to page A (return pageWithName(A)).
If clicking on this hyperlink, page A shall be shown in the same state as it
has been left (e.g. the same filter options, etc.).
Mike Schrag msch...@mdimension.com
My recommendation is not to think of this in terms of preserving the
page instance, and instead think of it in terms of preserving the
underlying model state for the page and pass that around. Now you
COULD actually pass a previous page instance into the next page
instance so you come back
I have some cases where before returning the 'next' page, I store the
current page on a var on the next page, like 'previousPage'
nextPage=pageWithName(blabla);
nextPage.setPreviousPage(this);
Then on that page I have a link or button that returns previousPage.
return previousPage;
Seems
Dear List,
in an Applications Session, a NSMutableDictionary object is used for
caching pages. Everytime the pageWithName method is called, the
dictionary is queried in order to determine if the requested page does
already exist, if true the existing page is returned, else a new one is
generated
You are messing up WO's maintenance of page state. I am surprised
this does not cause more issues for you.
Why are you doing this? It seems like a rather bad idea.
Chuck
On Oct 13, 2009, at 1:29 AM, Andri vonAllmen wrote:
Dear List,
in an Applications Session, a NSMutableDictionary
Hi!
Chuck is right, your completely screwing WebObjects up.
pageWithName returns you a component initialized for a given context
(WOContext, not EOEditingContext). If you are using the same pages for
different situations and mixing up sessions and stuff, NOTHING will
work. Nothing.
The code has been removed.
I read about caching pages using the same approach (more or less) on
this list
(http://lists.apple.com/archives/webobjects-dev/2003/Nov/msg00608.html).
I understand that WO is not supposed to work like that. But methods
like the WOComponents ensureAwakeInContext or
10 matches
Mail list logo
