I don't think this may help but tapestry modifies your pages\components at
the run time so it's all handled behind the scenes.
Although I can't explain the results of your test here !
On Tue, Jun 5, 2012 at 4:50 AM, Thiago H de Paula Figueiredo
thiag...@gmail.com wrote:
On Mon, 04 Jun 2012
On Tue, 05 Jun 2012 08:45:41 -0300, Muhammad Gelbana m.gelb...@gmail.com
wrote:
I don't think this may help but tapestry modifies your pages\components
at the run time so it's all handled behind the scenes.
Although I can't explain the results of your test here !
I'd guess Tapestry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried to reproduce that (being the curious person that I am ;-) ),
but the constructor of a page is called only once on my machine - just
as one would expect (Tap 5.3.3)
If you want to analyze I suggest adding
new Error().printStackTrace();
to
.1045711.n5.nabble.com/Confusion-about-tapestry-singleton-page-tp5713619.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e
On Mon, 04 Jun 2012 21:56:28 -0300, xieweiguo xiewei...@139.com wrote:
Hello!
Hi!
I heard that from tapepstry 5.2,all page is singleton-object.But,I write
some code in the constructor of page class like this:
You should avoid using constructors in page classes.
So,my question is: Is the
