Issue Type: Bug Bug
Affects Versions: 0.8
Assignee: Unassigned
Components: configuration, core
Created: 11/Mar/13 9:38 AM
Description:

according to https://github.com/jboss-switchyard/core/blob/master/config/src/main/resources/org/switchyard/config/model/switchyard/v1/switchyard-v1.xsd I assume that minimal switchyard.xml should be:

<?xml version="1.0" encoding="UTF-8"?>
<switchyard xmlns="urn:switchyard-config:switchyard:1.0" name="orders" targetNamespace="urn:abcd:1.0">

</switchyard>

but when I try to deploy the archive ... SY throws NPE

10:33:28,570 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.subunit."auditing.ear"."integration-qa-audit-1.0.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.subunit."auditing.ear"."integration-qa-audit-1.0.jar".SwitchYardService: java.lang.NullPointerException
    at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:85)
    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$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: java.lang.NullPointerException
    at org.switchyard.deploy.internal.Deployment.getActivationTypes(Deployment.java:214)
    at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:101)
    at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:78)
    ... 5 more
Project: SwitchYard
Priority: Major Major
Reporter: Ivo Bek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira