ERROR - Problem Reading Data From Server - java.io.EOFException

[Former Member]

Hi All,

I am using MII v12.

I need to generate table data dynamically. So I am using transaction to generate the table HTML code which will be like "<table><tr><td>col1</td>......</table>". This value is assigned into a string output parameter.This parameter value is fetched from APPLET and displayed on the web page.

This is working fine for small table data. But for large table data its giving the following error in java console.

"ERROR - Problem Reading Data From Server - java.io.EOFException"

document.iCommandApplet.executeCommand() is returning false.

When the transaction is executed from BLS, it is displaying the whole large data in the tracer. When executed through Xacute QRY its working.

But it is failing in web-page, when executed through APPLET.

Please suggest what might be the problem and what should be done to solve this.

Thanks,

Nalini

[Former Member · Accepted solution]

Hi Nalini,

1.

I don't know if you have heard about the possibility to assign XSL Stylesheets to a MII query

maybe this is another way for u creating HTML Dynamically.

So the output of your Transaction will be in MII XML Format an you assign a Stylesheets in a

Servelt call to build your HTML Table. This link gives you a good starting point to investigate:

2.

Suggestion: Let your Transaction save the Table to an HTML file. Call this HTML Page in an iframe

on your main page. Refresh the iframe after execution of your Transaction. So u don't need to worry about putting to much characters in your Output String (every thing in life has a limit ).

Hope that helps

Ciao

Martin

[Former Member · Accepted solution]

Hi Martin,

Thanks for the ideas and samples shared.

Solution 2 didnt work as there is a problem with cache.

The file in the cache is being loaded when the iframe is refreshed.

Solution 1 worked.

Transaction generates XML output.

XSL is written according to the requirement.

<SERVLET> is used to map XML with XSL to genearte HTML output.

<SERVLET> code is included in an iFrame and the iFrame is refreshed whenever required.

Thanks,

Nalini

[Former Member]

Hi Martin,

Thanks for the ideas and samples shared.

Solution 2 didnt work as there is a problem with cache.

The file in the cache is being loaded when the iframe is refreshed.

Solution 1 worked.

Transaction generates XML output.

XSL is written according to the requirement.

<SERVLET> is used to map XML with XSL to genearte HTML output.

<SERVLET> code is included in an iFrame and the iFrame is refreshed whenever required.

Thanks,

Nalini

[Former Member]

Hi Nalini,

How does the Transform URL of the XSL file look like..I guess you used XML Transformation action block..? Where did you store the XSL file ?.

cheers

Domnic