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 @@
  • Where do I put my <typeMapping>/<beanMapping> information?
  • -
      +
  • +What is the relationship between JAXM and AXIS?
  • + +
  • +How does Axis figure out which deployed service to call?
  • + +
  • +How do I associate a namespace mapping with my service?
  • +
    What is Axis? What is its relationship to Apache SOAP? @@ -75,10 +83,9 @@

    (According to the README, AXIS stands for "Apache eXtensible Interaction System", which could mean almost anything.) Is Axis close to a release of some kind? -

    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).
    +
    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).
    What is Axis's status overall?
    To keep track of Axis's progress:
    What if I can't find the answer to my question here?
    Try the mailing lists.
    How do I report bugs? @@ -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. +What is the relationship between JAXM and AXIS? +
    JAXM is a specification (NB. not an implementation) of two +sets of interfaces: javax.xml.soap and javax.xml.messaging. +

    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. +

    There is also an Axis to-do item to implement javax.xml.messaging, but +no-one has agreed to take that on.

    +How does Axis figure out which deployed service +to call? +
    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. +

    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. +

    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. +

    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: +

    <SOAP:Body> +
      <ns:MyMethod xmlns:ns="http://xml.apache.org/axis/Weather"/> +
    </SOAP:Body> +

    This message would look up "http://xml.apache.org/axis/Weather" in the +namespace mapping list to see if there was an associated service.

    +How do I associate a namespace mapping with my service? +
    The WSDD for your service should look something like this: +

    <service name="MyService" provider="java:RPC"> +
      <namespace>http://my.com/MyServiceNamespace</namespace> +
      ... +
    </service> +
      +
     

    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 @@ + - - + + + + + +  +
    - -Reference Library - -
    + + +
    Reference Library 
    -

    - -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: -

    -These resources are required reading for anybody contributing source code -to the project. -

    - -SOAP Specific Resources -

    - - -SOAP W3C Specification -
    -Required reading. -

    - - -SOAP Messaging with Attachments W3C Specification -
    -SOAP combined with MIME. -

    - - -SOAP Security Extensions: Digital Signature Specification -
    -Adding security to SOAP. -

    - -Other Resources -

    - - -The Java Language Specification -
    -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. -

    - - -Javadoc -
    -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. -

    - - -The Java Code Conventions -
    -This Sun document specifies the de-facto standard way of formatting Java -code. All code written for this project must follow these conventions. -

    - - -Open Source Development with CVS -
    -Written by Karl Fogel, this is an online version of many of the primary -chapters from the dead-tree version of his book. -

    - - -Introduction to CVS -
    -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. -

    - - -Version Management with CVS -
    -Written by Per Cederqvist at al, this is the main manual for CVS. It -provides details on all documented CVS features. -

    - +

    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: +

    These resources are required reading for anybody contributing source +code to the project. +

    SOAP Specific Resources +

    SOAP W3C Specification +
    Required reading. +

    SOAP +Messaging with Attachments W3C Specification +
    SOAP combined with MIME. +

    SOAP Security +Extensions: Digital Signature Specification +
    Adding security to SOAP. +

    Other Specifications +

    Web Services Description Language +(WSDL) 1.1 +

    Java +API for XML-based RPC (JAX-RPC) +

    Other Resources +

    The +Java Language Specification +
    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. +

    Javadoc +
    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. +

    The +Java Code Conventions +
    This Sun document specifies the de-facto standard way of formatting +Java code. All code written for this project must follow these conventions. +

    Open Source Development +with CVS +
    Written by Karl Fogel, this is an online version of many of the primary +chapters from the dead-tree version of his book. +

    Introduction +to CVS +
    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. +

    Version +Management with CVS +
    Written by Per Cederqvist at al, this is the main manual for CVS. It +provides details on all documented CVS features. 1.1 xml-site/targets/axis/beta1-beta2.html Index: beta1-beta2.html ===================================================================  
    Changes from Beta 1 to Beta 2

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