Analysis and Code Snippet
We have uploaded one text file using file upload facility in OAF custom page. It is working fine in JDeveloper but it is not working when we run from oracle application page. The file has been uploaded with wrong data. Broken pipe character (¦) is converted into box (�) in OAF page while we run from oracle eBz application.
OA Framework Version : 12.1.3
JDeveloper Patch: p9879989_R12_GENERIC
IE MAIN¦Standard Purchase Order¦AXASM0100855000¦24-OCT-2013¦0000500.00¦EUR¦¦¦¦SL616H¦2294¦DUBLIN 24 ¦Edinburgh, Standard Life House, (GBR)¦Edinburgh, Baileyfield, (GBR)¦30 Days Net¦Approved¦
Line in Oracle Application Page
IE MAIN�Standard Purchase Order�AXASM0100855000�24-OCT-2013�0000500.00�EUR����SL616H�2294�DUBLIN 24 �Edinburgh, Standard Life House, (GBR)�Edinburgh, Baileyfield, (GBR)�30 Days Net�Approved�
Thanks a lot for your effort.
But still the issue is not resolved. We have modified the encoding style to UTF-8. Please find the below error message.
Error during Date converstion java.text.ParseException: Unparseable date: "Order�AXASM0100855000�24-OCT-2013�0000500.00�EUR����SLBE82�2294�DUBLIN"
The source data for this line is given below.
IE MAIN¦Standard Purchase Order¦AXASM0100855000¦24-OCT-2013¦0000500.00¦EUR¦¦¦¦SLBE82¦2294¦DUBLIN 24 ¦Edinburgh, Standard Life House, (GBR)¦Edinburgh, Baileyfield, (GBR)¦30 Days Net¦Approved¦
Please find java code in AM class for this file upload.
getOADBTransaction().writeDiagnostics(this,"dataFileLine in AM" + dataFileLine ,OAFwkConstants.STATEMENT);
linetext = dataFileLine.split("¦");
Please let me know if you need more information on this regard.
Can you please verify the following steps again:
1. After performing the above mentioned updates, did you complied the code again?
2. Also mention, where do you compile the code? Local system or directly on Application Server?
3. If on local system (Jdeveloper), then please move the latest .class file to server (from myclasses respective directory), bounce and test the results.
4. Lastly, if nothing above works, then try creating a small Demo Project in Jdeveloper and try testing the text in your local system (Displaying text with broken pipe characters on screen). This would not help much actually, but it would surely make sure whether your Jdeveloper has the correct settings enabled.