icefaces interview questions and answers

ICEFACES INTERVIEW QUESTIONS AND ANSWERS ANDROID

You already seem to have made upt your mind about the cons, and I have to a gree with some of them (it does not separate layout and logic enough, and the resulting HTML is often atrocious), but disagree on others (if you use Facelets, which I would very much recommend, then the output should definitely be valid). Now, what are pros/cons? How can I emphasize my point to not use JSF? What are strong points to use JSF over my suggestion? As the Internet is evolving, I really don't see why we should use this 'rake'. I doubt, that JSF is the best solution nowadays.

ICEFACES INTERVIEW QUESTIONS AND ANSWERS ANDROID

(or some flavor of MVC.) By the way we will need the REST api anyway, as we are developing a partial Android front-end, too. Then create a HTML5/Javascript client with client side MVC. My suggestion would be to implement a REST api, using JAX-RS. Due to everything above the service tier is in control of JSF. I don't see how I can implement all of our first GUI mock-up (Besides we have no JSF Expert in our team). Or the front-controller pattern at all.Īnd Lastly, I think we will have to start over in, say 2 years. It solves really many problems - we wouldn't have if we wouldn't use JSF. Hundreds of components? I see ten-thousands of HTML/CSS snippets, ten-thousands of JavaScript snippets and thousands of jQuery plug-ins in addition. What benefits do I have? None, if you think about. If you ask me, it's a poor abstraction of basic web technologies, crippled and useless in the end. I don't see how I would be able to extend this output comfortably, whether styling with CSS, adding UI candy (like configurable hot-keys, drag-and-drop widgets) or whatever. Furthermore it throws together, what never should be so tightly coupled: Layout, Design, Logic and Communication with the server. It violates every single rule I learned in web-development. But now I am trying to implement a functional prototype, and have some really serious concerns about using it.įirst of all, it creates the worst, most cluttered invalid pseudo-HTML/CSS/JS mix I've ever seen. Our first thought was JSF, as it is the standard in Java EE. Due to many many changes, the UI and parts of the business logic will completely be rethought and reimplemented. We're crating a new Java Enterprise application, replacing an legacy JSP solution.

I am new to StackExchange, but I figured you would be able to help me.

Icefaces interview questions and answers