You Are Here:

Community: Blogs

Hartti Suomela's Forum Nokia Blog

Who would need JNI for Java ME?

hartti | 21 May, 2007 08:36

Java ME (MIDP over CLDC) does not allow access to native APIs - in other words, JNI (Java Native Interface) is not implemented. However, I was asked to gather feedback from mobile developers, if there is interest in accessing native functionality from MIDlets. Of course this would require that there would be some way to do native programming, which sort of leaves Series 40 out of the question (when speaking of Nokia developer platforms).

 

Now, feel free to give us your comments. Either to me directly, or as a response to this blog post. If you do not want to get your feedback published, remember to write "DO NOT PUBLISH" in the beginning of your reply. (..or you could also use my screen name in Forum Nokia discussion boards).

 

And, instead of not just saying "Yes!" or "Interested", could you please note why you would need it (like getting around the limitations on the Java ME, performance, or something else), and if you are representing some company/application, please state that too.

 

Final note: Please remember, that this is feedback gathering. Not a promise to implement this kind of functionality (but your feedback is valuable in making decisions!)

 
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fpaulE2dcoultonsE2dforumE2dnokiaE2dblogE2farchivesE2f2009E2f04E2fX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ