we are on 2 projects with the target to share code and to use the seam framework. everything running fine. now, one of our customers fixed the architecture to tomcat using remote interfaces on bea 8.x. As u pointed out, seam will not be extended to remote connection via remote interface, only to use local once.
now we are in the dilemma to migrate this one project to a framework managing remote communication. :(
can you help me with the second best framework?
I don't understand. EJB3 already gives you a framework for remoteable components. No, it will not have Seam's nice contextual stuff, but it has virtually everything that any other framework has...