I've been debugging and reading a lot this weekend to find an explanation. And
I'm not 100% sure, but I think I found one. When executing an asynchronous
method invocation, the jboss backend server will create a callback object
allowing to process the final result of the asynchronous invocation.
If you want I can setup a test project this weekend (because I cannot post the
code from the customer I'm working for) and try to do some debugging.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179993#4179993
Reply to the post :
http://www.jboss.com/index.
I'm currently using JBoss 4.2.2. In my backend jboss I've a stateless session
bean where one of the method is annotated with @Asynchronous.
In my frontend server (which also uses jboss 4.2.2), I create an asynchronous
proxy for my session bean and invoke the method. Everything works fine and als
Thnx,
I got it working today. Two jboss instances, one containing the ejb3 business
logic and one containing the web application based on seam, reusing the
entities from the ejb3 layer.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111763#4111763
Reply to
Did you ever found a solution for this?
I'm looking to do something similar. We have some presentation layer (based on
seam) that is integrating with an EJB3 backend. If we create one ear for that
it works great. But now we would like to put the presentation layer on a
separate machine and have
