I would agree with this. If your components need their own variables use a combination of parameters along with persitent properties. I've never found this to be a limiting factor in creating components, and allows for a 'stateful stateless state' of sorts. :)
In most cases just setting the direction to auto is good enough, and will just work. Only special case I can think of is with form components. Either way, if you need to you can think of parameters as constructor values for the components. -Nick On 6/22/05, Hensley, Richard <[EMAIL PROTECTED]> wrote: > The way I would solve this problem is to use component parameters. > > If you are using Tapestry 4.0, they are very straight forward to use. > > If you are using Tapestry 3.0, you will have to play with the direction > parameter. It is likely that the "in" value for direction is what you want. > > Richard > > -----Original Message----- > From: Edward Scanzano [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 22, 2005 10:41 AM > To: Tapestry users > Subject: RE: Number of component instances on a page > > Yes I mean java class instance. Yes the enclosing loop > does know the unique value. > > E > > --- "Hensley, Richard" <[EMAIL PROTECTED]> > wrote: > > > When you say component instance, do you mean the > > java class instance? In > > this case, does the enclosing loop on the containing > > page know the unique > > value? > > > > The reason I ask is because all you really have is a > > unique instance in time > > where the component is being rendered. > > > > Richard > > > > > > -----Original Message----- > > From: Edward Scanzano [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 22, 2005 10:17 AM > > To: Tapestry users > > Subject: RE: Number of component instances on a page > > > > Actually this is exactly what I need. The properties > > I > > pass in must be unique to that component instance. > > > > E > > > > --- "Hensley, Richard" > > <[EMAIL PROTECTED]> > > wrote: > > > > > Ed, > > > > > > Can you give a little more detail about your use > > > case? Maybe there is > > > another way to solve your problem, because it is > > not > > > likely that the core > > > specification management in Tapestry will change. > > > > > > Are you needing property values on a per component > > > instance? Maybe > > > persistent properties are the answer. > > > > > > Richard > > > > > > -----Original Message----- > > > From: Edward Scanzano [mailto:[EMAIL PROTECTED] > > > > > Sent: Wednesday, June 22, 2005 10:05 AM > > > To: Tapestry users; Nick Stuart > > > Subject: Re: Number of component instances on a > > page > > > > > > This is exactly what I do not want. How do I > > prevent > > > this and make it so that they are individual > > > instances > > > and not shared. > > > > > > Ed > > > > > > --- Nick Stuart <[EMAIL PROTECTED]> wrote: > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > > > > > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
