[
https://issues.apache.org/jira/browse/WSCOMMONS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved WSCOMMONS-304.
---------------------------------------
Resolution: Invalid
Axiom uses the Commons Logging framework, which is only a thin abstraction
layer. My guess is that in absence of log4j, another logging implementation was
found by Commons Logging (probably the JDK 1.4 logging implementation) and that
either that implementation takes more time to initialize or that it had a quite
verbose default log level, explaining the difference in execution time.
Please note that JIRA is a bug tracking system. General questions should be
addressed to the project's mailing list (commons-dev@ws.apache.org).
> parsing with AXIOM speeds up when using log4j.. why is that?
> ------------------------------------------------------------
>
> Key: WSCOMMONS-304
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-304
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Environment: Windows XP, Eclipse SDK, Java Standard Edition Runtime
> Environment
> Reporter: senad biser
>
> I've programmed a small AXIOM parser for testing...
> First I've had no logger configured and my parsing time for a 5.6MB Xml file
> was about 5.6 sec.
> Then I've extended my test program a bit and I've imported log4j and
> configured it very simple, but that was enough to speed up my parsing, which
> is now about 3.7 sec.
> I was wondering about that because I couldn't find anywhere anything that
> indicates that a logger is a must be for AXIOM parsing.
> In near future I'm attending to implement a web service which probably will
> be based on AXIOM and I would like to resolve this little issue before..
> Tnx in advance
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
