Building your own service in SwitchYard (JUDCon China)

The JUDCon was held in China first time in the end of Nov in Beijing, it has almost been 3 years after I moved to Australia, and it has been great to see the colleagues, and the community there.

I presented a talk named "Building your own service In SwitchYard", it has two parts, first part is to give a very basic introduction to the SwitchYard project, and then have a live demo to build a simple sayHello service from scratch by using the SwitchYard editor in JBoss Dev studio. The other part is to introduce the steps on integrating a project as a component in the SwitchYard, this basically is the experience that we had on integrating the RiftSaw project as the BPEL component in SwitchYard, hopefully it will help some users/developers that want to integrate their in-house or other projects as components in SwitchYard.

The audience is great in JUDCon, I was approached by some developers that are impressed by the SwitchYard, the editors etc, some questions between the camel and SwitchYard, and even some questions on how to get involved in the open source development. 

It was a great experience in JUDCon, and looking forward to the next one.

Cheers

Jeff Yu

RiftSaw 3.0.0-M2 released

As we said previously, the RiftSaw 3 will be a BPEL component in SwitchYard project. Therefore, as  part of the SwitchYard 0.4 release, we have released the RiftSaw 3.0.0-M2, and below are some highlights in the M2 release.

• Previous version only supported H2. 0.4 now includes support for other databases, documentation can be found at here.
• BPEL console integrated, documentation can be found at here.
• BPEL engine configuration can now be override by defining properties in the AS7 standalone.xml
• Additional quickstarts (simple correlation and jms binding)
• Bug fixes, including variable initialization support (RIFTSAW-301) and ORACLE 11G exception (RIFTSAW-470)

So you can try out the above improvements by downloading the SwitchYard 0.4, and if you have found any issues, please report them at RiftSaw Jira system, and we will try to get them fixed as soon as possible.