JSF tooling to enforce ids

[damianharvey]

I've just started a testing phase of my project using Selenium (which is very cool btw). However as I'm a lazy coder and didn't follow JSF best practices of assigning IDs to every component, I now have to go back and set these IDs for each page that I want to test (otherwise Selenium can't reliably find the component if it is based on a dynamic JSF id).

So, I was thinking maybe a feature request for the RHDS JSF tooling that you can select something like "Enforce JSF IDs" where you get big nasty errors in your Eclipse problems area if you haven't set an ID on a JSF component.

Might stop me being so lazy (although I doubt it).

Cheers,

Damian.

[maxandersen]

Good idea, though I'm not sure you would like id for *every* component, but sounds like a good thing to have optional validation for ...possibly combined with a list of components to include/exclude in this validation.

Feel free to post it in our jira.

[amitev]

There was a discussion on the jsf mailing list about such functionality.