Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (asf.osuosl.org: domain of larry.meadors@gmail.com
 designates 66.249.92.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=VAi/2QCprzqtb9th90E8OJ8DPUO+hldfl7xLTDe1+Uki4NegSnk2oHgyGYgigFldThYig8a0mkGEMNsa5/XqfizEjolpc0n7xzooWH/X8hmLKfBJvyyQl7LhoAlW9Yd4iIk1XE61/8qz00QMO2YCGKaVeKtn/2RkGrClSrQhIbE=
Message-ID: <a10a823c0606020756s2e343e25p50731b27023c612d@mail.gmail.com>
Date: Fri, 2 Jun 2006 08:56:24 -0600
From: "Larry Meadors" <lmeadors@apache.org>
Reply-To: lmeadors@apache.org
Sender: larry.meadors@gmail.com
To: user-java@ibatis.apache.org
Subject: Re: When returning mutiple objects and transforming "directly to xml
In-Reply-To: <48CC2EED5175B540BCE9633A5D94F144057367D0@mail4.pennmutual.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48CC2EED5175B540BCE9633A5D94F144057367D0@mail4.pennmutual.com>

I can help you build a row handler to do the transformation if you
need some help (though I suspect you won't), just contact me off-list,
and we can work on it - shouldn't take more than a few minutes to
"rough it in", then you can refine it.

Larry


On 6/2/06, Morone, Bill <Morone.Bill@pennmutual.com> wrote:
>
>
> Gentlemen:
>
> I do thank you and believe you have a fine thing going. Like I said I
> created a very clean little design that basically uses the xml objects
> emitted by iBATIS and transforms them anyway you want (great for little
> docs). I'd like to see stuff move a little forward -- I'll help!!!
>
>
> Bill
>
>
>
>
> -----Original Message-----
> From: Clinton Begin [mailto:clinton.begin@gmail.com]
> Sent: Friday, June 02, 2006 9:45 AM
> To: user-java@ibatis.apache.org
> Subject: Re: When returning mutiple objects and transforming "directly to
> xml
>
>
> Hi Bill,
>
> It will probably go away in version 3.0.  We'd never remove a feature from
> the current major version.  It will continue to be supported in 2.0.
>
> In it's place we'll likely either suggest or build-in second stage xml
> support, for turning classes, beans and maps into XML.  That will allow you
> to map them to domain objects AND convert them to XML.  Plus, there are
> already a number of XML libraries that support exactly that.  The current
> implementation creates too much complexity in the implementation, yet offers
> little additonal value over the formerly described approach.
>
> Don't worry though, we'll always help you upgrade.  Even if it doesn't exist
> in 3.0, we'll have a suggested upgrade path that shouldn't leave you
> floundering.
>
> Cheers,
> Clinton
>
>
>
>
> On 6/2/06, Morone, Bill <Morone.Bill@pennmutual.com> wrote:
> > 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: larry.meadors@gmail.com [mailto:larry.meadors@gmail.com]On Behalf
> > Of Larry Meadors
> > Sent: Thursday, June 01, 2006 4:45 PM
> > To: user-java@ibatis.apache.org
> > Subject: Re: When returning mutiple objects and transforming "directly
> > to xml
> >
> >
> > On 6/1/06, Morone, Bill <Morone.Bill@pennmutual.com> 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.
> >
> >
>
>
>  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.
>
>
>