The web community is eagerly seeking a light-weight, templating framework backed by JavaServer Faces as the industry standard. While JavaServer Faces and JavaServer Pages technology (JSP) are meant to be aligned, Facelets steps outside of the JSP specification and provides a highly performant, JSF-centric view technology. Anyone who has created a JSP page will be able to do the same with Facelets and familiar XML-tag use. The difference is under the hood where all the burden of the JSP vendor API is removed to greatly enhance JSF as a platform and provide easy plug-and-go development without requiring JSP tag development. JavaServer Faces UIComponents are first class citizens within Facelets; there's no need to develop extra objects to integrate. There's also no need to learn yet another XML schema to define your views. Facelets includes many features such as: * Works with JSF 1.1 and JSF 1.2, including Sun's RI and Apache MyFaces. * Zero Tag development time for UIComponents * Fast Templating/Decorators for Components and Pages * The ability to specify UIComponent trees in separate files (UICompositions) * Line/Tag/Attribute precise Error Reporting * Specify Tags in Separate Files, even packaged with Jars * Full EL support, including Functions * Build-time EL Validation * XML configuration files aren't necessary * Reserves the 'jsfc' attribute which acts the same as Tapestry's jwcid (Example: ) * Plugable Decorators to really make designer's job easy (Example: transform to at compile time) * Works with any RenderKit * Facelet APIs aren't dependent on a Web Container

void doAccept(SelectionKey key) throws IOException, InterruptedException { if (isLowOnResources()) return; ServerSocketChannel server = (ServerSocketChannel) key.channel(); SocketChannel channel = server.accept(); channel.configureBlocking(false); SelectionKey readKey = channel.register(_selector, SelectionKey.OP_READ); Socket socket=channel.socket(); try

# lib (ver.5.0, ver.1.4.2, ver.1.3.1) - a set of useful tools that I've been developing for the last several years: * Foundation package (map a list or iterable, map to function, function to map, filter a list or iterable, compound iterator, indexOf...) - and an article; * Objects (map, composition, inverse, crc32, indexOf...); * Strings (split, join, replace, zip, fill, countChar, findDiff, grep, decode ,chars...); * Files (find, chdir, relPath, writeToFile, copy, deleteFile, compare, synchronize, bytes, chars, lines files tree...) and an article; * FormattedWriter (uses MessageFormat for creative output); * Web (downloadFile, getHtmlCharset, sendMail...); * Tools (bark, inform, fatalError, runCommand...); * ZipInput (gets input from various sources and retrieves the contents).

converts and validates SOAP WSDL, clients and servers

Axis book: Developing Web Services with Apache AxisFront cover Learn web services and Apache Axis easily If you'd like to learn how to create web services (in particular, using Apache Axis) and make some sense of various standards like SOAP, WSDL, JAX-RPC, SOAP with attachments, WS-Security, XML Encryption and XML Signature, then this book is for you. Why?

Fire: The easy and simple way to develop Web services

Fire: The easy and simple way to develop Web services

JAX-RPC is Bad, Bad, Bad! There I’ve said it. It wasn’t as painful as I thought it would be to admit that the subject of my last book, J2EE Web Services, is a terribly flawed piece of technology. I’m glad I wrote that book, I think it has helped a lot of people understand a very, very complex Java technology (i.e. JAX-RPC), but I’m sorry that JAX-RPC and the rest of the J2EE Web services stack became the standard for Java web services.

J2SE 5.0 adds classes and methods that can make every day tasks easier to perform. In this tip you will see how the newly added java.util.Scanner class makes it easier to read and parse strings and primitive types using regular expressions.