The id attribute of the RDCs does not allow the value to be set via
an expression, unlike all other attributes I've found.
We're implementing our applications using the simplest possible
pattern, where each JSP contains a single RDC. So the JSPs
themselves are identical for a given type of RDC. We have quite a
few selectOne tags in an average application. The bits that vary
between page, in our design, are populated by expressions, getting
their values from state stored in the session.
The only one causing trouble is the id. I've made the changes to the
RDCs we're using, and will be working though any kinks tomorrow. I
just wanted to find out if there was a particular reason why this
constraint was added, and so maybe anticipate issues with other
plumbing bits.
Thanks,
Stu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
