User: jung
Date: 00/08/11 01:37:19
Modified: etc/html index.html
Log:
adopted html pages to reflect Alpha-Status.
added an announcement document folder with the
release mailings
Revision Changes Path
1.2 +101 -92 zoap/etc/html/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/zoap/etc/html/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.html 2000/08/10 21:05:14 1.1
+++ index.html 2000/08/11 08:37:19 1.2
@@ -1,5 +1,5 @@
<!--
=========================================================================================================
-->
-<!-- $Id: index.html,v 1.1 2000/08/10 21:05:14 jung Exp $ -->
+<!-- $Id: index.html,v 1.2 2000/08/11 08:37:19 jung Exp $ -->
<!-- Copyright (c) 2000 infor:business solutions AG, Hauerstrasse 12, -->
<!-- D-66299 Friedrichsthal, Germany. All Rights Reserved. -->
<!-- -->
@@ -34,89 +34,103 @@
<h2>The Zero-Effort Object Access Package (ZOAP) Binary Distribution. Alpha
Release. </h2>
-<h3> From SOAP ... </h3>
+<h3> From SOAP ... </h3>
+
+The <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Simple Object Access
Protocol
+(SOAP)</a> is a lightweight protocol for the exchange of information in a globally
+distributed and loosely coupled environment. The current
+<a href="http://msdn.microsoft.com/xml/general/soapspec.asp">SOAPV1.1
specification</a>,
+inter alia authored by <a href="http://www.microsoft.com">Microsoft Corp.</a> and
+<a href="http://www.ibm.com">International Business Machines (IBM)</a>, has been
recently
+submitted to and acknowledged by the <a href="http://www.w3c.org/">World-Wide Web
+Consortium (W3C)</a> (see <a
href="http://www.microsoft.com/presspass/press/2000/May00/SoapW3CPR.asp">
+this press article</a>).
+
+<p>
+By embracing existing Internet technologies, SOAP has the potential to become a
powerful and really
+interoperable standard for messaging middleware: The
+<a href="http://www.w3.org/TR/1998/REC-xml-19980210">eXtensible Markup Language
(XML)</a> is chosen as a
+flexible and tolerant medium for encoding messages and their payload. For shipping
such envelopes in a
+resource-saving and possibly asynchronous manner, a variety of bullet-proof and
widely available transport
+protocols is applicable, such as the
+<a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">Hypertext Transfer
Protocol (HTTP1.1)</a>
+and the <a href="http://www.faqs.org/rfcs/rfc821.html">Simple Mail Transfer
Protocol (SMTP)</a>.</font>
+</p>
+
+<h3> ... to ZOAP </h3>
+
+The <a href="http://www.jboss.org/zoap/zoap.htm">Zero-Effort Object Access Package
(ZOAP)</a> is an Open Source
+SOAP implementation for the Java2 platform running under the
+<a href="license.html">GNU General Public License</a>. It aims to be a lightweight
and modular
+alternative to the existing reference implementations. Furthermore, ZOAP is deeply
integrated into the
+<a href="http://www.jboss.org/">jBoss application server</a> to transparently turn
+<a href="http://www.j2ee.com/">Enterprise Java-Beans (TM)</a> into globally
interoperable web services. The source
+distribution is available via cvs under
:pserver:[EMAIL PROTECTED]/products/cvs/ejboss/zoap
+
+<p>
+ZOAP has been initiated as a part of <a href="http://www.infor.de/">infor business
solutions AG</a> application
+component platform. The current alpha is released in August 2000 and comes
+already with a decent set of <a href="#features">outstanding functionalities</a>.
+The <a href="#todo">short-term roadmap</a> ensures that ZOAP, in combination with
the technologically
+advanced jBoss project, will develop into an up-front application middleware. A
first beta release
+is planned for September/October 2000.
+</p>
+
+<h3> Contact </h3>
+
+For questions around ZOAP, please contact <a
href="mailto:[EMAIL PROTECTED]">Dr. Christoph G. Jung</a> or
+<a href="mailto:[EMAIL PROTECTED]">Michael Wolber</a>. For questions around
jBoss, please contact
+the <a href="mailto:[EMAIL PROTECTED]">jBoss Organisation</a>.
+
+
+<h2> Features </h2>
+
+<ul>
+<li> 100% pure and lightweight Java implementation. </li>
+<li> On-the-fly (De-)Serialization (SAX, no intermediate DOM is generated). </li>
+<li>
+Extensible and expressive XML-Schema (draft as of May,2000) based Meta-Model
Architecture;
+Supports Null-values and Polymorhpism.
+</li>
+<li>
+Powerful Builtin Encoding-Style Compliant to Java2 Serialization (Including
Arbitrarily Nested Arrays and
+Collections).
+</li>
+<li> "Automatic-Mode" for Generating Deployment Meta-Data via Java Reflection. </li>
+<li> "Bootstrapping-Mode" for Reading Deployment Meta-Data. </li>
+<li> Service Contract Language is a Hybrid of the Microsoft Service Contract
Language and XmlSchema. </li>
+<li> Builtin HTTP support (no servlet engine needed); Support for persistent
HTTP/1.1 connections. </li>
+<li> Transparent Proxy Access </li>
+<li> Special Proxy Support for XML-enabled Web-Clients (no full (de-)serialisation
needed). </li>
+<li> Ready-Made Container-Plugin for jBoss2.0. Supports Stateless Beans. </li>
+</ul>
+
+<h2> Roadmap </h2>
+
+<ul>
+<li> Filter Architecture to Configure Verbosity and Depth of the Serialisation
Process </li>
+<li> Support for Stateful Beans through Persistent HTTP/1.1 connections. </li>
+<li> More Sophisticated (type-safe) Array and Collection Support: Lazy-Modes,
Delta-Interpretation. </li>
+<li> Transactional and Asynchronous Messaging. </li>
+<li> Connection of the Filter Architecture to Security Roles. </li>
+<li> Support for Soap-Encoding-Style, XMI-Encoding-Style and Bean-Encoding-Style.
</li>
+<li> Integration with Java Messaging Service and EJB2.0�s message-based beans.
</li>
+<li> Enhanced Constraints and Validations as defined in XML-Schema. </li>
+<li> SMTP-support </li>
+</ul>
+
+<H2> Known Holes/Bugs </h2>
+
+<ul>
+<li> Binding.class indeed represents what is called an EncodingStyle in SOAP.
Should be renamed. </li>
+<li> Lacking optmizing cache for Class-To-XmlType associations. </li>
+<li> Lacking In-VM optimization for
SOAPInvocationHandler/SOAPTie/SOAPContainerInvoker. </li>
+<li> Not all license annotations in the src-files have yet been updated to GPL.
</li>
+<li> minOccurs and maxOccurs of elements are not yet supported. (default:
0/unbounded) </li>
+<li> required of attributes is not yet supported. (default: false) </li>
+<li> SOAPContainerInvoker takes connection data out of ejb-jar.xml and jboss.xml,
not the contract.scl.</li>
+</ul>
-The <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Simple Object Access
Protocol (SOAP)</a>
-is a lightweight protocol for the exchange of information in a globally distributed
and loosely
-coupled environment. The current
-<a href="http://msdn.microsoft.com/xml/general/soapspec.asp">SOAPV1.1
specification</a>, inter
-alia authored by engineers from <a href="http://www.microsoft.com">Microsoft
Corp.</a> and
-<a href="http://www.ibm.com">International Business Machines (IBM)</a>, has been
recently
-submitted to and acknowledged by the <a href="http://www.w3c.org/">World-Wide Web
Consortium (W3C)</a>
-(see <a
href="http://www.microsoft.com/presspass/press/2000/May00/SoapW3CPR.asp">this press
article</a>).
-
-<p>
-By embracing existing Internet technologies, SOAP has the potential to become a
powerful and really
-interoperable standard for messaging middleware: The
-<a href="http://www.w3.org/TR/1998/REC-xml-19980210">eXtensible Markup Language
(XML)</a> is chosen as a
-flexible and tolerant medium for encoding messages and their payload. For shipping
such envelopes in a
-resource-saving and possibly asynchronous manner, a variety of bullet-proof and
widely available transport
-protocols is applicable, such as the
-<a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">Hypertext Transfer
Protocol (HTTP1.1)</a>
-and the <a href="http://www.faqs.org/rfcs/rfc821.html">Simple Mail Transfer
Protocol (SMTP)</a>.</font>
-</p>
-
-<h3> ... to ZOAP </h3>
-
-The <a href="http://www.jboss.org/zoap/zoap.htm">Zero-Effort Object Access Package
(ZOAP)</a> is an Open Source
-implementation of SOAP for the Java2 platform running under the
-<a href="license.html">GNU General Public License</a>. It aims to be a lightweight
and modular
-alternative to the existing reference implementations. Furthermore, ZOAP is deeply
integrated into the
-<a href="http://www.jboss.org/">jBoss application server</a> to transparently turn
-<a href="http://www.j2ee.com/">Enterprise Java-Beans (TM)</a> into globally
interoperable web services.
-
-<p>
-ZOAP has been initiated as a part of <a href="http://www.infor.de/">infor:business
solutions AG</a> application
-platform, the infor Component Engine (infor:CE). The current alpha has been
released in August 2000 and comes
-already with a decent set of <a href="#features">outstanding functionalities</a>.
-The <a href="#todo">short-term roadmap</a> ensures that ZOAP, in combination with
the technologically
-advanced jBoss project, will develop into an up-front application middleware. A
first beta release
-is planned for September 2000.
-</p>
-
-<h3> Contact </h3>
-
-For questions around ZOAP, please contact <a
href="mailto:[EMAIL PROTECTED]">Dr. Christoph G. Jung</a>.
-
-<h2> Features </h2>
-
-<ul>
-<li> 100% pure and lightweight Java implementation. </li>
-<li> On-the-fly (De-)Serialization (no intermediate DOM is generated). </li>
-<li> Extensible XML-Schema based Meta-Model Architecture; Supports Null-values and
Polymorhpism. </li>
-<li> Powerful Default Encoding-Style Compliant to Java2 Serialization. </li>
-<li> "Automatic-Mode" for Generating Deployment Meta-Data via Java Reflection. </li>
-<li> "Bootstrapping-Mode" for Reading Deployment Meta-Data. </li>
-<li> Service Contract Language is a Hybrid of the Microsoft Service Contract
Language and XmlSchema. </li>
-<li> Builtin HTTP support (no servlet engine needed); Support for persistent
HTTP/1.1 connections. </li>
-<li> Transparent Proxy Access </li>
-<li> Special Proxy Support for XML-enabled Web-Clients (no full (de-)serialisation
needed). </li>
-<li> Ready-Made Container-Plugin for jBoss2.0. Support Stateless Beans. </li>
-</ul>
-
-<h2> Roadmap </h2>
-
-<ul>
-<li> Filter Architecture to Configure Verbosity and Depth of the Serialisation
Process </li>
-<li> Support for Stateful Beans through Persistent HTTP/1.1 connections. </li>
-<li> Sophisticated (type-safe) Array and Collection Support. </li>
-<li> Transactional and Asynchronous Messaging. </li>
-<li> Connection of the Filter Architecture to Security Roles. </li>
-<li> Support for Soap-Encoding-Style, XMI-Encoding-Style and Bean-Encoding-Style.
</li>
-<li> Integration with Java Messaging Service and EJB2.0�s message-based beans.
</li>
-<li> Enhanced Constraints and Validations as defined in XML-Schema. </li>
-<li> SMTP-support </li>
-</ul>
-
-<H2> Known Bugs </h2>
-
-<ul>
-<li> I think that the Binding classes must be renamed into EncodingStyle, because
that is what they
-represent indeed. </li>
-<li> No cache for Class-To-XmlType association. </li>
-<li> Not all license annotations in the src-files have yet been updated to GPL.
</li>
-</ul>
-
<h2>Contents</h2>
The ZOAP binary distribution consists of the following folders and files:
@@ -149,7 +163,7 @@
<a href="http://www.jboss.org"><img
src="lib/resources/images/powered_by_jboss_flat_blue.gif" height="72"></a>
<hr>
-<small> Last change of $RCSfile: index.html,v $ by $Author: jung $ on $Date:
2000/08/10 21:05:14 $;
+<small> Last change of $RCSfile: index.html,v $ by $Author: jung $ on $Date:
2000/08/11 08:37:19 $;
See source for logging information.
<p>
Copyright 2000 (C) <a href="http://www.infor.de">infor:business solutions AG</a>,
Hauerstrasse 12,
@@ -162,14 +176,11 @@
<!--
$Log: index.html,v $
- Revision 1.1 2000/08/10 21:05:14 jung
- Initial revision
-
- Revision 1.1.1.1 2000/07/06 14:11:25 jung
- Import of a pre beta version of ZOAP source with a new directory structure,
- ant-based make, apache-kind of license, etc.
-
- jars are coming later because of cvs-history reasons.
-
-
+ Revision 1.2 2000/08/11 08:37:19 jung
+ adopted html pages to reflect Alpha-Status.
+ added an announcement document folder with the
+ release mailings
+
+ Revision 1.1.1.1 2000/08/10 21:05:14 jung
+ Initial import.
-->
