Skip to Content
author's profile photo Former Member
Former Member

Anyone doing extensive custom development?

Hello,

Is there anyone out there who has done a lot of custom development with the MDK? I have uncountered numerous bugs/features which are really troublesome, and would like to exchange stories. The biggest aggravation I have had so far is that I have to keep starting and stopping the Mobile Engine after doing a synchronization. Any work-arounds found here?

Bill

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Feb 18, 2005 at 09:36 AM

    Hello Bill,

    please post some more information on your problem. As you will be aware of, the Mobile Engine has to be restarted every time a new mobile application or a new version of an application, an addon or a patch is downloaded and applied via the synchronisation process.

    For regular application communication (e.g. simple data synchronisation) no restart should be necessary.

    Regards,

    Tim

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Tim,

      Thank you for responding. I have a number of problems with Mobile development. These are not simple matters. Let's focus on the issues one at a time. We'll worry about my synchronization problems a little bit later. This discourse should be very valuable to the readers.

      Let's first deal with dependent and independent applications.

      I have an application that uses SyncBo. This application provides a local Material Master on the device. This material master is a tiny slice of the actual material master that resides in CRM system. This application was developed using the SmartSync wizard in Eclipse and the SyncBO builder in CRM. I ran the wizard and plugged in the meRepMeta.xml file from the backend, and then modified/extended the generated code by adding search capability and other front end things. This application is working well. Let's call this the independent application.

      I then started working on a dependent application. This application is looking up inventory, and therefore must access the material master on the device, without duplicating the material master or modifying it in any way. After the user selects the material he is interested in seeing inventory for, the application uses generic synchronization to get the inventory position.

      I began the dependent application by copying my material master application and making extensive modifications to it. Perhaps this was not the right strategy. Nevertheless, I completed the application, and everything seemed to be working find.

      Then I started to do some development testing. The first problem was that the materials in dependent application were duplicated. I also noticed that the material in the material master application were also duplicated. I am not sure what caused the duplication. I made some more modification to the dependent application, and the application began to exhibit intermittant behavior and eventually went down completely. That is where the application stands as I am writing this.

      After extensive debugging, I see that the variable SYNC_BO_DESCR is set to null after the following initialization, causing the entire application to fail upon startup:

      private static final SyncBoDescriptor SYNC_BO_DESC =

      DESC_FACADE.getSyncBoDescriptor(SYNC_BO_NAME);

      The variable SYNC_BO_NAME is the same in both independent and dependent applications, as is the file meRepMeta.xml. I tried a variation of the dependent application that uses the classes in the independent application to access the SyncBo. This variation did not have its own meRepMeta.xml file. This did not solve the problem.

      What do I do from here?

      Many thanks.

      Bill

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.