design - How should you split pages into JSF components? -


i working on jsf web app project external web developers providing (static) html, css & javascript. best way split pages jsf components manage changes design in future.

is bad practice leave html pages intact, , add jsf components required dynamic content? (this managing versions)

or should entire site split atomic jsf components , follow standard jsf guidelines?

what issues think encounter doing this?

ideally, external developers able jsf too, , create reusable composite components.

but if providing static html & css, must manually convert code reusable components. so, whenever need change layout related, update components , client code up-to-date. also, you'll find ways of reducing code duplication common in stylized html/css.

you could, yes, start adding jsf components required, feasible if had 1 page, or if every page did needed different markup , styles. , wouldn't version control, because end having update every 1 of pages whenever need change something.

i suggest take @ jsf 2.0 composite components, , try use them as can. sometimes, though, ui:include might better option, you'll want understand difference between these 2 able to know when use which.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -