[
https://issues.apache.org/jira/browse/PIVOT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038047#comment-13038047
]
Andrei Pozolotin commented on PIVOT-747:
----------------------------------------
Noel: thank you very much for looking into this.
my problem is this:
1) I receive shutdown(optional==true) from the user;
2) before I run (or cancel) actual shutdown, including osgiShutdown()
I need to perfom negotiation with the user;
3) this negotiation happens in osgi bundle wich runs on non-ETD thread
and which uses EventQueue.invokeLater() to converse with the user;
4) while the negotiation is going on, I must block original ETD which called
shutdown()
(or else pivot will just shut me down) and permit new working EDT in the
meanwhile;
5) this is pretty much the same problem as net beans people discussed some time
back:
http://bugs.sun.com/view_bug.do?bug_id=6424157
http://netbeans.org/bugzilla/show_bug.cgi?id=90590
am I making more sense?
Andrei.
> pivot & blocking edt
> --------------------
>
> Key: PIVOT-747
> URL: https://issues.apache.org/jira/browse/PIVOT-747
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Affects Versions: 2.0
> Reporter: Andrei Pozolotin
>
> Greg, hello;
> in this thread:
> http://mail-archives.apache.org/mod_mbox/pivot-user/201001.mbox/%[email protected]%3E
> your final word is:
> "Sorry, it is not possible"
> but I know that you know that it is possible :-)
> the reason I need this is same as Martin here:
> http://netbeans.org/bugzilla/show_bug.cgi?id=90590
> namely: do some cleanup after shutdown was requested and confirmed:
> org.apache.pivot.wtk.Application
> public boolean shutdown(boolean optional) throws Exception;
> since you call shutdown(boolean optional) from EDT I need to block it, using
> this approach:
> http://bugs.sun.com/view_bug.do?bug_id=6424157
> wich "almost works", except you have this check everywhere:
> Container.assertEventDispatchThread();
> which fails, as described above:
> http://bugs.sun.com/view_bug.do?bug_id=6424157
> due to EventQueue.isDispatchThread() failing on the "T1 vs T1*" distinction
> my request is this:
> do you think you could make
> Container.assertEventDispatchThread();
> less pedantic, and allow both "current and past/next" EDT threads to pass
> which are created during EventQueue push() / pop()
> thanks!
> Andrei
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
