Character encoding on other platforms (previously os/390)
I've had a couple folks ask me for the modified code so the proper character
encoding is returned on the toString().getBytes()
is US-ASCII. This is cool that other people besides me need this.
I downloaded this snapshot xml-fop_20020515162132 and I don't see any
modification to the code.
Is this change going to be incorporated or has been incorporated in a way
that I missed?
Basically I had to dig through and change every instance from
return result.toString().getBytes();
to
try {
return result.toString().getBytes(PDFConstants.Encoding);
} catch ( UnsupportedEncodingException e ) {
return result.toString().getBytes();
}
The constant in the class is just my habit and could easily be replaced by
just the string constant US-ASCII.
Is there anything else I can do to make sure that these changes get
incorporated if they are not already?
Many Thanks,
Jason West
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: help to get started on WebSphere 3.5
This is how I do it Websphere 4.
Using Websphere Application developer I put the jar files
into the WEB-INF/lib directory in my war file. If using VAJ
just add some entries to the WS Testenvironment classpath to
where these are.
I then used the code examples in the docs.
here is a little code snippet
( it's contextual to my program and I use the oracle xml/xslt
engines as well. )
import org.apache.fop.apps.Driver;
import org.apache.fop.apps.Version;
import org.apache.fop.apps.XSLTInputHandler;
import org.apache.log.*;
if ( sUseFOP.equals("Y") ) {
XMLDocumentFragment foDocFrag =
processor.processXSL(xsl, resultXML);
XMLDocument foDoc = new XMLDocument();
foDoc.appendChild( foDocFrag);
renderXML((Document) foDoc, response, outW);
} else {
processor.processXSL(xsl, resultXML, outW);
}
HTH, Jason
-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 03, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: Re: help to get started on WebSphere 3.5
[EMAIL PROTECTED] wrote:
>
> I have to generate PDF letters files. To do that I have decided to use
> FOP files as letter templates supplying
> variables(name, address...) via XML. It is going to be a batch job,
> running "main" method developing
> with Visual Age, WebSphere 3.5. Is anyone has examples?
> Most importantly, I have no idea what libraries to download, where to
> install and how to configure.
You are asking for something big. Moreover, i can't
quite figure out what your actual requirements are.
The easiest way seems to be to contact your friendly
IBM support.
Other than that it would be useful to know:
1. How much experience do you have in running WebSphere
and deploying code for WebSphere?
2. How much experience do you have in Java programming
in general and in servlet/JSP stuff in particular?
3. How extensive have you already dealt with XML stuff?
4. How much experience do you have in developing
XSLT/XSLFO?
5. How much experience do you have in running FOP?
6. What do you mean by "batch job"? Conventionally
this is not used in assiciation with a web application
server.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
A how-to question:
I need to be able to print a table under a landscape type setup but, I would like the report flow to print all the columns and then all rows. Another way to say it is I may have more columns that will fit on a page so I want the page breaking to first break and complete all the columns for the row and then I guess go back to start the next row. Anyone have a solution for this? TIA, Jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: EBCDIC os390
I now have FOP working on our OS/390.
My solution was to add a class called PDFConstants that only held a static
string variable for the encoding type.
All places in the code where there was a
str.getBytes();
I replaced with
try {
str.getBytes(PDFConstants.Encoding);
} catch ( UnsupportedEncodingException ue ) {
str.getBytes();
}
If there is a better way, please holler.
If this is an ok way to fix it, how do post the patches?
(never done this before on a public project like this )
Thanks, Jason
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 01, 2002 3:16 AM
To: [EMAIL PROTECTED]
Subject: Re: EBCDIC os390
> I'll apologize upfront as I think my question is really for the users list
> but,
> I was unable to find how to subscribe to it.
No, I think you're in the right place.
> I'm developing under Websphere 4.0 and have had success in using FOP .20
> on my NT machines. I take that ear file and install it on our os390
> Websphere
> server and I get back garbage. If I convert the garbage from EBCDIC to
ASCII
> with a tool, it appears the uncompressed streams convert fine. The
document
> still does not work. How can I make FOP ensure that all of it's temporary
> streams
> use the proper encoding? The following snippet is how I'm using FOP.
Ben Fowler posted a similar mail two days ago.
http://marc.theaimsgroup.com/?l=fop-dev&m=101480100804070&w=2
You're in the same boat. I think it would be good if you one of you two
could really track down the problem, create a patch for it and post it
to the list for inclusion into FOP along with some documentation
(guidelines) what has to be done to ensure non-ascii-environment
compatibility in FOP for the future.
Cheers
Jeremias Märki
mailto:[EMAIL PROTECTED]
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch
-
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: EBCDIC os390
Anyone have any documents on how the software works already to help me speed up where to look and what to patch? What it looks like to me, is that there are some compressed streams inside the entire pdf stream. So, a conversion at the final output won't work; appears to convert the non-compressed parts ok though. Thanks, Jason -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Friday, March 01, 2002 3:16 AM To: [EMAIL PROTECTED] Subject: Re: EBCDIC os390 > I'll apologize upfront as I think my question is really for the users list > but, > I was unable to find how to subscribe to it. No, I think you're in the right place. > I'm developing under Websphere 4.0 and have had success in using FOP .20 > on my NT machines. I take that ear file and install it on our os390 > Websphere > server and I get back garbage. If I convert the garbage from EBCDIC to ASCII > with a tool, it appears the uncompressed streams convert fine. The document > still does not work. How can I make FOP ensure that all of it's temporary > streams > use the proper encoding? The following snippet is how I'm using FOP. Ben Fowler posted a similar mail two days ago. http://marc.theaimsgroup.com/?l=fop-dev&m=101480100804070&w=2 You're in the same boat. I think it would be good if you one of you two could really track down the problem, create a patch for it and post it to the list for inclusion into FOP along with some documentation (guidelines) what has to be done to ensure non-ascii-environment compatibility in FOP for the future. Cheers Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Tel. +41 41 317 2020 - Fax +41 41 317 2029 Internet http://www.outline.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
EBCDIC os390
I'll apologize upfront as I think my question is really for the users list
but,
I was unable to find how to subscribe to it.
I'm developing under Websphere 4.0 and have had success in using FOP .20
on my NT machines. I take that ear file and install it on our os390
Websphere
server and I get back garbage. If I convert the garbage from EBCDIC to ASCII
with a tool, it appears the uncompressed streams convert fine. The document
still does not work. How can I make FOP ensure that all of it's temporary
streams
use the proper encoding? The following snippet is how I'm using FOP.
ByteArrayOutputStream out = new ByteArrayOutputStream();
response.setContentType("application/pdf");
Driver driver = new Driver();
driver.setRenderer(Driver.RENDER_PDF);
driver.setOutputStream(out);
driver.render( foDoc );
byte[] content = out.toByteArray();
response.setContentLength(content.length);
response.getOutputStream().write(content);
response.getOutputStream().flush();
TIA, Jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
