Hi Arun,
We were asking for client-side logs from the "Results" tab of the Developer Console. Those are server-side logs from the SmartClient Java Server. Since you are deploying to ASP.NET, the SmartClient Java Server shouldn't even be involved, these logs are irrelevant (by the way, the line you highlighted in the logs does not indicate an error).
Let's start over:
1. install SmartClient into your ASP.NET server using the Client Integration instructions
http://www.smartclient.com/docs/5.6/...up..iscInstall
2. Place your HTML file with your SmartClient application in your ASP.NET server
3. Ensure that the URL on the <soap:address> tag of your WSDL file has the same protocol (http or https) and port as the URL where you will access the HTML file on your ASP.NET server
4. As described under the WSDL Binding docs, use the WSDL tab in the Developer Console to obtain a .js file for your .wsdl binding. Just enter the WSDL url and pick "Download -> as .js". For this step and this step only, you want to access the Developer Console via the SmartClient SDK, not your ASP.NET deployment. Copy the resulting .js file to your ASP.NET deployment and add a <SCRIPT src=> tag to load it in your HTML file, after the SmartClient libraries but before any application code.
http://www.smartclient.com/docs/5.6/...p..wsdlBinding
5. Access the HTML file via your ASP.NET server
If you run into trouble, open a Developer Console from the HTML page served via ASP.NET, enable DEBUG-level RPCManager logging, reload the page, and capture the output in the "Log messages" area of the Results Tab.
We were asking for client-side logs from the "Results" tab of the Developer Console. Those are server-side logs from the SmartClient Java Server. Since you are deploying to ASP.NET, the SmartClient Java Server shouldn't even be involved, these logs are irrelevant (by the way, the line you highlighted in the logs does not indicate an error).
Let's start over:
1. install SmartClient into your ASP.NET server using the Client Integration instructions
http://www.smartclient.com/docs/5.6/...up..iscInstall
2. Place your HTML file with your SmartClient application in your ASP.NET server
3. Ensure that the URL on the <soap:address> tag of your WSDL file has the same protocol (http or https) and port as the URL where you will access the HTML file on your ASP.NET server
4. As described under the WSDL Binding docs, use the WSDL tab in the Developer Console to obtain a .js file for your .wsdl binding. Just enter the WSDL url and pick "Download -> as .js". For this step and this step only, you want to access the Developer Console via the SmartClient SDK, not your ASP.NET deployment. Copy the resulting .js file to your ASP.NET deployment and add a <SCRIPT src=> tag to load it in your HTML file, after the SmartClient libraries but before any application code.
http://www.smartclient.com/docs/5.6/...p..wsdlBinding
5. Access the HTML file via your ASP.NET server
If you run into trouble, open a Developer Console from the HTML page served via ASP.NET, enable DEBUG-level RPCManager logging, reload the page, and capture the output in the "Log messages" area of the Results Tab.
Comment