Ok, I admit I haven't been looking at the source code very long, but I've
been somewhat frustrated with some of the things I'm trying to accomplish
with FOP. For instance, the Driver class only has void methods, which does
nothing for its pluggability.
When I say API that conforms to..., I
Hi Sunitha,
That's what the XSLT part comes in: the Xalan classes
are available with fop so you can use these (together
with an XSLT style sheet) to convert XML to PDF.
Check http://xml.apache.org/fop/running.html to see
how to call fop with such a style sheet and let fop (or
rather Xalan)
Isn't logging going to be a standard part of JDK 1.4? I thought that was
going to be based on IBM's Log4J. Is Avalon's logging based on that? If
not, should the 'standard' be considered? IIRC JDK 1.4 logging includes
the ability to log to syslog (on unix) and whatever the logging
So do others agree that this would be the way to go.
I do.
I have one question that hopefully someone knows answer (or knows who to
ask).
Since FOP is can be run in a number of ways (command line, in servlet
(cocoon), embedded), how can the logging be setup so that the fop logger
will
On Thu, 02 Aug 2001 08:56:55 Jeremias Maerki wrote:
Isn't logging going to be a standard part of JDK 1.4? I thought that
was
going to be based on IBM's Log4J. Is Avalon's logging based on that? If
not, should the 'standard' be considered? IIRC JDK 1.4 logging includes
the ability
Hi, Runar
Alright, these are the kind of comments I was looking for. I don't
necessarily disagree with some of them, particularly as it relates to the
interface.
Sorry if I was a bit irritable in my last reply. I've spent literally months
wrestling with customer and technical support for a
Keiron Liddle wrote:
So between logkit and log4j I think logkit is the better option simply
because cocoon uses it. (that's the only thing that tips the balance, I'd
rather just choose than not go anywhere.)
I think it's possible to do in FOP what was done in Velocity. They have
a middleware
