JBossDeveloper

It will be in 1.0.  I have the fix for this in my SWITCHYARD-1483 branch.  Unfortunately, it will immediately drag you into SWITCHYARD-915, which has mostly been just a mild annoyance until now.  Not a big deal as I've been meaning to fix that for a while, but it means it will be a bit later in the week until I have that second issue tidied up.  Once that's in, you can take a nightly build of 1.0 to verify it with your application (I will verify with my modified version of the cluster quickstart).

The root cause here is that local invocations in the SCA bindings rely on the fact that the target service reference is resolvable directly from another application domain.  The unit tests use a single application domain and the cluster tests test this along another code path (where it does in fact work).  Sorry for the trouble.

Ignore what I said about SWITCHYARD-915.  I looked a bit deeper and that issue won't impact this use case.  The fix involves a few extra pieces for 1.0 after the Camel Bus refactor, so I went ahead and backported the required changes onto 0.8.  They can be found here:

https://github.com/kcbabo/core/tree/SWITCHYARD-1483_0.8

You can either build it from source or use the attached version of switchyard-runtime which contains the fix.  Just drop it in the modules/org/switchyard/runtime/main directory of your AS install and you should be good to go (restart required, natch).  That fixed things up with my test app - let me know if you still run into issues.

Thanks for verifying.

There will not be a 0.8.1 release of SwitchYard.  The fixes applied on that branch are targeted at SOA-P 6.0 Alpha.  All fixes made on that branch are also applied to master which feeds the SwitchYard 1.0 release.

Third week of June.