Hi Jesse,

had to look up the message myself again...
here is a quote of what i wrote:

----------------------------------

i'm experiencing some trouble here with Tapestry4.1.2 SNAPSHOT and ognl-expressions.

I've got the following construct in a table-component in my template:

<div jwcid="[EMAIL PROTECTED]">
<span jwcid="@If" condition="ognl:showPrices">
<span jwcid="@If" condition="ognl:positionEditable">
<input jwcid="[EMAIL PROTECTED]" value="ognl:orderPosition.price.netPrice" size="6" translator="translator:bisoNumber,pattern=#0.00#" displayName="message:PRICE" validators="validators:required"/>
</span>
<span jwcid="@Else">
 <span jwcid="@Insert" value="ognl:netPrice"/>
</span>
</span>
</div>

from the state of the application both methods isShowPrices() and isPositionEditable() both should return true.

T4.1.1 builds html-code like following:

<td class="PRICEColumnValue" id="informal_18">
   <span>
       <span>
<input type="text" name="price" value="365,00" id="price" size="6" />
       </span>
   </span>
</td>

however, if i switch to T4.1.2 SNAPSHOT i get the following:

<td class="PRICEColumnValue" id="informal_18">
   <span>
       <span>
           365,00
       </span>
   </span>
</td>

using the identical application state, which would imply that isPositionEditable has returned false which it shouldn't. I've put some debug output into the isPositionEditable() method to track it's result and had to realize that the method was called only once for a table containing 6 rows in
each of which it should've been called.

Additionally to that i'm experiencing some trouble with the latest tap/ognl snapshot as expressions like "ognl:conditionA||conditionB" result in an exception.

Does anyone have an idea about to avoid the first first problem?

I guess the second one came with the latest snapshot of ognl as it worked with 4.1.2-SNAPSHOT last week...

--------------------------------------------

The snipplet is part of a table in one of our pages which is also the only one showing this behavior in our application. We got other order-related pages which are working perfectly with very similar code to that one...

Regards,
   Patrick

I have no idea what you are talking about Patrick. Was there something
more specific you found problems with?

On 4/5/07, Patrick Klein <[EMAIL PROTECTED]> wrote:
Hi, Jesse,

I just tried the latest snapshot of tapestry but still got the same
result as in my last post ("If-component and T4.1.2-Snapshot") from the
28th of march. Rendering of the page differs major between T4.1.1 and
T4.1.2 Snapshot.

Regards,
    Patrick
> I think I've resolved most of the issues over the weekend already, but
> since I ran across a new ognl jira issue this morning I went ahead and
> enabled the promised fail-safe compilation features.
>
> If anyone gets any exceptions related to ognl javassist please report
> them asap, if they're just stack dumps to system.out it would be
> ~nice~ if you filed the bugs but hopefully they won't affect the
> operation of your respective apps.
>
> This was only enabled / deployed an hour or so ago so you'll need to
> get the new snapshot to see the changes.
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to