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);
|
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 :
The normal approach here is to write a JCA adaptor. But this does require an
endpoint in your application. Another option is to use the Seam Manager
component pattern (@Unwrap).
Dan's approach also seesm good to me.
View the original post :
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 :
You can't call a session bean remotely and invoke it from your client? Doing
that is synchronous.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4097230#4097230
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4097230
