What you're experiencing is really a limitation in iBATIS 2 dynamic
SQL. The legacy generator generated *a lot* of code and still was
pretty limited in function. The new generators generate better code
IMHO, and you really can create very flexible WHERE clauses. There are
still some inefficiencies
No - rootClasspath only applies to looking for any rootClass that
might be specified. Other objects (like DAO generators) are found
through the normal runtime classpath settings - like an Ant classpath
or a JVM classpath.
Jeff Butler
On 3/29/08, Ryan Shelley <[EMAIL PROTECTED]> wrote:
> Jeff, d
The Abator criteria methods are runtime methods. They allow you to
generate different where clauses at runtime based on different
"filters" that you might want to set. I think its worth taking a look
because it demonstrates the real power available with iBATIS dynamic
SQL.
Jeff Butler
On 2/7/0
I would guess that this is moderately complex. Besides the complexity
of the introspection, there could be difficult class path issues if
the base class is not in abator's class path. But this is the beauty
of open source...you can give it a try and see how well it works. You
would need to impl
Abator does not introspect the base classes to see if there is a match
or not. So no, abator will not do what you are asking for at present.
It is an interesting idea however.
Jeff Butler
On 5/9/07, Ashok Madhavan <[EMAIL PROTECTED]> wrote:
Hi all,
i want to have a common super class for som
