So I edited my rules, and I saw this during editing a platform, with no Obs
bound :
So Obs and Ship are mixed up. It should be Obs. I checked relationships inside
my eomodel, they seem to be correct...
And on another edit page (for another entity not mentioned till now), this
problem happens between PTF and Ship (after editing rules to avoid the previous
problem) :
For the query form, it is just the name which is not correct, the form fields
are the ones from PTF...
I will focus on Ship, hopping it's not a lure... :)
Anthonin
On Mon, 2015-02-09 at 12:55 +0100, Lize Anthonin (@JCOMMOPS) wrote:
Fabian,
Thank you for your reply.
Actually I didn't set any rule for that page (it's coming only from D2W
framework). It's indeed the page EditPtf, but that page displays the ship
information through the relationship. And it displays also Obs information
through a M-to-N relationship.
But as a quick fix, I'll try to override displayPropertyKeys when
pageConfiguration is "EditRelationshipEmbeddedObs", so that it matches "Obs"
entity fields.
Thanks,
Anthonin
On Mon, 2015-02-09 at 10:42 +0000, Fabian Peters wrote:
Hi Anthonin,
Looking at the stacktrace I see "D2W-EntityName" = "Ship", but
the page is "EditPtf" and the pageConfiguration is
"EditRelationshipEmbeddedObs". I'd say you're applying a displayPropertyKeys
rule that's meant for the "Ship" entity to the "Obs" entity. But I may be
entirely wrong…
Fabian
Am 09.02.2015 um 09:11 schrieb Lize Anthonin (@JCOMMOPS)
<[email protected]>:
> Hi all,
>
> I ran into the following - quite classic - error, and I don't
know what is causing this :
> <com.webobjects.eocontrol.EOGenericRecord 0x4813735d>
valueForKey(): lookup of unknown key: 'autonomy'. This class does not have an
instance variable of the name autonomy or _autonomy, nor a method of the name
autonomy, _autonomy, getAutonomy, or _getAutonomy
>
> Just to present the situation, in my design, a Platform (PTF)
is bound to a Ship (SHIP).
> It's a D2W app and it appears when I want to edit a PTF, but
not when I want to edit a SHIP (so probably tied to a not nullable constraint
or something like that).
>
> Here is what I have checked so far :
> - Given the attached stack trace, I checked the Ship entity
and the "autonomy" field is indeed present in my table.
> - The Ship_id field in PTF is indeed nullable.
> - If I delete from my eomodel the 'autonomy' field (which is
the first in alphabetical order), the next one fires the same exception.
> - If you look at the stacktrace, you can see that the rule
'pageConfiguration' is set to EditEmbeddedRelationshipObs :
> "D2W-PageConfiguration" = "EditRelationshipEmbeddedObs";
> Obs is another table (a PTF is bound to * Obs). But Obs
is not bound to Ship in the model. It is like it is looking for Ship fields
when listing the Obs and obviously it does not find the ship fields inside the
obs entity.
>
> It seems to be a quite obvious problem to resolve, but I
can't see it apparently.
> If someone has an idea, it would be very helpful!
>
> I keep digging.
> Thanks
> --
> Anthonin Lizé
> <stacktrace.txt>
_______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list
([email protected])
> Help/Unsubscribe/Update your Subscription:
>
https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com
>
> This email sent to [email protected]
Cliquez sur l'url suivante
https://www.mailcontrol.com/sr/Ma8NcAX!KTvGX2PQPOmvUnk1PR6ftzo0HYbJRywOFupRbHy353ajyWCFrGjftC+SZGQNskQ9zi8FoPzuIXnePg==
si ce message est indésirable (pourriel).
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
