[GeoNetwork-devel] PDFPrint fails with exception [SEC=UNCLASSIFIED]

Hi Kevin,

GA is currently in production with a locally modified version of BlueNet taken from change #1411, so we are some way behind the current baseline. My contract here finishes next week so I am leaving any future merges to my replacement :wink:

Cheers,

Steve

-----Original Message-----
From: Kevin Gunn [mailto:k.gunn@anonymised.com]
Sent: Thursday, 23 October 2008 10:35
To: Davies Stephen; geonetwork-devel@lists.sourceforge.net
Subject: RE: [GeoNetwork-devel] PDFPrint fails with exception[SEC=UNCLASSIFIED]

Hi Steve,

Thx for the response. I don’t feed it any doc, it takes the entire Jeeves request and puts it through the XSLT FOP transformation. I’ll try to track down exactly where in the XML it’s having issues. It could be DB related as the md sub-xml sections come from the DB. The records I’m testing with are straight copies of the default ISO19139.mcp template with a new title. We’re using oracle as the DB and the default driver that comes with the latest GN libs.

I’ll wack a little method into Xml.java to check the chars in the XML being transformed; perhaps something like this could be added into the current impl to fail it nicely.

Are you guys using this latest source as your Geonetwork production version?

Cheers,

Kevin


From: Stephen.Davies@anonymised.com [mailto:Stephen.Davies@anonymised.com]
Sent: Wednesday, 22 October 2008 15:44 PM
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] PDFPrint fails with exception[SEC=UNCLASSIFIED]

Hi Kevin,

I’ve encountered UTF encoding issues in the past. Generally my first port of call is to check that the data is actually valid UTF-8. I’ve attached a utility that simply dumps details of non-ascii characters to the console. This will give you a starting point. I generally use textpad to view the file in hex once the potential problem characters have been found. Not all programs, e.g. Windows notepad, behave correctly when ‘special’ characters exist (nor does it handle XML encoding declarations).

You may also like to consider the database settings and support for UTF-8. I think MySQL requires additional settings in the JDBC connect string.

Cheers,

Steve

-----Original Message-----
From: Kevin Gunn [mailto:k.gunn@anonymised.com]
Sent: Wednesday, 22 October 2008 4:20
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] PDFPrint fails with exception

Hi,

The latest BlueNetMEST’s PDFPrint fails on exception for me. Is there a known solution for this?

C:_work\geonetwork\BlueNet_MEST_SVN\web\geonetwork/xsl/portal-present-fop.xsl

2008-10-22 13:53:44,755 ERROR [jeeves.service] - → (C) message : org.xml.sax.SAXParseException: Invalid byte 2 of 4-byte UTF-8 sequence.

2008-10-22 13:53:44,755 ERROR [jeeves.service] - → (C) exception : XPathException

2008-10-22 13:53:44,755 DEBUG [jeeves.service] - Raised exception while executing service

org.xml.sax.SAXParseException: Invalid byte 2 of 4-byte UTF-8 sequence.

XPathException

en

pdf.search

Thx,

Kevin Gunn

Software Engineer

Australian Institute of Marine Science

Ph: (07) 47534305

Fax: (07) 4772 5852

E-mail: k.gunn@anonymised.com

------------------------------------------------------------------------|

The information contained in this communication is for the use of the |

individual or entity to whom it is addressed, and may contain |

information which is the subject of legal privilege and/or copyright. |

If you have received this communication in error, please notify the |

sender by return E-Mail and delete the transmission, together with any |

attachments, from your system. Thank you. |

------------------------------------------------------------------------|

 
 
--  
------------------------------------------------------------------------
The information contained in this communication is for the use of the 
individual or entity to whom it is addressed, and may contain 
information which is the subject of legal privilege and/or copyright.  
 
If you have received this communication in error, please notify the 
sender by return email and delete the transmission, together with any 
attachments, from your system. Thank you.
------------------------------------------------------------------------
 
 
--  
------------------------------------------------------------------------
The information contained in this communication is for the use of the 
individual or entity to whom it is addressed, and may contain 
information which is the subject of legal privilege and/or copyright.  
 
If you have received this communication in error, please notify the 
sender by return email and delete the transmission, together with any 
attachments, from your system. Thank you.
------------------------------------------------------------------------