 |
|
|
|
|
|
If you own a website that related to mobile developers you are welcome to participate in our website. |
|
| Join our partner list |
| Outsourcing online portal |
| Web Development Forum |
|
|
| | |
|
|
Article - Mobile Developers And Outsourcing In East Europe on Web Development Forum |
 |
| Website about Mobile Developers - Outsourcing portal. Other useful information: stylesheet" type="text/css" media="screen" href="http://blog.vufone.com/wp-content/plugins/sociable-zyblog-edition/sociable.css" /
J2EE: EJB, JSP, Servlets, JSF, JSTL, JCA, JMS, JTA, JNDI, JDBC, JMX, RMI, etc.
Frameworks: Struts, Hibernate, JPA, iBATIS, JBoss AOP, Spring, JSF, AJAX, GWT, YUI, Flex/Flash, JUnit, and Jakarta common libraries.
Integration: Web Services on Axis and WebMethods; as well as the Web Service Standards such as SOAP, WSDL and UDDI.
| | For you information - For Any Supply Chain Function, The Most Significant Decision Is Whether To Outsource The Function Or Perform It In-house. The Decision To Outsource Is Made At A Strategic Level And Normally Requires Board Approval. |
| Mobile Developers | Vufone Blog - mobile phone backup, sync and sharing
Almost a decade ago, in the JavaOne conference of 1999, Sun Microsystems introduced a new Java Virtual Machine for small-memory, limited-resource, connected devices, such as mobile phones . The first K Virtual Machine (KVM) was demonstrated on Palm OS, as a proof of concept. Since then, it has become part of the Java 2 Micro Edition (J2ME) platform , or as it is called now, Java ME. Today, Java ME is the most common application platform for mobile devices, including most GSM and iDEN phones and some CDMA phones , such as those that are provided by Sprint in the US. The importance of Java ME is that it has opened mass-market phones that are running embedded operating systems to third party application developers. However, the main challenge now is how to develop an application that would be portable across different devices, seamlessly.
Although most mobile phones today support Java ME, it doesn’t ensure any compatibility between them. Realizing the different capabilities of different devices, Java ME is not a monolithic platform. A specific Java ME runtime environment is defined by 3 layers: configuration, profile and optional APIs. Most mobile phones support the Connected Limited Device Configuration (CLDC). On top of that you will usually find the Mobile Information Device Profile (MIDP). But, when it comes to optional APIs, the number of combinations is enormous. Each API is defined in a specific Java Specification Request (JSR), which is denoted by a number. Common examples are JSR-75 , which includes the PIM API and the File Connection API, JSR-82 , which specifies the Bluetooth API, and JSR-120 , which specifies the Wireless Messaging API. Many applications require one or more optional APIs. The vufone mobile application, for example, requires JSR-75 and JSR-120.
Mobile Developers | vufone blog
.broken_link, a.broken_link {
text-decoration: line-through;
}
vufone blog
About
Downloads
Jan 13
CTO Corner: Java Micro Edition in a Nutshell
CTO Corner , Uncategorized 4 Comments »
|
|
| |
|
