Peter B. wrote:
I am interested in purchasing a server license of your XSL Server. But I
have a few questions:
1. Are there any known problems using XSL Server within Tomcat under
one Debian 6 Virtual Machine (On our own physical server running XEN)?
I'm sorry but I cannot answer this question.
I can only say that XMLmind XSL Server runs fine on Tomcat. Please click
on any of the Word and OpenOffice icons found in the ``bread crumb''
area of any of the page of our web site.
See http://www.xmlmind.com/foconverter/xsl_server.html. Search for "Give
it a try".
Yes, these icons request XMLmind XSL server running on Tomcat to convert
the body of the current HTML page to PDF, RTF, WML, .docx, .odt.
All in all, we strongly recommend that you use our Evaluation Edition to
test this before purchasing the product.
See http://www.xmlmind.com/foconverter/evaluate.html
2. What would be a minimum of required memory?
It depends on the size of the documents.
* In case your input documents are not XSL-FO but DocBook, DITA, XHTML,
etc, then Saxon v6 or v9, the XSLT engine (converts XML to XSL-FO) ,
does not consume much memory.
* XMLmind XSL-FO Converter (the engine which converts XSL-FO to RTF,
WML, .docx, .odt) consumes even less memory.
* On the other hand, Apache FOP (converts XSL-FO to PDF and PostScript)
which is included in XSL Server is a memory hog. Note that this is not
specific to Apache FOP. RenderX XEP, a commercial product, is a memory
hog too.
My usage would be
maximum 100 documents per day (no concurant document generations).
This does not seem to be a lot of documents, but once again this depends
on the size of the documents.
Notes:
* Concurrent document generation would not be a problem at all.
* XMLmind XSL Server features a very useful converted document cache.
May be you could use it to save CPU and memory.
3. Next to .RTF, .DOCX, .ODT is it still also possible to generate
normal .PDF files from .XML data?
Sure. Apache FOP (converts XSL-FO to PDF and PostScript) is also
included in XMLmind XSL Server out of the box.
4. What WYSIWYG tools would you recommend to implement the XSL-FO
source files? I took a look at "XF Designer" from Ecrion. Quiet easy
for me as newby but very expensive.
We have not tried any WYSIWYG design tools. We always write XSLT
stylesheets, even very complex ones, by hand.
In general, XMLmind XSL-FO Converter (the engine which converts XSL-FO
to RTF, WML, .docx, .odt) does not give good results with *needlessly*
*complex* XSL-FO.
For example a block-container, which includes a wrapper, which includes
a block, which includes a block, which includes a block, in a situation
where a single, non-nested, block suffices. I'm not kidding. I've
already seen this.
Please understand that what is output by XMLmind XSL-FO Converter needs
to be fed to a word processor. And for a word processor, a document is
merely a flat list of paragraphs (or tables).
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support
