Hi Andreas thanks for your reply,
the XML is very little (ranging from 50 to 250 nodes with size less than
10Kb) that change it with a BufferedReader or even using a DOMSource (I
already parse XML elsewhere) not give me a real gain.
Maybe a 1 or 2 seconds but I'm not sure because could be depends
On Dec 3, 2007, at 13:12, Noya Paolo wrote:
Hi Andreas thanks for your reply,
the XML is very little (ranging from 50 to 250 nodes with size less
than
10Kb) that change it with a BufferedReader or even using a
DOMSource (I
already parse XML elsewhere) not give me a real gain.
Maybe a 1 or
On Nov 28, 2007, at 16:46, Noya Paolo wrote:
Hi
Sorry for the late reply.
As Jeremias already indicated, profiling is one option. There are
various tools and there is lots of documentation available on the
internet concerning profiling of the JVM. Just Google around for
'java profiling'
Jeremias thanks for your reply,
can you explain me what do you mean for profile the JVM and how i can
archieve the goal?
sorry for my annoyance
Thanks
No idea where that could come from. I think the only thing you can do
is
profile the JVM and find out where exactly the time is lost. When
No idea where that could come from. I think the only thing you can do is
profile the JVM and find out where exactly the time is lost. When you
say transformer.transform() takes more than 30 seconds it can still be
one of thousand things. Profiling is the only option really.
Jeremias Maerki
On
I'm using FOP 0.94 with JDK 1.4 for producing a simple 1 page PDF
transforming a simple XML on a Mandrake Linux release 9.2 for i586.
If I try with command line the result is about in 3 or 4 second.
Next I write a Servlet on JRun 4.0:
public void init() throws ServletException {
uriResolver
