Berin,
I'm just saying....
Honestly, I am interested in the Avalon DB project. I just haven't the
time to learn about it right now. I need to land a nice cushy R&D job
where I can spend 40 hours a week working on Avalon and Company ;)
Well I am unemployed, so my wish would be the same.
What we wanted to do was compile 'SELECT * FROM WHERE ( ( ( X = 1 AND B =2 ) OR ( C LIKE "Fred%") ) AND D <> "Green" )' into.....
class Select1234 extends BaseSelect {
boolean rowMatches(Row row) {
(
(
(
row.getValue("X") == 1
&
row.getValue("B") == 2
)
OR
(
row.getValue("C").startsWith("Fred")
)
)
& !row.getValue("D").equals("Green")
}
}
}on the server side. And for all selects not just prepared statements. It would be an assembly choice (to use that parser).
I don't know if it is replaced by another class/entry point, I just know
that when I use JDK 1.4 I get a deprecation warnings when compiling the
classes.
I guess the Jasper team will work it out.
main(..) is the anti-pattern for IoC. Roll on an Apache beanlike compiler. Maybe son of BCEL.
Invoking compilers dynamically has always been a bit of a hack, because
there is no direct interface to the compiler class--you have to go through
the command line. Any time you rely on com.sun.* you run the risk of seeing
the classes change due to restructuring. There is no contract beyond what
they expose to you (i.e. the command line).
I have a feeling that direct use of com.sun classes is outside the agreement we have with Sun when we use Java. Just like use of -xbootclasspath.
Also, the Jikes compiler works quite well....
Not written in Java :-(
Regards,
- Paul H
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
