Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using eclipse to create my jsf project.
I created my own components, and I don’t want the other programmers to be able to use jsf regular components like h:inputtext etc.
How can I do it in eclipse, that if the user adds specific tags like h:inputtext he will see errors in the page and also when trying to run it?
That is not Java, that is JavaServer Faces.
You cannot – on a general principle – make that happen for other developers. They will circumvent it if needed.
What you can do, is to have a policy enforced that your components are to be used instead of stock JSF ones, and then verify that when building. Either your source repository or your build server (preferred) should test for this and fail the operation. This will also allow a developer to use standard JSF if needed for debugging locally as long as it is not shared.
For checking a JSF page, you can take advantage of it being an XML document and use XSLT to validate all tags and attributes. My approach would be to check the name space on all tags and trigger failure if found in a blacklist.