• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
Bartenders:
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

OTA Provisioning

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To properly deliver J2ME applications OTA our server should have these mime types configured.

jad :text/vnd.sun.j2me.app-descriptor
jar :application/java-archive

I already check that tomcat 5 above already configure correctly ( conf/servler.xml).
But I still cannot use when i try using Sun wireless toolkit ->OTA provisioning.They say..no JAD file cannot found on this URL..
Any suggestion?
 
Saloon Keeper
Posts: 25608
183
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Try issuing that URL from a desktop web browser and see if it works. If it does, you may have a problem finding the server via the OTA HTTP connection, either because of DNS issues or security rights (including improper app signing).
 
Ashiela Papu
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I check its url into web browser, it's work.
Hmm....dns issue/ security signing? Could you explain more?
How it affect with OTA provisioning works.
 
Tim Holloway
Saloon Keeper
Posts: 25608
183
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you have a DNS problem, the phone won't be able to lookup the URL and resolve it to an IP address. Another problem I didn't think of earlier could be if there's no internet path between the phone and the server. Both of these can be checked by manually entering the URL in the phone's web browser.

If you do OTA provisioning, you'd normally have to digitally sign the app. When installing the app via a direct connection (WiFi, Bluetooth or USB), which you'd normally do for testing purposes, signing may not be required. App signing is for 2 reasons:

1. The phone company usually controls the signing process, so you'd have to pay them a fee.

2. It protects everyday phone users by ensuring that their phone won't be casually infected by a rogue app. The phone company has asserted that the app was built by a developer whom they declare it trustworthy (because their phone verified the signature).
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic