Hello Chuck;
In general my apps are wrapped in a switch component so many
invokeActions are finally returning 'null' to get back to the same
"page-wrapper",
return context().page() is probably the better choice.
For various reasons, returning null is better for my architecture.
I think yo
Hi Andrew,
On Feb 6, 2007, at 12:41 PM, Andrew Lindesay wrote:
Hello;
In general my apps are wrapped in a switch component so many
invokeActions are finally returning 'null' to get back to the same
"page-wrapper",
return context().page() is probably the better choice.
but (possibly fo
Hello;
In general my apps are wrapped in a switch component so many
invokeActions are finally returning 'null' to get back to the same
"page-wrapper", but (possibly for the first time in a long while) I
am trying to get one of my re-usable components to fire an action,
the result of which
Nope - all in the same model.
On Feb 6, 2007, at 12:20 PM, Mike Schrag wrote:
This is reaching a bit, but are your subclasses defined in another
model and maybe you're being bitten by the "my connection
dictionaries are exactly equal" thing? WEIRD side-effects happen
when that is the ca
This is reaching a bit, but are your subclasses defined in another
model and maybe you're being bitten by the "my connection
dictionaries are exactly equal" thing? WEIRD side-effects happen
when that is the case ...
uh ".. are exactly equal .."
ms
This is reaching a bit, but are your subclasses defined in another
model and maybe you're being bitten by the "my connection
dictionaries are exactly equal" thing? WEIRD side-effects happen
when that is the case ...
On Feb 6, 2007, at 12:05 PM, John Larson wrote:
Sounds like you're moving
John,
The concrete sub-entities are not abstract - and yes, I've been
bitten by that EOModeler 'feature' too.
Unfortunately, I found another case where it's difficult to work
around it... so I'm still stuck trying to figure this out. I have a
feeling that I'm going to have to iterate ove
Sounds like you're moving on already, but I want to remember having
this problem before when using EOModeler. Creating subclasses of
abstract entities defaults the subclasses to abstract. Are you sure
your subclasses are not abstract? I use horizontal inheritance all
the time for some do
Unfortunately, that didn't work. Even with setIsDeep set to true, it
still has NULL for the table name. And yes, the abstract entity is
set to abstract.
Oh well - I'm going to go with single table for this particular
situation.
Thanks again Mike.
Ken
On Feb 6, 2007, at 10:58 AM, Mike
If you use eogen, check out the 6th template under my name on http://
en.wikibooks.org/wiki/Programming:WebObjects/EOF/Using_EOF/
EOGenerator ... I ran into this same thing a while back and grew
tired of having to remember this little nugget.
ms
On Feb 6, 2007, at 11:01 AM, Ken Anderson wrot
An excellent point Mike! I'll try it right now.
Ken
On Feb 6, 2007, at 10:58 AM, Mike Schrag wrote:
If I had to guess, I bet it's because none of the EOUtilities
methods do a fetchSpec.setIsDeep(true) and thus don't fetch on
subclasses. If you steal the code from that method and add the
If I had to guess, I bet it's because none of the EOUtilities methods
do a fetchSpec.setIsDeep(true) and thus don't fetch on subclasses.
If you steal the code from that method and add the setIsDeep, maybe
that will work?
EOQualifier qualifier = EOQualifier.qualifierWithQualifierFormat
Everyone,
I swear this has worked in the past - if I'm mistaken, please remind me!
I have an entity (MemberRuleField) with a relationship to an abstract
entity (MemberRule). MemberRule (and it's sub-entities) has a
relationship called MemberCompanyRole (this defines what company the
rule
WOServerSessionStore sessionStore = (WOServerSessionStore)
WOApplication.application().sessionStore();
* Note: this is assuming you're not using servlets and you're using
the default session store. If you're using servlets I believe this
is a different session store, and I haven't look
You are treading in some weird waters here. You have the potential
to cause very strange things from the user's perspective. For
instance, if you hijack their session, you'll be using the same
context ids they are. This means you can blow out their page cache
and cause strange state tran
Dave,
It sounds to me like this could depend on a number of factors related
to how you have designed your login system.
Do you have some type of "gate keeper" login where the first page
displayed is the login panel, or do you have a more "on demand" login
system?
I generally do the latt
Hi,
I would like to login as a user from a admins session. I don't want to do this
by a DA for security reasons. It would be great if the admin clicks on "Login
as whoever" and gets a new session with the user data in a new browser window.
The admin session should not be terminated in between.
17 matches
Mail list logo
