Re: More D2W basics
Re: More D2W basics
- Subject: Re: More D2W basics
- From: David LeBer <email@hidden>
- Date: Mon, 14 Jun 2010 15:48:57 -0400
On 2010-06-14, at 3:40 PM, Andrew R. Kinnie wrote:
> I used that rule, and unchecked my old rule. It worked! Thanks. However, now I am having issues if I want to delete the related performance (more precisely, remove that performance). I click remove, and the page does not refresh and continues to show the old related performance (though apparently the relationship has been removed, because saving causes an error . . . missing the required relationship).
The ERMActionButtons (inspect, remove, delete, etc) perform ajax updates.
You might want to try and debug that in FireFox/FireBug to see if there is something breaking.
>
> Anyway, thanks.
>
> On Jun 14, 2010, at 3:22 PM, Ramsey Gurley wrote:
>
>> A picture is worth a thousand words (^_^)
>>
>> Try a rule like
>>
>> 100: not(pageConfiguration like '*Embedded*') => pageWrapperName = "AdminPageWrapper" [Assignment]
>>
>> instead. I suspect those are embedded pageConfigurations and your rule has overridden the use of their default wrapper component (D2WEmptyWrapper I think...). If you click the D2W link in your debug helpers, you'll get tables telling you your configuration names. It might also work to simply lower the priority.
>>
>> If that isn't the case, using those trace rule loggers to trace differences in the pageWrapperName rules for a modern template app and your modified app could probably help a lot.
>>
>> log4j.category.er.directtoweb.rules.ERD2WTraceRuleFiringEnabled=DEBUG
>> log4j.category.er.directtoweb.rules.pageWrapperName.cache=DEBUG
>> log4j.category.er.directtoweb.rules.pageWrapperName.candidates=DEBUG
>> log4j.category.er.directtoweb.rules.pageWrapperName.fire=DEBUG
>>
>> Ramsey
>>
>> On Jun 14, 2010, at 2:47 PM, Andrew R. Kinnie wrote:
>>
>>> OK, my rule file is based on the ERModernDemo. Specifically in to-one situations like this, I looked at the relationship from movie to PlotSummary. Clearly there are things I am not fully understanding. I didn't see anything about embedded components with regard to that.
>>>
>>> Anyway, basically, a booking is an EO representing one performance's act on one date. So aBooking.performance is a to-one. The relevant rules are pasted below (unless there are others I didn't see, but there don't seem to be. (there is another issue about trying to get the auto-generated date picker to allow the user to pick a time as well as a date, but that's not related to this)
> _______________________________________________
> 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
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
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