Re: Bunch of issues...

> > Ok, well if you want to do it the HARD way :-)
> > 
> > I'd suggest looking at the type conversion docs
> and
> > have an
> > 
> This is a ridiculous assertion, and an equally
> ridiculous suggestion.
> 
> The problem has nothing to do with type conversion,
> or shouldn't at least.
> 
> It's pretty ludicrous that I cannot pass stuff around
> within my page without it going through a conversion
> in every step, and forcing me to define mappers for
> said conversion.
> 

The fact is I don't [b]KNOW[/b] what the problem is, and I'm trying to work with you to [b]DIAGNOSE[/b] it. Do I think this should have worked? Yes. Do I know why it didn't? No. Are you willing to try things to see if they shed any light on what the problem might be? Apparently not. Apparently that would take time away from bitching at people. 

> Sure, maybe that's what I need to go to get this
> working, which would convince me that I should go
> with the caching in the action (which, incidentally,
> is NOT the right solution, since the parameter to the
> getReports() method can vary, and so I'd have to
> cache about 20 lists). Obviously, if ognl converts
> all the time instead of passing stuff around, then I
> don't want to incur THAT performance hit.

Well, unless you're doing all 20 in one page, you only need to cache them when you call it the first time and you'll only have the ones you've asked for. You'll have them in memory anyway if you're saving them in the page.

> 
> > Overall I'd say you're getting too fancy in your
> > page, and putting too much script there. 
> 
> Well, that's a matter of opinion. Looking up
> something, then passing it to another method to
> calculate some displayed value is, to most normal
> people, not 'getting too fancy' or having 'too much
> script'. It's two lines, and it's a lot less code
> than anything you've suggested so far, as well as
> ensuring that there's never any stale data around no
> matter what context I use my action in. It's more
> reusable, scalable, maintainable, and clearer than
> anything you've suggested so far.
> 

No, that's not getting too fancy in Java code in a method... It's getting a bit too much like coding in the page for me. You should still be able to do it, but I'm saying maybe if you had a different design it would work more easily :-)

> I don't want to debate design. From what you're
> saying, I gather the answer boils down to 'sorry, you
> can't, what you're doing isn't supported, ognl is
> invasive and will not pass lookups around by ref, and
> will crap itself if you don't explicitly tell it how
> to map in every step'.

Like I said, I don't know why it's not working. I think we'd be happy to work with you to figure that out, though, if you're willing to work with us too.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=26282&messageID=51873#51873

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]