on 03-08-2010 11:50 AM
Hello friends,
I am facing a strange issue while doing an export to excel from WD table only in a production environment. The code works fine in dev and qa systems. the only difference is the lanscape where the production server is clustered wheras the other servers are of single node. The code i use to do the export is as below.
..get byte data
Resource= WDResourceFactory.createResource(new ByteArrayInputStream(tabledata_byte),fileName,WDWebResourceType.XLS,true);
wdContext.currentContextElement().setTableResource(Resource);
IWDWindow window = wdComponentAPI.getWindowManager().createNonModalExternalWindow(Resource.toString(),"Excel Window");
window.show();
Kindly let me know if there is anything to be done in a clustered environment to make it work.
Regards,
Karthikeyan R
hi,
maybe you can try createCachedResource.
Best regards,
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>Kindly let me know if there is anything to be done in a clustered environment to make it work.
Please clarify what is the problem with the code exactly.
BR, Siarhei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Karthikeyan,
I was also facing the same issue, and the reason was the diifferrence in the protocol of the J2EE WAS and that of Diapatcher.
check whether J2EE WAS and that of Diapatcher are both on http or on https. If they both are not same, that's the issue.
Hope it helps!!
Warm Regards,
Upendra Agrawal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.