Advices required for a JAWT implementation for Windows Mobile 5 and 6

Question

Hi,
I want to create a jni bridge in order to open a player in a java Frame. This player works fine in a mobile native application.
I want to know if somebody tried already to create such a bridge keeping in mind that this is for mobile environment. If yes, is there some specific problems which I should be aware of?
Specifically I have 2 problems.
1. My jni getHWND method always return 0.
JNIEXPORT jint JNICALL Java_JavaRMEngineInterface_getHWND
(JNIEnv *env, jobject obj, jobject component){
     HWND hWnd = 0;
//try {
typedef jboolean (JNICALL PJAWT_GETAWT)(JNIEnv, JAWT*);
JAWT awt;
JAWT_DrawingSurface* ds;
JAWT_DrawingSurfaceInfo* dsi;
JAWT_Win32DrawingSurfaceInfo* dsi_win;
jboolean result;
jint lock;
bstrt jawtPath = "\\Windows"; // Put Path String from jrePath to jawtPath
//Load AWT Library
if(!_hAWT)
//for Java 1.4
hAWT = LoadLibrary(jawtPath + bstr_t("\\jawt.dll"));
//if(!_hAWT)
//for Java 1.3
//_hAWT = LoadLibrary(jawtPath + bstrt("\\awt.dll"));
if(_hAWT)
PJAWT_GETAWT JAWT_GetAWT = (PJAWT_GETAWT)GetProcAddress(_hAWT, L"_JAWT_GetAWT@8");
if(JAWT_GetAWT)
awt.version = JAWT_VERSION_1_3; // Init here with JAWT_VERSION_1_3 or JAWT_VERSION_1_4
//Get AWT API Interface
result = JAWT_GetAWT(env, &awt);
if(result != JNI_FALSE)
ds = awt.GetDrawingSurface(env, component);
if(ds != NULL)
lock = ds->Lock(ds);
if((lock & JAWT_LOCK_ERROR) == 0)
dsi = ds->GetDrawingSurfaceInfo(ds);
if(dsi)
dsi_win = (JAWT_Win32DrawingSurfaceInfo*)dsi->platformInfo;
if(dsi_win)
hWnd = dsi_win->hwnd;
ds->FreeDrawingSurfaceInfo(dsi);
ds->Unlock(ds);
awt.FreeDrawingSurface(ds);
return (jint)hWnd;
//}catch()
return (jint)hWnd;
2. this second method throw an "error C2100 illegal indirection" at the last line on g_hwndMain.
JNIEXPORT jboolean JNICALL Java_JavaRMEngineInterface_construct
(JNIEnv *env, jobject obj, jlong peer, jint hwnd, jlong top, jlong left, jlong bottom, jlong right, jstring lpszSystemLanguage, jint nCacheSize){
     CRMEngineInterface cpp_obj = (CRMEngineInterface)peer;
     HWND g_hwndMain = (HWND)hwnd;
     HDC hDC = ::GetDC(g_hwndMain);
     SIZE size;
size.cx = (LONG) right - (LONG) left;
size.cy = (LONG) bottom - (LONG) top;
     TCHAR sInstallDir[MAX_PATH];
     ::GetModuleFileName(NULL, sInstallDir, MAX_PATH);
     TCHAR* pEndPath = _tcsrchr(sInstallDir, L'\\');
     if (pEndPath != NULL)
          *(pEndPath + 1) = 0;
     TCHAR sContentDir[MAX_PATH];
     memcpy(sContentDir, sInstallDir, MAX_PATH);
     UINT nCacheSizeCPP = (UINT) nCacheSize;
     return *cpp_obj->construct( hDC, g_hwndMain, size, sInstallDir, sContentDir, 0);
Any advice will be very helpful.

Answer 1

Hello Brian,
the client technology is based on web dynpro, but it runs in an own Mobile Client. Therefore you do not need the internet browser for the application.
During the client development you can use the web dynpro tools to design the layout and the screen flow of your application. In the last step you can deploy the application to your mobile client and run it without a browser.
The mobile client includes a web dynpro runtime to display the data. Therefore you do not need a J2EE server in order to run an application.
The mobile occasionally connected scenario provides a api to access the local database. NetWeaver Mobile 7.1 for PDA supports two different databases:
1. MinDB ( from SAP, included no additionals license fee required )
2. DB2E
NetWeaver Mobile includes a complete queing mechanism.
You can also take a look into two eLearnings which provide a good technical overview:
Link:  [Architecture and Runtime|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e048e20c-7246-2a10-e8a5-8b2b78b5b994]
Link: [Development Cycle and Tools|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/204fc387-6646-2a10-99b7-bba030bc3f68]
Unfortunetly there is no fixed timeline for WM6.But I guess this will be available soon.
I'm afraid but also don't know of any fixed timeline regarding Adobe Interactive forms.
The architecture of NetWeaver Mobile 7.1 is pretty new and full of great new functionalites. The User Interface for NetWeaver Mobile 7.1 uses eSWT to render the UI elements.
Best Regards,
Stefan