ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Goodin" <brandon.goo...@gmail.com>
Subject Re: stored proc call with list items in parameter
Date Thu, 17 Apr 2008 01:27:06 GMT
There are several reason we don't use OGNL, none of which have anything to
do with the quality of OGNL as a specification. I would say the primary
reason we don't use OGNL is because it just wasn't that well known when we
started iBATIS. As time marched on it was easier to continue to support the
manner in which we parse properties and values. The parsing is very integral
to the iBATIS code base. So, hooking in OGNL would not be a simple task.
Additionally, the iBATIS project has a zero dependency policy. This means
that we would not want iBATIS to depend on an additional jar in order to
accomplish what it is designed to do. This is because our belief is that
iBATIS isn't complex enough to "require" any external jars.
That being said we are certainly not against designing towards flexibility
if it makes sense. In the case you have outlined it certainly points towards
a need and the OGNL specification has some great features. As we work on
iBATIS 3 perhaps we can incorporate the OGNL specification into how we
access properties. I completely agree with you that the current
implementation could stand to be more powerful. I did notice a couple issue
in JIRA for this issue. Perhaps you can vote on those or make a whole new
JIRA issue that is more specific about desiring the use of the OGNL
specification in iBATIS 3.

On Wed, Apr 16, 2008 at 2:20 PM, Darren Davison <darren@davisononline.org>

> On Tue, Apr 15, 2008 at 08:48:36AM -0500, Brandon Goodin wrote:
> >    We've looked into this in the past and for whatever reason haven't
> added
> >    this feature. I think there were some difficulties. There is
> currently not
> >    a way to refer to a particular index of a list in a parameter using
> >    notation. You could flatten your parameters into a Map  and then pass
> the
> >    map in as a parameter object. Please let me know if this is suitable
> for
> >    your situation. If not, please expound on why it will not work for
> you.
> hi Brandon, thanks for the reply.
> Using the domain instance "as-is" is obviously more convenient than
> putting them all in a map - especially when some of those objects are
> quite complex and the SP needs various bits from several related
> objects.
> We do have a workaround, but we just wondered whether we were missing
> something in the object access notation.
> Out of interest, what was the difficulty you encountered?  Are you using
> OGNL (or if not, did you try it)?
> Cheers!
> --
> Darren Davison
> Public Key: 0xE855B3EA
> Version: GnuPG v1.4.6 (GNU/Linux)
> iD8DBQFIBlFpVgOfSOhVs+oRAijqAKCq/CX4i60pmJ6t3JhGnW6ynyNxuACcD5fs
> HNsXCxfa40vqd5NuwwyH8/s=
> =xLbF

View raw message