| Category | SAP Note | Description |
| Problem Reporting | 742674 | Required information for web dynpro problem reporting
You want to report a web dynpro problem. To help us working on the reported problem, please provide the following information. |
| 962319 | Detailed error messages with stack trace in Web Dynpro
The error messages raised by Web Dynpro for Java, part of SAP NetWeaver, don't have the required level of detail. |
| Compatibility | 718949 | Web Dynpro Application Compatibility WebAS SPx -> SPx+n
Will applications developed and run under a specific NetWeaver release and service pack SPx (e.g. SP8) run under SPx+n (e.g. SP9 or SP10) engines and vice versa? |
| HTML Client | 991449 | Web Dynpro and Microsoft Internet Explorer Version 7.0
Web Dynpro applications are not displayed in the browser version of Microsoft Internet Explorer 7.0, Exception is "Sorry, your browser/program is not supported by Web Dynpro!"
Solution: Microsoft IE 7 browser version will be supported starting with support packages NetWeaver04 SPS19 and NetWeaver04s SP10. If an earlier version of Web Dynpro is used, there are two possibilities to enable IE7 for Web Dynpro. |
| 706938 | Popup Blocker Enabled: Memory usage grows - Backend connections keep alive
Web Dynpro Applications do not terminate when the browser is closed or navigation to other applications/pages is triggered. Thus memory usage grows as well as backend connections and thus database locks keep open until http session timeout occurs (preconfigured to 30 min). Solution: Please deactivate the popup blocker for those URLs that point to the SAP Web Application Servers and/or the Enterprise Portal. |
| Controller Coding | 928485 | Do not use internal APIs (java.lang.NoSuchMethodError)
java.lang.NoSuchMethodError and due to the improper use of internal API other errors, side effects, program failure. See also Never Ever Hijack Internal Web Dynpro Classes and Interfaces ... |
| Deployment | 784677 | Deployment destroys other DC
Deployment of a Web Dynpro DC destroys another (previously deployed) DC. The thrown exception is "Cannot find repository information for ..." or other effects indicating that some data is missing (or is superfluous) in the Web Dynpro Runtime Repository.
Reason: A qualified name (for a class, Web Dynpro Application, Web Dynpro Component) must be used only in one DC. The DC concept provides assigning packages uniquely to a DC for reaching this goal. However, the DC tools do not enforce this restriction. If a Web Dynpro Component (or Application) with the same qualified name is contained in more than one DC then deploying one of the DCs destroys the meta data in the runtime repository of the other DC.
NOTE: Beginning with SAP NetWeaver 04s SP Stack 11 the deployment manager will check the existance of the same package in an already deployed DC during deployment. In case such a package collision is detected the DC deployment is aborted. This check will not be provided within SAP NetWeaver 04. |
| Adaptive RFC Model | 947376 | Troubleshooting JCo and AdaptiveRFC in Web Dynpro for Java
Problems when using JCo connections and AdaptiveRFC in SAP Web Dynpro for Java, part of SAP NetWeaver.- When using JCo connections to the backend some sessions in the backend stay alive though they are not refered to anymore.
- Test of JCo connection in Web Dynpro Content Administrator fails
- SSO ticket is expired when accessing backend systems via JCo connections
|
| 859950 | Inconsistent Metadata with AdaptiveRFC
- DataAccessException: Type conversion error, field ...
- Metadata Destination does not point to the same system as the Data Destination
- Displayed Type information (such as label texts or field lengths) are not consistent with the types information of the underlying ABAP backend system
- Metadata is not invalidated without J2EE Engine restart
NOTE: SAP is currently investigating a possible workaround to explicitly invalidate the Adaptive RFC Dictionary Cache within a non-productive, i.e. development or test environment, without mandatory restart of the SAP NetWeaver Application Server. This explicit invalidation could either be based on some workaround coding or on an additional administrative function "Invalidate Adaptive RFC Dictionary Cache" within the Web Dynpro console. SAP Note 859950 and this WebLog will be updated as soon as this workaround is implemented. |
| Session Management | 842635 | Session Management for Web Dynpro Applications- Web Dynpro session unknown
- Exception "SessionExpiredLongJumpException"
- Problems with Web Dynpro session management
- Error message like com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleExpiration, Session unknown, Request with URI={0} was sent to unknown session, com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException, Application session has expired
- Error message like Session expiration, Request with URI=<...> was sent to expired session, Destruction reason=<...>
|
| 842878 | Switch on traces for Web Dynpro session management in NW04
In case of problems in Web Dynpro session management (e.g. an application instance isn't terminated as expected, unexpected session expired messages), switch on the tracing of the Web Dynpro runtime. |
| Internationalization | 947081 | Locales, languages, date and time formats in Web Dynpro- A wrong language or locale is used after you logged on to the system?
- Calendar dates are formatted in an unintended way?
- Language change in the portal (through portal personalization) does not get immediately reflected in the Web Dynpro iViews?
|
| Business Graphics | 704604 | Business Graphics and/or Geo Maps are not displayed
Business graphics and/or GeoMaps are not displayed in Web Dynpro. Solution: Maintain the default of URL of the IGS. |
