Re: Problem Executing FopServlet on bea weblogic6.1

2002-07-15 Thread Oleg Tkachenko

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

2002-07-15 Thread Amit Rangari

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: Image Rendering Problem.

2002-07-15 Thread Oleg Tkachenko

Purvesh Vora wrote:

 It really takes lot of generate pdf. Somebody on the fop-user list suggested
 me to scale down the image before feeding to image. 
 Could this help me. or any other solution. Also can you please suggest me
 some java library( or any other efficient software) to scale down image.
Sun's JAI API is not bad one. See http://java.sun.com/products/java-media/jai

-- 
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

2002-07-15 Thread Amit Rangari

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]


cvs commit: xml-fop/src/org/apache/fop/render/xml XMLRenderer.java

2002-07-15 Thread pietsch

pietsch 2002/07/15 12:28:08

  Modified:src/org/apache/fop/render Tag: fop-0_20_2-maintain
Renderer.java
   src/org/apache/fop/render/awt Tag: fop-0_20_2-maintain
AWTRenderer.java
   src/org/apache/fop/render/mif Tag: fop-0_20_2-maintain
MIFRenderer.java
   src/org/apache/fop/render/pcl Tag: fop-0_20_2-maintain
PCLRenderer.java
   src/org/apache/fop/render/pdf Tag: fop-0_20_2-maintain
PDFRenderer.java
   src/org/apache/fop/render/ps Tag: fop-0_20_2-maintain
PSRenderer.java
   src/org/apache/fop/render/svg Tag: fop-0_20_2-maintain
SVGRenderer.java
   src/org/apache/fop/render/txt Tag: fop-0_20_2-maintain
TXTRenderer.java
   src/org/apache/fop/render/xml Tag: fop-0_20_2-maintain
XMLRenderer.java
  Log:
  Replaced options Hashtable by HashMap
  Reproted by: Oleg Tkachenko
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.19.2.3  +2 -2  xml-fop/src/org/apache/fop/render/Renderer.java
  
  Index: Renderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/Renderer.java,v
  retrieving revision 1.19.2.2
  retrieving revision 1.19.2.3
  diff -u -r1.19.2.2 -r1.19.2.3
  --- Renderer.java 11 Jun 2002 00:01:14 -  1.19.2.2
  +++ Renderer.java 15 Jul 2002 19:28:06 -  1.19.2.3
  @@ -41,7 +41,7 @@
   /**
* set up renderer options
*/
  -public void setOptions(java.util.Hashtable options);
  +public void setOptions(java.util.HashMap options);
   
   /**
* set the producer of the rendering
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.38.2.5  +3 -3  xml-fop/src/org/apache/fop/render/awt/AWTRenderer.java
  
  Index: AWTRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/awt/AWTRenderer.java,v
  retrieving revision 1.38.2.4
  retrieving revision 1.38.2.5
  diff -u -r1.38.2.4 -r1.38.2.5
  --- AWTRenderer.java  11 Jun 2002 00:01:14 -  1.38.2.4
  +++ AWTRenderer.java  15 Jul 2002 19:28:07 -  1.38.2.5
  @@ -115,12 +115,12 @@
   /**
* options
*/
  -protected Hashtable options;
  +protected java.util.HashMap options;
   
   /**
* set up renderer options
*/
  -public void setOptions(Hashtable options) {
  +public void setOptions(java.util.HashMap options) {
   this.options = options;
   }
   
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.11.2.2  +3 -3  xml-fop/src/org/apache/fop/render/mif/Attic/MIFRenderer.java
  
  Index: MIFRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/mif/Attic/MIFRenderer.java,v
  retrieving revision 1.11.2.1
  retrieving revision 1.11.2.2
  diff -u -r1.11.2.1 -r1.11.2.2
  --- MIFRenderer.java  23 Apr 2002 22:33:39 -  1.11.2.1
  +++ MIFRenderer.java  15 Jul 2002 19:28:07 -  1.11.2.2
  @@ -80,7 +80,7 @@
   /**
* options
*/
  -protected Hashtable options;
  +protected java.util.HashMap options;
   
   /**
* create the MIF renderer
  @@ -92,7 +92,7 @@
   /**
* set up renderer options
*/
  -public void setOptions(Hashtable options) {
  +public void setOptions(java.util.HashMap options) {
   this.options = options;
   }
   
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.13.2.2  +3 -3  xml-fop/src/org/apache/fop/render/pcl/PCLRenderer.java
  
  Index: PCLRenderer.java
  ===
  RCS file: /home/cvs/xml-fop/src/org/apache/fop/render/pcl/PCLRenderer.java,v
  retrieving revision 1.13.2.1
  retrieving revision 1.13.2.2
  diff -u -r1.13.2.1 -r1.13.2.2
  --- PCLRenderer.java  23 Apr 2002 22:33:39 -  1.13.2.1
  +++ PCLRenderer.java  15 Jul 2002 19:28:07 -  1.13.2.2
  @@ -58,7 +58,7 @@
   private int xoffset =
   -180;   // X Offset to allow for PCL implicit 1/4 left 
margin.
   
  -private java.util.Hashtable options;
  +private java.util.HashMap options;
   
   /**
* Create the PCL renderer
  @@ -68,7 +68,7 @@
   /**
* set up renderer options
*/
  -public void setOptions(java.util.Hashtable options) {
  +public void setOptions(java.util.HashMap options) {
   this.options = options;
   }
   
  
  
  
  No   revision
  
  
  No 

Re: [PATCH] TXTRenderer output encoding

2002-07-15 Thread J.Pietschmann

Oleg Tkachenko wrote:
 Well, encoding-related code looks fine for me, but I cannot build fop in 
 cvs due to Hashtable/HashMap changes:

Oops, didn't clean the build directory before the test build.
It should be fixed now.

J.Pietschmann



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




DO NOT REPLY [Bug 10846] New: - retrieve-boundary=page-sequence gives error

2002-07-15 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846

retrieve-boundary=page-sequence gives error

   Summary: retrieve-boundary=page-sequence gives error
   Product: Fop
   Version: 0.20.4
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


If the retrieve-boundary attribute is set to page-sequence rather than page,
then org.apache.fop.apps.Fop quits with an [ERROR]: null message.

Example fragment:

 fo:retrieve-marker retrieve-class-name=message
  retrieve-boundary=page-sequence
  retrieve-position=first-including-carryover/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]