Originally posted by Patrick Wang:
My answer is:
1) Gather user��s requirement 2) Explore, analysis and design system architecture, select tools. 3) Software Architecture Design. 4) Finish coding 5) Unit Testing and performance tuning 6) Support customer.
Originally posted by Mark Herschberg:
Any employer with a clue will want the developer to know Java. Frankly, J2ME isn't really much different from J2SE or J2EE. The Midlet lifecycle isn't that complex, and most APIs behave in expected ways. The only trick, as I noted above, is that you have very limited resources, and need to know how to get good Java performance.
Employers without clues will want 5 years of J2ME experience.
Originally posted by Neha Sharma:
Just a question, Saran, for My own Info. Why would anyone use Applets and Swings etc, when you have the power of JSPs
Originally posted by M Arshad:
Sorry Buzz if I hurt your sentiments.But that is specifically meant for those who try to expoil the discussion.
Originally posted by Miftah Khan:
I don't believe this is possible. I checked the HTML 4.01 specification.
I want the request.parameter value different from what the Button dispalys.
Originally posted by Yongping Wang:
100% java code can do such task but it is sort of time-consuming.