sca binding across ear deployments

[mlybarger]

i have two projects, each is deployed as a jar inside of an ear.  projecta.jar -> projecta.ear, projectb.jar -> projectb.ear. Both of the jar files are switchyard deployments,  They use jms to endpoints to interact today,  I'd like to convert to an SCA binding.  is there anything I need to be aware of when referencing projectb.jar's components from projecta.jar?  Is this possible? I had read some folks had class loading issues and needed to put the interface classes into a common module that was shared by both ear/jars files?  Any thoughts would be most appreciated!

Thanks!

[igarashitm]

Yes shared interface/class should be exposed as a common library, otherwise possibly causes ClassCastException. One another thing I remember is about the namespace, I'd recommend to use different namespace for each SY application using SCA as SCA remote binding looks for the service with using namespace, otherwise possibly the SY applications using same namespace pollutes each other.

[mlybarger]

Thanks!  We got it working using this method.