[JBoss Seam] - Seam and Adobe Flex
by neilac333
There is some major momentum here at my client site about Adobe Flex as a view technology. As for me, I have been just as impressed as everyone else with all the cool stuff Flex does on the front end, but I find my own enthusiasm tempered by all the usual caveats: proprietary technology, support for BP workflow, security, transactional capability, general immaturity and lack of documentation and best practices, and so on.
Of course, as I have gotten to know technologies like Seam (and Spring), it seems to me that if I were to jump on the Flex bandwagon, I could do all the heavy lifting in Seam and simply let the managed components comuncate with the "bridge" objects Flex needs to talk to in order to convey a view.
My questions are the following:
1) Any general notions about Flex? (This isn't the right forum I know, but I respect the opinions on here so I thought I would ask.)
2) More pertinently, is integration with Seam even feasible, or is Spring my best bet here?
Thanks very much.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033231#4033231
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033231
19Â years
[JBoss Messaging] - Re: Failed to get a server session
by imaeses
Well the solution was breaking the deadlock, which is application specific. As long as the QueueConnection could be reestablished, the deadlock would be broken.
We stopped implementing message receive as a MessageListener and did it ourselves. This had the effect that we could control when receive() was called and how long it would block for. If onException() was called, we could set a flag in the receive thread. The receive thread would eventually return from receive() and close it's QueueSession object. So QueueConnection.close() always works. Then we reestablish the QueueConnection and the deadlock is cleared.
(The deadlock had to do with two threads. Thread A wanted to add a message to a data structure but had to wait() because it was currently full. Thread B wanted to read from this data structure but would first wait() on the same monitor if there was no valid QueueConnection.)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033224#4033224
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033224
19Â years