What seems like a very interesting presentation from the tech lead for JSF:
TheServerSide Java Symposium 2005. The description:
The need for a common API for Java-based web application user interface components was obvious – by the time that the Java Specification Request (JSR) for this API was started, there were over thirty open source and commercial libraries that covered all or part of this functional space. JSF’s goals included gaining consensus on a common API for building interoperable components, but it was also more aggressive in its goals: it was also to be the leading edge of a movement towards making Java APIs easier to use, as well as easier for tools vendors to create high quality design time experiences around that API. We will briefly review the history of JSF, and examine the ecosystem around this API, plus talk about what might be useful in the future.
Lucas Jellema, active in IT (and with Oracle) since 1994. Oracle ACE Director and Oracle Developer Champion. Solution architect and developer on diverse areas including SQL, JavaScript, Kubernetes & Docker, Machine Learning, Java, SOA and microservices, events in various shapes and forms and many other things. Author of the Oracle Press book Oracle SOA Suite 12c Handbook. Frequent presenter on user groups and community events and conferences such as JavaOne, Oracle Code, CodeOne, NLJUG JFall and Oracle OpenWorld.
Happy
0 0 %
Sad
0 0 %
Excited
0 0 %
Sleepy
0 0 %
Angry
0 0 %
Surprise
0 0 %
Like this:
Like Loading...
Wed Jun 8 , 2005
If there is one wave (or hype if you like) flooding the Java/J2EE arena right now – well, there is JSF and EJB 3.0 and AJAX and Java 5 and …. – it is probably the Spring Framework, founded by J2EE veteran Rod Johnson. Spring seems to be everywhere. And […]