David Dankwerth wrote:
Hi
I am using xstoreable.storeToURL from the api and getting
com.sun.star.io.IOException
When i am using OpenOffice UI to store to the URL it works fine.
I have added all the details + log of Tomcat's Webdav servlet that shows
differences
in the Http Request
Hi Kohei,
Alle 14:55, gioved 16 giugno 2005, Kohei Yoshida ha scritto:
[...]
Hi Paolo,
You, or perhaps someone else, may be interested in this hack of mine:
http://kohei.us/ooo/nsort/
which introduces a native natural sort algorithm in Calc.
Great ! :-)
The work was completed (with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paolo Mantovani schrieb:
| Hi all,
|
| During a recent job I have had to develop some functions for string
sorting.
| Some of these contains a very simple implementation of the natural sort
| algorithm.
[...]
Integrated into snippet collection and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Lutz schrieb:
| dev@api.openoffice.org schrieb am 13.06.05 08:21:35:
|
|integrated into the snippet collection here:
|http://codesnippets.services.openoffice.org/Writer/Writer.SimpleWrapperForUno_services.snip
|but doesn't it more belong to
Hi Tom,
Alle 10:35, venerd 17 giugno 2005, Tom Schindl ha scritto:
[...]
Integrated into snippet collection and can be found here:
http://codesnippets.services.openoffice.org/Office/Office.SimpleNaturalSort
Algorithm.snip
Thank you :-)
Paolo M.
Hello,
we uses the Java API in order to modify text documents. We execute a lot of
calls with the API. After 1000 (sometimes more - sometimes less) calls
OpenOffice.org (1.9.104) will crash. How stable is the Java API ? Is it not a
good idea in order to execute such a high number of calls.
Did you experience this in a Version 1.1.x as well?
I got similar problems with the C++ API using 1.1.3/1.1.4: After executing a
lot of API calls OO crashes (tries to send an error-report). The code-line
where the crashe is happening is always different. I could improve the
behaviour a little
Hello Martin,
yes - with OpenOffice.org 1.1.4 we have the same problems.
Best Regards
Andreas
-Original Message-
From: Martin Thoma [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 3:28 PM
To: dev@api.openoffice.org
Subject: RE: [api-dev] How stable is the Java API ?
Did
Hi Andreas,
then I think the profis have to start ;-)
Could you provide a simple code which crashes after a lot of executions? I
weren't able to do so, but I could not spend much time on it in the past.
Perhaps, if we find a peace of code that crashes in Java and C++ after
executing a lot of
Sorry for the idiot question, but how can i call the garbage collection
via Java???
Best Regars
Cristian
Andreas Brker ha scritto:
Hello,
if we call the Garbage Collection after every API call OpenOffice.org stays longer alive. Is it possible that the API produces too much references ?
Hello Stephan,
we have made several tests. If we run the code without the the GC we come up to
1000 calls - with GC we come up to 15000 calls and more.
No - we have only one thread.
What can we do ?
Best regards
Andreas
-Original Message-
From: Stephan Bergmann [mailto:[EMAIL
Since Andreas pointed out that OOo lives LONGER,
when calling System.gc() after each call, I would
rather suspect that the frequent cleanup prevents
zombie objects to walk around in memory with deadly
foam dropping out of their mouth ... ;-)
(Garbage rulez!)
Maybe the explicit disposal of
Hello
Cristian,
use
System.gc().
Regards
Andreas
-Original Message-From: Cristian Fonti
[mailto:[EMAIL PROTECTED]Sent: Friday, June 17, 2005 4:01
PMTo: dev@api.openoffice.orgSubject: Re: [api-dev] How
stable is the Java API ?Sorry for the idiot question, but
how can
@Andreas:
we have made a simple test programm that uses the XCellRange interface of
an XTextTable in order to return a cell range in a loop. That is enough in
order to crash OpenOffice.org.
Could you send me the code? I'll try it in C++.
@Jrgen
Maybe the explicit disposal of objects as
Andreas Brker wrote:
Hello Martin,
we have made a simple test programm that uses the XCellRange interface of an
XTextTable in order to return a cell range in a loop. That is enough in order
to crash OpenOffice.org.
Please send me the code, or, preferably, open an issue and attach the
code
Hello Stephan,
my login does not work properly. Sorry. Here is my code snippet:
XCellRange xCellRange = null;
for(int i=0; i10; i++) {
if(xCellRange == null)
xCellRange = (XCellRange)UnoRuntime.queryInterface(XCellRange.class,
xTextTable);
XCellRange newXCellRange =
Hi Paolo (and all),
Paolo Mantovani wrote:
Finally, I thought to submit the thing as a code-snippet, in the hope it will
be useful to someone.
I tried your snippet, but I receive an error every time I start the
macros. :-(
In particular the problem is located in the function RegExpStrReplace
sounds like a memory leak...
Have you tried to give it a look using a profiler?
hth
Alexander
-Original Message-
From: Andreas Brker [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 3:04 PM
To: 'dev@api.openoffice.org'
Subject: [api-dev] How stable is the Java API ?
Hello,
we
A quick search of the archives suggests that nobody asked
before, that the class
com.sun.star.lang.WrappedTargetException
is not found when booting an implementation of
officebean.jar along the lines of the example applet. All
the jars in the sdk 1.9.109 were scanned and no such
classpath was
* Emanuele [EMAIL PROTECTED] [170605, 18:57]:
Hi Paolo (and all),
...
I tried your snippet, but I receive an error every time I start the
macros. :-(
In particular the problem is located in the function RegExpStrReplace
at the line:
.searchFlag = [EMAIL PROTECTED]
Dear OpenOffice.org community,
This is the monthly reminder of important things to know about the
dev@api.openoffice.org mailing list. We, the project leads of the
OOo API project, would like to give you some general information to
help you with your questions.
***
21 matches
Mail list logo
