AFAIK Tap should create two separate page instances. But to be sure you could check page pool size with a small prototype appliction. Another way to check, you could implement a static counter in your shared page class and increment it in the constructor. Then you'd know for sure.
On 3/17/06, Andreas Idl <[EMAIL PROTECTED]> wrote: > Hi > > In our application we use pages for multiple purposes. A simple example is the > "EditPersonPage", which is used for the insert and the edit user action. My > question is, if it would be save to do the following in the application file: > <page name="EditPersonPage" specification-path="pages/EditPersonPage.page"/> > <page name="InsertPersonPage" specification-path="pages/EditPersonPage.page"/> > > In my opinion Tapestry will instantiate two Objects of the page and pool them > seperatly. Is this assumption right, or will something go terribly wrong with > it? > > thx for help, > Andreas > > --------------------------------------------------------------------- > 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]
