Easier said than done unless you know how to replace oracles JDK.
I've found when the problem is arising from. In the FormulaParser's parse
method. It does a synchronize on tokens. I commented this out and it all
worked real nice. I put a synchronized in the method and it worked nice. I
On Sat, 2002-07-06 at 10:05, Adam wrote:
Just a question from the lurker pool, but why are you stuck using JServ?
The whole point of using 9iAS is the OC4J container, which is a licensed
version of the Orion server. JServ hasn't been updated in years.
Just for clarification (from my
Well here is the problem:
http://java.sun.com/products/jdk/1.2/docs/api/java/lang/IllegalMonitorStateException.html
public class IllegalMonitorStateException
extends RuntimeException
Thrown to indicate that a thread has attempted to wait on an object's
monitor or to notify other threads
Yes. I sometimes question their judgment on that. The current release
(which is out for everything but windows) is based off of tomcat so.
Shawn Laubach
SAIC - Web Developer
B-1B System Support Management Division
OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma
dsn: 336-2473 comm:
Hi Shawn,
I just removed the thread safety stuff from the head. Give it a whirl.
We need a better solution for formula workbook context, but this should
at least make us nice and able to run in single threaded contexts for
the moment.
Thanks,
Andy
On Sat, 2002-07-06 at 11:08, Laubach, Shawn
Hi, All.
I am a newer of this project, living in Japan.
Wandering the Jakarta Project Web Site, I've luckily
found this project. I am using XLS file format a lot
because my clients want to.
I wondered how to contribute to this project, and I
noticed that the translation is the best way for
On Sat, 2002-07-06 at 17:07, Tetsuya Kitahata wrote:
Hi, All.
I am a newer of this project, living in Japan.
Wandering the Jakarta Project Web Site, I've luckily
found this project. I am using XLS file format a lot
because my clients want to.
Excellent. If you get the opportunity
Hi, Andrew,
I am very glad to your prompt reply.
UTF-8 or 16 is the general standard. Due to the nature of this project,
we should assume that the user may be using non-windows environments as
well. (I hail from a Linux box)
In xdocs files (.xml files), the encoding is not UTF-8 but
On Sat, 2002-07-06 at 18:50, Tetsuya Kitahata wrote:
Hi, Andrew,
I am very glad to your prompt reply.
UTF-8 or 16 is the general standard. Due to the nature of this project,
we should assume that the user may be using non-windows environments as
well. (I hail from a Linux box)
