From: Nikolai Grigoriev (grig@renderx.com)
Date: Wed Feb 18 2004 - 12:01:01 PST
David,
XEP 3.7 introduces a completely new interface. The old one is maintained
for compatibility but is deprecated: we don't recommend using it for
new development anymore.
The principal change is the introduction of the explicit formatter instance.
Instead of calling a static Driver.init(), you now create a FormatterImpl
object, passing configuration parameters (in the form of a java.util.Properties
object) as arguments in the constructor. The render() method also resides
on the instance. So, in XEP 3.7, you can create several instances of the
formatter, each having its own settings.
To capture errors, you should now use com.renderx.xep.lib.Logger interface.
An instance of Logger can be supplied in the argument to either
a FormatterImpl constructor (in which case, it will receive notifications
about problems in the formatter setup), or render() method (to capture
messages pertaining to a single formatting session). To disable logging,
you can simply pass 'null' as a logger object. (There is a special constant, com.renderx.xep.lib.Logger.NULL_LOGGER, defined as
(com.renderx.xep.lib.Logger)null; the cleanest way is to use it).
You can find more details on this in doc/applications.pdf: note that
this document has been almost completely rewritten for 3.7. Please
also look at the samples: all of them have been changed to use
the new interfaces (and most of them became shorter than in 3.6 :-)).
Regards,
Nikolai Grigoriev
RenderX
----- Original Message -----
From: "Duncan, David" <David.Duncan@bskyb.com>
To: <xep-support@renderx.com>
Sent: Wednesday, February 18, 2004 6:18 PM
Subject: RE: [xep-support] xep performance
I notice that many methods have been deprecated since xep3.6 and 371. I
previously used
EventLogger.logger().setContentHandler(s_defaultHandler);
to set the content handler and to suppress logging. What is the alternative
now?
Many thanks,
David.
-----Original Message-----
From: owner-xep-support@renderx.com
[mailto:owner-xep-support@renderx.com]On Behalf Of Alexander Peshkov
Sent: Tuesday, February 17, 2004 10:00 AM
To: Duncan, David
Subject: Re: [xep-support] xep performance
Hello David,
I suppose you have upgraded from version 3.6. In this case it's unlikely
to observe any significant performance changes since in XEP 3.7 basic
algorithms weren't modified.
Best regards,
Alexander Peshkov mailto:peshkov@renderx.com
RenderX
DD> Hi,
DD> I am working on a transformation engine (coded in Java) which uses XEP
to
DD> render pdf's. With a multi-threaded process i can achieve around 10
DD> docs/second. I have recently upgraded to XEP3.7.1 but have not managed
to
DD> run a full volume test yet. Do you know if there is likely to be any
DD> performance impact with this upgrade? Also if there are any tips or
DD> suggestions that you are aware of that may improve the performance of
XEP
DD> engine i would be very interested. Im looking to generate around 80,000
DD> pdf's in around 2 hours....currently i can achieve this in around 3 -
3.5
DD> hours.
DD> I have VALIDATE option turned to false and logging is suppressed using
DD>
com.renderx.xep.lib.EventLogger.logger().setContentHandler(s_defaultHandler)
DD> ;
DD> I cant think of any other way of quickening things up....except for have
2
DD> publish jobs running and partioning the data out...but this should be a
last
DD> resort.
DD> Thanks,
DD> David.
DD> -----------------------------------------------------------------------
DD> Information in this email may be privileged, confidential and is
DD> intended exclusively for the addressee. The views expressed may
DD> not be official policy, but the personal views of the originator.
DD> If you have received it in error, please notify the sender by return
DD> e-mail and delete it from your system. You should not reproduce,
DD> distribute, store, retransmit, use or disclose its contents to anyone.
DD> Please note we reserve the right to monitor all e-mail
DD> communication through our internal and external networks.
DD> -----------------------------------------------------------------------
DD> -------------------
DD> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
DD> in the body of the message to majordomo@renderx.com from the address
DD> you are subscribed from.
DD> (*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
.
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Wed Feb 18 2004 - 13:14:28 PST