Apologies to Bogus, I've had to sanitize the encoding of your name.
Roedy,
Thanks for writing. See below inline...
On Nov 30, 2:28 am, Roedy Green <see_webs...@mindprod.com.invalid>
wrote:
[...]
Obviously SOMETHING has to parse the source and convert it into
something executable. The usual thing to do that is javac or the
on-the-fly equivalents.
Exactly. And this is why I have posted the inquiry. There seem to be 2
choices, and I can't determine the differences between them. I see the
choices as:
1. An actual compile into a class, and create/copy that class into a
jar, then copying that jar file into the ./deploy dir (my prototype is
JBoss 4).
2. Have the user fill in BeanShell, and run that.
I am very concerned about the speed of BeanShell in comparison to
compiled classes. Unfortunately, I need performance centered around
creating objects based on the user code at a very high rate. If I need
to parse BeanShell every time an object is instantiated, then it will
probably be exponentially slower than a compiled class, no?
Perhaps what you mean is you don't want the user to be involved in any
way with the compilation process. It should happen transparently.
Exactly. I just want them to configure any business logic, save their
session/work, and it just works.
I just don't know anything about the performance risks associated with
BeanShell, or whether there is another, oblique option I am not even
aware of.
Thanks again for writing!
remote end, and automatically handle the deployments there.
source text in there. Although in reality, if the client needs this
to use a full fledged compiler/ide/etc...