Loading ...
Sorry, an error occurred while loading the content.

RE: [XSL-FO] fop bug? sometimes only the body appears?

Expand Messages
  • Peter Wu
    Ken, I m glad you found a better way. Regards, peter ... === message truncated ===
    Message 1 of 7 , Dec 16, 2005
    • 0 Attachment
      Ken,

      I'm glad you found a better way.

      Regards,
      peter

      --- Ken Sands <kensands@...> wrote:

      > Thanks, for the moment I've simply changed my call
      > of fop to use the
      > postscript renerer and send the output straight to a
      > printer name. I had
      > a look at this and all I can find are examples of
      > how to use it via java
      > code and I can't see how i'd do it from foxpro.
      >
      > Thanks anyway.
      > Ken
      >
      >
      > -----Original Message-----
      > From: Peter Wu [mailto:peterlwu@...]
      > Sent: 15 December 2005 15:38
      > To: XSL-FO@yahoogroups.com
      > Subject: RE: [XSL-FO] fop bug? sometimes only the
      > body appears?
      >
      >
      > Greetings,
      >
      > Check out http://openjms.sourceforge.net/
      >
      > You can create a message queue and execute a message
      > sender to queue up your fop commands. OpenJMS will
      > grab the next message off the queue and execute fop
      > using the message receiver.
      >
      > They have built-in examples in the examples
      > subfolder
      > that you can set up and run in five to ten minutes.
      >
      > It's really very straight forward.
      >
      > Thanks,
      > peter
      >
      >
      > --- Ken Sands <kensands@...> wrote:
      >
      > > Too complicated? Well I'm all for a simple
      > solution.
      > >
      > > I run a system in Foxpro, this automatically
      > > processes client files as
      > > they are recieved.
      > >
      > > Once run, job report sheets need to be printed,
      > > and/or saved to pdf for
      > > view in a different part of the company.
      > > It also needs to print a second sheet with a copy
      > > stamp across the from
      > > to be filed away.
      > >
      > > So I output as xml the data from the job and I
      > have
      > > 2 standard xsl
      > > stylesheet which format that data to the report,
      > one
      > > simply has the
      > > addition of an overlaid graphic.
      > >
      > > From foxpro code i need to start fop, so i call it
      > > as is I'm starting an
      > > external program (there is no way to tell when it
      > > has finished like this
      > > but also it's a multiuser system and does not want
      > > to be waiting anyway)
      > >
      > > So from foxpro it does a "fop -xml
      > (saved_xml_file)
      > > -xsl
      > > my_standard_stylesheet.xsl -print"
      > > Followed by a "fop -xml (saved_xml_file) -xsl
      > > my_standard_stylesheet_copy.xsl -print"
      > > This could also have a third call for the same xml
      > > datafile if a pdf is
      > > required.
      > >
      > > The whole thing is automated and works fine aside
      > > from the first call
      > > producing half empty sheets. Is there anyway I can
      > > tell the JVM to queue
      > > the program calls or a simple solution?
      > >
      > > I've checked the fop site but not found anything
      > > more simple than this.
      > >
      > > Thanks for the help.
      > >
      > > Ken.
      > >
      > >
      > >
      > >
      > > -----Original Message-----
      > > From: J.Pietschmann [mailto:j3322ptm@...]
      > > Sent: 13 December 2005 19:54
      > > To: XSL-FO@yahoogroups.com
      > > Subject: Re: [XSL-FO] fop bug? sometimes only the
      > > body appears?
      > >
      > >
      > > Ken Sands wrote:
      > > > Grrr, so hard to recreate the error! It's always
      > > done it with the
      > > > output set to -print
      > > >
      > > > I have as yet not been able to recreate to pdf,
      > > not sure if thats
      > > > where the issue is though.
      > >
      > > The print renderer uses AWT functionality which is
      > > known to be
      > > thread-unsafe. It is possible that somehow a white
      > > text color was set.
      > > Do *never* run two FOP threads in the same JVM
      > when
      > > using the AWT or
      > > print renderer.
      > >
      > > BTW:
      > > > the xml data is
      > > > output to a file and then
      > > > Passed to fop just as if started from the
      > command
      > > line.
      > >
      > > This is unnecessary complicated, check the FOP
      > site
      > > for better
      > > solutions.
      > >
      > > J.Pietschmann
      > >
      > >
      > >
      > >
      > > Yahoo! Groups Links
      > >
      > >
      > >
      > >
      > >
      > >
      > >
      > > --
      > >
      > > Scanned by mailCritical.
      > > --
      > >
      > > The DSI Group of Companies
      > > International House, Barlow Way,
      > > Fairview Industrial Estate., Rainham, Essex, RM13
      > > 8EW, UK
      > > Tel: +44 (0) 1708 523 000
      > > Fax: +44 (0) 1708 524 000
      > > Email: enquiries@...
      > >
      > >
      >
      ************************************************************************
      > > This message and any attachments is intended only
      > > for the individual or company to which it is
      > > addressed and may contain information which is
      > > privileged, confidential or prohibited from
      > > disclosure or unauthorised use. If the recipient
      > of
      > > the transmission is not the intended recipient, or
      > > the employee or agent responsible for delivering
      > > such materials to the intended recipient, you are
      > > hereby notified that any use, any form of
      > > reproduction, dissemination, copying, disclosure,
      > modification,
      > > distribution and/or publication of this email
      > message or it's
      > > attachments other than by its intended recipients
      > is strictly
      > > prohibited by the sender. If you have received it
      > in error, please
      > > notify us immediately by telephone on the number
      > > above and destroy the message and all copies in
      > your
      > > possession.
      > >
      >
      ************************************************************************
      > >
      >
      >
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
      > --
      >
      >
      === message truncated ===
    Your message has been successfully submitted and would be delivered to recipients shortly.