You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by st...@apache.org on 2003/04/04 19:19:52 UTC
cvs commit: xml-axis/java/docs reading.html
stevel 2003/04/04 09:19:51
Modified: java/docs reading.html
Log:
updated reading matter
Revision Changes Path
1.15 +44 -3 xml-axis/java/docs/reading.html
Index: reading.html
===================================================================
RCS file: /home/cvs/xml-axis/java/docs/reading.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- reading.html 27 Mar 2003 07:23:51 -0000 1.14
+++ reading.html 4 Apr 2003 17:19:51 -0000 1.15
@@ -102,14 +102,27 @@
<li>
<a href="http://ietf.org/rfc/rfc2616.txt">
RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
- </a><
+ </a><br>
+ This is HTTP. You really do need to understand the basics of how this
+ works, to work out why your web service doesn't :)
+</li>
+<li>
+ <a href="http://java.sun.com/xml/saaj/index.html">
+ SOAP with Attachments API for Java (SAAJ)
+ </a><br>
+ SAAJ enables developers to produce and consume messages conforming to
+ the SOAP 1.1 specification and SOAP with Attachments note.
</li>
<li>
- <a href="http://java.sun.com/xml/downloads/jaxrpc.html">
- JAX-RPC Specification 1.0
+ <a href="http://java.sun.com/xml/jaxrpc/index.html">
+ Java API for XML-Based RPC (JAX-RPC)
</a><br>
The public API for Web Services in Java.
+ JAX-RPC enables Java technology developers to develop SOAP based
+ interoperable and portable web services. JAX-RPC provides the core API
+ for developing and deploying web services on the Java platform.
</li>
+
<li>
<a href="http://www.w3.org/TR/xmlschema-0/">
XML Schema Part 0: Primer
@@ -120,6 +133,17 @@
of this specification.
</li>
+<li>
+ <a href="http://java.sun.com/xml/jaxm/index.html">
+ Java API for XML Messaging (JAXM)
+ </a><br>
+ JAXM enables applications to send and receive document oriented XML
+ messages using a pure Java API. JAXM implements Simple Object Access
+ Protocol (SOAP) 1.1 with Attachments messaging so that developers can
+ focus on building, sending, receiving, and decomposing messages for
+ their applications instead of programming low level XML communications
+ routines.
+</li>
</ol>
@@ -183,6 +207,23 @@
to skirt round the interop problem.
</li>
+
+<li>
+ <a href="http://www.hpl.hp.com/techreports/2002/HPL-2002-274.html">
+ Making Web Services that Work</a><br>
+
+ A practical but suspiciously code free paper on how to get web
+ services into production. As well as coverage of topics such as
+ interop, versioning, security, this (57 page) paper looks at the
+ deployment problem, advocating a fully automated deployment process
+ in which configuration problems are treated as defects for which
+ automated test cases and regresssion testing are appropriate.
+ Happyaxis.jsp is the canonical example of this. The author, Steve
+ Loughran also looks a bit at what the component model of a federated
+ web service world would really be like.
+
+</li>
+
</ol>