This should work and I'm not aware of any problems that would keep it from working.
For example, the Palette component is a custom component that is a form component. The dynamic select boxes ... were they PropertySelection components, or something home-brewed? Can we see the code? If you are having problems, don't forget to add bugs! ----- Original Message ----- From: "Jason Owens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 05, 2002 7:25 PM Subject: [Tapestry-developer] Custom form components... > Hello, > > I don't know if this is fixed in newer versions (I'm using 2.0.0) - but > there seems to be a bug when creating custom form components. Basically, > if you create a composite form component using existing form components, > then actually try to use it, you'll get a StaleLinkException. > > I was building a component with 8 dynamic select boxes, but had a normal > Checkbox stuck in there as well. Wouldn't work. Finally took a wild > guess (after hours and hours of trying to discover this stupid thing), > and took out the checkbox. That remedied the symptom, but hasn't solved > the problem... > > No one's ever run into this before? > > Argh. > > -Jason > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
