If the object graph is too deep to easily code to in the web page, perhaps
you could "pull up" the low level lists with a method at the top of your
graph? I understand the frustration with verbose evaluations to get a
simple String! Let's suppose you have
Country--->State--->City--->Street--->Listing
and you are needing to output the Listings on a page. If you add a
convenience method getListing() to your Country type that chains together
all the method calls, you could use model.listings in your iterator.
Scott
On Fri, Feb 15, 2008 at 6:09 AM, Maxx <[EMAIL PROTECTED]> wrote:
> Of course the JSP if for prensentation.
>
> But this kind of "complex" OGNL expression is computed as each
> iteration of multiple <s:iterator> tags (that's why I put some X/Y/Z
> variables, each resulting of a %{#someStatus.index} expression).
>
> In fact, the myObj is exposed by the Action class through regular
> getMyObj/setMyObj couple of getter/setter, and has to be used as the
> target of a form.
> It's just that it has a complex sub-/object hierarchy in its
> structure, and this structured object is linked to some other one,
> I'll call "presentation structure" (made of field categories,
> fields...) presented in my JSP (to sum up things).
>
> Maxx
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Scott
[EMAIL PROTECTED]
