Fix: Make the JNI interface actually work
authorAlexandre Montplaisir <alexandre.montplaisir@polymtl.ca>
Thu, 5 Apr 2012 21:15:57 +0000 (17:15 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 5 Apr 2012 21:15:57 +0000 (17:15 -0400)
commita58ac6c80f99b1197a0133e0423e72c032845643
tree4ac95b06a379eb3522f6ce8fac007a2b3b62cba4
parent9501d22f55b3a23f382f631c99b2325d1419b5da
Fix: Make the JNI interface actually work

Now a user can import LTTngUst.java (which is now in a proper
package) and then define tracepoints in his application with:

LTTngUst.tracepointString(name, args);

We could eventually ship it in a .jar when the JNI interface is
enabled. It's still very basic, only string payloads are
implemented, and there is no mechanism to enable/disable trace
points call sites at runtime (they are always enabled). The event under
which these events appear is "lttng_ust_java:string".

Signed-off-by: Alexandre Montplaisir <alexandre.montplaisir@polymtl.ca>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
liblttng-ust-java/.gitignore
liblttng-ust-java/LTTNG_UST.c [deleted file]
liblttng-ust-java/LTTNG_UST.java [deleted file]
liblttng-ust-java/LTTngUst.c [new file with mode: 0644]
liblttng-ust-java/LTTngUst.java [new file with mode: 0644]
liblttng-ust-java/Makefile.am
This page took 0.025556 seconds and 5 git commands to generate.