Cover Pages: XML Daily Newslink: Thursday, 13 September 2007

A Cover Pages Publication http://xml.coverpages.org/
Provided by OASIS and Sponsor Members
Edited by Robin Cover

This issue of XML Daily Newslink is sponsored by:
SAP AG http://www.sap.com

Headlines

JBoss.org Delivers Update to RichFaces with AJAX Support
Tackle WS-Security Specification Interoperability Challenges
BEA Eyes a New Era with Project Genesis
jQuery 1.2 Release is "Massive"
Using XML Schema 1.0: When Can Language Components be Removed and Maintain Backwards or Forwards Compatibility?

Cover Pages

W3C GRDDL Recommendation Bridges HTML/Microformats and the Semantic Web

JBoss.org Delivers Update to RichFaces with AJAX Support
Staff, AJAXWorld News Desk

With the release of RichFaces 3.1, JBoss.org has delivered more Web 2.0 development capabilities on Java Platform, Enterprise Edition (EE). This latest update has built-in support for AJAX via Ajax4jsf, an AJAX framework on JavaServer Faces (JSF). Now, developers have a framework combined with a rich set of open source AJAX-enabled components out-of-the-box, eliminating the need to write any JavaScript for AJAX functionality. This release is the first major update of RichFaces since it was released into open source earlier in March 2007. Both RichFaces and Ajax4jsf were contributed to the JBoss.org community by Exadel. Though initially released as two separate projects on JBoss.org, RichFaces and Ajax4jsf projects and technologies have now been merged. Another important new feature in RichFaces 3.1 is integration with JBoss Seam. This integration enhances the RichFaces user experience by simplifying setup and 'plumbing code,' as well as providing powerful state and concurrency management for AJAX. Version 3.1 includes nine new components, including the highly requested rich calendar component, which enables a dynamic AJAX calendar component in Web applications.

See also: the RichFaces web site

Tackle WS-Security Specification Interoperability Challenges
Zeynep Latif and David Leigh, IBM developerWorks

This article shows you how to implement the new provider endpoint workaround for WS-Security specification-level interoperability problems. The approach involves packaging the J2EE 1.4 provider application with two Web service endpoints: One provides service for J2EE 1.3 consumers, and one provides service for J2EE 1.4 consumers. Implementing this workaround is a basic programming and packaging exercise, requiring no additional middleware infrastructure. This approach scales well when there's a large number of Web service consumer applications. After you add the new provider endpoint to the Web service application, any number of J2EE 1.3 Web service consumer applications can use it. An important note: This approach is best used when the Web service implementation classes are simple JavaBeans or Enterprise JavaBeans (EJBs). If the Web service implementation logic is contained in a servlet, in a Service Component Architecture (SCA) component, or in an Enterprise Service Bus (ESB) mediation module, then it's more difficult to create the servlet 2.2 (J2EE 1.3) Web project and package it with the Web service provider application.

BEA Eyes a New Era with Project Genesis
Darryl K. Taft, eWEEK

BEA Systems' new project, code-named Genesis, brings together service-oriented architecture, business process management, enterprise social computing and other technologies to enable users and IT administrators to deliver dynamic solutions that plug into existing application environments. With Project Genesis, both users and IT will be able to assemble, change and deploy dynamic business applications to achieve competitive advantage, he said. Genesis extends the vision of the BEA AquaLogic product family by including a simplified approach for assembling and modifying dynamic business applications. BEA also announced new performance results and unveiled product plans that will help the company expand its role in Java virtualization and further execute on its Liquid Enterprise vision. According to early lab test results jointly conducted by BEA and Intel, LiquidVM (the foundational technology behind WebLogic Server Virtual Edition) runs Java over two times more efficiently than using the normal operating system-based software stack on VMware Infrastructure. Because LiquidVM runs directly on top of the VMware ESX Server hypervisor platform without a traditional operating system, it can manage memory resources for Java applications much more efficiently than the alternative operating system model. BEA also announced that it is making key components of its Enterprise 360 offering available as virtual appliances ready to run directly in virtualized environments such as VMware Infrastructure. The company will start with WebLogic Portal and AquaLogic Service Bus and will eventually support additional products under the virtual appliance paradigm as part of its Liquid Enterprise strategy.

See also: the announcement

jQuery 1.2 Release is "Massive"
John Dorsey, Dr. Dobb's Journal

John Resig, the creator and lead developer of the jQuery JavaScript library has announced the release of jQuery 1.2, calling it a "massive new release ... that's been a long time in the making." Version 1.1 was released last January. The jQuery library is a collection of UI tools for web app development that includes simplified DOM traversal, creating animation, event handling, and so on. jQuery's dot notation "chainability" allows developers to write very concise code. jQuery 1.2 includes several new features. Additionally several inefficient or confusing features from 1.1 were dropped from the latest release, as was XPath selector support. Any projects that require these 1.1 features can be augmented with the jQuery 1.1 Compatibility Plugin and the XPath Selector Plugin. The compressed jQuery 1.2 library is 14 kb. The uncompressed version is 77 kb.

See also: Getting Started with jQuery

Using XML Schema 1.0: When Can Language Components be Removed and Maintain Backwards or Forwards Compatibility?
Dave Orchard, Blog

When can content be removed from a content model? The answer depends what we mean by "remove". The first aspect is whether the content is completely removed or if the minimum and/or maximum number of occurences of the content is reduced though possibly still allowed. The second aspect is whether the content that is removed from the definition is still allowed to occur in documents. In general, a newer language can be forwards and backwards compatible with an older language if the component is removed and still accepted. A newer language can be forwards compatible with an older language if the component is optional and is removed and not accepted. A newer language can be backwards compatible with an older language if the component is optional and is removed and not accepted only if the producers do not produce the optional component. A newer language cannot be backwards or forwards compatible with an older language if the component is required.

See also: on Forwards Compatibility

Selected from the Cover Pages, by Robin Cover

W3C GRDDL Recommendation Bridges HTML/Microformats and the Semantic Web

The World Wide Web Consortium has announced the publication of "Gleaning Resource Descriptions from Dialects of Languages (GRDDL)" as a W3C Recommendation, together with a separate "GRDDL Test Cases" Recommendation. The GRDDL specification represents "an important link between Semantic Web and microformats communities. With GRDDL (pronounced 'griddle'), software can automatically extract information from structured Web pages to make it part of the Semantic Web. Those accustomed to expressing structured data with microformats in XHTML can thus increase the value of their existing data by porting it to the Semantic Web, at very low cost." Tim Berners-Lee, W3C Director compared GRDDL to style specifications: "Sometimes one line of code can make a world of difference. Just as stylesheets make Web pages more readable to people, GRDDL makes Web pages, microformat tags, XML documents, and data more readable to Semantic Web applications, opening more data to new possibilities and creative reuse." The GRDDL specification introduces markup based on existing standards for declaring that an XML document includes data compatible with the Resource Description Framework (RDF) and for linking to algorithms (typically represented in XSLT), for extracting this data from the document. The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data.


SEARCH \| ABOUT \| INDEX \| NEWS \| CORE STANDARDS \| TECHNOLOGY REPORTS \| EVENTS \| LIBRARY

Headlines

Cover Pages

Sponsors