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 di...@apache.org on 2003/03/17 16:20:52 UTC
cvs commit: xml-axis/java/src/org/apache/axis/encoding TypeMappingDelegate.java TypeMappingImpl.java TypeMappingRegistryImpl.java
dims 2003/03/17 07:20:52
Modified: java/src/org/apache/axis/encoding TypeMappingDelegate.java
TypeMappingImpl.java TypeMappingRegistryImpl.java
Log:
Fix for Bug 18045 - Javadocs formatting errors in org.apache.axis.encoding
Revision Changes Path
1.10 +1 -2 xml-axis/java/src/org/apache/axis/encoding/TypeMappingDelegate.java
Index: TypeMappingDelegate.java
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/encoding/TypeMappingDelegate.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- TypeMappingDelegate.java 11 Dec 2002 22:38:14 -0000 1.9
+++ TypeMappingDelegate.java 17 Mar 2003 15:20:51 -0000 1.10
@@ -61,12 +61,11 @@
import javax.xml.rpc.JAXRPCException;
/**
- * @author Rich Scheuerle (scheu@us.ibm.com)
- *
* The TypeMapping delegate is used to simply delegate to
* the indicated type mapping. It is used by the TypeMappingRegistry
* to assist with chaining.
*
+ * @author Rich Scheuerle (scheu@us.ibm.com)
*/
class TypeMappingDelegate extends TypeMappingImpl {
1.40 +11 -6 xml-axis/java/src/org/apache/axis/encoding/TypeMappingImpl.java
Index: TypeMappingImpl.java
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/encoding/TypeMappingImpl.java,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- TypeMappingImpl.java 6 Jan 2003 22:25:00 -0000 1.39
+++ TypeMappingImpl.java 17 Mar 2003 15:20:51 -0000 1.40
@@ -70,27 +70,32 @@
import java.util.List;
/**
- * @author Rich Scheuerle (scheu@us.ibm.com)
- *
+ * <p>
* This is the implementation of the axis TypeMapping interface (which extends
* the JAX-RPC TypeMapping interface).
- *
+ * </p>
+ * <p>
* A TypeMapping is obtained from the singleton TypeMappingRegistry using
* the namespace of the webservice. The TypeMapping contains the tuples
* {Java type, SerializerFactory, DeserializerFactory, Type QName)
- *
+ * </p>
+ * <p>
* So if you have a Web Service with the namespace "XYZ", you call
* the TypeMappingRegistry.getTypeMapping("XYZ").
- *
+ * </p>
+ * <p>
* The wsdl in your web service will use a number of types. The tuple
* information for each of these will be accessed via the TypeMapping.
- *
+ * </p>
+ * <p>
* Because every web service uses the soap, schema, wsdl primitives, we could
* pre-populate the TypeMapping with these standard tuples. Instead,
* if the namespace/class matches is not found in the TypeMapping
* the request is delegated to the
* Default TypeMapping or another TypeMapping
+ * </p>
*
+ * @author Rich Scheuerle (scheu@us.ibm.com)
*/
public class TypeMappingImpl implements TypeMapping
{
1.23 +15 -10 xml-axis/java/src/org/apache/axis/encoding/TypeMappingRegistryImpl.java
Index: TypeMappingRegistryImpl.java
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/encoding/TypeMappingRegistryImpl.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- TypeMappingRegistryImpl.java 2 Mar 2003 20:21:35 -0000 1.22
+++ TypeMappingRegistryImpl.java 17 Mar 2003 15:20:51 -0000 1.23
@@ -58,27 +58,25 @@
import org.apache.axis.Constants;
import org.apache.axis.utils.Messages;
-import javax.xml.rpc.JAXRPCException;
import java.util.HashMap;
/**
- * @author James Snell (jasnell@us.ibm.com)
- * @author Sam Ruby (rubys@us.ibm.com)
- * Re-written for JAX-RPC Compliance by
- * @author Rich Scheuerle (scheu@us.ibm.com
- *
+ * <p>
* The TypeMappingRegistry keeps track of the individual TypeMappings.
- *
+ * </p>
+ * <p>
* The TypeMappingRegistry for axis contains a default type mapping
* that is set for either SOAP 1.1 or SOAP 1.2
* The default type mapping is a singleton used for the entire
* runtime and should not have anything new registered in it.
- *
+ * </p>
+ * <p>
* Instead the new TypeMappings for the deploy and service are
* made in a separate TypeMapping which is identified by
* the soap encoding. These new TypeMappings delegate back to
* the default type mapping when information is not found.
- *
+ * </p>
+ * <p>
* So logically we have:
* <pre>
* TMR
@@ -91,7 +89,8 @@
*
* But in the implementation, the TMR references
* "delegate" TypeMappings (TM') which then reference the actual TM's
- *
+ * </p>
+ * <p>
* So the picture is really:
* <pre>
* TMR
@@ -158,6 +157,12 @@
* So now the service uses the DefaultTM of the Deploy TMR, and
* the Service TM properly delegates to the deploy's TM. And
* if either the deploy defaultTM or TMs change, the links are not broken.
+ * </p>
+ *
+ * @author James Snell (jasnell@us.ibm.com)
+ * @author Sam Ruby (rubys@us.ibm.com)
+ * Re-written for JAX-RPC Compliance by
+ * @author Rich Scheuerle (scheu@us.ibm.com
*/
public class TypeMappingRegistryImpl implements TypeMappingRegistry {