That is an easy one. Run these commands to check out tcljava from the
cvs.
% setenv CVSROOT :pserver:[EMAIL PROTECTED]:/cvsroot
% cvs login (password is cvs)
% cvs checkout tcljava
This will create a tcljava directory with all the src code in it.
Copy your modified files into the tcljava/src/t
Sorry, I'm a little pressed for time at the moment and honestly don't know
if I still have the original to diff against.
The problem boiled down to a security exception. The class Class is in a
jar file that did not have the proper policy set. By using getClass(), the
result would be from the J
What was the problem you were running into? Would the applet fail to run
without the patch you suggest? Could you post a diff -u style patch
for the change you suggest?
Mo Dejong
Red Hat Inc.
On Mon, 17 Jan 2000, Thomas McKay wrote:
...
> + Changed Class.class.getResourceAsStream() in Interp.j
Actually, you can use Jacl in an applet; at least in Netscape. By using the
Java 2 plug-in there is a finer-grained security mechanism called
"policies." By setting the correct policies, an applet can get permission
to read files from jars (such as init.tcl) and examine classes (like using
java:
Mo DeJong wrote:
> On Thu, 6 Jan 2000, Lubos Vrba wrote:
>
> > Hello *,
>
> This is a tricky issue. Jacl (using Tcl commands in an applet)
> works but the java::* commands do not.
>
> > in jacl web pages I've read that Jacl 1.25 won't work in browsers.
>
> There is nothing wrong with Jacl that we
