Examples of org.apache.axis.encoding.TypeMappingRegistryImpl

org.apache.axis.encoding.TypeMappingRegistryImpl

@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.comThe TypeMappingRegistry keeps track of the individual TypeMappings. 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. 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. So logically we have: TMR | | | +---------------> DefaultTM | ^ | | +----> TM --delegate---+ But in the implementation, the TMR references "delegate" TypeMappings (TM') which then reference the actual TM's So the picture is really: TMR | | | +-----------TM'------> DefaultTM | ^ | | +-TM'-> TM ----+ This extra indirection is necessary because the user may want to change the default type mapping. In such cases, the TMR just needs to adjust the TM' for the DefaultTM, and all of the other TMs will properly delegate to the new one. Here's the picture: TMR | | | +-----------TM'--+ DefaultTM | ^ | | | +---> New User Defined Default TM +-TM'-> TM ----+ The other reason that it is necessary is when a deploy has a TMR, and then TMR's are defined for the individual services in such cases the delegate() method is invoked on the service to delegate to the deploy TMR Deploy TMR | | | +-----------TM'------> DefaultTM | ^ | | +-TM'-> TM ----+ Service TMR | | | +-----------TM'------> DefaultTM | ^ | | +-TM'-> TM ----+ ServiceTMR.delegate(DeployTMR) Deploy TMR | | | +------------TM'------> DefaultTM | ^ ^ | | | +-TM'-> TM ----+ | ^ | +-------+ | | | | Service TMR | | | | | | | +----------TM'-+ | | | | | +-TM'-> TM + | | +----------------+ 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.

        if (defaultConfiguration != null)
            return defaultConfiguration.getTypeMappingRegistry();


        // No default config, but we need a TypeMappingRegistry...
        // (perhaps the TMRs could just be chained?)
        tmr = new TypeMappingRegistryImpl();
        return tmr;
    }

        this.endpointURL = endpointURL;
    }


    public TypeMappingRegistry getTypeMappingRegistry() {
        if (tmr == null) {
            tmr = new TypeMappingRegistryImpl();
        }
        return tmr;
    }

        for (Iterator iter = operations.iterator(); iter.hasNext();) {
            OperationDesc operation = (OperationDesc) iter.next();
            serviceDesc.addOperationDesc(operation);
        }


        TypeMappingRegistryImpl tmr = new TypeMappingRegistryImpl();
        tmr.doRegisterFromVersion("1.3");


        TypeMapping typeMapping = tmr.getOrMakeTypeMapping(serviceDesc.getUse().getEncoding());


        serviceDesc.setTypeMappingRegistry(tmr);
        serviceDesc.setTypeMapping(typeMapping);


        List typeInfo;

Examples of org.apache.axis.encoding.TypeMappingRegistryImpl

Related Classes of org.apache.axis.encoding.TypeMappingRegistryImpl