When should invocationXXXNotify() be invoked

最新推荐文章于 2023-07-12 15:01:51 发布

iqueen

最新推荐文章于 2023-07-12 15:01:51 发布

阅读量1k

点赞数

CC 4.0 BY-SA版权

分类专栏： Java 文章标签： constructor thread rest

本文链接：https://blog.youkuaiyun.com/iqueen/article/details/1681103

Java 专栏收录该内容

22 篇文章

订阅专栏

本文探讨了在JSR211规范下HandlerMidlet的正确调用流程，尤其是在设置监听器之后如何正确地调用invocationRequestNotify()方法。文章指出实际的执行顺序是在构造函数中设置监听器时会启动新的线程来执行invocationRequestNotify()，而主线程则继续执行构造函数中的其余代码。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

When should invocationRequestNotify() be invoked for a handler midlet?

Before reading, you should know jsr211, should know the invoke/response processes between caller and handler.

Normally, we think, the right flow should be

Constructor()
invocationRequestNotify()
startApp()

but actually, the order is not like that, if we have setListener(javax.microedition.content.RequestListener) in the constructor, the order should be,

Constructor() ->setListener()->fork() ->invocationRequestNotify()
startApp()

The entry invocationRequestNotify() will start in new thread when executing reach the statement setListener(), and the father thread keep executing the rest code in the Constructor().

The same process order happens for the invocationResponseNotify() for the ResponseListener.