Code still needs to be cleaned up a bit (more than a bit in some places), but it's functional and nothing in terms of configuration or setup should change between now and beta 2. If you have a few spare cycles, please bang on it real quick and see how quickly the wheels fall off the cart.
First thing you need to do is pull from my parent, core, components, and release branches and run a build. There's a small issue with the AS7 extension where standalone is broken (you need to use standalone-ha). I will sort that out as part of my clean-up. For now, build release with "mvn -Dmaven.test.skip clean install".
git pull git://github.com/kcbabo/parent.git SWITCHYARD-730
git pull git://github.com/kcbabo/core.git SWITCHYARD-730
git pull git://github.com/kcbabo/components.git SWITCHYARD-730
git pull git://github.com/kcbabo/release.git SY-730 (note the branch name change)
After that, unzip the built switchyard-as7.zip into two directories (e.g. node1, node2). Start each one using the following configuration:
node1 : "bin/standalone.sh -c standalone-ha.xml"
node2 : "bin/standalone.sh -c standalone-ha.xml -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=2000"
You can setup more instances if you like, but be sure to provide a unique node name and port offset for each additional instance.
Once the servers are running, build and deploy the attached apps. Deploy app1 to node1 and app2 to node2. Then go into the app1 project and run the following to bounce a message off the instance:
That will send a test message to node1, which will find the service in node2 and invoke it. The return value is passed back to node1 and then back to the original invoker.
Hopefully, all of the above will work for you. :-) If it doesn't, let me know. If it does, see if you can try some alternate scenarios like taking a quickstart and breaking it across two nodes. Anything like that will help out.