Write character to excel using POI

[Thomas Greene]

I have hex code of a special character.

Say, String str="2122";

I want to write the character corresponding to this hex code to an excel file (using POI).

This is my code

   public class Test 
{
 
void func() {

String str="2122";

char c=(char)Integer.parseInt(str, 16);
 System.out.println(c);
 try{
     File writeXcel=new File("C:/new.xls");
FileOutputStream fileOut = new FileOutputStream(writeXcel);
HSSFWorkbook wb=new HSSFWorkbook();
HSSFSheet sheet=wb.createSheet();
HSSFRow row=sheet.createRow(0);
HSSFCell cell=row.createCell((short)0);

cell.setCellValue(c);
wb.write(fileOut);
fileOut.close();
 }catch(Exception e) {
 e.printStackTrace();
 }
 
}
public static void main(String[] args) 
{
Test hc=new Test();
hc.func();
 
}
 
} 

Problem is that in the console I am getting the correct character. But when it is written to the excel sheet, i get the corresponding decimal value (rather than the charcter). So the value that i get in the excel sheet is 8482.
Please tell me how can I get the character in the excel sheet.

[Joel McNary]

According to the javadoc,
there isn't a setValue method that takes a char as a parameter, so it must be being converted to a double and calling that method.

What happens if you say:

cell.setValue(String.valueOf(c));

or, since the setValue(String) is deprecated,

cell.setValue(new HSSFRichTextString(String.valueOf(c)));

[Thomas Greene]

Originally posted by Joel McNary:
According to the javadoc,
there isn't a setValue method that takes a char as a parameter, so it must be being converted to a double and calling that method.

What happens if you say:

cell.setValue(String.valueOf(c));

or, since the setValue(String) is deprecated,

cell.setValue(new HSSFRichTextString(String.valueOf(c)));

If I do this

cell.setCellValue(new HSSFRichTextString(String.valueOf(c)));

this is the error I get

The method setCellValue(double) in the type HSSFCell is not applicable for the arguments (HSSFRichTextString)

[Joel McNary]

Try the first one, with the argument as a String. Does that produce a similar error?