-
No, not currently.
Please don't use javax.script if you don't have to, it's poorly thought-out. To get it to work Jep has to be run in interactive mode, which is meant for console interfaces. It'll be slow.
2009-08-26 18:33:41 UTC by mrjohnson0
-
Does Jep support JSR-233 Invocable? I am particularly interested in the getInterface method. But I am unable to cast the engine to it.
Thanks.
2009-08-26 18:24:36 UTC by fphsml
-
I realize that I am stretching things, but I also have a bit of the ability to help out resolving the issues. I tired building on my F11 x86_64 System and had a couple of issues up front with .configure. The first was that the script looks in /us/lib/python(version)/config...but on F11 that file is in /usr/lib64/pythong2.6/config. That I solved with a symlink.from expected to actual...
2009-07-17 20:50:54 UTC by admiyo
-
Sorry, I didn't read that close enough. Seems you might have an older version in /usr/local/lib ? The error message "wrong architecture" is pretty strange.
2009-07-14 19:28:00 UTC by mrjohnson0
-
Make sure you check out the README in the source distribution. It has a step it sounds like you missed.
Basically, you need to copy the compiled .so to /Library/Java/Extensions/libjep.jnilib.
2009-07-14 15:58:24 UTC by mrjohnson0
-
Hello,
I'm trying to install Jepp on MacOS X 10.5.7 with Python 2.5.2. My install process has gone, so far:
download and untar jepp to ~/Develop/jep-2.3
./configure
make
sudo make install
export LD_PRELOAD=/usr/lib/libpython2.5.dylib
export LD_LIBRARY_PATH=/usr/local/lib
sudo ln -s /usr/local/lib/libjep.dylib /Library/Java/Extensions/libjep.jnilib
-- so far everything seems pretty...
2009-07-14 15:16:10 UTC by mikedewar
-
Ach, you're on Windows. Looks like I might have missed that in 2006(?).
Anyway, you're going to need to compile Jep with the same compiler that was used for both Python and Java... MSVC is about your only choice. Sorry... You need to have the same C runtime for all three.
2009-06-25 17:55:25 UTC by mrjohnson0
-
I am still having problems with this... I ran the build and everything compiled. This is what was created:
invocationhandler.o
libjep-2.dll
libjep.la
pyjarray.o
pyjmethod.o
jep.o
libjep.a
libjep.lai
pyjclass.o
pyjobject.o
jep_object.o
libjep.dll.a
pyembed.o
pyjfield.o
util.o
I copied the libjep-2.dll into the directory it is supposed to be and renamed it to jep.dll...
2009-06-25 16:53:06 UTC by mvschenkelberg
-
Ach, you're right. Sorry about that.
The Jep class as method overloads for setting arrays, but the javax.scripting interface has only put(String, Object). It's setting an array as an object in Python, so that's why you're getting that error.
Eh... I suppose the JepScriptEngine class should be changed to do some reflection and set the right type.... Or just use the Jep class. :-)
2009-06-24 16:38:01 UTC by mrjohnson0
-
Thanks for the response. I'm going to not worry too much about the javax scripting interface at the moment unless it really gives me troubles.
I'm more concerned about getting data in and out of Python! If I try to do what you suggest, I get the following:
Caused by: jep.JepException: <type 'exceptions.TypeError'>: 'PyJobject' object is unsubscriptable
at jep.Jep.run(Native Method)
2009-06-24 16:27:09 UTC by mikedewar
