You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "dan evans (JIRA)" <ax...@ws.apache.org> on 2004/12/06 23:40:14 UTC

[jira] Created: (AXIS-1699) Code page issue in org.apache.axis.configuration.FileProvider

Code page issue in org.apache.axis.configuration.FileProvider
-------------------------------------------------------------

         Key: AXIS-1699
         URL: http://nagoya.apache.org/jira/browse/AXIS-1699
     Project: Axis
        Type: Bug
  Components: Basic Architecture  
    Versions: 1.2    
 Environment: only effects non ANSI codepage systems (such as IBM mainframe, As/400)
    Reporter: dan evans


FileProvider reads configuration as an InputStream (ie no code page conversion) but writes configuration using a PrintWriter (ie UNICODE -> native code page conversion). 

On a non-ansi system, the axis config files are stored on the file system as utf-8 and are loaded correctly, but when FileProvider updates the config files, PrintWriter writes them back to the file system as EBCDIC - meaning that they are not readable when AXIS is restarted.

Changing the writeEngineConfig method as follows should fix this. Replace following code:

PrintWriter writer = new PrintWriter(new FileInputStream(configFile));
XMLUtils.DocumentToWriter(doc, writer);
writer.println();
writer.close;

to:

BufferredOutputStream out = new BufferredOutputStream (new FileInputStream(configFile));
XMLUtils.DocumentToStream(doc, out);
out.close();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Resolved: (AXIS-1699) Code page issue in org.apache.axis.configuration.FileProvider

Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXIS-1699?page=history ]
     
Davanum Srinivas resolved AXIS-1699:
------------------------------------

    Resolution: Fixed

dan, Please review current CVS code - http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/configuration/. i think this has been fixed.

thanks,
dims

> Code page issue in org.apache.axis.configuration.FileProvider
> -------------------------------------------------------------
>
>          Key: AXIS-1699
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1699
>      Project: Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.2
>  Environment: only effects non ANSI codepage systems (such as IBM mainframe, As/400)
>     Reporter: dan evans

>
> FileProvider reads configuration as an InputStream (ie no code page conversion) but writes configuration using a PrintWriter (ie UNICODE -> native code page conversion). 
> On a non-ansi system, the axis config files are stored on the file system as utf-8 and are loaded correctly, but when FileProvider updates the config files, PrintWriter writes them back to the file system as EBCDIC - meaning that they are not readable when AXIS is restarted.
> Changing the writeEngineConfig method as follows should fix this. Replace following code:
> PrintWriter writer = new PrintWriter(new FileInputStream(configFile));
> XMLUtils.DocumentToWriter(doc, writer);
> writer.println();
> writer.close;
> to:
> BufferredOutputStream out = new BufferredOutputStream (new FileInputStream(configFile));
> XMLUtils.DocumentToStream(doc, out);
> out.close();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira