ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Maletta" <simonemale...@alice.it>
Subject WAR and JBI
Date Mon, 10 Mar 2008 13:51:06 GMT
Hi guys,
    I'm trying to develope a project I create for ODE war version into jbi one.
I've got problem doing this thing: always I've got this error stack:
ERROR - OdeServiceUnit                 - Unable to load {http://localhost:8080/call}Call-13
org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint {urn:/echo.wsdl}echoOutService:echoOutPort
for process {http://localhost:8080/call}Call-13
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:48)
        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
        at org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104)
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:123)
        at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jbi.JBIException: An internal endpoint for service {urn:/echo.wsdl}echoOutService
and endpoint echoOutPort is already registered
        at org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint(EndpointRegistry.java:189)
        at org.apache.servicemix.jbi.framework.Registry.activateEndpoint(Registry.java:192)
        at org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:126)
        at org.apache.ode.jbi.OdeService.activate(OdeService.java:82)
        at org.apache.ode.jbi.OdeContext.activateEndpoint(OdeContext.java:189)
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:46)
        ... 14 more
ERROR - OdeSUManager                   - Error starting service unit "call-ode".
org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint {urn:/echo.wsdl}echoOutService:echoOutPort
for process {http://localhost:8080/call}Call-13
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:48)
        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
        at org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104)
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:123)
        at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jbi.JBIException: An internal endpoint for service {urn:/echo.wsdl}echoOutService
and endpoint echoOutPort is already registered
        at org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint(EndpointRegistry.java:189)
        at org.apache.servicemix.jbi.framework.Registry.activateEndpoint(Registry.java:192)
        at org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:126)
        at org.apache.ode.jbi.OdeService.activate(OdeService.java:82)
        at org.apache.ode.jbi.OdeContext.activateEndpoint(OdeContext.java:189)
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:46)
        ... 14 more
[Fatal Error] :1:1: Content is not allowed in prolog.
WARN  - ServiceAssemblyLifeCycle       - Could not parse result exception
org.xml.sax.SAXParseException: Content is not allowed in prolog.
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.parse(ServiceAssemblyLifeCycle.java:421)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.getComponentFailure(ServiceAssemblyLifeCycle.java:402)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:132)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
INFO  - ServiceUnitLifeCycle           - Starting service unit: call-http
INFO  - DeploymentService              - Error in start
java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message" version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result>
<component-name>OdeBpelEngine</component-name>
<component-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Unable to parse result string</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<loc-token/>
<loc-message>Error starting service unit "call-ode".</loc-message>
<stack-trace><![CDATA[javax.jbi.management.DeploymentException: Error starting service
unit "call-ode".
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:127)
        at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint {urn:/echo.wsdl}echoOutService:echoOutPort
for process {http://localhost:8080/call}Call-13
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:48)
        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
        at org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104)
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:123)
        ... 9 more
Caused by: javax.jbi.JBIException: An internal endpoint for service {urn:/echo.wsdl}echoOutService
and endpoint echoOutPort is already registered
        at org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint(EndpointRegistry.java:189)
        at org.apache.servicemix.jbi.framework.Registry.activateEndpoint(Registry.java:192)
        at org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:126)
        at org.apache.ode.jbi.OdeService.activate(OdeService.java:82)
        at org.apache.ode.jbi.OdeContext.activateEndpoint(OdeContext.java:189)
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:46)
        ... 14 more
]]></stack-trace>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>

        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
ERROR - AutoDeploymentService          - Failed to update Service Assembly: echo-jms/http-sa
java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message" version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result>
<component-name>OdeBpelEngine</component-name>
<component-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Unable to parse result string</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<loc-token/>
<loc-message>Error starting service unit "call-ode".</loc-message>
<stack-trace><![CDATA[javax.jbi.management.DeploymentException: Error starting service
unit "call-ode".
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:127)
        at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint {urn:/echo.wsdl}echoOutService:echoOutPort
for process {http://localhost:8080/call}Call-13
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:48)
        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
        at org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104)
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:123)
        ... 9 more
Caused by: javax.jbi.JBIException: An internal endpoint for service {urn:/echo.wsdl}echoOutService
and endpoint echoOutPort is already registered
        at org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint(EndpointRegistry.java:189)
        at org.apache.servicemix.jbi.framework.Registry.activateEndpoint(Registry.java:192)
        at org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:126)
        at org.apache.ode.jbi.OdeService.activate(OdeService.java:82)
        at org.apache.ode.jbi.OdeContext.activateEndpoint(OdeContext.java:189)
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:46)
        ... 14 more
]]></stack-trace>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>

        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
WARN  - AutoDeploymentService          - Directory: deploy: Automatic install of /home/jars/apache/apache-servicemix-3.1.2/deploy/call-sa.zip
failed
javax.jbi.management.DeploymentException: Failed to update Service Assembly: echo-jms/http-sa
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:349)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message" version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result>
<component-name>OdeBpelEngine</component-name>
<component-task-result-details>
<task-result-details>
<task-id>start</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Unable to parse result string</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<loc-token/>
<loc-message>Error starting service unit "call-ode".</loc-message>
<stack-trace><![CDATA[javax.jbi.management.DeploymentException: Error starting service
unit "call-ode".
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:127)
        at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:646)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentService.java:62)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:609)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: org.apache.ode.bpel.iapi.ContextException: Could not activate endpoint {urn:/echo.wsdl}echoOutService:echoOutPort
for process {http://localhost:8080/call}Call-13
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:48)
        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
        at org.apache.ode.jbi.OdeServiceUnit.start(OdeServiceUnit.java:104)
        at org.apache.ode.jbi.OdeSUManager.start(OdeSUManager.java:123)
        ... 9 more
Caused by: javax.jbi.JBIException: An internal endpoint for service {urn:/echo.wsdl}echoOutService
and endpoint echoOutPort is already registered
        at org.apache.servicemix.jbi.framework.EndpointRegistry.registerInternalEndpoint(EndpointRegistry.java:189)
        at org.apache.servicemix.jbi.framework.Registry.activateEndpoint(Registry.java:192)
        at org.apache.servicemix.jbi.framework.ComponentContextImpl.activateEndpoint(ComponentContextImpl.java:126)
        at org.apache.ode.jbi.OdeService.activate(OdeService.java:82)
        at org.apache.ode.jbi.OdeContext.activateEndpoint(OdeContext.java:189)
        at org.apache.ode.jbi.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:46)
        ... 14 more
]]></stack-trace>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>

        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:121)
        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:107)
        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:144)
        at org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:374)
        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:337)
        ... 5 more

My project is very simple:
an async Echo Server is exposed on jms and another service call, a sync one, try to interact
with it, using port defined by echo . Call service too is exposed on jms.
The fact is that in the WAR version it works and in the jbi I've got the error.
May I by-pass it?
To be clear I attach here my files:
-------------------call.wsdl------------------------
<wsdl:portType name="callPortType">

<wsdl:operation name="call">

<wsdl:input message="tns:callMessage" name="Input"/>

<wsdl:output message="tns:callMessage" name="Output"/>

</wsdl:operation> 

</wsdl:portType> 

<plnk:partnerLinkType name="callPartnerLinkType">

<plnk:role name="me" portType="tns:callPortType"/>

<!-- <plnk:role name="you" portType="tns:callPortType"/>-->

</plnk:partnerLinkType>



-----------------------------echo.wsdl-------------------------------------

<wsdl:portType name="echoOutPortType">

<wsdl:operation name="echoOut">

<wsdl:input name="outMex" message="tns:echoMessage"/>

</wsdl:operation>

</wsdl:portType>



<plnk:partnerLinkType name="echoInPartnerLinkType">

<plnk:role name="provider" portType="tns:echoInPortType"/>

<plnk:role name="consumer" portType="tns:echoOutPortType"/>

</plnk:partnerLinkType>

----------------------------echo.bpel------------------------



<partnerLink 

name="echoInPartnerLink" 

partnerLinkType="test:echoInPartnerLinkType"

myRole="provider"

partnerRole="consumer"/>



-------------------------------call.bpel--------------------------------

<partnerLink

name="echoIn"

partnerLinkType="echo:echoInPartnerLinkType"

myRole="consumer"

partnerRole="provider"/>

---------------deploy.xml----------------------------

<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"

xmlns:callB="http://localhost:8080/call" 

xmlns:callW="http://localhost:8080/call.wsdl"

xmlns:pns="urn:/echo" 

xmlns:wns="urn:/echo.wsdl">

<process name="callB:Call">

<active>true</active>

<provide partnerLink="callPartnerLink">

<service name="callW:callService" port="callPort"/>

</provide>

<provide partnerLink="echoIn">

<service name="wns:echoOutService" port="echoOutPort"/>

</provide>

<invoke partnerLink="echoIn">

<service name="wns:echoInService" port="echoInPort"/>

</invoke>

</process>

<process name="pns:Echo">

<active>true</active>

<provide partnerLink="echoInPartnerLink">

<service name="wns:echoInService" port="echoInPort"/>

</provide>

<invoke partnerLink="echoInPartnerLink">

<service name="wns:echoOutService" port="echoOutPort"/>

</invoke>

</process>

</deploy>



I make another test: I split partnerLinkType from echo into two one, echoInPartnerLinkType
and echoOutPartnerLinkType, changing properly other files obviuosly, but I hang the same error.

Please, there is someone who has got a solution for my problem?

It is a master point into my own thesis.

Thank you, regards,

Simone


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message