DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33331>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33331 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-25 21:18 ------- (In reply to comment #4) > Hi Matt > > I've just commit code and documentation which (I believe) should enable your > use > case (as i understand it) to be addressed. The ObjectToStringConverter > signatures now include the context and the context includes a property to get > the current options. You should be able to factor the conversion code into > custom object-to-string converters. If you find that any of your use cases > can't > be done in this fashion, please reopen this bug and include a test case or two > demonstrating what you need. > > Robert Implementation is much cleaner. Thanks. One thing that this doesn't appear to resolve for me (but will fit 99.99% of other users) is that I was trying to be able to specify the custom converter class in the .betwixt file as well as the actual "flavour". I didn't see a way to specify the objectstringconverter implementation in the bindingconfiguration via a .betwixt file. Maybe I'm missing something. In some special cases someone may actually want to have a different converter implementation for different properties (i.e. reuse some code already written) as well. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
