>From: Ryan Wynn <[EMAIL PROTECTED]> > > I just stumbled upon a problem that clay might be able to catch. > > The scenario is that one clay component references a clayJsfid that > includes a reference to an already included clayJsfid. The result is > a out of memory exception because clay goes into a infinite loop. > With the nature of clay using a chain context it might be able to > capture a list of already includes clayJsfids and return an error if > there is a duplicate.
This is problem when using symbols to dynamically build the subtree. Otherwise there is a check for recursive component definitions. The symbols are evaluated just prior to pushing the value to the components. I think it's something we should look into but it's a tough one to solve. Gary
