Apple

It might be useful... let me finish the Wonder version and organize how I would document it.

What I am doing here is more stop gap to create custom reports for the client.

Here is the general relationship:

project -->> cat <<-- section.

However a project can have only one cat from 0-x sections.

The sections and categories are all entered by the user.

There are other similar relationships.

So.... I figured that I could create a separate rule file or pageConfiguration

for each of the custom reports. This meant that I needed to create some

generic components that addressed the above relationship and of course

custom calculating components.

So, by creating a rule that maps lookup string with a property key, I get the value.

In my original problem case that is essential what metricListValueByMetric does.

However, the one snag is that I can't have phantom non eo keys.

So I created some attributes in the EO.... rptCol01 ... rptColXX

And then map those properties to a customComponent.

Seems to be working as clean as I could design it.

James

On Dec 8, 2011, at 12:23 PM, David Holt wrote:

On 2011-12-08, at 9:17 AM, James Cicenia wrote:

That all makes sense now and works perfectly. This conversion might go better than I originally planned.

Thank you very much.
James

ps: now I can make a nice generalized custom reporting engine!

It would be nice if you had time to share how you went about it. It sounds good!

David
On Dec 8, 2011, at 10:25 AM, Ramsey Gurley wrote:
Instead of using rules
(entity.name = 'PortfolioProject' and propertyKey = 'primaryGroup') componentName = "D2WCustomComponent"

(entity.name = 'PortfolioProject' and propertyKey = 'primaryGroup') customComponentName = "D2WPrimaryAlignmentMetricByKey"

use

(entity.name = 'PortfolioProject' and propertyKey = 'primaryGroup') componentName = "D2WPrimaryAlignmentMetricByKey"

Since you are extending ERDCustomComponent, you shouldn't need the wrapper. Then you can just call valueForBinding to get whatever you need from the d2wContext.

public String value(){
return ((PortfolioProject)object).metricListValueByMetric(valueForBinding("lookupString"));
}

Ramsey
On Dec 8, 2011, at 6:19 AM, James Cicenia wrote:
OK -

I spent a lot of hours last night converting a test version of this application to extend ERXApplication.... etc. I would be doing it the first of the year anyway.

Now I have a little D2W rendering component. I want the rule to change an attribute of it. But I can't seem to make it happen.

here is my simple component:

public class D2WPrimaryAlignmentMetricByKey extends ERDCustomComponent {
public EOEnterpriseObject object;
public String key;
public String lookupString;

public D2WPrimaryAlignmentMetricByKey(WOContext context) {
super(context);
}

public String value(){
return ((PortfolioProject)object).metricListValueByMetric(lookupString);
}
}

What can I do to get lookupString to be supplied by a rule??

Here is my rule:

(entity.name = 'PortfolioProject' and propertyKey = 'primaryGroup') ==> lookupString com.webobjects.directtoweb.Assignment "Primary Group"

lookupString is always null when I run my report and debug my component.

What am I missing.
James Cicenia
cell: 773.398.4649

smime.p7s
Description: S/MIME cryptographic signature
 _______________________________________________
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
Follow-Ups:

Re: A little rule help here.
From: Ramsey Gurley <email@hidden>

References:

>A little rule help here. (From: James Cicenia <email@hidden>)

>Re: A little rule help here. (From: Ramsey Gurley <email@hidden>)

>Re: A little rule help here. (From: James Cicenia <email@hidden>)

>Re: A little rule help here. (From: David Holt <email@hidden>)

Prev by Date: Direct access to binding with WOOgnl

Next by Date: Re: A little rule help here.

Previous by thread: Re: A little rule help here.

Next by thread: Re: A little rule help here.

Index(es):

Date

Thread