Software Reality
Programming with
a dose of satire.

Site Map Search


Agile Development
 
Extreme Programming
 
Code Generation


Articles
Lifecycle
Design
Programming
Soapbox
Reviews
Cthulhu

Java Swing
Swing's greatest threat isn't SWT, it's Flash
Swing Survival Guide


 
Check out our ageing Reviews Section


Use Case Driven
Use Case Driven Object Modeling with UML: Theory and Practice
Get from use cases to working, maintainable source code. Examples use Spring Framework, JUnit and Enterprise Architect

Agile UML
Agile Development with ICONIX Process
A practical subset of agile development techniques, illustrated by example

Get Controversial!
Extreme Programming Refactored
Extreme Programming with a dose of satire
Available now:



Programming

JavaServer Faces 1.0 Early Access Draft (Page 8)

<< Page 7 (Nice to have / Readability)


Conclusion

Well folks, that's most of the comments I had on the JSF 1.0 Specification Early Access Draft. I hope that this has also addressed some of the issues that others might have. Of course, there might be other issues that I've neglected.

One last note to the world in general. JSF and all the other frameworks out there are trying to make programming better in a world that wasn't meant for applications. HTML over HTTP is stateless, making it difficult to program applications that require request event handling (mentioned above), session control, client side logic and true client server interactions.

After a decade, I'm still surprised that the world hasn't realized its own mistakes and abandoned HTML over HTTP in favor of a better cross-platform, cross-vendor remote application protocol and language.


<< Message Forum

<< Back to Programming

All trademarks and copyrights on this page are owned by their respective owners.
Stories and articles are owned by the original author.
All the rest Copyright © 1998-2008 Matt Stephens. ALL RIGHTS RESERVED.