This action might not be possible to undo. Are you sure you want to continue?
Skins are used for a web application to look in a different way without the need to write one page for each skin or using CSS. A skin manages colors, fonts and images of your web page. In early Java-Server-Side days, you used to put HTML hardcoded in a Servlet. Then, JSP came to allow you to put your HTML outside Java code. Nowadays, the same happens with taglibs that have HTML tags hardcoded in Java code. Using Xkins you can put this HTML outside your code with an additional and powerful feature: Skins. Xkins stands from eXtendable Skins. You can define as many skins as you like, and each skin can extend other skin, so it can use all its parent's components and override what it needs to look in a different way. With this feature, maintaining multiple skins becomes a simpler task. Xkins framework uses Velocity to process snippets of HTML, but you can use any other template processor (Xkins comes with it's own default processor). Xkins also comes with Forms Tag Libs, that allows you to create forms using Xkins and comes with four Skins. Xkins Forms integrates with Struts framework. Xkins also fits perfect in JSF world, playing a role as a RenderKit, and can work with other presentation frameworks, Struts-Layout. http://xkins.sourceforge.net/definition.html http://www.javaworld.com/javaworld/jw-10-2004/jw-1025-xkins.html?page=3#resources Besides, You need to have the ot-commons-1.0.jar file. http://www.javaworld.com/javaforums/printthread.php?Cat=0&Board=959464&main=44 933&type=thread Introduction Apache Axis is an implementation of the SOAP ("Simple Object Access Protocol") submission to W3C. From the draft W3C specification: SOAP is a lightweight protocol for exchanging structured information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. This project is a follow-on to the Apache SOAP project.
Please see the Reference Library for a list of technical resources that should prove useful. Axis 1.2 and beyond Axis 1.1 has proven itself to be a reliable and stable base on which to implement Java Web services. There is a very active user community and there are many companies who use Axis for Web services support in their products. For Axis 1.2, we are focusing on our document/literal support to better address the WS-I Basic Profile 1.0 and JAX-RPC 1.1 specifications. And we are fixing as many bug as possible.