Larry, Really? I think it bears great merit. I little expansion would make it really practical. In fact hearing of its departure has me a little worried.
Does this mean the resultClass="xml" is going away? I created a little (restlet front-end) framework that translates the xml output for web services. I extended ArrayList to deal with the "non-webformedness" of the queryForObject "list of little docs" situation and it works great. Our system is scheduled to go into production in October -- what are the future plans for the xml stuff -- I assume we'll have to subclass to extend. Will your superclass stuff stay the same? Bill Morone -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Larry Meadors Sent: Thursday, June 01, 2006 4:45 PM To: [email protected] Subject: Re: When returning mutiple objects and transforming "directly to xml On 6/1/06, Morone, Bill <[EMAIL PROTECTED]> wrote: > Coming soon, right? On the contrary, going away. I'd suggest processing the results of the query manually to create XML with a row handler if you really need to create xml results. Larry This message, including any attachments, is intended only for the recipient(s) named above. It may contain confidential and privileged information. If you have received this communication in error, please notify the sender immediately and destroy or delete the original message. Also, please be aware that if you are not the intended recipient, any review, disclosure, copying, distribution or any action or reliance based on this message is prohibited by law.
