xml-general-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bu...@apache.org
Subject cvs commit: xml-site/targets/axis faq.html
Date Mon, 22 Apr 2002 13:38:25 GMT
butek       02/04/22 06:38:25

  Modified:    targets/axis faq.html
  Log:
  Added some FAQ items (courtesy Glen).
  
  Revision  Changes    Path
  1.5       +97 -23    xml-site/targets/axis/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/axis/faq.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- faq.html	11 Mar 2002 11:42:40 -0000	1.4
  +++ faq.html	22 Apr 2002 13:38:25 -0000	1.5
  @@ -2,7 +2,7 @@
   <html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  -   <meta name="GENERATOR" content="Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686) [Netscape]">
  +   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
   </head>
   <body text="#000000" bgcolor="#FFFFFF">
   &nbsp;
  @@ -14,27 +14,57 @@
   
   <p>These questions seem to be frequently asked:
   <ul>
  -<li><a href="#faq1">What is Axis? What is its relationship to Apache SOAP?</a></li>
  +<li>
  +<a href="#faq1">What is Axis? What is its relationship to Apache SOAP?</a></li>
  +
  +<li>
  +<a href="#faq2">Why call it "Axis"?</a></li>
   
  -<li><a href="#faq2">Why call it "Axis"?</a></li>
  +<li>
  +<a href="#faq3">Is Axis close to a release of some kind?</a></li>
  +
  +<li>
  +<a href="#faq4">What is Axis's status overall?</a></li>
   
  -<li><a href="#faq3">Is Axis close to a release of some kind?</a></li>
  +<li>
  +<a href="#faq5">Why do some classes fail to load under Tomcat?</a></li>
   
  -<li><a href="#faq4">What is Axis's status overall?</a></li>
  +<li>
  +<a href="#faq6">What if I can't find the answer to my question here?</a></li>
   
  -<li><a href="#faq5">Why do some classes fail to load under Tomcat?</a></li>
  +<li>
  +<a href="#faq7">How do I report bugs?</a></li>
   
  -<li><a href="#faq6">What if I can't find the answer to my question here?</a></li>
  +<li>
  +<a href="#faq8">How does Axis create my backend service objects?&nbsp;
  +Can I control this?</a></li>
   
  -<li><a href="#faq7">How do I report bugs?</a></li>
  -</ul>
  -<hr>
  -<a name="faq1"></a><i>What is Axis? What is its relationship to Apache
SOAP?</i>
  +<li>
  +<a href="#faq9">So does Axis support sessions?</a></li>
  +
  +<li>
  +<a href="#faq10">Cool, SOAP header-based sessions?&nbsp; How do I make
  +that work?</a></li>
  +
  +<li>
  +<a href="#faq11">What else can I do with sessions?</a></li>
  +
  +<li>
  +<a href="#faq12">How do I get access to the MessageContext in my service
  +object?</a></li>
  +
  +<li>
  +<a href="#faq13">Where do I put my &lt;typeMapping>/&lt;beanMapping>
information?</a></li>
  +
  +<br>&nbsp;</ul>
  +
  +<hr><a NAME="faq1"></a><i>What is Axis? What is its relationship
to Apache
  +SOAP?</i>
   <blockquote>Axis is essentially Apache SOAP 3.0. It is a from-scratch rewrite,
   designed around a streaming model (using SAX internally rather than DOM).
   The intention is to create a more modular, more flexible, and higher-performing
   SOAP implementation (relative to Apache SOAP 2.0).</blockquote>
  -<a name="faq2"></a><i>Why call it "Axis"?</i>
  +<a NAME="faq2"></a><i>Why call it "Axis"?</i>
   <blockquote>The name "Axis" was chosen because, when the project started,
   the XML Protocol working group had not chosen a name for its protocol.
   The intent was for Axis to support SOAP 1+, XML-RPC, and XMLP (whatever
  @@ -44,14 +74,12 @@
   the Apache SOAP project. C'est la vie.
   <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
  +<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>
  -<a name="faq4"></a><i>What is Axis's status overall?</i>
  +implemented, but we envisage a beta in the very near future (as of 11 March
  +2002).</blockquote>
  +<a NAME="faq4"></a><i>What is Axis's status overall?</i>
   <blockquote>To keep track of Axis's progress:
   <ul>
   <li>
  @@ -63,15 +91,61 @@
   requirements &amp; status page.</a></li>
   </ul>
   </blockquote>
  -<a name="faq5"></a><i>Why do some classes fail to load under Tomcat?</i>
  +<a NAME="faq5"></a><i>Why do some classes fail to load under Tomcat?</i>
   <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>
  -<a name="faq6"><i>What if I can't find the answer to my question here?</i>
  +<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>
  +<a NAME="faq7"></a><i>How do I report bugs?</i>
   <blockquote>See <a href="bugs.html" target="body">bugs</a>.</blockquote>
  +<a NAME="faq8"></a><i>How does Axis create my backend service objects?&nbsp;
  +Can I control this?</i>
  +<blockquote>Axis supports a "scope" parameter on services, which can be
  +set to "request" (make a new object to service each request - this is the
  +default), "session" (associate a new object with each session), and "application"
  +(all users share a singleton object).&nbsp; WARNING: If you set the scope
  +to "session" or "application", it is possible that multiple threads of
  +control may attempt to access your object's methods at the same time. It
  +is your responsibility to ensure that your objects are thread-safe in these
  +cases.</blockquote>
  +<a NAME="faq9"></a><i>So does Axis support sessions?</i>
  +<blockquote>Yes.&nbsp; We have a session abstraction which allows an extensible
  +set of underlying implementations - take a look at the class org.apache.axis.session.Session
  +for details.&nbsp; In particular, we currently support sessions based on
  +HTTP cookies and also transport-independent sessions based on SOAP headers.&nbsp;
  +It is up to some handler on the request chain to set up an appropriate
  +Session implementation and attach it to the MessageContext with MessageContext.setSession()
  +so that anyone who wants to use session semantics can get at it.</blockquote>
  +<a NAME="faq10"></a><i>Cool, SOAP header-based sessions?&nbsp; How
do I
  +make that work?</i>
  +<blockquote>There is a Handler class called "org.apache.axis.handlers.&nbsp;
  +SimpleSessionHandler" which implements this functionality. You need to
  +include this handler in the request and response flows of both your client
  +and your server.&nbsp; Take a look at our session test (test.session.TestSimpleSession)
  +for an example.</blockquote>
  +<a NAME="faq11"></a><i>What else can I do with sessions?</i>
  +<blockquote>Any time after the session context has been established, calling
  +getSession() on the current messageContext will obtain you a reference
  +to a Session object.&nbsp; You may use this object like a Hashtable to
  +store arbitrary data associated with this Session.&nbsp; For instance,
  +on one request you might extract the caller's name and address from a database
  +(an expensive operation), and then cache them in the Session object for
  +fast access on subsequent invocations from the same caller.&nbsp; This
  +functionality can be used either by custom Handlers or by your backend
  +service object itself.</blockquote>
  +<a NAME="faq12"></a><i>How do I get access to the MessageContext in my
  +service object?</i>
  +<blockquote>Use the static MessageContext.getCurrentContext() method at
  +any time during a method call on your object.</blockquote>
  +<a NAME="faq13"></a><i>Where do I put my &lt;typeMapping>/&lt;beanMapping>
  +information?</i>
  +<blockquote>There are two places in the WSDD where type mappings are appropriate.&nbsp;
  +At the top level, just under &lt;deployment>, they become <b>global</b>
  +type mappings, and all services deployed in the Axis engine will be able
  +to use them.&nbsp; Alternately, you can place them inside your &lt;service>
  +tag, and then the mappings will only be accessible by that particular service.</blockquote>
   
   </body>
  -</html>
  \ No newline at end of file
  +</html>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: general-cvs-help@xml.apache.org


Mime
View raw message