axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9891] New: - Why does TypeMappingImpl.register require AXIS factories?
Date Sat, 15 Jun 2002 15:52:43 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9891>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9891

Why does TypeMappingImpl.register require AXIS factories?

           Summary: Why does TypeMappingImpl.register require AXIS
                    factories?
           Product: Axis
           Version: current (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: butek@us.ibm.com


There is code in TypeMappingImpl.register:

        // Make sure the factories conform to the Axis interfaces
        if (sf != null &&
            !(sf instanceof SerializerFactory)) {
            throw new JAXRPCException();
        }
        if (dsf != null &&
            !(dsf instanceof DeserializerFactory)) {
            throw new JAXRPCException();
        }

If sf isn't an AXIS Serializer and/or dsf isn't an AXIS DeserializerFactory, 
registration fails.

The TCK factories are not AXIS factories, so the TCK fails when it calls
TypeMapping.register.

Mime
View raw message