Re: Problem Executing FopServlet on bea weblogic6.1
Amit Rangari wrote: I am not able to execute the FOServlet on weblogic6.1. I get a blank PDF in the IE when I try to execute the FOServlet. The message on Weblogic console is: [DEBUG] Using weblogic.xml.jaxp.RegistryXMLReader as SAX2 Parser Please help me to resolve this issue. You didn't give us enough information to help you. That could be and fop problem and IE one. The debug message you have posted is usual fop's debug message, which only says which xml parser is in use, show us the rest of messages. And look at the list archive for IE and blank pdf, that's actually faq, try to put dummy parameter at the end of url: http://./FopServlet?dummy=.pdf This way probably IE able to understand that response is going to be pdf. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Problem Executing FopServlet on bea weblogic6.1
Sorry about cross posting to both the list, This isn't an IE problem because I am able to view other PDF properly in IE, and I am not getting anything else in the weblogic log other than [DEBUG] Using weblogic.xml.jaxp.RegistryXMLReader as SAX2 Parser I checked the size of the ByteArrayOutputStream it is showing 0 this means nothing is being rendered. Thanks Amit -Original Message- From: Oleg Tkachenko [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 1:07 PM To: [EMAIL PROTECTED] Subject: Re: Problem Executing FopServlet on bea weblogic6.1 Amit Rangari wrote: I am not able to execute the FOServlet on weblogic6.1. I get a blank PDF in the IE when I try to execute the FOServlet. The message on Weblogic console is: [DEBUG] Using weblogic.xml.jaxp.RegistryXMLReader as SAX2 Parser Please help me to resolve this issue. You didn't give us enough information to help you. That could be and fop problem and IE one. The debug message you have posted is usual fop's debug message, which only says which xml parser is in use, show us the rest of messages. And look at the list archive for IE and blank pdf, that's actually faq, try to put dummy parameter at the end of url: http://./FopServlet?dummy=.pdf This way probably IE able to understand that response is going to be pdf. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Problem Executing FopServlet on bea weblogic6.1
Hi, Please find attached the FopServlet.java that I am using and the output on the weblogic console that I am getting is as below: DRIVER OBJECT CREATED SET LOGGER EXECUTED SET RENDERER EXECUTED OUT PUT STREAM IS SET [DEBUG] Using weblogic.xml.jaxp.RegistryXMLReader as SAX2 Parser RENDERING DONE CONTENT LENGTH: 0 DONE And the CLASSPATH I am using is as follows: .; E:\bea\wlserver6.1\lib\fop\avalon-framework-4.1.2b.jar; E:\bea\wlserver6.1\lib\fop\batik.jar; E:\bea\wlserver6.1\lib\fop\fop.jar; E:\bea\wlserver6.1\lib\fop\logkit-1.0.1.jar; E:\bea\wlserver6.1\lib\fop\xalan-2.3.1.jar; E:\bea\wlserver6.1\lib\fop\xercesImpl-2.0.1.jar; E:\bea\wlserver6.1\lib\fop\xml-apis.jar; E:\bea; E:\bea\jdk131; E:\bea\wlserver6.1; E:\bea\wlserver6.1\config\alphadomain2_2; E:\bea\wlserver6.1\config\alphadomain2_2\serverclasses; E:\bea\wlserver6.1\config\alphadomain2_2\servletclasses; E:\bea\jdk131\lib\tools.jar; E:\bea\wlserver6.1\config\alphadomain2_2\applications\TestBean.jar; E:\bea\wlserver6.1\lib\weblogic_sp.jar; E:\bea\wlserver6.1\lib\weblogic.jar Thanks Amit -Original Message- From: Oleg Tkachenko [mailto:[EMAIL PROTECTED]] Sent: Monday, July 15, 2002 1:44 PM To: [EMAIL PROTECTED] Subject: Re: Problem Executing FopServlet on bea weblogic6.1 Amit Rangari wrote: Sorry about cross posting to both the list, This isn't an IE problem because I am able to view other PDF properly in IE, and I am not getting anything else in the weblogic log other than [DEBUG] Using weblogic.xml.jaxp.RegistryXMLReader as SAX2 Parser I checked the size of the ByteArrayOutputStream it is showing 0 this means nothing is being rendered. Well, probably some exception has occured and you have to find its stack trace in logs somewhere, actually FopServlet throws new ServletException object and it's servlet engine responsibility to log it. Or alternatively try to redirect the logger fop uses to a file in order to see fop debug mesages. How you can do it depends on fop version you are using. -- Oleg Tkachenko Multiconn International, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] FopServlet.java Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
