Bill, I would say that we are in the same boat. In our platform, we want to use AJAX in the web tier. Therefore xml representation is more straight forwards than other approaches. We want to build a generic object structure using xml. Thus we can get rid of some meaningless reflections in our platform.
We have tried Hibernate. Unfortunately, its performance is poor in processing large result. IBatis is much faster. In the current situation, I recommend you to use HashMap result instead of xml, which is also a generic structure. Then convert the Map to xml in your own code. Although this approach will delay your program a little bit, it is acceptable. Actually, I'm now trying to modify the source of IBatis to enable a better xml support. However, it seems the IBatis team has planned to get rid of xml support from 3.0's core. If so, using HashMap result may be a better decision in the current status. It can be also efficient and generic, with only a little cost. Anyway, we insist that xml support is very important, even more important than beans, for it is a more generic and flexible representation. No matter how 3.0 is implemented, a powerful and efficient support of xml result mapping is a very competitive feature. -- View this message in context: http://www.nabble.com/When-returning-mutiple-objects-and-transforming-%22directly-to-xml-t1718587.html#a4709836 Sent from the iBATIS - User - Java forum at Nabble.com.
