[jboss-user] [JBoss Seam] - Re: Starting Threads and Socket listeners

2007-11-06 Thread dcowan
For anyone that stumbles upon this I solved this by using Lifecycle.beginCall within my callback method Lifecycle.beginCall(); | | try { | IEventDataService eventDataService = (IEventDataService) Component.getInstance(eventDataService, true); |

[jboss-user] [JBoss Seam] - Re: Starting Threads and Socket listeners

2007-10-29 Thread dcowan
I currently use an application scoped bean to start the Socket listener so using the Seam Manager compenent sounds like a good option. If I used that would Threads created from the socket threads be able to call the manager in the context of a transaction? View the original post :

[jboss-user] [JBoss Seam] - Re: Starting Threads and Socket listeners

2007-10-20 Thread dcowan
I did some research on this and was wondering what peoples thoughts on using a Resource Adapter to do this or is there a more general way to do it in seam. My sockets that listen need to access my beans in a synchronous manner so mdb's are out. View the original post :

[jboss-user] [JBoss Seam] - Starting Threads and Socket listeners

2007-10-16 Thread dcowan
I'm trying to determine the best method to integrate a legacy protocol that starts Threads that listen on ServerSockets within a seam application. I have considered writing an MBean wrapper, but haven't really determined the most appropriate method. My legacy protocol start several threads