[
https://issues.apache.org/jira/browse/CASSANDRA-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205958#comment-14205958
]
Dave Brosius commented on CASSANDRA-8241:
-----------------------------------------
TBH, not a big fan of either solution, each is nasty in its own right. I agree
with Robert, using Java Assist means you will always be in a state of catch up
language wise. But relying on eclipse means dragging an elephant of
configuration test matrix problems around with you forever.
I'm also not a big fan of building prototype java code up in StringBuilders.
Can we externalize the prototype into a first class file that get's
getResourceAsStream'ed in and modified thru markers of some sort?
> Use javac instead of javassist
> ------------------------------
>
> Key: CASSANDRA-8241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8241
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Labels: udf
> Fix For: 3.0
>
> Attachments: 8241-ecj.txt, udf-java-javac.txt
>
>
> Using JDK's built-in Java-Compiler API has some advantages over javassist.
> Although compilation feels a bit slower, Java compiler API has some
> advantages:
> * boxing + unboxing works
> * generics work
> * compiler error messages are better (or at least known) and have line/column
> numbers
> The implementation does not use any temp files. Everything's in memory.
> Patch attached to this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
