Hi all,
I am on Tap 4.1.3 (using the released binary) and I am also experiencing
this behavior. I cannot find any documentation on this situation or a
workaround other than Jesse's comments in this thread. Can someone
point me to more information on how to work around this multiple ognl
eva
It's something that will happen to all ognl expressions for the next week or
two. After that they will be resolved as per normal in development mode and
jit'ed in production.
On 5/17/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
Jesse, I stepped away from the computer for a bit, and I had just now
Jesse, I stepped away from the computer for a bit, and I had just now
submitted the JIRA before updating this conversation.
https://issues.apache.org/jira/browse/TAPESTRY-1477
I am happy to know it is something that happens on purpose, and for
developmental issues. I would hate to have my DAO's
No need for JIRA issues - I know exactly why it's doing it and intentionally
have it running this way.
Unfortunately it's the only sane way I know to make sure 4.1.2 is
releasable. There's no actual need for OGNL expressions to be compiled in
dev mode but otherwise I'd have no way of ensuring th
Add a JIRA please.
At least since 4.1.2-20070501.233137-64, i can see the first If getting
called 3 times!
And it's probably the first @If after an app reset that gets evaluated 3
times and not
the first @If of a page.
An old 4.1.2-20070215.051249-15 worked correctly, i cant test other (in
betwee
Ugh. This is a big pain now. I have a huge dynamic form that has
lots of IFs, and I can see the same queries being called 3 times or
more. =(
Everything still works, it's just about 3 times slower.
If anyone has solved this problem please let me know!
On 5/17/07, Daniel Jue <[EMAIL PROTECTED]
Here is another example when more than one IF component is used.
It seems the conditional for the first IF gets called 3 times, then
the others just get called once.
plain.java:
package com.phy6.app;
import org.apache.tapestry.IComponent;
import org.apache.tapestry.annotations.Component;
impor
Glad to know I'm not alone. I've simplified the problem code even
more, to eliminate any confusion:
plain.java:
package com.phy6.app;
import org.apache.tapestry.IComponent;
import org.apache.tapestry.annotations.Component;
import org.apache.tapestry.annotations.InitialValue;
import org.apache.t
I have noticed similar things happening in my code on the 4.1.2 snapshot
as well.
Trying to debug the issue I'm having w/ DatePicker (different thread) I
added a conditional to the page, and used your strategy of counting @If
calls just to see what I get.
The first time I load the page, on t
Hi,
I experienced this problem after upgrading from Tap 4.1 to Tap 4.1.2 Snapshot.
The problem is that I have an IF component that is being called 3
times, when it should only be called once.
I have extracted the problem into a simpler page for examination:
plain.page:
http://jakarta.apache.
10 matches
Mail list logo
