[IB3] Some questions

[Zoran Avtarovski <zo...@sparecreative.com>]

First off, fantastic effort guys. This looks like a unbelievable release.
The improvements over the previous version are just incredible. I¹m
especially a fan of the new collection tag.

I¹ve been reading over the user guide and I have a couple of questions :

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¹s 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? The reason
I ask is that EL supports tests like NOT EMPTY while OGNL doesn¹t. So ³value
!= null² isn¹t the same as ³NOT EMPTY value². Also the structure 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¹m 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 used in
IB3 follow what¹s been done in more established projects. For example if
OGNL is used than I¹d prefer to use if, elseif, else as that¹s where my mind
is and if I¹m using EL then I go to the choose, when, otherwise. It may be
just me, and I¹m happy to concede that, but I find these little things
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, the
iBatis community, should be stepping up for?

Again, a great release and I can¹t wait to try it.

Z.

Re: [IB3] Some questions

[Anoop kumar V <an...@gmail.com>]

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 <an...@gmail.com>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 works
> 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 <cl...@gmail.com>wrote:
>
>> Yep, horrible typos... darn copy and paste!  That's what I get for writing
>> 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 <cl...@gmail.com>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 incorrect
>>>> 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 <if test="foo != null">  or <if test="_parameter.foo" !=
>>>> null">.
>>>>
>>>> Jeff Butler
>>>>
>>>>
>>>>
>>>> On Wed, Aug 12, 2009 at 7:22 PM, Zoran
>>>> Avtarovski<zo...@sparecreative.com> wrote:
>>>> > First off, fantastic effort guys. This looks like a unbelievable
>>>> release.
>>>> > The improvements over the previous version are just incredible. I’m
>>>> > especially a fan of the new collection tag.
>>>> >
>>>> > I’ve been reading over the user guide and I have a couple of questions
>>>> :
>>>> >
>>>> > 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’s 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? The
>>>> reason
>>>> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn’t. So
>>>> “value
>>>> > != null” isn’t the same as “NOT EMPTY value”. Also the structure 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’m
>>>> 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 used
>>>> in
>>>> > IB3 follow what’s been done in more established projects. For example
>>>> if
>>>> > OGNL is used than I’d prefer to use if, elseif, else as that’s where
>>>> my mind
>>>> > is and if I’m using EL then I go to the choose, when, otherwise. It
>>>> may be
>>>> > just me, and I’m happy to concede that, but I find these little things
>>>> > 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,
>>>> the
>>>> > iBatis community, should be stepping up for?
>>>> >
>>>> > Again, a great release and I can’t 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
>>>>
>>>>
>>>
>>
>

Re: [IB3] Some questions

[Anoop kumar V <an...@gmail.com>]

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 works
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 <cl...@gmail.com>wrote:

> Yep, horrible typos... darn copy and paste!  That's what I get for writing
> 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 <cl...@gmail.com>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 incorrect
>>> 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 <if test="foo != null">  or <if test="_parameter.foo" !=
>>> null">.
>>>
>>> Jeff Butler
>>>
>>>
>>>
>>> On Wed, Aug 12, 2009 at 7:22 PM, Zoran
>>> Avtarovski<zo...@sparecreative.com> wrote:
>>> > First off, fantastic effort guys. This looks like a unbelievable
>>> release.
>>> > The improvements over the previous version are just incredible. I’m
>>> > especially a fan of the new collection tag.
>>> >
>>> > I’ve been reading over the user guide and I have a couple of questions
>>> :
>>> >
>>> > 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’s 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? The
>>> reason
>>> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn’t. So
>>> “value
>>> > != null” isn’t the same as “NOT EMPTY value”. Also the structure 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’m
>>> 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 used
>>> in
>>> > IB3 follow what’s been done in more established projects. For example
>>> if
>>> > OGNL is used than I’d prefer to use if, elseif, else as that’s where my
>>> mind
>>> > is and if I’m using EL then I go to the choose, when, otherwise. It may
>>> be
>>> > just me, and I’m happy to concede that, but I find these little things
>>> > 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,
>>> the
>>> > iBatis community, should be stepping up for?
>>> >
>>> > Again, a great release and I can’t 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
>>>
>>>
>>
>

Re: [IB3] Some questions

[Clinton Begin <cl...@gmail.com>]

Yep, horrible typos... darn copy and paste!  That's what I get for writing
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 <cl...@gmail.com>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 incorrect
>> 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 <if test="foo != null">  or <if test="_parameter.foo" !=
>> null">.
>>
>> Jeff Butler
>>
>>
>>
>> On Wed, Aug 12, 2009 at 7:22 PM, Zoran
>> Avtarovski<zo...@sparecreative.com> wrote:
>> > First off, fantastic effort guys. This looks like a unbelievable
>> release.
>> > The improvements over the previous version are just incredible. I’m
>> > especially a fan of the new collection tag.
>> >
>> > I’ve been reading over the user guide and I have a couple of questions :
>> >
>> > 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’s 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? The
>> reason
>> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn’t. So
>> “value
>> > != null” isn’t the same as “NOT EMPTY value”. Also the structure 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’m 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 used
>> in
>> > IB3 follow what’s been done in more established projects. For example if
>> > OGNL is used than I’d prefer to use if, elseif, else as that’s where my
>> mind
>> > is and if I’m using EL then I go to the choose, when, otherwise. It may
>> be
>> > just me, and I’m happy to concede that, but I find these little things
>> > 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, the
>> > iBatis community, should be stepping up for?
>> >
>> > Again, a great release and I can’t 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
>>
>>
>

Re: [IB3] Some questions

[Clinton Begin <cl...@gmail.com>]

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
<zo...@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 incorrect
> 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 <if test="foo != null">  or <if test="_parameter.foo" !=
> null">.
>
> Jeff Butler
>
>
>
> On Wed, Aug 12, 2009 at 7:22 PM, Zoran
> Avtarovski<zo...@sparecreative.com> wrote:
> > First off, fantastic effort guys. This looks like a unbelievable release.
> > The improvements over the previous version are just incredible. I’m
> > especially a fan of the new collection tag.
> >
> > I’ve been reading over the user guide and I have a couple of questions :
> >
> > 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’s 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? The
> reason
> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn’t. So
> “value
> > != null” isn’t the same as “NOT EMPTY value”. Also the structure 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’m 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 used in
> > IB3 follow what’s been done in more established projects. For example if
> > OGNL is used than I’d prefer to use if, elseif, else as that’s where my
> mind
> > is and if I’m using EL then I go to the choose, when, otherwise. It may
> be
> > just me, and I’m happy to concede that, but I find these little things
> > 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, the
> > iBatis community, should be stepping up for?
> >
> > Again, a great release and I can’t 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
>
>

Re: [IB3] Some questions

[Zoran Avtarovski <zo...@sparecreative.com>]

Thanks Jeff,

I asked about the string substitution because the docs use the ${...}
notation for primitives or simple data types. Is the user guide incorrect
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 <if test="foo != null">  or <if test="_parameter.foo" !=
> null">.
> 
> Jeff Butler
> 
> 
> 
> On Wed, Aug 12, 2009 at 7:22 PM, Zoran
> Avtarovski<zo...@sparecreative.com> wrote:
>> > First off, fantastic effort guys. This looks like a unbelievable release.
>> > The improvements over the previous version are just incredible. I¹m
>> > especially a fan of the new collection tag.
>> >
>> > I¹ve been reading over the user guide and I have a couple of questions :
>> >
>> > 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¹s 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? The
>> reason
>> > I ask is that EL supports tests like NOT EMPTY while OGNL doesn¹t. So
>> ³value
>> > != null² isn¹t the same as ³NOT EMPTY value². Also the structure 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¹m 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 used in
>> > IB3 follow what¹s been done in more established projects. For example if
>> > OGNL is used than I¹d prefer to use if, elseif, else as that¹s where my
>> mind
>> > is and if I¹m using EL then I go to the choose, when, otherwise. It may be
>> > just me, and I¹m happy to concede that, but I find these little things
>> > 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, the
>> > iBatis community, should be stepping up for?
>> >
>> > Again, a great release and I can¹t 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
> 

Re: [IB3] Some questions

[Jeff Butler <je...@gmail.com>]

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 <if test="foo != null">  or <if test="_parameter.foo" !=
null">.

Jeff Butler



On Wed, Aug 12, 2009 at 7:22 PM, Zoran
Avtarovski<zo...@sparecreative.com> wrote:
> First off, fantastic effort guys. This looks like a unbelievable release.
> The improvements over the previous version are just incredible. I’m
> especially a fan of the new collection tag.
>
> I’ve been reading over the user guide and I have a couple of questions :
>
> 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’s 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? The reason
> I ask is that EL supports tests like NOT EMPTY while OGNL doesn’t. So “value
> != null” isn’t the same as “NOT EMPTY value”. Also the structure 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’m 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 used in
> IB3 follow what’s been done in more established projects. For example if
> OGNL is used than I’d prefer to use if, elseif, else as that’s where my mind
> is and if I’m using EL then I go to the choose, when, otherwise. It may be
> just me, and I’m happy to concede that, but I find these little things
> 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, the
> iBatis community, should be stepping up for?
>
> Again, a great release and I can’t 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