Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 15758 invoked from network); 23 Aug 2009 02:19:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Aug 2009 02:19:23 -0000 Received: (qmail 85425 invoked by uid 500); 23 Aug 2009 01:17:44 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 85382 invoked by uid 500); 23 Aug 2009 01:17:44 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 85373 invoked by uid 99); 23 Aug 2009 01:17:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Aug 2009 01:17:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anoopkumarv@gmail.com designates 209.85.218.208 as permitted sender) Received: from [209.85.218.208] (HELO mail-bw0-f208.google.com) (209.85.218.208) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Aug 2009 01:17:34 +0000 Received: by bwz4 with SMTP id 4so1208874bwz.0 for ; Sat, 22 Aug 2009 18:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=L+IAOsYcqH7CE/vFQx7JZ34UjIbPvxe4vKgs8zGBvLM=; b=EWhjNKPfAQxtxQeZxCC0CZeBBaj+NwYpfyvGho/o7OhvVFozTBliR9Pnr0b2lRPDVM itjcntJTK2pcIxWOOgu+6MAKSogxCpvNmjfS5BUyZNQiG6liwUt4HH4ahLVbymCofbWo 0w2GAiFk9Nxcqyxf1JgHuK3WMszSJ/ouEXKz0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Tq5sDaNXiYHBrIw2vu2hFffLffTkm3f+PO8Tb3sBMVQvYL9t1aNL2NsiyAHdIH3Wlf vI0IkJqBTTy4I17FnruMvFYBms4t9/HbC9tjxAxvVs0sDzeFemHHXRyfbw+EytwFm0J5 jA+8XxyY51FGUrAdhR8UecbQHMnI1gPcxQqSs= MIME-Version: 1.0 Received: by 10.103.202.3 with SMTP id e3mr570318muq.55.1250990233128; Sat, 22 Aug 2009 18:17:13 -0700 (PDT) In-Reply-To: References: <16178eb10908122052x6a72531ek90eed25c04467f40@mail.gmail.com> <16178eb10908122135v7920a987m36ef1e1293be26fb@mail.gmail.com> From: Anoop kumar V Date: Sat, 22 Aug 2009 21:16:53 -0400 Message-ID: Subject: Re: [IB3] Some questions To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=0022159f040e7691a00471c4dca4 X-Virus-Checked: Checked by ClamAV on apache.org --0022159f040e7691a00471c4dca4 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Please disregard my question. it is working now, not entirely sure what happened. But the link to the documentation would still be useful. Thanks, Anoop On Sat, Aug 22, 2009 at 8:53 PM, Anoop kumar V wrote= : > I tried searching a lot, can you please post a link to your blurb, I am > interested in reading more about the usage of {} to pass strings. > > Or you could also answer this question... > > If I am passing a map as a parameter that contains a string as one of the > values to a select query in the sqlmap, can I use #stringvalue# or > #stringvalue:VARCHAR#and assume the quotes will be taken care of. It work= s > automatically when I add an Integer using #value#. > > I am thinking I need to pass the string as {stringvalue} or > '{stringvalue}'... still trying to search for the documentation, I know I= am > looking in the wrong place! > > Thanks, > Anoop > > > > On Thu, Aug 13, 2009 at 12:35 AM, Clinton Begin = wrote: > >> Yep, horrible typos... darn copy and paste! That's what I get for writi= ng >> 80 pages of documentation after the hours of 11pm. :-) >> >> I've updated all of the inappropriate usages of ${} and redeployed the >> documentation. I also added a quick blurb on proper usage of ${}... >> >> Clinton >> >> >> On Wed, Aug 12, 2009 at 9:52 PM, Clinton Begin = wrote: >> >>> Probably a typo. You can place any typos in the Wiki in the >>> documentation contributions. >>> >>> >>> On Wed, Aug 12, 2009 at 9:42 PM, Zoran Avtarovski < >>> zoran@sparecreative.com> wrote: >>> >>>> Thanks Jeff, >>>> >>>> I asked about the string substitution because the docs use the ${...} >>>> notation for primitives or simple data types. Is the user guide incorr= ect >>>> then? >>>> >>>> Z. >>>> >>>> >>>> Some answers... >>>> >>>> String substitution is still there. Use this: ${...} >>>> >>>> The expression language is OGNL - OGNL is included basically as is in >>>> iBATIS3. iBATIS will make all bean properties available in the OGNL >>>> context, and also the parameter object itself (as "_parameter"). So >>>> you can do or >>> null">. >>>> >>>> Jeff Butler >>>> >>>> >>>> >>>> On Wed, Aug 12, 2009 at 7:22 PM, Zoran >>>> Avtarovski wrote: >>>> > First off, fantastic effort guys. This looks like a unbelievable >>>> release. >>>> > The improvements over the previous version are just incredible. I=92= m >>>> > especially a fan of the new collection tag. >>>> > >>>> > I=92ve been reading over the user guide and I have a couple of quest= ions >>>> : >>>> > >>>> > In V2 and prior $value$ resulted in a string substitution while >>>> #value# used >>>> > prepared statements and safe escaping. Is there still a string >>>> substitution >>>> > option? I know it=92s not recommended, but we do have cases where we >>>> need it. >>>> > >>>> > With regards to he expression language support in the dynamic sql >>>> tags, is >>>> > OGNL being used to evaluate the test fields or a variation of EL? Th= e >>>> reason >>>> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn=92t.= So >>>> =93value >>>> > !=3D null=94 isn=92t the same as =93NOT EMPTY value=94. Also the str= ucture of >>>> the >>>> > conditional tags follows the JSTL convention of choose, when, >>>> otherwise and >>>> > not the more contemporary if, elseif, else. I guess the point I=92m >>>> trying to >>>> > make is that in a world where using multiple frameworks (struts, jsf= , >>>> etc) >>>> > is the norm, it might be a good idea that some of the conventions us= ed >>>> in >>>> > IB3 follow what=92s been done in more established projects. For exam= ple >>>> if >>>> > OGNL is used than I=92d prefer to use if, elseif, else as that=92s w= here >>>> my mind >>>> > is and if I=92m using EL then I go to the choose, when, otherwise. I= t >>>> may be >>>> > just me, and I=92m happy to concede that, but I find these little th= ings >>>> > really make a difference. >>>> > >>>> > Finally a question about Spring integration. One of the great sellin= g >>>> points >>>> > for iBatis has always been its tight spring integration. Is there an= y >>>> work >>>> > going on at their end to integrate IB3 or is this something that we, >>>> the >>>> > iBatis community, should be stepping up for? >>>> > >>>> > Again, a great release and I can=92t wait to try it. >>>> > >>>> > Z. >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org >>>> For additional commands, e-mail: user-java-help@ibatis.apache.org >>>> >>>> >>> >> > --0022159f040e7691a00471c4dca4 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Please disregard my question. it is working now, not entirely sure what hap= pened. But the link to the documentation would still be useful.

Thanks,
Anoop


On Sat, Aug 22, 2009 at 8:53 PM, Anoop k= umar V <anoop= kumarv@gmail.com> wrote:
I tried searching a lot, can you please post a link to your blurb, I am int= erested in reading more about the usage of {} to pass strings.

Or yo= u could also answer this question...

If I am passing a map as a para= meter that contains a string as one of the values to a select query in the = sqlmap, can I use #stringvalue# or #stringvalue:VARCHAR#and assume the quot= es will be taken care of. It works automatically when I add an Integer usin= g #value#.

I am thinking I need to pass the string as {stringvalue} or '{strin= gvalue}'... still trying to search for the documentation, I know I am l= ooking in the wrong place!

Thanks,
Anoop



On Thu, Aug 13, 2009 at 12:35 AM, Clinto= n Begin <clinton.begin@gmail.com> wrote:
Yep, horrible typos... darn copy and paste!=A0 That's what I get for wr= iting 80 pages of documentation after the hours of 11pm.=A0=A0 :-)

I= 've updated all of the inappropriate usages of ${} and redeployed the d= ocumentation.=A0 I also added a quick blurb on proper usage of ${}...

Clinton


O= n Wed, Aug 12, 2009 at 9:52 PM, Clinton Begin <clinton.begin@gmail.c= om> wrote:
Probably a typo.=A0 You can place any typos in the Wiki in the documentatio= n contributions.


On = Wed, Aug 12, 2009 at 9:42 PM, Zoran Avtarovski <zoran@sparecreative.= com> wrote:

Z.

Some answers...

String substitution is still there. =A0Use this: ${...}

The expression language is OGNL - OGNL is included basically as is in
iBATIS3. =A0iBATIS will make all bean properties available in the OGNL
context, and also the parameter object itself (as "_parameter"). = =A0So
you can do <if test=3D"foo !=3D null"> =A0or <if test=3D= "_parameter.foo" !=3D
null">.

Jeff Butler



On Wed, Aug 12, 2009 at 7:22 PM, Zoran
Avtarovski<= zoran@sparecreative.com> wrote:
> First off, fantastic effort guys. This looks like a unbelievable relea= se.
> The improvements over the previous version are just incredible. I=92m<= br> > especially a fan of the new collection tag.
>
> I=92ve been reading over the user guide and I have a couple of questio= ns :
>
> In V2 and prior $value$ resulted in a string substitution while #value= # used
> prepared statements and safe escaping. Is there still a string substit= ution
> option? I know it=92s not recommended, but we do have cases where we n= eed it.
>
> With regards to he expression language support in the dynamic sql tags= , is
> OGNL being used to evaluate the test fields or a variation of EL? The = reason
> I ask is that EL supports tests like NOT EMPTY while OGNL doesn=92t. S= o =93value
> !=3D null=94 isn=92t the same as =93NOT EMPTY value=94. Also the struc= ture of the
> conditional tags follows the JSTL convention of choose, when, otherwis= e and
> not the more contemporary if, elseif, else. I guess the point I=92m tr= ying to
> make is that in a world where using multiple frameworks (struts, jsf, = etc)
> is the norm, it might be a good idea that some of the conventions used= in
> IB3 follow what=92s been done in more established projects. For exampl= e if
> OGNL is used than I=92d prefer to use if, elseif, else as that=92s whe= re my mind
> is and if I=92m using EL then I go to the choose, when, otherwise. It = may be
> just me, and I=92m happy to concede that, but I find these little thin= gs
> really make a difference.
>
> Finally a question about Spring integration. One of the great selling = points
> for iBatis has always been its tight spring integration. Is there any = work
> going on at their end to integrate IB3 or is this something that we, t= he
> iBatis community, should be stepping up for?
>
> Again, a great release and I can=92t wait to try it.
>
> Z.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org





--0022159f040e7691a00471c4dca4--