SwitchYard and WildFly

[synclpz]

Hi all, did any one have experience installing and running SwitchYard on WildFly beta?

Are you, developers, planning to support it? As I know WildFly 8.0.0.CR1 is going to be released in november and 8.0.0.Final in november/december. Our team have an activity which requires wildfly capabilities and we are going to use SY also, it would be nice to have it all-in-one platform

[kcbabo]

Viktor - sorry for not replying to this earlier.  Yes, we definitely have plans to run on Wildfly.  We will have a 1.1 release out in the next couple weeks, then our master branch will reset to 2.0 where we are scheduled to begin work on supporting Wildfly.

[jaspervault]

Thank you for supporting Wildfly in the next release. Do you have the date to release 1.1 so far?

[kcbabo]

It's out now.  Release details available in the blog:

SwitchYard 1.1.0.Final Released

[jaspervault]

Thank you very much for your reply.

May I know this SwitchYard 1.1 supports which version of WildFly?

Right now, looks still got same errors for SwitchYard 1.1.0 final in Wildfly.

I installed wildfly-8.0.0.Beta1, and do ANT to add SwitchYard 1.1 to WildFly, then run WildFly from Eclipse. I got:

14:21:51,426 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) JBAS014612: Operation ("add") failed - address: ([

    ("subsystem" => "switchyard"),

    ("module" => "org.switchyard.component.bean")

]): java.lang.NoClassDefFoundError: org/jboss/as/web/WebSubsystemServices

    at org.switchyard.as7.extension.SwitchYardModuleAdd.performRuntime(SwitchYardModuleAdd.java:107)

    at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:609) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:487) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:343) [wildfly-controller-8.0.0.Beta1.jar:8.0.0.Beta1]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]

    at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]

    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]

Caused by: java.lang.ClassNotFoundException: org.jboss.as.web.WebSubsystemServices from [Module "org.switchyard:main" from local module loader @1ded246d (finder: local module finder @3bf27f74 (roots: C:\apache\wildfly8beta\modules,C:\apache\wildfly8beta\modules\system\layers\soa,C:\apache\wildfly8beta\modules\system\layers\base))]

    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) [jboss-modules.jar:1.3.0.Final]

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final]

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final]

    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]

    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]

    ... 11 more

I checked the standalone_full.xml file, The following has been added in the file:

<subsystem xmlns="urn:jboss:domain:switchyard:1.0">

    <modules>

        <module identifier="org.switchyard.component.bean" implClass="org.switchyard.component.bean.deploy.BeanComponent"/>

           .....

    </modules>

    <extensions>

        ...

    </extensions>

</subsystem>

Looks BeanComponent needs org.jboss.as.web.WebSubsystemServices, but it could not find it.

Anyway, "switchyard:1.0" in the first line maybe a typo, I guess.

Thank you in advance for your patience.

[kcbabo]

SwitchYard 1.1 will not work with Wildfly.  We are working on Wildfly compatibility as part of SwitchYard 2.0.

[patkul]

Is there any ETAs for a 2.0 alpha, beta or release?

[kcbabo]

We have not scheduled the 2.0 Alpha yet, but you can expect details on the high-level goals for the 2.0 release in the next couple weeks.  I would give a ballpark now, but we're still working out whether we will go with smaller .x releases like we have been doing or if we will make 2.0 much bigger and do more AlphaX and BetaX releases inside of 2.0.

[kcbabo]

I should also mention that nightly builds are always available for 2.0-SNAPSHOT here:

SwitchYard-Release [Jenkins]

[patkul]

We have been eager to, and looking into, migrating to SY from JBoss ESB ever since SY 0.6/0.7 but had a showstopper in terms of a JBoss AS 7 bug that was solved in Wildfly 8 Alpha 1.

Since then, we have been waiting for Wildfly to stabilize so we could try again, and now the last piece is to actually have SY run on Wildfly.

We now want to get an idea of when it would be possible for us to start porting again?

We obviously have a lot to do, learn and test so we'd like to get started as soon as possible and not wait for the final Wildfly 8 and SY 2 releases.

However, we'd also prefer to not bang our heads against bugs in Wildfly and SY

We'll gladly help out to find any bugs in SY 2 to speed up SY development.

I guess we'd want SY 2 to boot properly in Wildfly and that basic service integration is in place before we start porting.

Is this already in place or expected to work in the near time?

Would this be a plausible main goal for the first alpha?

[mageshbk]

Is this already in place or expected to work in the near time?

Would this be a plausible main goal for the first alpha?

Yes it is and we are targeting this for our next release 2, alpha or beta. Please vote and watch for it here:

[SWITCHYARD-1923] Add support for Wildfly - JBoss Issue Tracker

[zurchman]

Doesn't look like much has changed.  I downloaded the nightly build of switchyard-installer-2.0 and installed it against a fresh wildfly-8.0.0.Final. 

Doesn't look like WebSubsystemServices is any part of WildFly.

18:11:51,504 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final

18:11:51,743 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final

18:11:51,819 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final "WildFly" starting

18:11:52,590 INFO  [org.switchyard] (ServerService Thread Pool -- 25) SwitchYard version 2.0.0-SNAPSHOT

18:11:52,733 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

18:11:52,751 INFO  [org.xnio] (MSC service thread 1-12) XNIO version 3.2.0.Final

18:11:52,761 INFO  [org.xnio.nio] (MSC service thread 1-12) XNIO NIO Implementation Version 3.2.0.Final

18:11:52,782 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 47) JBAS013171: Activating Security Subsystem

18:11:52,790 INFO  [org.switchyard] (ServerService Thread Pool -- 53) Activating SwitchYard Subsystem

18:11:52,791 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.

18:11:52,799 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem

18:11:52,799 INFO  [org.jboss.as.security] (MSC service thread 1-9) JBAS013170: Current PicketBox version=4.0.20.Final

18:11:52,802 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 40) JBAS012615: Activated the following JSF Implementations: [main]

18:11:52,823 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 50) JBAS017502: Undertow 1.0.0.Final starting

18:11:52,823 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017502: Undertow 1.0.0.Final starting

18:11:52,826 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 51) JBAS015537: Activating WebServices Extension

18:11:52,843 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)

18:11:52,883 INFO  [org.jboss.remoting] (MSC service thread 1-12) JBoss Remoting version 4.0.0.Final

18:11:52,889 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

18:11:52,895 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 53) JBAS014612: Operation ("add") failed - address: ([

    ("subsystem" => "switchyard"),

    ("module" => "org.switchyard.component.bean")

]): java.lang.NoClassDefFoundError: org/jboss/as/web/WebSubsystemServices

  at org.switchyard.as7.extension.SwitchYardModuleAdd.performRuntime(SwitchYardModuleAdd.java:107)

  at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:75) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:591) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:469) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:273) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:268) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:343) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

  at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

  at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]

Caused by: java.lang.ClassNotFoundException: org.jboss.as.web.WebSubsystemServices from [Module "org.switchyard:main" from local module loader @4c4db085 (finder: local module finder @8012e6 (roots: /usr/local/Applications/JBoss/wildfly-8.0.0.Final/modules,/usr/local/Applications/JBoss/wildfly-8.0.0.Final/modules/system/layers/soa,/usr/local/Applications/JBoss/wildfly-8.0.0.Final/modules/system/layers/bpms,/usr/local/Applications/JBoss/wildfly-8.0.0.Final/modules/system/layers/base))]

  at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) [jboss-modules.jar:1.3.0.Final]

  at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final]

  at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final]

  at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]

  at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]

  ... 11 more

[kcbabo]

Doesn't look like the installer was updated as part of the initial integration work.  Magesh can provide an idea of when to expect it, but one thing to keep in mind is that Wildfly integration is a WIP, so don't expect everything to work on the first nightly. :-)  For the first 2.0 Alpha, you should expect the installer and a list of things that work and don't work in the release notes.

[mageshbk]

Yes, the installer issue will be dealt separately here [SWITCHYARD-2012] Add WildFly support in installer - JBoss Issue Tracker

Sidney, if you want an early look at it, then you can build the dist from source. Just skip the tests for now.

[zurchman]

Can you tell me how I can install the release on Wildfly?

I built the release-master but I'm not sure where to go from here.

I see the targets below, and I see Wildfly modules and extensions under jboss-as7/wildfly, but I'm used to using the installer and I'm afraid I'm a bit lost at the moment.

Thanks

./jboss-as7/bundle/target/switchyard-as7-bundle.zip

./jboss-as7/modules/target/switchyard.deployer.zip

./jboss-as7/standalone/dist/target/switchyard-2.0.0-SNAPSHOT-EAP6.1.Alpha.zip

./jboss-as7/standalone/dist/target/switchyard-2.0.0-SNAPSHOT-EAP6.1.GA.zip