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 24145] - TypeMapping not inheriting
Date Mon, 27 Oct 2003 12:08:18 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=24145>.
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=24145

TypeMapping not inheriting





------- Additional Comments From matthew_pocock@yahoo.co.uk  2003-10-27 12:08 -------
OK - tracked this down. The emitter's defaultTM property is null untill init()
is called, but this is a protected method that's only called in the code
generation methods.

A work arround is to use:

DefaultTypeMappingImpl.getSingleton()

instead of:

emitter.getDefaultTypeMapping()

One approach to fixing this would be to remove the default type mapping property
all together, and use the type mapping delegation system to get the job done. We
could document that when you call setTypeMapping, you should probably be using a
TypeMapping instance that chains back to the previous getTypeMapping result. The
object could be initialized with getTypeMapping returning
DefaultTypeMappingImpl.getSingleton() - this has the benefit of removing lots of
if/else blocks that currently cruft up the code. However, perhaps the default
type mapping was for some other job.

Mime
View raw message