Replying myself after some investigation.
I found that for Switchyard release 2.0 the BPEL Console version used was 2.4.8 (SY 2.1 uses 2.4.6), which don't have overlord and picketlink dependencies. Also, in there has a message that inform to create a user on JBoss EAP. This seems to work fine with SY 2.1.
But I also tried to migrate BPEL Console to overlord 2.0.13. After some time, I stopped on this issue when trying to start the server:
Caused by: LifecycleException: no protocol: /overlord-idp/
at org.picketlink.identity.federation.bindings.tomcat.sp.AbstractSPFormAuthenticator.initKeyProvider(AbstractSPFormAuthenticator.java:253) [picketlink-jbas7-2.5.4.SP4-redhat-1.jar:2.5.4.SP4-redhat-1]
at org.picketlink.identity.federation.bindings.tomcat.sp.BaseFormAuthenticator.startPicketLink(BaseFormAuthenticator.java:656) [picketlink-jbas7-2.5.4.SP4-redhat-1.jar:2.5.4.SP4-redhat-1]
BPEL Console server start without problem.
Also, everything seems to be ok regarding overlord 2.0.13 instalation.
Any suggestions here?
Thanks in advance.
I'm afraid to say that SwitchYard will be no longer maintained. There will be no more official releases.
In the spirit of Open Source, it's welcome to fork it and maintain your own branch. Maybe it's also possible that you contact to Tom Cunningham and get the maintainer rights of SY project if you are eager enough to do so.
Ow, ok. I'm not aware of this.
In this case, there's a viable JBOSS replacement for SY?
Regarding the demise of SY. The main purpose to use SY was due BPEL. Also, SY offers a dev environment similar to Oracle SOA Suite. What is pretty cool, since you can create a create the bindings and processes in a visual way, and also you can use use Camel as a router to many BPEL processes in the same SY panel/project.
Also, BPEL is stateful, what fit in perfectly to the current project needs.
My question is: can camel provide the same functionalities of SY that I mentioned above?
Finally, what happens to SY that the project was abandoned?
Thanks in advance!!!