[Trinidad] forbidden binding names

Hi, I just discovered that there are a number of names which cannot be used for binding iterating component variables - such as in tr:table. In short, I needed to render a set of parameters in a tr:table, so that it seemed obvious to me setting var=param. But the table was rendered empty, event

Re: [Trinidad] forbidden binding names

That's a nice issue, and we have no way to provide all the reserved names either... I guess the best we could do is alter the parameter description to mention that it must not take the value of any predefined object and should not take the name of a managed bean either. Anyone see a better

Re: [Trinidad] forbidden binding names

Well - I admit was a bit unlucky to meet one of them - but after all calling "param" a parameter shouldn't be too naif. In the context of iterating components - param, header, cookie and view might be dangerous names. All the others are quite unlikely to be used this way. Hopefully this game

Re: [Trinidad] forbidden binding names

Well, we do know the predefined objects: pageContext servletContext session request response param paramValues header headerValues cookie initParam pageScope requestScope sessionScope applicationScope facesContext view Plus in Trinidad requestContext pageFlowScope/processScope All of these are

Re: [Trinidad] forbidden binding names

Well, I know from earlier tests that setting var=person if you have a scoped bean named person will bring you into trouble as well - so this is not only related to the predefined values. regards, Martin On 8/1/07, Renzo Tomaselli [EMAIL PROTECTED] wrote: Well - I admit was a bit unlucky to

Re: [Trinidad] forbidden binding names

Well, we could have a Set for the JSP predefined values as well as JSF ones, but the problem is still going to happen when/if there's another unknown Variable/ELResolver installed. So, we do know the standard predefined objects, but not library predefined ones (except for Trinidad of course),