On 17.04.2006, at 20:34 Uhr, Jonathan Miller wrote:
e.g. when someone hits the back button and then uses a WOHyperlink
w/n the page it performs the wrong action.
In which context is the hyperlink?
cug
smime.p7s
Description: S/MIME cryptographic signature
___
Dunno if that is your problem but one of the most likely causes is
having the underlying array of a WORepetition change between the time
it rendered and the time the link was clicked (object inserted/
deleted, sort order changed, batch size changed etc). You have these
options:
- use Direc
Hi, Jon,
On Apr 18, 2006, at 12:42 AM, Jonathan Miller wrote:
Hi,
I'm certainly guilty of using the appendToResponse method without
understanding its true role in the response generation, so this
could very well apply to me. Since I'm mainly using
appendToResponse to reset counters I u
Hi Lists,
This is about WOFileUpload again... :D
Sorry to ask about this again but I can't find any solution
to this problem.
I have to Components;
1. Main
2. ViewPhotoPage
2. SubmitPhotoPage
The Main page has a WOSwitchComponent where the variable
"strPageNameToShow" is bound to. The default p
Hi,
I'm certainly guilty of using the appendToResponse method without
understanding its true role in the response generation, so this could
very well apply to me. Since I'm mainly using appendToResponse to
reset counters I use during page generation do you think I'd be
better served by
Hi, Jonathan,
I don't know what the abbreviation "w/n" means in your second
sentence, so your message is a little difficult to parse, but it
doesn't sound like you're facing a page caching issue (except,
perhaps, indirectly).
Performing the wrong action tends to be a characteristic of the
Hi Baiss,
On Apr 17, 2006, at 11:04 AM, Baiss Eric Magnusson wrote:
Chuck,
Thanks much for below, things are better.
The timeouts I have worked with are:
sun.net.client.defaultReadTimeout=15000
in the Properties file loaded in Web Server, this time in milli-
seconds
Receive timeout: 180
Peter,
On Apr 17, 2006, at 3:07 PM, "peter Burnes" <[EMAIL PROTECTED]>
wrote:
While I do use automated primary key generation, I inherited a few
tables that are "join tables" where the primary keys are compounded.
It seems like from reading the Apple docs and even seeing the
propagate primar
Assuming your model is correct and that you have a join table properly
defined and joining two entities named, e.g. Person and FavoriteFood
then using the required compound key can be as easy as:
Person aPerson = new Person();
editingContext().insertObject(aPerson);
FavoriteFood BenAndJerry =
Compound primary keys work fine, so do custom generated ones. I use
both in several models (lots of compound ones, a few custom ones).
Using compound keys for join tables is "the WebObjects way", and
there shouldn't be any problems setting them up. Check the rules
about using key propagat
Hi,
I'm following Apple's Guidelines on setting up server side page
caching (i.e. setPageRefreshOn... && setPageCacheSize(int)) but it
doesn't seem to be working...
e.g. when someone hits the back button and then uses a WOHyperlink w/
n the page it performs the wrong action.
Does anyone
Chuck,
Thanks much for below, things are better.
The timeouts I have worked with are:
sun.net.client.defaultReadTimeout=15000
in the Properties file loaded in Web Server, this time in milli-
seconds
Receive timeout: 180
in the Adaptor Settings of JavaMonitor, this time in seconds
a
Hello,
Does anyone out there use compound primary keys in their EO model? I
know there are several ways to model persistence, but I am sort of
stuck with a database structure that cannot be changed (at the
moment). I have read/been told some WebObjects advice that we seem to
give dire warnings a
13 matches
Mail list logo