The type converter is registered with Ognl when the ValueStack is created. I just created an issue to add the type converter to the ObjectFactory.
I'm not sure how much sense it makes, though... You can already register your own default type converter with the XWorkConverter, and the XWorkConverter reads the .properties files to see what other converters it should use. Where / which of these do you envision loading from an IoC container?
Can you describe more of what you're trying to do?
My primary concern is how the XWorkConverter figures out which *-conversion.properties file to use. If I have a Shape interface and a Square and Triangle subclass, I'd like the TypeConverter to be smart enough to look for Shape-conversion.properties if it can't find Square-conversion.properties.
Fred Lamuette mentioned that this can be configured via xwork-conversion.properties, but I'd rather not have to worry about an extra config file.
-Mark
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
