Jay and Jay,
IF you really want to help othersIf you see a bug, log a bug
report. If you can, please submit a patch too then it will get fixed
faster. FYI, we are very close to 1.2 Final, so any help in fixing
issues like these is appreciated.
thanks,
dims
On Sat, 1 Jan 2005 13:14:07 -0500,
Found the
answer.
Windows control panel contains a
java plugin control panel application. On the advanced tab there is a "Java
Runtime Parameter" edit window, which allows one to use any of the standard java
command line arguments, like -cp (classpath) for example.
The jre
]
Subject: RE: Axis and Applets -
Missing Feature (bug) Report
Try www.wingfoot.com for
a more lightweight Java SOAP client.
-Original Message-
From: Rui Craveiro
[mailto:[EMAIL PROTECTED]
Sent: 10 August 2004 04:43
To: [EMAIL PROTECTED]
Subject: Axis and Applets -
Missing
Try www.wingfoot.com for a more lightweight
Java SOAP client.
-Original Message-From: Rui Craveiro
[mailto:[EMAIL PROTECTED]Sent: 10 August 2004
04:43To: [EMAIL PROTECTED]Subject: Axis and
Applets - Missing Feature (bug) Report
Hello,
I am starting a new project
I have some more information, in case any one has some time to point me
in the right direction. For starters I'm always using a single signed
applet. I uncompiled all the jar files and put them into a single jar
With plugin 1.4.2_02 and downloading my applet by http the applet works
without a p
One clarification: I had it working with java plugin 1.4.2_02, but I
upgraded to 1.4.2_03 because of the Versign certificate issue. Also
note that I extracted all of the jar files, and created a single jar.
lou fox wrote:
I know there has been alot of messages on applets and axis but I
haven'
Sent: Tuesday, July 23, 2002 2:32 AM
Subject: RE: Axis and applets
> Hi Michael
>
> I ran into similar problems and tracked it down to the fact that
> commons logging
> was trying to read environment variables to determine which logging
> implementation to
> use, this causes a se
Hi Michael
I ran into similar problems and tracked it down to the fact that
commons logging
was trying to read environment variables to determine which logging
implementation to
use, this causes a security exception in an unsigned applet. We
experimented with
rebuilding commons logging
