My guess is there will be a few issues in domain mode as we haven't devoted any time yet to testing out the console and admin pieces outside of standalone. Magesh was going to start looking at this for 0.5, but I wouldn't expect it to be seamless until 0.6.
Yes plans are underway. If you go ahead and do something, please let us know your experience and we can use that to leverage our testing.
What I have tried so far with no success.
I have tried modifying the ANT build file by chaning "standalone" with "domain".
I also tried copying the changes the ANT build made to standalone.xml to domain.xml under available profiles.
Both of these were done after copying the modules that are installed during the ANT build.
Also did a Windiff to determine which files were changed and viewed them in comparison via notepad++ and saw no mention of standalone.
I hope this helps.
Does Switchyard support domain mode yet ?
I have a AS7.1.3.Final environment configured with sy modules acquired from the latest switchyard.deployer.zip from hudson.
i've added the switchyard extension and subsystem to domain.xml (the sy subsystem is configured in the 'default' profile)
when deploying a switchyard quickstart to a server that uses the default profile, the following is the stack trace in the server.log :
21:26:02,138 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "switchyard-quickstart-camel-binding.jar"
21:26:02,163 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment switchyard-quickstart-camel-binding.jar
21:26:02,175 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstart-camel-binding.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstart-camel-binding.jar".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "switchyard-quickstart-camel-binding.jar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05-icedtea]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: org.switchyard.component.bean.SwitchYardCDIServiceDiscovery from [Module "deployment.switchyard-quickstart-camel-binding.jar:main" from Service Module Loader]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
... 5 more
Caused by: java.lang.ClassNotFoundException: org.switchyard.component.bean.SwitchYardCDIServiceDiscovery from [Module "deployment.switchyard-quickstart-camel-binding.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA]
when deploying the same switchyard quickstart in the same AS7.1.3.Final environment running in standalone mode, the quickstart works well.
so it seems that the switchyard subsystem configs found in a sy modified standalone.xml might need some adjustments for domain.xml ??
Yes, I think you are missing the extension in that configuration. Could you place these in their appropriate location and see what happens?
<extensions> ..... <extension module="org.switchyard"/> </extensions> .... <subsystem xmlns="urn:jboss:domain:switchyard:1.0"> <modules> <module identifier="org.switchyard.component.bean" implClass="org.switchyard.component.bean.deploy.BeanComponent"/> <module identifier="org.switchyard.component.soap" implClass="org.switchyard.component.soap.deploy.SOAPComponent"/> <module identifier="org.switchyard.component.camel" implClass="org.switchyard.component.camel.deploy.CamelComponent"/> <module identifier="org.switchyard.component.rules" implClass="org.switchyard.component.rules.deploy.RulesComponent"/> <module identifier="org.switchyard.component.bpm" implClass="org.switchyard.component.bpm.deploy.BPMComponent"/> <module identifier="org.switchyard.component.bpel" implClass="org.switchyard.component.bpel.deploy.BPELComponent"/> <module identifier="org.switchyard.component.hornetq" implClass="org.switchyard.component.hornetq.deploy.HornetQComponent"/> <module identifier="org.switchyard.component.http" implClass="org.switchyard.component.http.deploy.HttpComponent"/> <module identifier="org.switchyard.component.jca" implClass="org.switchyard.component.jca.deploy.JCAComponent"/> <module identifier="org.switchyard.component.resteasy" implClass="org.switchyard.component.resteasy.deploy.RESTEasyComponent"/> </modules> </subsystem> ....
yes ... i have the sy extension included in both my standalone.xml and domain.xml (without it .... AS7 bombs at start-up)
the sy subsystem config you've provided above is slightly different than what i was previously using ..... however in re-testing with your sy subsystem config i continue to get the same problem
ok .. well, if you have sy working in domain mode in your environment using the above configs then the problem is specific to my environment ... so i'll keep digging.
thank you Magesh!
I forgot to mention one thing. I test my AS 7.1.1 instance, as that is the one we run our release builds against, like this:
- Overlay the switchyard modules from the switchyard distribution
- Edit the domain.xml configuration as mentioned above
- Start the server using domain script
This actually works, except for a snag in the JBossWS stack
java.lang.ClassNotFoundException: org.apache.cxf.binding.soap.SoapTransportFactory from [Module "org.jboss.ws.cxf.jbossws-cxf-server:main"
This goes away when I restart. Now I deployed the application camel-binding and the deployment looked fine. But this application is not deployed as a SwitchYard application yet. There is much more we need to do in the deployment code I guess.
Whether it can work with AS 7.1.3 is another question. Have you tried building SwitchYard release by changing the AS 7 version to begin with?
thanks for the confirmation Magesh.
this helps a lot.