butek 02/04/25 12:27:01 Modified: targets/axis faq.html ref.html Added: targets/axis beta1-beta2.html Log: - Added a changes-from-beta1-to-beta2 doc. - added some FAQ items. - added some spec references. Revision Changes Path 1.6 +62 -6 xml-site/targets/axis/faq.html Index: faq.html =================================================================== RCS file: /home/cvs/xml-site/targets/axis/faq.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- faq.html 22 Apr 2002 13:38:25 -0000 1.5 +++ faq.html 25 Apr 2002 19:27:00 -0000 1.6 @@ -56,7 +56,15 @@ <li> <a href="#faq13">Where do I put my <typeMapping>/<beanMapping> information?</a></li> -<br> </ul> +<li> +<a href="#faq14">What is the relationship between JAXM and AXIS?</a></li> + +<li> +<a href="#faq15">How does Axis figure out which deployed service to call?</a></li> + +<li> +<a href="#faq16">How do I associate a namespace mapping with my service?</a></li> +</ul> <hr><a NAME="faq1"></a><i>What is Axis? What is its relationship to Apache SOAP?</i> @@ -75,10 +83,9 @@ <p>(According to the README, AXIS stands for "Apache eXtensible Interaction System", which could mean almost anything.)</blockquote> <a NAME="faq3"></a><i>Is Axis close to a release of some kind?</i> -<blockquote>Yes, depending on who you ask :-) The current code base already -supports most of the standard interop tests. Some features remain to be -implemented, but we envisage a beta in the very near future (as of 11 March -2002).</blockquote> +<blockquote>The first beta was released on March 15, 2002. The second +beta will be released late April, with a beta once a month until the 1.0 +release (hopefully summer of 2002).</blockquote> <a NAME="faq4"></a><i>What is Axis's status overall?</i> <blockquote>To keep track of Axis's progress: <ul> @@ -95,7 +102,7 @@ <blockquote>Tomcat will not load classes with package names starting "java." or "javax." from the WEB-INF directory. jars containing such classes need to be installed in $TOMCAT_HOME/common/lib rather than in WEB-INF/lib. -Currently (21 Feb. 2002), axis.jar is such a jar.</blockquote> +Currently (April 25, 2002) jaxrpc.jar is such a jar.</blockquote> <a NAME="faq6"></a><i>What if I can't find the answer to my question here?</i> <blockquote>Try the <a href="mail.html" target="body">mailing lists</a>.</blockquote> <a NAME="faq7"></a><i>How do I report bugs?</i> @@ -146,6 +153,55 @@ type mappings, and all services deployed in the Axis engine will be able to use them. Alternately, you can place them inside your <service> tag, and then the mappings will only be accessible by that particular service.</blockquote> +<a NAME="faq14"></a><i>What is the relationship between JAXM and AXIS?</i> +<blockquote>JAXM is a specification (NB. not an implementation) of two +sets of interfaces: javax.xml.soap and javax.xml.messaging. +<p>Axis currently (April 25, 2002) implements *some* of the javax.xml.soap +interfaces, although these are not mentioned in the list of published interfaces +in the Axis Users Guide as the job is only partly complete. We hope to +implement the other JAXM SOAP interfaces as a low-priority, background +task, but would welcome help from anyone who is keen to see them implemented +sooner. +<p>There is also an Axis to-do item to implement javax.xml.messaging, but +no-one has agreed to take that on.</blockquote> +<a NAME="faq15"></a><i>How does Axis figure out which deployed service +to call?</i> +<blockquote>Axis has a very flexible dispatch mechanism, with three built-in +options, and the ability to customize your own. Dispatch to a service +in Axis really means setting the service field in the MessageContext as +it flows through the various Handlers in your configuration. Once +the service is set, the engine will be able to call it at the appropriate +time. So who does the setting? Any Handler who wants to. +<p>The default dispatch mechanism for Axis is by URL, so that if you access +http://myhost/axis/services/WeatherReport, you will get the "WeatherReport" +service. This mechanism works because the HTTP transport in Axis +has the URLMapper (org.apache.axis.handlers.http.URLMapper) Handler deployed +on the request chain. The URLMapper takes the incoming URL, extracts +the last part of it as the service name, and attempts to look up a service +by that name in the current EngineConfiguration. +<p>Similarly you could deploy the HTTPActionHandler to dispatch via the +SOAPAction HTTP header. You can also feel free to set the service +in your own custom way - for instance, if you have a transport which funnels +all messages through a single service, you can just set the service in +the MessageContext before your transport calls the AxisEngine. Or +if you dispatch based on the contents of a SOAP header, or the time of +day, you could write a Handler which did that. +<p>If no Handler has set the service by the time someone needs to deserialize +the SOAP message, we will attempt to look it up using the namespace of +the first body element. So for instance: +<p><SOAP:Body> +<br> <ns:MyMethod xmlns:ns="http://xml.apache.org/axis/Weather"/> +<br></SOAP:Body> +<p>This message would look up "http://xml.apache.org/axis/Weather"; in the +namespace mapping list to see if there was an associated service.</blockquote> +<a NAME="faq16"></a><i>How do I associate a namespace mapping with my service?</i> +<blockquote>The WSDD for your service should look something like this: +<p><service name="MyService" provider="java:RPC"> +<br> <namespace>http://my.com/MyServiceNamespace</namespace> +<br> ... +<br></service> +<br> +<br> </blockquote> </body> </html> 1.7 +58 -86 xml-site/targets/axis/ref.html Index: ref.html =================================================================== RCS file: /home/cvs/xml-site/targets/axis/ref.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- ref.html 6 Mar 2001 13:05:42 -0000 1.6 +++ ref.html 25 Apr 2002 19:27:00 -0000 1.7 @@ -1,91 +1,63 @@ +<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> -<body bgcolor="#ffffff" text="#000000"> -<table width=100%><tr bgcolor="#82ADF6"><td> -<b><font size=+2> -Reference Library -</font></b> -</td></tr> +<head> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]"> +</head> +<body text="#000000" bgcolor="#FFFFFF"> + +<table WIDTH="100%" > +<tr BGCOLOR="#82ADF6"> +<td><b><font size=+2>Reference Library </font></b></td> +</tr> </table> -<p> - -The Axis Project lives or fails based on its human resources. Users and -contributors alike help the project with ideas and brainpower. A common -foundation of knowledge is required to effectively participate in this -virtual community. The following is a list of documents that we have -found helpful for us and may be helpful to you: -<p> -These resources are required reading for anybody contributing source code -to the project. -<p> - -<b><font size=+1>SOAP Specific Resources</font></b> -<p> - -<a target="new" href="http://www.w3.org/TR/SOAP/";> -<b>SOAP W3C Specification</b></a> -<br> -Required reading. -<p> - -<a target="new" href="http://www.w3.org/TR/SOAP-attachments";> -<b>SOAP Messaging with Attachments W3C Specification</b></a> -<br> -SOAP combined with MIME. -<p> - -<a target="new" href="http://www.w3.org/TR/SOAP-dsig/";> -<b>SOAP Security Extensions: Digital Signature Specification</b></a> -<br> -Adding security to SOAP. -<p> - -<b><font size=+1>Other Resources</font></b> -<p> - -<a target="new" href="http://java.sun.com/docs/books/jls/index.html";> -<b>The Java Language Specification</b></a> -<br> -Written by the creators of the Java Programming Language, this online book -is considered by many to be the bible for programming in Java. A must read. -<p> - -<a target="new" href="http://java.sun.com/products/jdk/javadoc/index.html";> -<b>Javadoc</b></a> -<br> -Javadoc is the automatic software documentation generator used by Java since -it was first released. All code written for this project must be documented -using Javadoc conventions. -<p> - -<a target="new" - href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html";> -<b>The Java Code Conventions</b></a> -<br> -This Sun document specifies the de-facto standard way of formatting Java -code. All code written for this project must follow these conventions. -<p> - -<a target="new" href="http://cvsbook.red-bean.com/";> -<b>Open Source Development with CVS</b></a> -<br> -Written by Karl Fogel, this is an online version of many of the primary -chapters from the dead-tree version of his book. -<p> - -<a target="new" href="http://www.cvshome.org/docs/blandy.html";> -<b>Introduction to CVS</b></a> -<br> -Written by Jim Blandy, this brief introduction gives a first look into -CVS. If you have never used CVS before, you'll want to start here. -<p> - -<a target="new" href="http://www.cvshome.org/docs/manual/cvs.html";> -<b>Version Management with CVS</b></a> -<br> -Written by Per Cederqvist at al, this is the main manual for CVS. It -provides details on all documented CVS features. -<p> - +<p>The Axis Project lives or fails based on its human resources. Users +and contributors alike help the project with ideas and brainpower. A common +foundation of knowledge is required to effectively participate in this +virtual community. The following is a list of documents that we have found +helpful for us and may be helpful to you: +<p>These resources are required reading for anybody contributing source +code to the project. +<p><b><font size=+1>SOAP Specific Resources</font></b> +<p><b><a href="http://www.w3.org/TR/SOAP/"; target="new">SOAP W3C Specification</a></b> +<br>Required reading. +<p><b><a href="http://www.w3.org/TR/SOAP-attachments"; target="new">SOAP +Messaging with Attachments W3C Specification</a></b> +<br>SOAP combined with MIME. +<p><b><a href="http://www.w3.org/TR/SOAP-dsig/"; target="new">SOAP Security +Extensions: Digital Signature Specification</a></b> +<br>Adding security to SOAP. +<p><b><font size=+1>Other Specifications</font></b><b><font size=+1><a href="http://www.w3c.org/TR/wsdl.html";></a></font></b> +<p><a href="http://www.w3c.org/TR/wsdl.html";>Web Services Description Language +(WSDL) 1.1</a> +<p><a href="http://jcp.org/aboutJava/communityprocess/first/jsr101/index.html";>Java +API for XML-based RPC (JAX-RPC)</a> +<p><b><font size=+1>Other Resources</font></b> +<p><b><a href="http://java.sun.com/docs/books/jls/index.html"; target="new">The +Java Language Specification</a></b> +<br>Written by the creators of the Java Programming Language, this online +book is considered by many to be the bible for programming in Java. A must +read. +<p><b><a href="http://java.sun.com/products/jdk/javadoc/index.html"; target="new">Javadoc</a></b> +<br>Javadoc is the automatic software documentation generator used by Java +since it was first released. All code written for this project must be +documented using Javadoc conventions. +<p><b><a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html"; target="new">The +Java Code Conventions</a></b> +<br>This Sun document specifies the de-facto standard way of formatting +Java code. All code written for this project must follow these conventions. +<p><b><a href="http://cvsbook.red-bean.com/"; target="new">Open Source Development +with CVS</a></b> +<br>Written by Karl Fogel, this is an online version of many of the primary +chapters from the dead-tree version of his book. +<p><b><a href="http://www.cvshome.org/docs/blandy.html"; target="new">Introduction +to CVS</a></b> +<br>Written by Jim Blandy, this brief introduction gives a first look into +CVS. If you have never used CVS before, you'll want to start here. +<p><b><a href="http://www.cvshome.org/docs/manual/cvs.html"; target="new">Version +Management with CVS</a></b> +<br>Written by Per Cederqvist at al, this is the main manual for CVS. It +provides details on all documented CVS features. </body> </html> 1.1 xml-site/targets/axis/beta1-beta2.html Index: beta1-beta2.html =================================================================== <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]"> </head> <body text="#000000" bgcolor="#FFFFFF"> <table WIDTH="100%" > <tr BGCOLOR="#82ADF6"> <td><b><font size=+2>Changes from Beta 1 to Beta 2</font></b></td> </tr> </table> <ul> <li> javax interfaces are now fully compatible with JAX-RPC version 0.8. And the implementation mostly supports these interfaces.</li> <li> Server-side skeletons are no longer generated by default (they can still be generated with the option '--skeletonDeploy true'). If the skeleton exists, WSDL metadata resides within it. If the skeleton does not exist, WSDL metadata resides in deploy.wsdd.</li> <li> Generated beans now include robust toString(), equals(..) and hashCode() methods.</li> <li> Additional XML-type support:</li> <ul> <li> attribute/element "format" attributes.</li> <li> derived complexTypes.</li> <li> an element or attribute without a type correctly defaults to xsd:anyType.</li> <li> abstract attributes on complexTypes.</li> </ul> <li> The bindings for the echo sample are now generated from a wsdl file.</li> <li> WSDL2Java only generates referenced types (unless --all is specified). Now, derived types are considered referenced if their base type is referenced. If the WSDL file contains xsd:anyType, then all types are considered referenced.</li> <li> Meta data and serializer/deserializer access can be embedded in the bean class or a helper class.</li> <li> Password support in WSDL2Java</li> <li> Improvements to SerializationContext to allow specifcation of both javaType and xmlType.</li> <li> Serialization/deserialization of beans that have public fields instead of getter/setter methods.</li> <li> Various bug fixes and improvements.</li> </ul> </body> </html>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
