Runar,
It explains my problem but doesn't solve it :). JBuilder under Win32
inserts this encoding for deployment descriptors whenever the DD is
modified. Fortunately, JB also allows me to remove it in the source view -
so the irritation is very minor. Thanks for the explanation and pointer.
Regards
Joshua
On Fri, 10 Nov 2000, Runar Svendsen wrote:
> The problem lies not within xerces, but in the fact that any XML parser will
> fail with a fatal error when encountering an encoding name it doesn't
> recognize. The encoding you are using (cp-1252) is the default windows
> encoding, but it is also known as "ISO-8859-1" and it is by this name XML
> will recognize it.
> Your XML header should then read:
>
> <?xml version="1.0" encoding="ISO-8859-1">
>
> For further info, see
> http://msdn.microsoft.com/library/psdk/sql/2_006_15.htm
> <http://msdn.microsoft.com/library/psdk/sql/2_006_15.htm>
>
>
> Hope this solves your problem!
>
>
>
> kind regards,
> for Exense ASA
> Runar Svendsen
>
> [EMAIL PROTECTED] Karenslyst alle 9a
> phone. +47 23 13 65 00 P.O.Box 303 Skoyen
> fax. +47 23 13 65 01 N-0213 Oslo
> mobil. +47 93 42 56 19 http://www.exense.com/
> <http://www.exense.com/>
>
> - makes sense of the e in your business
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [ mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> ]On Behalf Of Joshua Goodall
> Sent: 9. november 2000 21:48
> To: Orion-Interest
> Subject: xerces limitation?
>
>
>
> if I begin my ejb-jar.xml with:
>
> <?xml version="1.0" encoding="Cp1252"?>
>
> rather than <?xml version="1.0"?> (sans encoding)
>
> then Orion cannot parse it. Is this a known limitation of Xerces?
>
> - Joshua
>
>
>
>
>
