Re: need rule help
Re: need rule help
- Subject: Re: need rule help
- From: Theodore Petrosky <email@hidden>
- Date: Wed, 13 Mar 2013 12:48:31 -0700 (PDT)
you came in in the middle of this. I have my own component TPMDSimpleListPageRepetition that replaces ERMDSimpleListPageRepetition. My component has a WOSwitchComponent at the top so I can fly in an Instructional Component if the user's permissions dictate. It is wrapped in a conditional and seems to be working as advertised.
Ted
--- On Wed, 3/13/13, David Holt <email@hidden> wrote:
> From: David Holt <email@hidden>
> Subject: Re: need rule help
> To: "Theodore Petrosky" <email@hidden>
> Cc: "WebObjects Development" <email@hidden>
> Date: Wednesday, March 13, 2013, 2:39 PM
> Sounds like a rules issue to me.
>
> headerComponent is a key that is recognized by the
> templates.
>
> If you want to change the header, why don't you just use the
> key that exists?
>
> If you need the new key "headerInstructionComponentName",
> make sure you have a fall back rule somewhere that resolves
> to true (i.e. if you are using this key in the templates,
> the template has to find a value for it, even it is a blank
> component or something - this is why I suggest using the
> default key).
>
> Take a look at the rules for headerComponent to see how the
> pros do it.
>
> d
>
> On 2013-03-13, at 11:33 AM, Theodore Petrosky <email@hidden>
> wrote:
>
> > the issue was. when I clicked the tab (takes you to the
> list page) the headerInstructionComponentName componentName
> was set in the method that fires when you click the tab.
> >
> > However if you were on the Query page and clicked the
> submit button, the key was not set so I got the error.
> >
> > Finally, I took the assignment out of the list method
> and created a rule:
> >
> > 100 : pageConfiguration like '*ProjectWorkOrder' =>
> headerInstructionComponentName =
> "ProjectWorkOrderInstructions" [Assignment]
> >
> > and this is working in all cases.
> >
> > Is there something betterer?
> >
> >
> >
> > --- On Wed, 3/13/13, David Holt <email@hidden>
> wrote:
> >
> >> From: David Holt <email@hidden>
> >> Subject: Re: need rule help
> >> To: "Theodore Petrosky" <email@hidden>
> >> Cc: "WebObjects Development" <email@hidden>
> >> Date: Wednesday, March 13, 2013, 2:05 PM
> >> If you expect the submit button to
> >> take you to a list page, why are you setting the
> header on
> >> the query page?
> >>
> >>
> >> On 2013-03-13, at 10:50 AM, Theodore Petrosky
> <email@hidden>
> >> wrote:
> >>
> >>> I think I am finally understanding the issue.
> in my d2w
> >> app, when I click the tab for a 'ListAgenda' page,
> I fire a
> >> method that ultimately does:
> >>>
> >>> ((D2WPage)
> >>
> lpi).d2wContext().takeValueForKey("AgendaInstructions",
> >> "headerInstructionComponentName");
> >>>
> >>> but when I click the submit button on the query
> page,
> >> there is no assignment of this key. So, I get this
> error:
> >>>
> >>> (ListAgenda) -
> >>
> <er.extensions.appserver.ERXComponentRequestHandler>:
> >> Exception occurred while handling request:
> >>> java.lang.IllegalStateException:
> >>
> <er.extensions.components._private.ERXSwitchComponent>
> >> : componentName not specified or componentName
> association
> >> evaluated to null.
> >>>
> >>> If I understand the problem, when I enter the
> >> QueryAgenda page, there is no assignment of the
> key
> >> 'headerInstructionComponentName' to
> 'AgendaInstructions'.
> >> this is why WO is throwing the error.
> >>>
> >>> I have tried a few iterations of rules:
> >>>
> >>> 100 : (task = 'query' and entity.name =
> 'Agenda') =>
> >> headerInstructionComponentName =
> "AgendaInstructions"
> >> [ERDKeyValueAssignment]
> >>>
> >>> 100 : (task = 'query' and entity.name =
> 'Agenda') =>
> >> headerInstructionComponentName =
> "AgendaInstructions"
> >> [ERDDelayedKeyValueAssignment]
> >>>
> >>> but no Joy!!
> >>>
> >>> Am I barking up the wrong tree? Could Joy help?
> Does
> >> anyone know Joy?
> >>>
> >>> Ted
> >>>
> _______________________________________________
> >>> 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
> >>
> >>
>
>
_______________________________________________
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