Ode will activate a JBI endpoint for all partner links with a myRole role IIRC.
So you need to make sure the parternLinks and the deploy.xml are consistent
with what you want to achieve.
If {urn:/echo.wsdl}echoOutService:echoOutPort represents an endpoint that will
be consumed, this means the partern link role is not myRole.

On Thu, Mar 6, 2008 at 4:15 PM, Simone Maletta <[EMAIL PROTECTED]> wrote:
> Hi Guillaume,
>   It's true the endpoint is activated yet by the service, deployed yet into
>  a different SA.
>  I want that a Mediator, deployed into another SA, use the endpoint activated
>  from the service, I need not to activate a new endpoint.
>  There is a way to say to the component to use that service?
>  This is my Holy Graal, I want to develope every single process into a
>  diffrent SA and mediator into its one.
>  I want that the mediator can communicate with services using async
>  communication channel.
>  May you help me?
>  Thank you
>  Regards
>  Simone
>
>
>  ----- Original Message -----
>  From: "Guillaume Nodet" <[EMAIL PROTECTED]>
>  To: <[email protected]>
>
>
> Sent: Thursday, March 06, 2008 3:45 PM
>  Subject: Re: Mediator and Services
>
>
>  > The problems comes from the fact that the endpoint that is being
>  > activated already exists.
>  > See
>  >  Caused by: javax.jbi.JBIException: An internal endpoint for service
>  > {urn:/echo.wsdl}echoOutService and endpoint echoOutPort is already
>  > registered
>  >
>  > Did you deploy your SA in a clean ServiceMix ?  Or maybe another SU
>  > has already activated this endpoint.
>  >
>  > On Thu, Mar 6, 2008 at 3:38 PM, Simone Maletta <[EMAIL PROTECTED]>
>  > wrote:
>  >> Re: Mediator and ServicesHi Guillaume,
>  >>     I think the error come from the fact that the mediator have to
>  >> provide the port but it does not implements it in its wsdl, because I
>  >> want that it use the one realized on the services.
>  >>  There is no problem when the're in the same SA but in the background I
>  >> depicted I got the error; here is the full stack trace:
>  >>
>  >>  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
>  >>
>  >>
>  >>  Mapping with the example I made in the previous mail Call is MyService
>  >> and echoOutPort is BPort.
>  >>  I add that I'm using JMS transport, but my goal is not using simply it
>  >> but hanging its semantic too.
>  >>  I underline, Mediator and services are in different SA.
>  >>  Thank you for your time, regards
>  >>  Simone
>  >>
>  >>
>  >>
>  >>   ----- Original Message -----
>  >>   From: Guillaume Nodet
>  >>   To: [email protected]
>  >>   Sent: Thursday, March 06, 2008 3:08 PM
>  >>   Subject: Re: Mediator and Services
>  >>
>  >>
>  >>   Well, I don't understand where the error comes from.
>  >>   What would be the reason ? The bpel should be able to activate new JBI
>  >>   endpoints.
>  >>   Do you have the full stack trace, maybe it contains some useful
>  >> informations ?
>  >>
>  >>   On Wed, Mar 5, 2008 at 7:05 PM, Simone Maletta <[EMAIL PROTECTED]>
>  >> wrote:
>  >>   > Hi guys,
>  >>   >     I'm using ServiceMix 3.1.2 and Ode 1.1 to develope my master
>  >> thesis.
>  >>   >  This is what I want to do:
>  >>   >    1) developing into a service architecture a BPEL process that
>  >> scores some JWS communicating with them using a synchronous interface on
>  >> HTTP and showing an asynchronous one on JMS, I will call these services.
>  >>   >  2) developing into a service architecture a BPEL process that scores
>  >> the services that I will call mediator. A mediator may scores mediators
>  >> to.
>  >>   >
>  >>   >  My problem is: to develope a service in an async way I have to
>  >> describe the output port in its wsdl, defining in its descriptor that I
>  >> invoke it; for example:
>  >>   >
>  >>   >  ---wsdl---
>  >>   >  <portType name="A">
>  >>   >     [...]
>  >>   >  </portType>
>  >>   >
>  >>   >  <portType name="B">
>  >>   >     [...]
>  >>   >  </portType>
>  >>   >
>  >>   >  <partnerLinkType name="Aplt" >
>  >>   >     <role name="Arole" portType="A"/>
>  >>   >  </partnerLinkType>
>  >>   >
>  >>   >  <partnerLinkType name="Bplt" >
>  >>   >     <role name="Brole" portType="B"/>
>  >>   >  </partnerLinkType>
>  >>   >
>  >>   >
>  >>   >  ----------deploy--------------
>  >>   >
>  >>   >  <service name="MyService">
>  >>   >     <provide partnerLink="Apl">
>  >>   >         <service name="AService" port="APort">
>  >>   >     </provide>
>  >>   >
>  >>   >     <invoke partnerLink="Bpl">
>  >>   >         <service name="BService" port="BPort">
>  >>   >     </invoke>
>  >>   >  </service>
>  >>   >
>  >>   >
>  >>   >
>  >>   >  If I want a service that communicate with this I have to write the
>  >> deploy file turned, providing B and invoking A.
>  >>   >  If I try doing so in two different service units I take this error:
>  >>   >
>  >>   >  org.apache.ode.bpel.iapi.ContextException: Could not activate
>  >> endpoint{ }BService: BPort for process {  }MyService
>  >>   >
>  >>   >  I understand where the error come from, but may I bypass It?
>  >>   >  There is a way to explore the bus in the deploy.xml or exposing the
>  >> link in a different way?
>  >>   >  please help me,
>  >>   >  Simone
>  >>   >
>  >>   >
>  >>
>  >>
>  >>
>  >>   --
>  >>   Cheers,
>  >>   Guillaume Nodet
>  >>   ------------------------
>  >>   Blog: http://gnodet.blogspot.com/
>  >>
>  >>
>  >
>  >
>  >
>  > --
>  > Cheers,
>  > Guillaume Nodet
>  > ------------------------
>  > Blog: http://gnodet.blogspot.com/
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to