Components, just like pages are pooled, and are expected to be stateless and thread safe. I believe that you are in fact only getting 1 component on your page, its just being spit out multiple times. And in fact, if you go to another page with the same component, and with permitting factors, you will again get that same component.
(some on shout if I'm off base here, but thats my understanding) -Nick On 6/22/05, Edward Scanzano <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a situtation where I have a page that includes > 0..n number of a component (let's call it A). I have > A.jwc A.html and A.java. Will tapestry create only one > A java object to represent each component or will each > component get it own java object instance. I noticed > that in my constructor for A it is getting called only > once and I have 2 components of type A on the page. > > Thanks > E > > > > > > > > > --------------------------------------------------------------------- > 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]
