Re: Passing a wrapper component to a page-level component
Re: Passing a wrapper component to a page-level component
- Subject: Re: Passing a wrapper component to a page-level component
- From: Paul Hoadley <email@hidden>
- Date: Thu, 7 May 2009 19:55:05 +0930
On 07/05/2009, at 1:50 PM, Ramsey Lee Gurley wrote:
It sounds like you're trying to use the WOContext like a d2wContext...
I think if you do something like this in a D2WComponent named
'MyD2WComponentWrapper'
<wo:WOSwitchComponent
componentName="$pageWrapperName"><wo:EditFooPage /></
wo:WOSwitchComponent>
and set up a rule like
100: task = 'edit' and entity.name = 'Foo' => pageName =
MyD2WComponentWrapper
and generate the page in your app by using
D2W.editPageForEntityNamed
... then I think it should work and you should be able to pass
bindings to your wrapper via the d2wContext using the rule system.
As I've mentioned earlier, I've never tried this without using a
real D2WPage. Perhaps you tried this already and ran into something
else?
Thanks---the information above was the extra kick along I needed.
This seems to work, and is obviously slightly neater and more
conventional than my home-brew approach. Because I have control over
the external frameworks, I've changed EditFooPage directly to extend
D2WPage, implement EditPageInterface, and switch in the supplied page
wrapper itself. So where you've got MyD2WComponentWrapper above, I
use EditFooPage itself. I can then pass key-value pairs to the LAF
via d2wContext, and LAF will look for them if d2wContext is available,
in much the same way as the code you recommended looking at in
ERD2WHead.
Thanks again, Ramsey.
--
Paul.
w http://logicsquad.net/
h http://paul.hoadley.name/
_______________________________________________
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