what is the best approach to communicate between 2 or more seam applications ?

as an example, the first application provides a set of basic services to be used by other applications.

i'm currently playing with a JNDI lookup approach. i'm having classloading issues however. to solve it i configured the two applications to use the samen classloader namespace but this is propr. to jboss.

what is a good way to setup the two applications to avoid classloading issues. where do you put the shared local and/or remote interfaces?

There really isn't a standard way to share classloaders between applications. For remote beans, you need the interfaces from app2 in app1 and the interfaces from app1 in app2. I don't know what other app servers offer to provide the equivalent of a shared-named repository.

If you are sharing classloaders, there's really no reason not to use one big ear instead. If you hot deploy app1 you nearly always need to hot deploy app2 also to avoid classloader issues. Why not bundle in one big ear and force yourself to do the right thing on redeploy? The alternative, in jboss, is to extract common classes to a third app. app1 and app2 can be safely separately redeployed. If the common classes change then both app1 and app2 should be redeployed.

No, we don't really have a link to JMX MBeans. You probably don't want direct app to mbean communication for the most part. Generally you want your MBeans to manage services that are exposed through JNDI or some other communications mechanism. In either case @Factory and @Unwrap are probably your best bets for exposing these services to Seam.

Well, at office we're are devolping two Enterprise Applicationa, one with plain EJB3 and one with Seam. Communication between both apps is done via WebServices which works very well for us (despite of unicode problems with JBossWS before patching)

Only thing I ran into problems is when both apps are deployed on the same server (there have been issues with class-level isolation and quartz imho). I didn't investigate further because we do not have the requirement to let both apps run on same JBoss.

Did not try multiple Seam apps on one server by now, but possibly in near future. Never say never...