APIbridge plugin tutorial - installing widget in s60 emulator

[alexisread]

I've been looking at the APIbridge plugin tutorial, it says you can install the echoServlet widget (for testing) by opening the file in the s60 emulator.
I can't seem to install any widget via this method, in fact the only thing i've managed to install this way is the dwindle java game.

I'm sure the emulator is working ok as the contacts/menu/sms etc all works, and the test carbide apps work fine. The ecom plugin project builds without errors as well. I'm using 5th ed SDK.
The error I'm getting when installing the widget is 'Application Closed: installer' which isn't much help - I don't know where to find the logfiles from the emu.

Is it possible to install widgets or do I need to manually paste the files into a widget folder?

Any pointers would be great!

[gurmukh]

Hi Alex

I managed to get it to work, although it took me a while!

To get it to work, I launched the N97 emulator seperatly (not from within Carbide). Then installed the widget (from filemanager). Once it was installed. I then closed it, started up Carbide and selected "build and run". This launched the n97 emulator. Once it has successfully loaded, I simply launched the app and saw the responses from api bridge.

HTH

[alexisread]

Thanks, once you'd said it could be done, I had another crack at it. After a couple of re-installs of the SDK it worked - I guess the SDK wasn't originally installed properly after all. Just got to write the plugin now!

[mail2kul]

Hi,
I am having issue in loading my custom plugin dll with the APIBridge.exe. When I request for services provided by custom DLL, I get 404 APIBridge returned Error:Not Found from the echoTest sample.

EchoServlet works fine for the path /sample/echo

I modified the path to /sample/test in the wwidget and created different plugin registered for the path in the widget. i get above mentioned error. I tried out all possible methods to resolve but no success.

It would be great if someone provides TIPS for the new plugin creation.


Thanks,

Mallik

[mail2kul]

I resolved the issue: my custom plugin was not getting loaded with the APIBridge.exe. stupid reason behind it is naming convention in the .mmp file.

Name should have DLL UID in TARGET of mmp .file.

projectname_<DLL UID>.dll
earlier i had given only
projectname.dll so it was not getting loaded.

I think ApiBridge.exe loads custom dll referring its DLL UID in the dll name.


Regards,

Mallikarjun

[diogomoreira]

Hello everybody,

You could run the custom plugin on any device? Example N97!

Do you have a document can help to create the file .pkg for EchoTest example?

Thanks !

[swarupk2007]

Hi,
I am having same problem for plugin creation as Mallikarjun.

I am having issue in loading my custom plugin dll with the APIBridge.exe. When I request for services provided by custom DLL, I get 404 APIBridge returned Error:Not Found from the Test example.

EchoServlet works fine for the path /sample/echo

Also checked following solution :

Name should have DLL UID in TARGET of mmp .file.
projectname_<DLL UID>.dll


I modified the path to /sample/test in the widget and created different plugin registered for the path in the widget. i get above mentioned error. I tried out all possible methods to resolve but no success.

It would be great if someone provides TIPS for the new plugin creation.

Can anyone tell me what can be the cause of the problem?
I have even tried changing UIDS or keeping same as EchoServlet example.
Can anyone tell how the Implemention UID is generated ?
Is there any doc explaining how APIBridge server check for DLL for loading it ?
I have checked rss ,mmp,proxy files for naming conventions and UID'S but dont know the cause of the problem............

Thanks,
Swarup

[swarupk2007]

I tried changing the path from /sample/echo to /sample/test in EchoServlet sample app and it does not work now even if I reverted the path to original /sample/echo. Is there any solution for this ?

[swarupk2007]

I have resolved this, Implementation UID has to be unique and clear the rsc and dll files generated previously and build the application again.