1) Changes the namespace from http://xml.apache.org/axis/java to one generated with the Namespace utils for auto-typed classes.
2) Instead of create serializers each time, it registers the serializers with Axis for future lookups.
3) Localizes all the type-mapping related functions into getTypeQName(Class)
Classes are auto-typed on the conditions that auto-typing is turned on and there exists no previously defined type mapping for the class.
Now, I believe Glen's question is how can you just throw everything into getTypeQName and expect it to work? I removed the auto-tying references from getSerializer/getDeserializer. This isn't a problem for getSerializer() because it calls getTypeQName directly. However, it does, as Glen pointed out, totally remove all direct reference to auto-typing from the getDeserializer method.
Now why did I do this? :) When a service is created which contains types that don't exist, ServiceDesc.createOperationForMethod calls getTypeQName before the service is up and running, thereby registering the serializers before getSerializer/getDeserializer are ever called.
Knowing this, do you see problems with this approach?
- Dan
Dan Diephouse wrote:
Hi,
I don't know if you're missing something or not. Probably not since you know much more about Axis than I do. I have free time today, so I will work on a fix for the test breakage and a test case for auto-typing the rest of the afternoon. I will let you know as soon as I have something.
- Dan
Glen Daniels wrote:
Argh - I don't have time to get into this right now (sorry, am still slammed with internal stuff), but this looks weird to me - it seems to actually remove the hooks for autoTyping to work in the first place (i.e. the check for the trigger namespace). Am I missing something here?
--Glen
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 12:48 PM
To: [EMAIL PROTECTED]
Subject: cvs commit: xml-axis/java/src/org/apache/axis/encoding TypeMappingImpl.java
