Blank html popups in a mobile webdynpro application

In a web dynpro application, each time we move from one view to
another, or from DC to another a blank html page in being opened
(besides the target one)
the url of the blank page is : \tcwddispwda\global\SSR\html\blank.html
<b>this is happening when we open the application in a PDA mobile device
(with Win CE 5.00 inside)
and it does not happen in a regular pc.</b>
any adeas ?
thanks
Morad Zeidan

Open an OSS message.
Armin

Similar Messages

Error while running the mobile webdynpro application in PDA

HI All,
I have created an online mobile Web Dynpro application. We have deployed the application in the portal and its working fine.
Now I am trying to run the applicaiton in a PDA via the portal link and it is giving error.
Scripting Alert:
An error occured while starting the iView.Application
/Webdynpro/dispatcher/sap.com/pb/PageBuilder;jsessionid=(hostname_systemID_system Number) Will run with a wrong client window ID! Do not continue Please report this problem to your administrator.
These are my PDA configuration :
PDA with OS = WM 6.0
Crème = CrEme329_ARM_CE42_PPC.exe
DB2E 9.22
Please provide the solution or hints to solve the problem.
Thanks and Regards
Neha Mahanty
This is the configuration of my PDA :-
OS = WM 6.0
Crème = CrEme329_ARM_CE42_PPC.exe
DB2E 9.22

HI Ashutosh,
I tried with both PieClient and Pie03Client.
http://Hostname:Port/webdynpro/dispatcher/accenture/Dashbrd/SupervisorApplication?SAPtestId=8sap-wd-client=PieClient
http://Hostname:Port/webdynpro/dispatcher/accenture/Dashbrd/SupervisorApplication?SAPtestId=8sap-wd-client=Pie03Client
But I got the same results :-
1. The button is not working.
2. I cannot select any particular order as the List box is displayed like a box with all the orders visible in the screen.
3. and obviously the date field is not working and I'll try with the drop down.
Can you please suggest what else should I try.
Thanks and Regards
Neha Mahanty
Edited by: Neha Mahanty on Oct 14, 2008 12:58 PM

How to Execut Mobile WebDynpro Application in Blackberry simulator.

Hi experts,
I've developed an application in webdynpro using NWDS, now i want to execute it in Balackberry simulator. I have followed this link for downloading the blackberry simulators.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/b2b0c072-0901-0010-ec93-ad7df7f2a8f6?rid=/library/uuid/32c0278c-0901-0010-e0ae-9806236443f3 [original link is broken]
I've installed following softwares[Simulators]:-
1. Install BlackBerry JDE v4.0.x
2. Install BlackBerry Handheld Simulator v4.0.x (use the JDE number)
3. You have installed the Mobile Data Service (MDS) and the handheld or device simulator. To use the BlackBerry Simulator, first open the MDS, then the device simulator.
I'm unable to understand this 3rd point....
Now i don't know how to go further about this. So please help me out....
Thanks in advance.

Hi Ali,
If you have installed the blackberry simulator, you need to simply launch it using the shortcut.
3rd point simply ask you to check that you hae installed the simulator.
When you will launch the device simulator, go to the browser of the simulator and type in the url for the application there.
Simulator is just like the device. You open the browser then use it to run any url. In this case you have the url to launch the Mobile Web Dynpro application.
Regards,
Ashwani Kr Sharma

Bugreport: Popup LOVs in jQuery mobile Smartphone Applications

Hi APEX Team,
I just looked at Popup LOVs for mobile, as this is a supported item type.
Unfortunately this wasn't adapted to JQM and still has a Desktop definition.
Somehow the created HTML isn't valid, seems there are duplicate CSS-File inherits and some unnecessary closing tags.
Also the pagination doesn't work. When requesting the next set of rows the font switches to tiny and doesn't show any results anymore.
Wishlist: Improve Popup LOV Templates so that developers have full control over structure of the page, the search items, buttons and result sets. Then we could adapt the template to use JQM Dialog. Having control over opening link (javascript) and choosing the result (javascript) would also be fine :-)
thanks,
Peter
get Syntax Highlighting for the Application Builder: http://apex.oracle.com/pls/apex/f?p=APEX_DEVELOPER_ADDON:ABOUT:0:::::
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
BuilderPlugin: http://builderplugin.oracleapex.info
Work: http://www.click-click.at and http://www.wirsindapex.at
Fantastic Plugins for APEX: http://www.tryfoexnow.com

Thoughts anyone?

Mobile WebDynpro Sample Application Problem

Hi,
Iam new to MI Technology, I have couple of doubts.
I have a application which is already developed using Java Webdynpro, now i want to view the application in the mobile. What should i do in-order to show it in a blacl-berry device. If so what all configurations need to done in SAP netweaver Studio. Is any softwares needs to be installed , I am using SAP Netweaver Portal 7.0 SP10. Also could anyone help in create a sample project(Step By Step ) .

Hi Sankar,
Any webdydnpro application can be viewed in the black berry emulator (UI elemnts rendering will be different though)
You need to have MDS and blackberry emulator installed on your system.
Run the webdynpro application make note on the URL and type the same URL in the blackberry browser.
Check the following Wikis:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/mobile/mobileWebDynpro-Alwaysconnected+client

How to create a popup view in mobile application?

Hi folks, i need some help to do popup window in mobile application, i see that mobile don´t have a wdComponentAPI that is a controller of Web Dynpro JAVA, so what i´ll should do?
So, thats it

Hi Ronaldo,
I suppose there is no such API for handheld applications.I have another suggestion.
You can also create another view (the popup view) and make it behave like a popup.
So, on an event handler of the first view, for ex click of a button, you fire the outbound plug of this view which is linked to the inbound plug of the popup view.This will bring up the popupview - the first view will be unloaded from memory.
In the popup view, on an event handler (for ex OK button), fire the outboundplug which is linked to inbound plug of first view.So the first view gets loaded when the Ok button is clicked.
To ensure that you dont loose the data on the first view, make sure that the controls on the view are bound to context attributes.
I hope this helps.Let me know if you have further queries.
Best Regards,
Amit

How to Call a WebDynpro application through html page.

I have created a webDynpro application.How can i call this application through a html page?
Thanks
Pankaj Kumar

Hi,
   You can add a link to your HTML page and set the anchor reference to the absolute URL of your WD application.
   The absolute URL of your WD application looks like
http://<j2ee server>:<port>/webdynpro/dispatcher/<wd component name>/<application name>
   So your HTML code will look like:
<a href="http://<j2ee server>:<port>/webdynpro/dispatcher/<wd component name>/<application name>">Link</a>
Regards,
Satyajit.

Webdynpro application in mobile

Hi friends ,
i have developed a webdynpro application.when i called the url in my system application is opening,but when i call the same url
its getting dump im my mobile showing rabax_state .can we directly call the urls in our mobiles .is there any configuration is required.

Hi Sudhir
if you want to develop a 'webdynpro' application specifically for mobile, then you will have to create a 'Mobile' web dynpro application (which is a separate design environment from WD). Please refer to below given link for the same
For laptops
<http://help.sap.com/saphelp_nwmobile71/helpdata/EN/8b/0b674240449c60e10000000a1550b0/frameset.htm>
For handhelds
<http://help.sap.com/saphelp_nwmobile71/helpdata/EN/8b/0b674240449c60e10000000a1550b0/frameset.htm>
Best Regards
vaidehi
Edited by: Vaidehi Pandya on Dec 15, 2010 11:13 AM

ABAP WEBDYNPRO Application Administrative DATA URL HOST & PORT empty/blank

My ABAP Webdynpro applications do not display the preview layout in SE80 just white page - no errors ANYWHERE.
Also in SE80 the properties on the application look like: https://:/sap/bc/webdynpro/sap/z_rep_text. Don't know why https, but I think if I could figure that out I may resolve the issue. Can't see why trying to run HTTPS, then the host & port are empty.
I have been reading SDN posts & notes for days on this. I HAVE ACTIVATED ALL SERVICES that is not the issue. This works fine in our QA system so I know it is some sort of configuration in the development system that is causing this issue.
We just applied support packs to 23 on SAP ECC 6.0. SAP_ABAP, SAP_BASIS 7.0 level 23. This was working before patches. There had to be some note that changed what WEBdynpro's look at so now development is no longer working.
Any suggestions would be appretiated.
Regards,
Diane Szmurlo

We found that the profile parameter login/ticket_only_by_https was set to 1. Once we changed to 0 everything worked fine.

WebDynpro Application for WinMobile 6.5

Hi Experts,
Can anybody tell if there is an official SAP statement that WebDynpro supports or not Windows Mobile 6.5 devices? I can not find anything about that in the PAM.
WebDynpro supports the URL Parameter sap-wd-client=PieClient to render WebDynpro applications on mobile Devices (Pocket Internet Explorer in our case). Our application works fine on a 5.5/6.0/6.1 device but with view bugs on a 6.5 device (seems that using ParameterMapping on IWDButton and IWDLinkToAction is ignored).
Regards
Michael

Hello Michael,
Windows Mobile 6.5 device has to be certified and for this the customer vendors should contact SAP to get it certified.
So, new devices that come out with 6.1 and later versions shall be supported by SAP, provided the devices are certified. Certification will be on a "device-level".
So, all you have to do is to ask your device vendor to get the devices certified with SAP.
So, if a device vendor wants to get a device certified - then they can approach SAP. We shall do the testing and then certify that the device can run SAP NetWeaver Mobile client. So, it does not matter if the device OS is 6.0 or 6.1 or later. We shall certify the device, and then customers can run the application on the certified mobile device.
I hope this helps you.
Regards,
Blanca

HOw to start the project for first view in webdynpro application

Hi,I am having a problem regarding scenario for customer feedback for portal end user i.e..wen user login to a application for feedback there it check the Id of the user wether it had given the feedback or not by comparing the Id with the database Idu2019s from SQLserver.If the feedback is thr of that Id then a view shud say u hav already given feedback otherwise feedback form shud open ,the user will giv feedback and closes by thanking with other view.My problem is how to openthe view were it will compare the userlogin Id with the database Id to move further.How shud I handle this scenario for first view.I am creating this application in webdynpro.In this project how shud I manage the viewsu2026

Hanif,
you can create a webdynpro application and create an iview and set the height and width to 0 .inside that webdynpro application open a popup that provides the feedback form .and you invoke this popup window in the WDDOINIT() or WDDOMODIFYVIEW() of the webdynpro main view.
apart from this you need to get the logged user id in main view and get the output from database whether you want to open the feedback form
check this forum on developing webdynpro application
Web Dynpro Java
Thanks
Bala Duvvuri

Refresh problem of Webdynpro application which is wrapped in a BSP IFrame

I have a BSP Iframe inside which I am calling a webdynpro application ('zwdc_re_replenishment'). The requirement is that this WD application should be reloaded whenever a timeout occurs. Currently, when there is a timeout, an error is shown.
In order to achieve this, for this WD Application , I have a SICF node to which I have attached a customized Errorpage via the option 'Redirect URL'.
Whenever the WD application undergoes a timeout error, my custom error page is called which is named as errorpage.htm. On this page in the 'OnInitialization event', I try to call the WD application URL again (via the following code) which should reload the application. But instead I get a blank page.
CALL METHOD cl_wd_utilities=>construct_wd_url
EXPORTING
    application_name = 'zwdc_re_replenishment'
IMPORTING
    out_absolute_url = lv_def_url.
response->redirect( url         = lv_def_url
                    permanently = 1 ).
Just as a note I have already tried out the following methods as well but nothing works
*navigation->exit( lv_def_url ).
*navigation->call_application( lv_def_url ).
Is this because my WD application is inside a BSP Iframe and therefore reloading it manually does not work ?
Please help!
Thanks.
Sukanya

Hi Thomas,
First of all, thanks a lot for replying !!
Sorry for the confusion. Although seems like you have answered my question already.
Actually the requirement for embedding WDA inside a BSP Iframe came up since there are some WD report applications that are accessed by very controlled environments in which the users were not able to close the WDA session directly (without the IFrame) and were getting some errors. Hence the WDAs had to be wrapped inside BSP IFrame which solved the above problem.
I am working with only one BSP app which has the Iframe and one WD app which is called within the BSP app.
Now, the other requirement that came up was that whenever the WDA session inside the BSP IFrame expires, there should be no error page and instead the WD app should be reloaded.
So I was trying to reload the WD App in the following way.
1. For the SICF node of WDA, I attached an errorpage.htm for all the tabs under the tab 'Error Pages'. I have defined this errorpage.htm inside the same BSP App which has got another default.htm page. So the BSP App has 2 views : default.htm which has the IFrame and Errorpage.htm.
2. So now when the WDA expires, the events of errorpage.htm are called like OnInitialization, In this event I was calling the methods navigation->exit( 'URL of the same WDA' ).
I did this because I wanted to reload the WDA whenever it expires. I tried to specify the WDA Url in the SICF node of the same WDA in 'Redirect URL' under the Error Page tabs but it didnot work.
Now I realize this is not gonna work. I didnot want to modify the WDA and so I didnot specify any exit plugs in the WDA which would have taken care of reloading the WDA. But that seems to be the only way out.
Actually speaking there are multiple WDAs which will open inside the same BSP IFrame via their own Application URLs. I have coded the BSP IFrame to read the URL Parameters and open up the corresponding WDA. So now I have to define an exit plug in all of these WDAs.
Do you suggest that this will solve the problem of WDA refresh ? Just to confirm.
Thanks again.

How to open a pdf file in Acrobat Reader from a webdynpro application

Hi,
I need to open a pdf file stored in the server from a web dynpro application. The pdf needs to be opened in the stand alone reader at the client and not in a reader embedded in the browser.
Cheers,
Krish

Hello,
I'm fairly new to webdynpro and am trying to render a pdf via webdynpro.
The webdynpro application runs but I see only a blank screen with the title.Is there any specific setting I need to do in order to view this pdf?I have used the FileDownload-UIElement.
Thanks in advance
Biraj

Error while running webdynpro application with an Interactive form

Hi all,
I am getting the following defect when I run a adobe interactive form (webdynpro application). Any pointers?
Regards,
Deepak
500   Internal Server Error
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:464)
    ... 47 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Oct 10 10:17:00 EDT 2007
J2EE Engine 7.00 patchlevel 109044.44
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Thu Oct 18 17:39:22 EDT 2007 (Java Time: 1192743562661)
Web Dynpro Code Generation Infos
local/NIBCOSecurityFormWD
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates (unknown)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:418)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:123)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:340)
     ... 29 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:408)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3948)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)
     at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
     ... 32 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
     ... 35 more
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:464)
     at java.net.Socket.connect(Socket.java:414)
     at java.net.Socket.<init>(Socket.java:310)
     at java.net.Socket.<init>(Socket.java:125)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:648)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
     at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
     ... 37 more

Hi Deepak,
If you have solved the issue could you kindly close the thread with the solution as this will help others as well. If not kindly update the thread with the status.

Error while previewing deployed webdynpro application.

Hi,
I am a newcomer to the EP environment. After installing the server and configuring NWDS, I created a simple webdynpro application. I was able to successfully deploy it to the portal but when I try to preview it I got the following error. Please shed some light on this. I am working on EP 6.0.
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC local/Test_WD:
SapDictionaryGenerationCore: 6.4019.00.0000.20061005103449.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:17:59[UTC], changelist=419709, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4019.00.0000.20061005104005.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:23:05[UTC], changelist=419717, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4019.00.0000.20061005103956.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:11:19[UTC], changelist=419716, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4019.00.0000.20061005104024.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:50:52[UTC], changelist=419718, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4019.00.0000.20061005104024.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:50:52[UTC], changelist=419718, host=PWDFM026)
SapGenerationFrameworkCore: 6.4019.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:10:28[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4019.00.0000.20061005104123.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:27:18[UTC], changelist=419723, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4019.00.0000.20060119123716.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:15:01[UTC], changelist=385561, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4019.00.0000.20061005103956.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:11:28[UTC], changelist=419716, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4019.00.0000.20061005104123.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:27:47[UTC], changelist=419723, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_05-b04, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/api/IWDEventHandlerId
     at java.lang.Class.getDeclaredConstructors0(Native Method)
     at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
     at java.lang.Class.getConstructors(Class.java:865)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:68)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.<init>(DelegatingInterfaceView.java:44)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:131)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi,
In NWDS, have you depoyed this application? while deploying does it throw any error??or successfully getting deployed? for deploying the application please choose deploy and Run option.This will deploy as well as run your application.
Regards,
Ameya
Message was edited by:
        Ameya Pimpalgaonkar

Blank html popups in a mobile webdynpro application

Similar Messages

Maybe you are looking for