I just want to add to that by saying it's like it calculates the first repetition correctly and then it just quits processing. Could that be the result of an illegal rule?
On Mar 14, 2013, at 12:13 PM, Johnny Miller < email@hidden> wrote: Hi Ramsey,
There is more than one rule. But that's the next issue I would like to get to. But it must be related to this one.
In my inspect page repetition
-> repetition for sections -> repetition for attributes // simplified version -> displayNameForProperty // always shows the answer for the first attribute -> objectPropertyValue // shows the right one?
i.e.
Name : Kahalawai Media Corporation Name: 42
The second column is right. The first column keeps repeating the answer for the first property??
It's bizarre. And it was all working and then mysteriously quit on me. I tried dumping my rule file and reentering the rules but that didn't fix anything.
That make any sense to you?
Thanks,
Johnny
On Mar 14, 2013, at 12:00 PM, Ramsey Gurley < email@hidden> wrote: You only have one rule? That would explain why it's the same every time :-) I assume you have other rules to override that one rule? Something like
look = "mylook" and propertyType = 'r' and smartRelationship.destinationEntity.name like 'ER*Attachment' => propertyNameComponentName = MyAttachmentComponentName [Assignment]
Assuming that is the case, you need to turn on rule tracing, and create loggers for the propertyNameComponentName key to see if/why you are using cached values. You can see how to do that here:
Notice in the video that the log4j page is a direct action. That's built into ERXDirectAction assuming you are using it. Notice that the rule loggers can be enabled without any special D2W components.
Ramsey On Mar 14, 2013, at 2:48 PM, Johnny Miller wrote: Hi Ramsey,
Still stuck over here....
How could I "permacahce" a key?
Thanks,
Johnny On Mar 13, 2013, at 4:01 PM, Ramsey Gurley < email@hidden> wrote: How are you setting propertyComponentName? I assume through rules, but if you are pushing the context, you're probably permacaching the value for your key. If not, debug your rule firings and see why it's choosing the cached value for your RHS.
Ramsey On Mar 13, 2013, at 5:14 PM, Johnny Miller wrote: Hi,
I'm trying to do the following:
I have an inspect page and inside of that I have an inspect page repetition. That all works fine and it looks like the ERD2W equivalents.
In the inspect page repetition I want to have a switch component that uses a rule to determine what kind of component to display i.e. if it is a string put one kind of component, if it's an ERAttachment put another.
Now here is where the strange things start occurring. I've defined my own key "propertyComponentName". For some odd reason whatever rule resolves to in the first property is what it displays for every property?
And what is equally strange is that suppose they all resolve to the same type of component so it doesn't matter... it will display the right property value but the property value for key always resolves to whatever the answer would be for the first property.
It's hard to describe so I created a couple of screenshots:
One of my questions is can you just arbitrarily create keys or do you need to register them somewhere?
Another Is localcontext and d2wcontext completely synonymous? Thanks in advance,
|
Aloha,
|
Mr. Johnny Miller
Web Development Manager
Kahalawai Media Company
Lahaina, HI 96761
tel: (808) 661-7962 | mobile: (808) 283-0791
website | e-mail
|
![]()
|
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|