by Jason Hunter
This talk gives web developers an understanding of what's going on in the layer beneath their code. By understanding HTTP you can become a more effective debugger, improve your site's cachability, design better deployment architectures, author more useful non-browser web clients such as spiders, and (most importantly) avoid a slew of subtle bugs. With an understanding of HTTP we'll look at advanced topics like HTTP request smuggling vulnerabilities and HTTP tunneling pros and cons.
by Kito D. Mann
Web applications are notoriously difficult test, and even though JavaServer Faces (JSF) is an excellent technology, it doesn't necessary make testing easier. If you want to go beyond black box testing, you need access some of the framework's infrastructure in order to write comprehensive integration tests and unit tests. This means that you either need mock/stub objects, or your tests must run inside the container.
In this session, we'll discuss different ways to test JSF applications, starting from outside the box with Selenium, and then moving inward by looking at tools like JSFUnit and Arquillian, as well as complete mock/stub environments like MyFaces-Test. Along the way, we'll discuss the best use cases for these tools, and point out their pros and cons.
Java EE is already the perfect solution for complex business/enterprise systems, and the improvements in JavaServer Faces 2.x provide the perfect chance to reach out to the consumer and small business market; JSF is easier to use than it's ever been before, now making it accessible to businesses of all sizes. In order to complete the user-experience, however, one must not overlook the URL.
by Brian Sletten
The steady adoption of REST brings with it architectural properties that made the Web of Documents so successful by freeing documents from their filesystems. Now, the same thing is happening to Webs of Data. REST is opening a door to share interlinked data in the Enterprise and on the Internet. The Semantic Web builds on this and frees the information from its containers whether they are databases, documents or services.
*improved search results
*sharing information on the Web
*weaving information into and extracting it from documents
*organizing content the way you want to see it
If you think the question, "Why should I be on the Web?" sounds silly to modern ears, come find out why "Why should I publish my data on the Web?" will someday sound as silly.
20th–23rd June 2011