Hi!

Commtens in bugzilla say, that its not easy to work around this issue. In
fact, there is a solution: use an entity resolver. The incorrect "URI" is
passed to the resolveEntity method, and you can return the desired input
source, yourself.

greetings
Heiner

-----Urspr�ngliche Nachricht-----
Von: Thomas B�rkel [mailto:[EMAIL PROTECTED]
Gesendet am: Montag, 21. Oktober 2002 09:24
An: [EMAIL PROTECTED]
Betreff: RE: Error parsing files, when filename contains german umlauts

HI!

Please see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12257.

Regards,
Thomas

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Freitag, 18. Oktober 2002 18:26
> To: [EMAIL PROTECTED]
> Subject: RE: Error parsing files, when filename contains 
> german umlauts
> 
> 
> Interesting. Could you attach you xml/dtd/xsd files along 
> with the java
> code? An instruction showing how to reproduce the problem will also be
> helpful. Thx.
> 
> Sandy Gao
> Software Developer, IBM Canada
> (1-905) 413-3255
> [EMAIL PROTECTED]
> 
> 
> 
>                                                               
>                                                               
>            
>                       Thomas B�rkel                           
>                                                               
>            
>                       <[EMAIL PROTECTED]>           To:       
> <[EMAIL PROTECTED]>                                
>                 
>                                                cc:            
>                                                               
>            
>                       10/18/2002 07:49         Subject:  RE: 
> Error parsing files, when filename contains german umlauts    
>             
>                       AM                                      
>                                                               
>            
>                       Please respond to                       
>                                                               
>            
>                       xerces-j-user                           
>                                                               
>            
>                                                               
>                                                               
>            
>                                                               
>                                                               
>            
> 
> 
> 
> Correction: 2.2.0 still has problems with spaces in the path. :-(
> 
> > -----Original Message-----
> > From: Thomas B�rkel
> > Sent: Montag, 14. Oktober 2002 08:59
> > To: [EMAIL PROTECTED]
> > Subject: RE: Error parsing files, when filename contains
> > german umlauts
> >
> >
> > 2.2.0 seems to work OK with both spaces and umlauts.
> >
> > > -----Original Message-----
> > > From: Thomas B�rkel
> > > Sent: Freitag, 11. Oktober 2002 09:59
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Error parsing files, when filename contains
> > > german umlauts
> > >
> > >
> > > HI!
> > >
> > > We had the same problem and switched back to 2.0.1 because of
> > > this. Haven't tested the new 2.2.0 release, yet.
> > >
> > > Regards,
> > > Thomas
> > >
> > > > -----Original Message-----
> > > > From: Amthauer, Heiner [mailto:[EMAIL PROTECTED]
> > > > Sent: Freitag, 11. Oktober 2002 09:28
> > > > To: 'Xerces'
> > > > Subject: Error parsing files, when filename contains
> > german umlauts
> > > >
> > > >
> > > > Hi there!
> > > >
> > > > (Using Xerces 2.0.2, JRE 1.3.1_02)
> > > >
> > > > I discovered an error, when parsing xml files when their
> > > name contains
> > > > german umlauts. The call to the SAXParser is:
> > > >
> > > > saxParser.parse(new File(file), this);
> > > >
> > > > As one can see, the File(...) itself is created before the
> > > > parser is called.
> > > > One should assume, that the parser does not care about
> > the filename.
> > > > However, when parsing the file, I get the following exception:
> > > >
> > > > java.net.MalformedURLException: no protocol: GBB_Datenmodell.dtd
> > > >         at java.net.URL.<init>(Unknown Source)
> > > >         at java.net.URL.<init>(Unknown Source)
> > > >         at java.net.URL.<init>(Unknown Source)
> > > >         at
> > > > org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityM
> > > > anager.java:79
> > > > 6)
> > > >         at
> > > > org.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEnti
> > > > tyManager.java
> > > > :756)
> > > >         at
> > > > org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTD
> > > > ScannerImpl.ja
> > > > va:267)
> > > >         ....
> > > >
> > > > By renaming the file, avoiding umlauts (not touching the
> > > > files contents),
> > > > the file can be parsed perfectly nice.
> > > >
> > > > One way to solve this is by not using german umlauts.
> > > > However, our customer
> > > > will not accept the fact that he should have such
> > > > restrictions on a windows
> > > > system, nowadays.
> > > >
> > > > I would appreciate any hint about solving this problem.
> > > >
> > > > regards
> > > > Heiner
> > > >
> > > > ---------------------------------------------------------------
> > > > Dipl. Ing. Heiner Amthauer
> > > >
> > > > T-Systems GEI GmbH
> > > >
> > > > Hausanschrift: Magirusstr. 39/1, 89077 Ulm
> > > > Postanschrift: Postfach 20 64, 89010 Ulm
> > > > Telefon: +49 ( 731) 9344-4422
> > > > Telefax: +49 (731) 9344-4409
> > > > Mobil: +49 (1 78) 4269335
> > > > E-Mail: [EMAIL PROTECTED]
> > > > Internet: http://www.t-systems.com
> > > >
> > > >
> > > >
> > > >
> > >
> > 
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > >
> > 
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

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

Reply via email to