TiledView within a TiledView

Hey Guys,

I have a TiledView within a TiledView. When I click on the "Mutual

Funds" href, it just re-displays the current ViewBean. I have tried

to put the handle method in both the

pgAccountInformationrDailyStatementsTiledView and the

pgAccountInformationrMutualFundsTiledView, but the method never gets

called. There are no errors.

I have been debating on incorporating the second TiledView into the

first one, but I thought that I would get your input first.

<jato:tiledView name="rDailyStatements"

type="com.ta.ppoc.pgAccountInformationrDailyStatementsTiledView">

<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="0" WIDTH="461">

<tr><td colspan="2" bgcolor="#cccccc"><img

src="/ppoc/gifs/tpixel.gif" width=4 height=20 align="left">

<font face="arial,helvetica"><b>Daily Statements</b></font>

</td>

</tr>

<jato:tiledView name="rMutualFunds"

type="com.ta.broker.pgAccountInformationrMutualFundsTiledView">

<tr><td></td>

<td><font face="helvetica,sans-serif" size="-1" color="003399"><b>

<jato:href name="linkAcctBalTransHist"

fireDisplayEvents="true">Mutual Funds</jato:href></b></font></td></tr>

</jato:tiledView>

</jato:tiledView>

Thanx,

John Teceno

Back Bay Technologies

[1538 byte] By [Guest] at [2007-11-25 9:31:01]
# 1

Hi John--

> I have a TiledView within a TiledView. When I click on the "Mutual

> Funds" href, it just re-displays the current ViewBean. I have tried

This appears to be a regression that crept into the 1.0 version before

release. I've fixed the problem for the 1.1 release. However, there is

potentially one complication in using nested tiled views with hrefs or

buttons (commands). The event handler for the commands indicates the row on

which the command was pressed, however, it only indicates the row of the

local repeated (it's direct parent). Therefore, if you want to efficiently

determine the row of the outer repeated, you will need to save that value in

the href or button (using addExtraValue()) as it's rendered. It may just be

easier to use a single repeated in some situations.

In any case, whenever you get the blank return page in JATO 1.0, it means

that the event wasn't handled or didn't load another page. In JATO 1.1,

I've added the capability for JATO to understand this situation and it

displays an error instead. This should help with debugging.

Todd

Guest at 2007-7-1 18:23:43 > top of Java-index,Development Tools,Java Tools...