Andreas Veithen wrote:
Questions are: * While TextMessageBuilder and TextMessageFormatter should clearly remain optional (i.e. they would only be implemented by builders and formatters that deal with text content), MessageFormatterEx could also be merged into MessageFormatter. The additional getDataSource method can easily be implemented (message formatters are already required to return byte[], so returning a DataSource is not difficult). However this would break existing MessageFormatter implementations outside of Axis2. What do you think?
+1 for merging getDataSource() into MessageFormatter.
* Is this in scope for Axis2 1.5?
No because Axis2 1.5 is already in progress. This is a breaking change and hence should not be rushed.
Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
