On Tuesday 02 July 2002 10:00, Scott Nichol wrote: > It is "inherent", but only for an exact match of the type Map. When the > Parameter instance is created, the type specified there is used to > determine the serializer. Specifying the type using HashMap.class does not > match the serializer for Map, which is registered using Map.class.
> Alternatively, you can specify HashMap.class when instantiating the > Parameter, but then you must add a mapping using > SOAPMappingRegistry#mapTypes for HashMap. I don't call either way "inherent". Inherent means to me; "I need to do nothing and it will work". Map.class is meaningless as "exact match". There is nothing that returns a "class java.util.Map" for getClass(), if that is what you mean. Parameter types are typically not a problem, since they are pretty much under control and can be modified for the occassion. It is the content of objects that really is annoying. Don't get me wrong. I like SOAP and I like the Apache SOAP implementation. We have used it in three parts of our system. A Login service, a business logic service, and a File System that can be plugged into NetBeans. Only the business logic is giving us a hard time, since we are dealing with objects instead of primitives. Niclas -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
