02-24-2009 08:56 AM
Solved! Go to Solution.
02-24-2009 09:00 AM
When you have compiled your cod file (with siblings) do the following.
Rename it to zip file.
If it unzipped ok - delete zip file. If it cannot be unzipped, there are no siblings inside. Rename zip file to cod.
Do not edit jad file manually. It is not necessary.
02-24-2009 09:29 AM
02-24-2009 09:35 AM
There is nothing to be edited in jad file manually.
If jad file does not contain references to sibling files - it means that there are no siblings inside the compled cod file.
02-24-2009 09:53 AM
03-16-2009 09:49 PM
What does the jad file end up looking like?
I finally had to cross the threshold and I'm getting someone appending
RelativeCodIndex=1 to the query string but now that I set up to respond to this no one
asks any more and I just get the error.
Do you have a sample jad file or is this transparent?
03-17-2009 08:58 AM
It seems if you run UpdateJAD on the input jad, it will in fact create new cod entries
so the jad probably does need to be fixed. I haven't gotten anyone to try a download
yet but none of the other approaches have worked so far.
Apparently the RIM-COD-URL-n doesn't require that "n" corresponds to midlet
or module numbers, at least that is what I'm hoping