Main
Posts
Links
Most Read Items
Twitter Feed
johnwargo:
Here we go - First-time smartphone buyers favor Android over iOS: http://t.co/mQwxRHDP
johnwargo:
Ummm, eating a handful of Dark Chocolate M&M's So good!
johnwargo:
Working on the book's preface, hard 2 keep myself from saying 'the book you hold in your hand' since many won't ever actually hold the book
johnwargo:
When sending an email to a group, why is it that Lotus Notes is smart enough to not send me a copy if I'm in the group but Outlook isn't?
johnwargo:
Staying at a hotel without a gym. Ugh. I didn't even think to check to see if they had one, assumed they did.
Powered by Twitter Feed
| Remarks |
 |
 |
 |
| Wednesday, 16 September 2009 06:36 | |||
OK, couple remarks.
1. I never heard anybody wrote on BlackBerry forums that JSR 172 is "junk".
2. JSR(172) is "baked" into J2ME (or Java ME) not Blackberry SDK, - JDE does not have that "little utility" to generate stub classes. Author had to admit that one has to install additional 'stuff' (WTK, or SDK 3.0) to be able to ...
3. JSR(172) is not a standard (http://jcp.org/en/jsr/overview), although it is used as a standard :)
On a positive spin, I agree/admit that
1. Usage of third-party approaches (ksoap2) increases (although slightly) size of a final app.
2. Complexity of JSR 172 implementation and ksoap2 are almost equal.
3. With generated stub classes one can use eclipse BB plug-in as a development tool, whereas to utilize (ksoap2) jar file JDE is the only choice.
So in the end, it is up to Developer to decide which road to take.
And of course, big thanks to author for these articles.
|