Re: xml, xsl = html
Thanks to all who responded, one last query, whether this will give me very proper printable format ? (i assume that client's pagesettings can be kept to a constant ? ) regards ManishaTommy Reynolds [EMAIL PROTECTED] wrote: Uttered [EMAIL PROTECTED], spake thus: Is this enough or do you need the complete file?That's fine, I get the idea.Thanks! Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses.
Re: xml, xsl = html
Thanks Loius, Do u mind sending me complete file ? I am totally new in this area. regards Manisha[EMAIL PROTECTED] wrote: A snippet of a very simple XSL that produces HTML is inlined below:xmlns:xsl="http://www.w3.org/1999/XSL/Transform"xmlns:fo="http://www.w3.org/1999/XSL/Format" Is this enough or do you need the complete file?-Lou~~LOG-NET, Inc.The Logistics Network Management System~~230 Half Mile RoadThird FloorRed Bank, NJ 07701PH: 732-758-6800FAX: 732-747-7497http://www.LOG-NET.com~~CONFIDENTIAL PRIVILEGEDUnless otherwise indicated or if obvious from the nature of the content,the information contained herein is privileged and confidentialinformation/work product. The communication is intended for the use of theindividual or entity named above. If the reader of this transmission isnot the intended recipient, you are hereby notified that anydissemination, distribution or copying of this communication is strictlyprohibited. If you have received this communication in error, pleasenotify the sender immediately by telephone (732-758-6800) or by electronicmail ([EMAIL PROTECTED]), and destroy any copies, electronic, paper orotherwise, which you may have of this communication. Thank you.~~Tommy Reynolds <[EMAIL PROTECTED] aCoder.com cc: Subject: Re: xml, xsl = html 03/09/2005 09:16 Please respond to fop-user Uttered "Arun Sinha" <[EMAIL PROTECTED]>, spake thus: You can achieve it without using fop. Simply outout the tags html in your xsl. Link your xsl to xml and call the XML directly in browser.Do you have a short example? I'd love to see it.Cheers(See attached file: attg4xc7.dat)-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED] Do you Yahoo!? Yahoo! Small Business - Try our new resources site!
RE: FopServlet
Hi,
ok I tried it again and get the same exception!!
Here is my code (well I have given you the equiv with project team!):
public void execute(HttpServletRequest request, HttpServletResponse
response)
throws IOException, ServletException {
try {
ProjectTeam projectTeam = new ProjectTeam();
// set up the logger for the driver
if (logger==null) {
logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
MessageHandler.setScreenLogger(logger);
}
MessageHandler.setScreenLogger(logger);
File xslFile = new File(./../myxsl, projectTeam2FO.xsl);
SAXSource xmlSource = new SAXSource(new IncidentsXMLReader(),
new IncidentsInputSource(projectTeam));
SAXSource xslSource = new SAXSource(
new InputSource(new FileInputStream(xslFile)));
TraxInputHandler input =
new TraxInputHandler(xmlSource.getInputSource(),
xslSource.getInputSource());
renderXML(input, response);
} catch (ServletException ex) {
throw ex;
}
catch (Exception e) {
throw new ServletException(e);
}
}
public void renderXML(TraxInputHandler input,
HttpServletResponse response) throws
ServletException {
try {
ByteArrayOutputStream out = new ByteArrayOutputStream();
response.setContentType(application/pdf);
Driver driver = new Driver();
driver.setLogger(logger);
driver.setRenderer(Driver.RENDER_PDF);
driver.setOutputStream(out);
input.run(driver);
byte[] content = out.toByteArray();
response.setContentLength(content.length);
response.getOutputStream().write(content);
response.getOutputStream().flush();
} catch (Exception ex) {
throw new ServletException(ex);
}
}
and here is the stack trace:
2005-03-10 07:40:21 StandardContext[/tracker]: Mapped to servlet 'fop' with
servlet path '/fop' and path info 'null' and update=true
2005-03-10 07:40:23 StandardWrapperValve[fop]: Servlet.service() for servlet
fop threw exception
javax.servlet.ServletException: java.net.MalformedURLException
at
com.ocado.tracker.common.FopServlet.renderXML(FopServlet.java:150)
at com.ocado.tracker.common.FopServlet.execute(FopServlet.java:116)
at com.ocado.tracker.common.FopServlet.doGet(FopServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:696)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:200)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:146)
at
org.springframework.orm.hibernate.support.OpenSessionInViewFilter.doFilterIn
ternal(OpenSessionInViewFilter.java:171)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestF
ilter.java:76)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:166)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:146)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:209)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:144)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
.java:445)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:594)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:596)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:118)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:594)
at
xml unicode problem
I amon MSSQL 2K. The field i am using to store chinese character is defiles as chinesename nvarchar(50) Using jsp file (meta tag set to UTF-8) to display form. User fill up the form and submit it. At backend i run servlet andinsert into table.When i insert the value i use statements like insertvalue (N'..'). When i view it using Enterprise Manager, i see some weird characters.Butstill when i use jsp file to retrive all data back,it shows on screen all correct. But the problem comes when i use these database values and create XML file. In XML file created i see the sameas what i see in Enterprise Manager. So PDF rendered also is showing same weird chars. I know MSSQL uses UCS2 but i am specifying UTF-8 for my jsp ? Any clues on this pls ? How i can have my XML file properly created ? regards Manisha Do you Yahoo!? Yahoo! Small Business - Try our new resources site!
Re: FopServlet
On 10.03.2005 08:49:26 Ben Gill wrote: Hi, ok I tried it again and get the same exception!! Here is my code (well I have given you the equiv with project team!): snip/ Hmm, you are still using the InputHandler approach which I personally don't consider ideal. I'd integrate the renderXML() method into the main execute method and use the pattern from ExampleObj2PDF 1:1. But I can't tell if your problem has something to do with that. Probably not. and here is the stack trace: 2005-03-10 07:40:21 StandardContext[/tracker]: Mapped to servlet 'fop' with servlet path '/fop' and path info 'null' and update=true 2005-03-10 07:40:23 StandardWrapperValve[fop]: Servlet.service() for servlet fop threw exception javax.servlet.ServletException: java.net.MalformedURLException at com.ocado.tracker.common.FopServlet.renderXML(FopServlet.java:150) at com.ocado.tracker.common.FopServlet.execute(FopServlet.java:116) Ok, this doesn't say much other than there's an URL somewhere that's making problems. snip/ at java.lang.Thread.run(Thread.java:534) Caused by: java.net.MalformedURLException at java.net.URL.init(URL.java:571) at java.net.URL.init(URL.java:434) at java.net.URL.init(URL.java:383) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startDocumentEntity(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.setInputSource(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) This here is more interesting. DTDConfiguration. Is there a DTD involved somewhere in your processing chain? If yes, I'd try to track that down. Obviously, the problem happens during XSLT stage, not within FOP itself. What I would suggest is even more than the above suggestion. Extract the whole transformation (XSLT+FOP) functionality of the servlet into a separate class that you can easily test outside the web container. Then just call this functionality from within the servlet. at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.java:495) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java: 658) I'm sorry that I can't just tell what went wrong. My suggestions should help you track down the problem further and maybe someone else has an additional idea. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xml unicode problem
Yes, this sounds very much like an encoding problem. UCS2 is definitely not the same as UTF-8. What you need to do in your case is not clear to me, however. It depends a lot from what the JDBC driver returns, how you create the XML file etc. etc. On 10.03.2005 10:05:47 Manisha Sathe wrote: I am on MSSQL 2K. The field i am using to store chinese character is defiles as chinesename nvarchar(50) Using jsp file (meta tag set to UTF-8) to display form. User fill up the form and submit it. At backend i run servlet and insert into table. When i insert the value i use statements like insertvalue (N'..'). When i view it using Enterprise Manager, i see some weird characters. But still when i use jsp file to retrive all data back, it shows on screen all correct. But the problem comes when i use these database values and create XML file. In XML file created i see the same as what i see in Enterprise Manager. So PDF rendered also is showing same weird chars. I know MSSQL uses UCS2 but i am specifying UTF-8 for my jsp ? Any clues on this pls ? How i can have my XML file properly created ? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTML Tables converted to FO Tables
Eckbert P. Dollhofer wrote: snip/ Hm? Are there any FO Formatters alternativ to apache-fop that will render tables with table-layout=auto to pdf? Would be off a big help! Yes. Try XEP 4 from RenderX Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Leader dots not showing up and Compilation exited abnormally with code 255 at Wed Mar 09 14:20:11
Glen Mazza wrote: snip/ (2) fo:blockSIGNITEKfo:leader rule-thickness=1pt leader-pattern=dots/ does not seem to be producing a complete row of dots for my table of contents. It did in 0.19. In our /examples directory, we have a leader.fo sample somewhere. Run that and see if it works, if so look in that file to see what needs to be done. I think the problem is that 0.20.5 is more conformant to the spec than 0.19 used to be. You need to justify the block containing the leader in order for the leader to stretch to the full width of the block. Use text-align-last=justify rather than text-align (as I'm guessing from your example that the block only has 1 line) snip/ Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FopServlet
Does the problem persist if you serialize the SAX events generated by
the Incident with an identity transformer to a file and run the XSL
transformation stand-alone from the command-line?
I don't think it's a problem but did you realize that you have two FOP
processing runs in your testGeneratePDF() method, the first started by
Transformer.transform() and the other by input.run()? Since I can't do
anything with the line numbers in the stack trace, this is something you
have to do.
On 10.03.2005 11:12:07 Ben Gill wrote:
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: 10 March 2005 09:37
To: [EMAIL PROTECTED]
Subject: Re: FopServlet
On 10.03.2005 08:49:26 Ben Gill wrote:
Hi,
ok I tried it again and get the same exception!!
Here is my code (well I have given you the equiv with project team!):
snip/
Hmm, you are still using the InputHandler approach which I personally
don't consider ideal. I'd integrate the renderXML() method into the main
execute method and use the pattern from ExampleObj2PDF 1:1. But I can't
tell if your problem has something to do with that. Probably not.
Ok, I tried this and still get the same error... I have created a Junit test
for this and here is my code, based upon the ExampleObj2PDF example:
public void testGeneratePDF() throws Exception {
try {
Incident incident = incidentsDAO.loadIncident(new
Long(121));
File baseDir = new File(.);
File outDir = new File(baseDir, out);
outDir.mkdirs();
File xslFile = new File(baseDir,
../source/src/com/ocado/tracker/incidents/fop/incident2FO.xsl);
Driver driver = new Driver();
Logger logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
driver.setLogger(logger);
MessageHandler.setScreenLogger(logger);
driver.setRenderer(Driver.RENDER_PDF);
ByteArrayOutputStream out = new ByteArrayOutputStream();
try {
driver.setOutputStream(out);
//Setup XSLT
TransformerFactory factory = TransformerFactory.newInstance();
Transformer transformer = factory.newTransformer(new
StreamSource(xslFile));
//Setup input for XSLT transformation
Source src = incident.getSource();
//Resulting SAX events (the generated FO) must be piped through
to FOP
Result res = new SAXResult(driver.getContentHandler());
//Start XSLT transformation and FOP processing
transformer.transform(src, res);
} finally {
if (out!=null) {
out.close();
}
}
SAXSource xmlSource = new SAXSource(new
IncidentsXMLReader(), new IncidentsInputSource(incident));
SAXSource xslSource = new SAXSource(
new InputSource(new
FileInputStream(xslFile)));
TraxInputHandler input =
new TraxInputHandler(xmlSource.getInputSource(),
xslSource.getInputSource());
input.run(driver);
byte[] content = out.toByteArray();
log.debug(Got content [ + content + ]);
}
catch (Exception e) {
log.error(Error [ + e.getMessage() + ], e);
}
}
obviously,my Incident is your ProjectTeam!!!
and here is the stack trace:
2005-03-10 07:40:21 StandardContext[/tracker]: Mapped to servlet 'fop'
with
servlet path '/fop' and path info 'null' and update=true
2005-03-10 07:40:23 StandardWrapperValve[fop]: Servlet.service() for
servlet
fop threw exception
javax.servlet.ServletException: java.net.MalformedURLException
at
com.ocado.tracker.common.FopServlet.renderXML(FopServlet.java:150)
at com.ocado.tracker.common.FopServlet.execute(FopServlet.java:116)
Ok, this doesn't say much other than there's an URL somewhere that's
making problems.
Yes, and it could be the way this:
../source/src/com/ocado/tracker/incidents/fop/incident2FO.xsl);
(but the it finds the xsl file and says it exists and this is the string I
use for my working version...)
or in the XSL:
xsl:stylesheet version=1.1
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
exclude-result-prefixes=fo
and/or
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
As you noted, the error is coming from the DTD:
Caused by: java.net.MalformedURLException
at java.net.URL.init(URL.java:571)
at
RE: FopServlet
Right, I have got it working!
Thanks for your help Jeremias - you were right about input.run() running in
my test (which was the old way - which was causing the error!).. the key
was to use the ExampleObj2PDF logic in the servlet...
Maybe the example can be updated with my version? I have not compiled this,
but I know it works...
Here is :
public void execute(HttpServletRequest request, HttpServletResponse
response)
throws IOException, ServletException {
ByteArrayOutputStream out = null;
try {
ProjectTeam projectTeam = new ProjectTeam();
projectTeam.setProjectName(test);
Driver driver = new Driver();
Logger logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
driver.setLogger(logger);
MessageHandler.setScreenLogger(logger);
driver.setRenderer(Driver.RENDER_PDF);
out = new ByteArrayOutputStream();
driver.setOutputStream(out);
File xslFile = new
File(./../webapps/myappname/WEB-INF/classes/mypkgname/fop,
projectteam2fo.xsl);
//Setup XSLT
TransformerFactory factory = TransformerFactory.newInstance();
Transformer transformer = factory.newTransformer(new
StreamSource(xslFile));
//Setup input for XSLT transformation
Source src = incident.getSource();
//Resulting SAX events (the generated FO) must be piped through
to FOP
Result res = new SAXResult(driver.getContentHandler());
//Start XSLT transformation and FOP processing
transformer.transform(src, res);
byte[] content = out.toByteArray();
response.setContentType(application/pdf);
response.setContentLength(content.length);
response.getOutputStream().write(content);
response.getOutputStream().flush();
} catch (Exception e) {
throw new ServletException(e);
} finally {
if (out!=null) {
out.close();
}
}
}
Regards
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: 10 March 2005 11:03
To: [EMAIL PROTECTED]
Subject: Re: FopServlet
Does the problem persist if you serialize the SAX events generated by
the Incident with an identity transformer to a file and run the XSL
transformation stand-alone from the command-line?
I don't think it's a problem but did you realize that you have two FOP
processing runs in your testGeneratePDF() method, the first started by
Transformer.transform() and the other by input.run()? Since I can't do
anything with the line numbers in the stack trace, this is something you
have to do.
On 10.03.2005 11:12:07 Ben Gill wrote:
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: 10 March 2005 09:37
To: [EMAIL PROTECTED]
Subject: Re: FopServlet
On 10.03.2005 08:49:26 Ben Gill wrote:
Hi,
ok I tried it again and get the same exception!!
Here is my code (well I have given you the equiv with project team!):
snip/
Hmm, you are still using the InputHandler approach which I personally
don't consider ideal. I'd integrate the renderXML() method into the main
execute method and use the pattern from ExampleObj2PDF 1:1. But I can't
tell if your problem has something to do with that. Probably not.
Ok, I tried this and still get the same error... I have created a Junit
test
for this and here is my code, based upon the ExampleObj2PDF example:
public void testGeneratePDF() throws Exception {
try {
Incident incident = incidentsDAO.loadIncident(new
Long(121));
File baseDir = new File(.);
File outDir = new File(baseDir, out);
outDir.mkdirs();
File xslFile = new File(baseDir,
../source/src/com/ocado/tracker/incidents/fop/incident2FO.xsl);
Driver driver = new Driver();
Logger logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
driver.setLogger(logger);
MessageHandler.setScreenLogger(logger);
driver.setRenderer(Driver.RENDER_PDF);
ByteArrayOutputStream out = new ByteArrayOutputStream();
try {
driver.setOutputStream(out);
//Setup XSLT
TransformerFactory factory = TransformerFactory.newInstance();
Transformer transformer = factory.newTransformer(new
StreamSource(xslFile));
//Setup input for XSLT transformation
Source src = incident.getSource();
//Resulting SAX events (the generated FO) must be
xsl:apply-templates
Hi, I am using apply-templates, but would like to always spit out one child (ie.TeamMemeber) entry in the PDF doc. At the momment, if there is no TeamMember, nothing gets written to the PDF document.. Is there a clever way of telling XSL to spit out at least one child anyway? or is the solution to dump out some empty XML from the ProjectTeamXMLReader? Thanks This message has been checked for all known viruses by the MessageLabs Virus Control Centre. * Notice: This email is confidential and may contain copyright material of Ocado Limited (the Company). Opinions and views expressed in this message may not necessarily reflect the opinions and views of the Company. If you are not the intended recipient, please notify us immediately and delete all copies of this message. Please note that it is your responsibility to scan this message for viruses. Company reg. no. 3875000. Ocado Limited Titan Court 3 Bishops Square Hatfield Business Park Hatfield Herts AL10 9NE * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Table cells and Borders
I am trying to render a table-row that has two table-cells without any spacing between the cells. In order to see what is happening, I had the cell borders drawn - turns out there is always a space about one character in width between the border of supposedly adjacent cells. The table property border-collapse=collapse does not seem to affect anything. I am setting padding-top and -bottom but not left and right. Kindly suggest how I can get these two cells to render with no space between. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RTF Renderer from command line?
I remember installing cocoon two years ago and getting rtf documents. Now I am using the command line and the documentation says the rtf renderer is not there by default! Why is this? Is there any documentation on where to get the rtf renderer and using it from the command line utility? Thanks, Siegfried - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master
Glen, On Wed, Mar 09, 2005 at 11:34:29AM -0800, Glen Mazza wrote: The property on fo:conditional-page-master-reference should be master-reference, not master-name [1]. I had this problem too the other day. Can you not throw some validation towards detecting a missing master-reference attribute? The idea that FOP goes searching for an empty master-reference name is not quite satisfactory. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
