On Apr 5, 2007, at 4:13 PM, Fred Shurtleff wrote:
Also I know what you are saying about the use of the primary key
use and EOF discouraging its explicit usage; but this does not
appear to be such a bad transgression in that it is not ever
displayed nor used as a user manipulated attribute.
Art - You have raised some interesting points not previously
highlighted. I was aware that the primary key was used for fetching, but
had not noticed the use of the special method -
objectWithPrimaryKeyValue. Also I know what you are saying about the use
of the primary key use and EOF discourag
On Apr 5, 2007, at 12:02 PM, Chuck Hill wrote:
public WOActionResults postsAction() {
WOComponent nextPage = pageWithName("TopicPosts");
Number topicID = request().numericFormValueForKey("topicID",
new NSNumberFormatter());
EOEnterpriseObject topic =
EOUtilities.objectWithPrima
Dear Colleagues,
On of our apps appears to call its Applications's:
handlePageRestorationErrorInContext at random times, during a login
session. We can not find any explanation for why this happens. To be
save, we tend to log the user out when this happens. We know, for
sure, that the af
On Apr 5, 2007, at 2:58 PM, Fred Shurtleff wrote:
Chuck,
Can you give me add'l details re: iCab - I could not reference it
in Safari Help or my handy Mac guide - "Mac OS X: The Missing Manual".
http://www.icab.de/
Also thanks for that snippet of code that reports new sessions. A
link o
Chuck,
Can you give me add'l details re: iCab - I could not reference it in
Safari Help or my handy Mac guide - "Mac OS X: The Missing Manual".
Also thanks for that snippet of code that reports new sessions. A link
on the path to where I ran into my problem does in fact create a new
session.
I am trying to work out how to use a nested editing context in my app.
I have an object that has a relationship to another object that it
owns. I am currently directing the user to another page to edit the
owned object, and need to implement a nested context to make save and
cancel work pro
Agreed ... Particularly if you turn on lock coalescing. That will eek
out some other corner cases related to churning locks without it on
(and makes editing contexts that are made on-the-fly behave more like
session default editing context).
ms
On Apr 5, 2007, at 2:45 PM, Guido Neitzer wro
On 05.04.2007, at 12:37, Karl Gretton wrote:
Does the Wonder autolocking mechanism work sufficiently that you do
not need to lock?
It seems to work well for me. I'd be careful in "corner case"
situations like LongResponsePages, spawned threads and so on, but for
"all day work" it seems to
all I can say is d'oh!
smacks his head.
On Apr 5, 2007, at 12:42 PM, Chuck Hill wrote:
Try this:
On Apr 5, 2007, at 10:30 AM, James Cicenia wrote:
OK -
Here is another one that is driving me a bit crazy...
I have a user eo. In that user eo I have a toMany relationship to
a groups table
Does the Wonder autolocking mechanism work sufficiently that you do
not need to lock?
Karl
On Apr 5, 2007, at 12:43 PM, Chuck Hill wrote:
On Apr 5, 2007, at 9:00 AM, Frank Stock wrote:
It's critical that you always lock the context (not just for
saving - for ANY operation) and that yo
Okay, now I'm having another issue with this wonderful form:
aRouting
aRouting.routingDescription
aRouting.part
aRoutingStep.stepNumber
aRoutingStep.stepName
aRoutingStep.instructions
Try this:
On Apr 5, 2007, at 10:30 AM, James Cicenia wrote:
OK -
Here is another one that is driving me a bit crazy...
I have a user eo. In that user eo I have a toMany relationship to a
groups table.
I have the following code:
public PortfolioUserGroup portfolioGroup(Portfolio po
Is the portfolio you pass in and the object receiving the message in
the same editing context?
On Apr 5, 2007, at 1:30 PM, James Cicenia wrote:
OK -
Here is another one that is driving me a bit crazy...
I have a user eo. In that user eo I have a toMany relationship to a
groups table.
I h
At first it feel strange, because my context is independant of the
thread executing the code, I don't see a relationship between the
thread running the code and the business context itself. Just that
one will be bound by the other. I would say it's a nice side effects
to be able to do it
OK -
Here is another one that is driving me a bit crazy...
I have a user eo. In that user eo I have a toMany relationship to a
groups table.
I have the following code:
public PortfolioUserGroup portfolioGroup(Portfolio portfolio){
for (int i = 0;i PortfolioUserGroup
On Apr 5, 2007, at 5:58 AM, Jean-François Veillette wrote:
Thanks Mike, I have a better picture now of what/where/how
ERXThreadStorage is helping.
I still think that I don't want per thread storage, we already have
request.userInfo for that and I use it only for web/request related
infor
I still think that I don't want per thread storage, we already
have request.userInfo for that and I use it only for web/request
related informations (used at the interface layer only).
The thread is valuable precisely for this, actually. Thread storage
lets you abstract away the "container".
Chuck,
I have to admit I did not read down far enough down in yesterday's reply
- wish I had as it would of saved me some time.
I will try your iCab advice - I'm not familiar with it and assume it is
an intuitive HTML checker?
Thanks - Fred
Chuck Hill wrote:
On Apr 5, 2007, at 9:16 AM, Fr
See Below
Guido Neitzer wrote:
On 05.04.2007, at 10:16, Fred Shurtleff wrote:
I checked the session (using Session session = (Session) session();)
immediately B4 setting the session user and again when I retrieved
the session user, and they were, in fact, DIFFERENT. So this explains
WHY the n
On Apr 5, 2007, at 9:00 AM, Frank Stock wrote:
It's critical that you always lock the context (not just for
saving - for ANY operation) and that you make sure you're not
crossing objects in different editing contexts.
I did not lock in a fetching-data -routine. Now that I have locked
On Apr 5, 2007, at 9:39 AM, Frank Stock wrote:
Ken,
I was to early with my conclusing, there are 'updates' again, only
it takes a much longer time now. I will try with 1 instance first
and see what I get.
That just means that there is still someplace in your code where you
are not loc
On Apr 5, 2007, at 9:16 AM, Fred Shurtleff wrote:
Hi All,
I checked the session (using Session session = (Session) session
();) immediately B4 setting the session user and again when I
retrieved the session user, and they were, in fact, DIFFERENT. So
this explains WHY the null user(and wh
Ken,
I was to early with my conclusing, there are 'updates' again, only it
takes a much longer time now. I will try with 1 instance first and
see what I get.
Op 5-apr-07, om 17:10 heeft Ken Anderson het volgende geschreven:
Frank,
On Apr 5, 2007, at 10:49 AM, Frank Stock wrote:
Ken,
- Storing IDs in Cookies and the browser does not accept the cookie?
Also, storing the ID in cookies and your host name changes (from
10.x.x.x to localhost, for instance)
ms
___
Do not post admin requests to the list. They will be ignored.
Webobjec
On 05.04.2007, at 10:16, Fred Shurtleff wrote:
I checked the session (using Session session = (Session) session
();) immediately B4 setting the session user and again when I
retrieved the session user, and they were, in fact, DIFFERENT. So
this explains WHY the null user(and why the KVC call
Hi All,
I checked the session (using Session session = (Session) session();)
immediately B4 setting the session user and again when I retrieved the
session user, and they were, in fact, DIFFERENT. So this explains WHY
the null user(and why the KVC calls seemingly did not work), but opens
up a
Ken,
Op 5-apr-07, om 17:10 heeft Ken Anderson het volgende geschreven:
Frank,
On Apr 5, 2007, at 10:49 AM, Frank Stock wrote:
Ken,
Our client uses 1 instances where we directly connect to and we
get this error:
Encountered a newly inserted EO with an owns destination
relationship but no
Frank,
On Apr 5, 2007, at 10:49 AM, Frank Stock wrote:
Ken,
Our client uses 1 instances where we directly connect to and we get
this error:
Encountered a newly inserted EO with an owns destination
relationship but no snapshot.
These types of errors are usually in response to abuse of EO
Ken,
Our client uses 1 instances where we directly connect to and we get
this error:
Encountered a newly inserted EO with an owns destination relationship
but no snapshot.
I am currently testing our application to work with more instances, I
can't repeat the error above, but I wan't to u
Frank,
If you run with a single instance, does it ever have a problem?
Sounds to me like you're having problems with the snapshot not being
fresh.
Ken
On Apr 5, 2007, at 10:27 AM, Frank Stock wrote:
Hi All,
I have been working for 2 days on this. Readed 'Managing the Object
Grapth' a
Hi All,
I have been working for 2 days on this. Readed 'Managing the Object
Grapth' again. But I don't understand this.
I have 3 instances running with this application. I have a second
application that randomly fetch, insert/update and delete one row
choosing one of the instances. (I use S
Thanks Mike, I have a better picture now of what/where/how
ERXThreadStorage is helping.
I still think that I don't want per thread storage, we already have
request.userInfo for that and I use it only for web/request related
informations (used at the interface layer only).
I still feel uncom
Hi, David,
On Apr 5, 2007, at 7:07 AM, David Avendasora wrote:
Okay, I spoke a little too soon.
Besides all the code I had written to update the values manually, I
also had calls to other methods that updated things dependent upon
the values set in the form.
Now that I'm letting WO do al
It is almost what I had in mind, only that I don't want a different
map per thread, I need a single map no mater how many threads.
Why would we want a different map per thread when you use the
editing context as a key ?
When you receive a request (worequest), you have to set the map
every tim
Hi,
I have deployed a webobjects application as a servlet in a JBOSS
container.
I have another servlet deployed in the same container through which I
am trying to invoke the webobjects servlet using
requestdispatcher.include
I am getting the below error when requestdispatcher tries to inc
Okay, I spoke a little too soon.
Besides all the code I had written to update the values manually, I
also had calls to other methods that updated things dependent upon
the values set in the form.
Now that I'm letting WO do all the work, it apparently waits to do it
until "return context()
Never-mind. It seems to be working correctly after-all. Now reading
Chapter 6 of Practical WebObjects.
Dave
On Apr 5, 2007, at 6:07 AM, David Avendasora wrote:
Okay, I spoke a little too soon.
Besides all the code I had written to update the values manually, I
also had calls to other meth
38 matches
Mail list logo
