sca.binding invocations across deployments
I am not able to successfully reference one service sitting in an EAR from a SwitchYard enabled Arquillian test sitting on a separate WAR Deployment.
The concept if the following:
- An Arquillian test configured to use a managed JBoss-Switchyard 0.8 container.
- This test contains two deployments:
- the first one is an EAR file that contains a JAR file with the Switchyard Application sitting on the root of the application and a JAR file with the API sitting on the /lib folder.
- the second one is a WAR file that contains the Arquillian enabled test and the JAR file with the API sitting in the WEB-INF/lib folder.
- The test has a @Inject @Reference service that ideally should be calling the service made available by the EAR file.
- In the WAR file there is a switchyard.xml configuration file with the reference and a sca binding as well as a component having the test as a bean.implementation.
- In the JAR file inside the EAR there is another switchyard.xml implementation which contains the composite service declaration promoting the appropriate Component.
The result is a NullPointerException as shown in the following stacktrace:
/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/bin/java -Dmaven.home=/Applications/apache-maven-3.0.4 -Dclassworlds.conf=/Applications/apache-maven-3.0.4/bin/m2.conf -Didea.launcher.port=7540 "-Didea.launcher.bin.path=/Applications/IntelliJ IDEA 12.app/bin" -Dfile.encoding=UTF-8 -classpath "/Applications/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar:/Applications/IntelliJ IDEA 12.app/lib/idea_rt.jar" com.intellij.rt.execution.application.AppMain org.codehaus.classworlds.Launcher --fail-fast --strict-checksums -s /Users/edevera/.m2/zimory-settings.xml org.apache.maven.plugins:maven-failsafe-plugin:2.14.1:integration-test -P arquillian-jbossas-managed
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building switchyard-ejb-app2 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.switchyard:switchyard-test:jar:0.8.0.Final is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
[INFO]
[INFO] --- maven-failsafe-plugin:2.14.1:integration-test (default-cli) @ switchyard-ejb-app2 ---
[INFO] Failsafe report directory: /Users/edevera/Documents/Development/switchyard_ejb/switchyard-ejb-app2/target/failsafe-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.edevera.switchyard.app2.ServiceBIT
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
May 01, 2013 6:23:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
INFO: Starting container with: [/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre/bin/java, -Xmx512m, -XX:MaxPermSize=128m, -ea, -Djboss.home.dir=/Applications/switchyard-as7-0.8, -Dorg.jboss.boot.log.file=/Applications/switchyard-as7-0.8/standalone/log/boot.log, -Dlogging.configuration=file:/Applications/switchyard-as7-0.8/standalone/configuration/logging.properties, -Djboss.modules.dir=/Applications/switchyard-as7-0.8/modules, -Djboss.bundles.dir=/Applications/switchyard-as7-0.8/bundles, -jar, /Applications/switchyard-as7-0.8/jboss-modules.jar, -mp, /Applications/switchyard-as7-0.8/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone-full.xml]
18:23:32,444 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
18:23:32,653 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
18:23:32,717 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
18:23:33,415 INFO [org.switchyard] SwitchYard version 0.8.0.Final
18:23:33,563 INFO [org.xnio] XNIO Version 3.0.3.GA
18:23:33,564 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
18:23:33,573 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
18:23:33,581 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
18:23:33,597 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
18:23:33,609 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 33) JBAS016200: Activating ConfigAdmin Subsystem
18:23:33,610 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) JBAS010280: Activating Infinispan subsystem.
18:23:33,616 INFO [org.switchyard] (ServerService Thread Pool -- 61) Activating SwitchYard Extension
18:23:33,619 INFO [org.jboss.as.security] (ServerService Thread Pool -- 55) JBAS013101: Activating Security Subsystem
18:23:33,627 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 50) JBAS011940: Activating OSGi Subsystem
18:23:33,628 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 49) JBAS011800: Activating Naming Subsystem
18:23:33,635 INFO [org.jboss.as.security] (MSC service thread 1-15) JBAS013100: Current PicketBox version=4.0.7.Final
18:23:33,646 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 39) JBAS016300: Activating JacORB Subsystem
18:23:33,664 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 59) JBAS015537: Activating WebServices Extension
18:23:33,681 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
18:23:33,755 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
18:23:33,772 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default]
18:23:33,784 INFO [org.jboss.jaxr] (MSC service thread 1-6) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
18:23:33,800 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 34) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:23:33,807 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
18:23:34,034 WARN [jacorb.codeset] (MSC service thread 1-14) Warning - unknown codeset (ASCII) - defaulting to ISO-8859-1
18:23:34,128 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) JBAS016330: CORBA ORB Service started
18:23:34,296 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:23:34,297 WARN [org.jboss.as.messaging] (MSC service thread 1-15) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
18:23:34,345 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/Applications/switchyard-as7-0.8/standalone/data/messagingjournal,bindingsDirectory=/Applications/switchyard-as7-0.8/standalone/data/messagingbindings,largeMessagesDirectory=/Applications/switchyard-as7-0.8/standalone/data/messaginglargemessages,pagingDirectory=/Applications/switchyard-as7-0.8/standalone/data/messagingpaging)
18:23:34,348 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Waiting to obtain live lock
18:23:34,355 INFO [org.jboss.as.jacorb] (MSC service thread 1-10) JBAS016328: CORBA Naming Service started
18:23:34,573 INFO [org.hornetq.core.persistence.impl.journal.JournalStorageManager] (MSC service thread 1-6) Using NIO Journal
18:23:34,660 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-6) Waiting to obtain live lock
18:23:34,661 INFO [org.hornetq.core.server.impl.FileLockNodeManager] (MSC service thread 1-6) Live Server Obtained live lock
18:23:34,705 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:23:34,705 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]
18:23:34,849 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory /Applications/switchyard-as7-0.8/standalone/deployments
18:23:34,858 INFO [org.jboss.as.remoting] (MSC service thread 1-10) JBAS017100: Listening on localhost/127.0.0.1:4447
18:23:34,858 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:9999
18:23:35,243 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-6) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5455 for CORE protocol
18:23:35,244 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-6) Started Netty Acceptor version 3.2.5.Final-a96d88c localhost:5445 for CORE protocol
18:23:35,245 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Server is now live
18:23:35,246 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) HornetQ Server version 2.2.13.Final (HQ_2_2_13_FINAL_AS7, 122) [d3696df4-b1f2-11e2-b8c5-e0f847371cc8]) started
18:23:35,249 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) trying to deploy queue jms.queue.testQueue
18:23:35,257 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:/queue/test
18:23:35,257 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test
18:23:35,271 INFO [org.jboss.as.messaging] (MSC service thread 1-9) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
18:23:35,272 INFO [org.jboss.as.messaging] (MSC service thread 1-10) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
18:23:35,273 INFO [org.jboss.as.messaging] (MSC service thread 1-10) JBAS011601: Bound messaging object to jndi name java:/RemoteConnectionFactory
18:23:35,274 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) trying to deploy queue jms.topic.testTopic
18:23:35,293 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:/topic/test
18:23:35,294 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test
18:23:35,297 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
18:23:35,306 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-4) HornetQ resource adaptor started
18:23:35,307 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
18:23:35,309 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-16) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
18:23:35,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
18:23:35,330 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3202ms - Started 197 of 277 services (78 services are passive or on-demand)
serviceb-imp.jar:
/com/
/com/edevera/
/com/edevera/switchyard/
/com/edevera/switchyard/app2/
/com/edevera/switchyard/app2/TransformerServiceB.class
/com/edevera/switchyard/app2/RequestB.class
/com/edevera/switchyard/app2/ServiceBBean.class
/com/edevera/switchyard/app2/ServiceB.class
/META-INF/
/META-INF/switchyard.xml
/META-INF/beans.xmltest.war:
/META-INF/
/META-INF/switchyard.xml
/WEB-INF/
/WEB-INF/beans.xml
/WEB-INF/classes/
/WEB-INF/classes/com/
/WEB-INF/classes/com/edevera/
/WEB-INF/classes/com/edevera/switchyard/
/WEB-INF/classes/com/edevera/switchyard/app2/
/WEB-INF/classes/com/edevera/switchyard/app2/ServiceBIT.classserviceb.ear:
/lib/
/lib/switchyard-ejb-api-1.0-SNAPSHOT.jar
/test.war
/serviceb-imp.jar
/META-INF/
/META-INF/application.xml18:23:40,289 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /Applications/switchyard-as7-0.8/standalone/data/content/5e/8b8ec9d6248c3d5561edc481606e441e918182/content
18:23:40,304 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "serviceb.ear"
18:23:40,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "serviceb-imp.jar"
18:23:40,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015876: Starting deployment of "test.war"
18:23:40,648 INFO [org.jboss.weld.deployer] (MSC service thread 1-14) JBAS016002: Processing weld deployment serviceb.ear
18:23:40,665 INFO [org.jboss.weld.deployer] (MSC service thread 1-14) JBAS016002: Processing weld deployment serviceb-imp.jar
18:23:40,702 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment test.war
18:23:40,749 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016005: Starting Services for CDI deployment: serviceb.ear
18:23:40,830 INFO [org.jboss.weld.Version] (MSC service thread 1-10) WELD-000900 1.1.6 (Final)
18:23:40,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016008: Starting weld service for deployment serviceb.ear
18:23:40,849 INFO [org.switchyard] (MSC service thread 1-9) Deploying SwitchYard application 'serviceb-imp.jar'
18:23:40,906 INFO [org.switchyard] (MSC service thread 1-11) Deploying SwitchYard application 'test.war'
18:23:41,241 INFO [org.switchyard] (MSC service thread 1-16) Starting SwitchYard service
18:23:41,241 INFO [org.switchyard] (MSC service thread 1-1) Starting SwitchYard service
18:23:41,334 INFO [org.jboss.web] (MSC service thread 1-9) JBAS018210: Registering web context: /test
18:23:41,414 INFO [org.apache.camel.management.ManagementStrategyFactory] (MSC service thread 1-1) JMX enabled.
18:23:41,414 INFO [org.apache.camel.management.ManagementStrategyFactory] (MSC service thread 1-16) JMX enabled.
18:23:41,430 INFO [org.switchyard.security.SecurityProvider] (MSC service thread 1-1) Using SecurityProvider implementation: org.switchyard.security.jboss.JBossJaasSecurityProvider
18:23:41,434 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-1) Apache Camel 0.8.0.Final (CamelContext: camel-1) is starting
18:23:41,434 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-16) Apache Camel 0.8.0.Final (CamelContext: camel-2) is starting
18:23:41,435 INFO [org.apache.camel.management.DefaultManagementLifecycleStrategy] (MSC service thread 1-1) StatisticsLevel at All so enabling load performance statistics
18:23:41,435 INFO [org.apache.camel.management.DefaultManagementLifecycleStrategy] (MSC service thread 1-16) StatisticsLevel at All so enabling load performance statistics
18:23:41,553 INFO [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-1) Loaded 179 type converters
18:23:41,553 INFO [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-16) Loaded 179 type converters
18:23:41,580 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-1) Total 0 routes, of which 0 is started.
18:23:41,581 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-16) Total 0 routes, of which 0 is started.
18:23:41,581 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-1) Apache Camel 0.8.0.Final (CamelContext: camel-1) started in 0.146 seconds
18:23:41,582 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-16) Apache Camel 0.8.0.Final (CamelContext: camel-2) started in 0.147 seconds
18:23:41,595 INFO [org.switchyard.component.sca.deploy.SCAActivator] (MSC service thread 1-16) Unable to resolve cache-container cluster. clustering for <binding.sca> will not be available for services and references.
18:23:41,595 INFO [org.switchyard.component.sca.deploy.SCAActivator] (MSC service thread 1-1) Unable to resolve cache-container cluster. clustering for <binding.sca> will not be available for services and references.
18:23:41,734 INFO [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-16) Loaded 179 type converters
18:23:41,929 INFO [org.switchyard.as7.extension.cluster.RemoteEndpointListener] (MSC service thread 1-1) Published Remote Service Endpoint /switchyard-remote
18:23:42,248 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-1) Route: direct:{urn:com.edevera.switchyard.app2:switchyard-ejb-app2-test:1.0-SNAPSHOT}Service started and consuming from: Endpoint[direct://%7Burn:com.edevera.switchyard.app2:switchyard-ejb-app2-test:1.0-SNAPSHOT%7DService]
18:23:42,251 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-16) Route: direct:{urn:com.edevera.switchyard.app2:switchyard-ejb-app2:1.0-SNAPSHOT}ServiceB started and consuming from: Endpoint[direct://%7Burn:com.edevera.switchyard.app2:switchyard-ejb-app2:1.0-SNAPSHOT%7DServiceB]
18:23:42,302 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "serviceb.ear"
18:23:43,076 INFO [org.switchyard.handlers.MessageTrace] (http--127.0.0.1-8080-2)
------- Begin Message Trace -------
Service -> {urn:com.edevera.switchyard.app2:switchyard-ejb-app2-test:1.0-SNAPSHOT}Service
Operation -> operation
Phase -> IN
State -> OK
Exchange Context ->
Message Context ->
org.switchyard.contentType : java:com.edevera.switchyard.api.Request
org.switchyard.messageId : 981ca863-99c2-4bdf-9695-3146d4b372fd
Message Content ->
com.edevera.switchyard.api.Request@53f1fe88
------ End Message Trace -------
18:23:43,083 WARN [org.switchyard.security.jboss.JBossJaasSecurityProvider] (http--127.0.0.1-8080-2) SwitchYard security domain (other) does not match JBoss security domain (jboss-web-policy).
18:23:43,088 WARN [org.switchyard.internal.ExchangeImpl] (http--127.0.0.1-8080-2) Fault generated during exchange without a handler: org.switchyard.HandlerException: java.lang.NullPointerException
--- Caused by java.lang.NullPointerException: null
18:23:43,133 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-12) Apache Camel 0.8.0.Final (CamelContext: camel-1) is shutting down
18:23:43,133 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-5) Apache Camel 0.8.0.Final (CamelContext: camel-2) is shutting down
18:23:43,135 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (MSC service thread 1-12) Starting to graceful shutdown 1 routes (timeout 300 seconds)
18:23:43,135 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (MSC service thread 1-5) Starting to graceful shutdown 1 routes (timeout 300 seconds)
18:23:43,139 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (Camel (camel-1) thread #2 - ShutdownTask) Route: direct:{urn:com.edevera.switchyard.app2:switchyard-ejb-app2-test:1.0-SNAPSHOT}Service shutdown complete, was consuming from: Endpoint[direct://%7Burn:com.edevera.switchyard.app2:switchyard-ejb-app2-test:1.0-SNAPSHOT%7DService]
18:23:43,139 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (Camel (camel-2) thread #3 - ShutdownTask) Route: direct:{urn:com.edevera.switchyard.app2:switchyard-ejb-app2:1.0-SNAPSHOT}ServiceB shutdown complete, was consuming from: Endpoint[direct://%7Burn:com.edevera.switchyard.app2:switchyard-ejb-app2:1.0-SNAPSHOT%7DServiceB]
18:23:43,140 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (MSC service thread 1-12) Graceful shutdown of 1 routes completed in 0 seconds
18:23:43,141 INFO [org.apache.camel.impl.DefaultShutdownStrategy] (MSC service thread 1-5) Graceful shutdown of 1 routes completed in 0 seconds
18:23:43,151 INFO [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-5) TypeConverterRegistry utilization[attempts=0, hits=0, misses=0, failures=0] mappings[total=179, misses=0]
18:23:43,151 INFO [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-12) TypeConverterRegistry utilization[attempts=1, hits=1, misses=0, failures=0] mappings[total=179, misses=0]
18:23:43,154 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-5) Apache Camel 0.8.0.Final (CamelContext: camel-2) is shutdown in 0.021 seconds. Uptime 1.720 seconds.
18:23:43,154 INFO [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-12) Apache Camel 0.8.0.Final (CamelContext: camel-1) is shutdown in 0.021 seconds. Uptime 1.720 seconds.
18:23:43,156 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016009: Stopping weld service for deployment serviceb.ear
18:23:43,172 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015877: Stopped deployment serviceb-imp.jar in 49ms
18:23:43,173 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment test.war in 51ms
18:23:43,179 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment serviceb.ear in 56ms
18:23:43,193 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /Applications/switchyard-as7-0.8/standalone/data/content/5e/8b8ec9d6248c3d5561edc481606e441e918182/content
18:23:43,194 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "serviceb.ear"
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.778 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.682s
[INFO] Finished at: Wed May 01 18:23:43 CEST 2013
[INFO] Final Memory: 25M/337M
[INFO] ------------------------------------------------------------------------
Process finished with exit code 0
Doubts I have:
- I don't understand why I see two services shown (bold on previous log), the service itself and the reference.
- I have added the JAR file inside the EAR as an ejb module in the application.xml, otherwise SwitchYard would not recognize the SwitchYard Application.
- Why does the message trace point to calling a service with the targetnamespace of the reference instead of the targetnamespace of the actual service?
The source code can be found at the following Github link.
