Client_text_io does not write the file but does create it.

Question

Hello there!
I have a form which generates a .txt file using client_text_io webutil function.
this is the procedure:
PROCEDURE CREA_FILE IS
MYFILE CLIENT_TEXT_IO.FILE_TYPE;
OUTFILE CLIENT_TEXT_IO.FILE_TYPE;
MFILE VARCHAR2(1000);
MLINE VARCHAR2(5000);
RESP NUMBER;
BEGIN
MLINE:='LINE TO WRITE...';
MFILE := C:\test.txt;
OUTFILE := CLIENT_TEXT_IO.FOPEN(MFILE,'w');
CLIENT_TEXT_IO.put_line(OUTFILE, MLINE || ' 123');
CLIENT_TEXT_IO.Fclose(OUTFILE);
EXCEPTION
     WHEN OTHERS THEN
     CLIENT_TEXT_IO.Fclose(MYFILE);
     message('ERROR: '||SQLERRM);
END;
It works on OAS 10g + forms 10g. the file is created fine, BUT I have tried with forms 11g unsuccessful.
My forms 11g are running under weblogic and the RedHat server.
Im running the forms app from my laptop Windows XP.
I configured webutil as the MOS note said, the thing is, the file is created, but no data is writted.
I can open the file test.txt but the line I tried to print is not there, the same thing with 10g and the file is good.
help me please.

Answer 1

What are you doing after writing to the file? Are you leaving the form? Forms performs event bundling when sending data over to java beans;
v_FILE_HANDLE := CLIENT_TEXT_IO.FOPEN (FPATH, 'W'); most certainly uses get_custom_property at the end to retrieve the file handle from the bean which will cause a "synchronize" as data must be retrieved from the bean before continuing in the PL/SQL code whereas
CLIENT_TEXT_IO.Put_line(v_FILE_HANDLE,v_string_prov);
CLIENT_TEXT_IO.FCLOSE (v_FILE_HANDLE); most certainly uses set_custom_property which is a one-way street and data is bundled up and sent as one package. If you have e.g. a exit_form right after those calls there is a chance that forms waits for some other data to be sent over to the bean but won't send it, as the form doesn't exist anymore after the exit_form. The same would happen if you'd do a
v_FILE_HANDLE := CLIENT_TEXT_IO.FOPEN (FPATH, 'R');
CLIENT_TEXT_IO.FCLOSE (v_FILE_HANDLE); right after writing your form as fopen will cause the sync (with the possibility that java will still hold a file lock on the file as the fclose method won't be called).
cheers