You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Simone Maletta <si...@alice.it> on 2008/03/05 19:05:42 UTC
Mediator and Services
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
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
Hi Guillaume,
I've got now a better behaviour from the one I had in the past; I
discovered that I was activating two endpoint: one with the deploy.xml file
for Call, using the partnerLink, the other one was the jms endpoint,
associating to the server the queue.
I understand that I do not have more than a couple service+endpoint.
Now, my SA is deployed but I've got problem at runtime:
If I change the endpoint name, my Echo server is activated but I've got no
feedback, also if I change the service name putting the endpoint to the
callService I hang this error:
ERROR - BpelEngineImpl - Scheduled job failed;
jobDetail={ckey=-1~hqejbhcnphr33sbirhcl2v, correlatorId=15.echoOut,
inmem=false, iid=3803, type=MATCHER}
java.lang.NullPointerException
at
org.apache.ode.dao.jpa.MessageExchangeDAOImpl.getCorrelationKeys(MessageExchangeDAOImpl.java:320)
at
org.apache.ode.dao.jpa.CorrelatorDAOImpl.dequeueMessage(CorrelatorDAOImpl.java:74)
at
org.apache.ode.bpel.engine.BpelRuntimeContextImpl.matcherEvent(BpelRuntimeContextImpl.java:1316)
at
org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:342)
at
org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:318)
at
org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:364)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:335)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:334)
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:173)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:333)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:330)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
ERROR - SimpleScheduler - Error while executing transaction
org.apache.ode.bpel.iapi.Scheduler$JobProcessorException:
java.lang.NullPointerException
at
org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:328)
at
org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:364)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:335)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:334)
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:173)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:333)
at
org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:330)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at
org.apache.ode.dao.jpa.MessageExchangeDAOImpl.getCorrelationKeys(MessageExchangeDAOImpl.java:320)
at
org.apache.ode.dao.jpa.CorrelatorDAOImpl.dequeueMessage(CorrelatorDAOImpl.java:74)
at
org.apache.ode.bpel.engine.BpelRuntimeContextImpl.matcherEvent(BpelRuntimeContextImpl.java:1316)
at
org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:342)
at
org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:318)
... 11 more
It's true I don't desire to put the endpoint on the client because I need a
client indipendent server.
A thing I observe: the ConsumerQueue is not created.
To be clear I attach here my xbean.xml configuration file:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:jms="http://servicemix.apache.org/jms/1.0"
xmlns:lb="urn:/echo.wsdl"
xmlns:cl="urn:/call.wsdl">
<jms:endpoint service="lb:echoInService"
endpoint="echoInPort"
targetService="lb:echoInService"
defaultOperation="lb:echoIn"
role="consumer"
connectionFactory="#jmsFactory"
destinationStyle="queue"
soap="true"
jmsProviderDestinationName="ProviderQueue"
defaultMep="http://www.w3.org/2004/08/wsdl/in-only" />
<!-- <jms:consumer service="lb:echoInService"
endpoint="echoInPort"
targetService="lb:echoInService"
concurrentConsumers="1"
connectionFactory="#jmsFactory"
destinationName="ProviderQueue"
synchronous="true"/>-->
<jms:endpoint service="lb:echoOutService"
endpoint="OutPort"
role="provider"
connectionFactory="#jmsFactory"
destinationStyle="queue"
soap="true"
jmsProviderDestinationName="ConsumerQueue" />
<jms:endpoint service="cl:callService"
endpoint="callPort"
targetService="cl:callService"
defaultOperation="cl:call"
role="consumer"
connectionFactory="#jmsFactory"
destinationStyle="queue"
soap="true"
jmsProviderDestinationName="callProviderQueue"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out" />
<bean id="jmsFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="tcp://localhost:61616" />
</bean>
</property>
</bean>
</beans>
Please Help me, I'm sure today I may close my work.
Thank you for your time, regards
Simone
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Sunday, March 09, 2008 7:56 PM
Subject: Re: Mediator and Services
> Your deploy.xml looks good, but as I said, they must be correct wrt
> the wsdl and
> bpel process sections for partnerLinks, especially the myRole info in the
> bpel
> process.
>
> I think there may be a problem, but unrelated to the exception you
> pasted earlier.
> The problem may be if Ode requires the JBI endpoint to exist at the
> time the SU is
> started. As you have two BPEL process that call each-other, it would
> fail in such
> case. But I can't recall if the endpoint is discovered when started
> or the first time
> it is actually used.
>
> On Sun, Mar 9, 2008 at 9:46 AM, Simone Maletta <si...@alice.it>
> wrote:
>> Hi Guillaume,
>> I looed at Loan-Broker BPEL examples but it is very different from my
>> own, in fact in my deploy.xml file for echo I write:
>> <process name="pns:Echo">
>>
>> <type>pns:Echo</type>
>>
>> <provide partnerLink="echoPartnerLink">
>>
>> <service name="wns:echoService" port="echoInPort"/>
>>
>> </provide>
>>
>> <invoke partnerLink="echoPartnerLink">
>>
>> <service name="wns:echoService" port="echoOutPort"/>
>>
>> </invoke>
>>
>>
>>
>> While in the one for call I've got:
>>
>>
>> <process name="callB:Call">
>>
>> <active>true</active>
>>
>> <provide partnerLink="callPartnerLink">
>>
>> <service name="callW:callService" port="callPort"/>
>>
>> </provide>
>>
>> <provide partnerLink="asyncPartnerLink">
>>
>> <service name="wns:echoService" port="echoOutPort"/>
>>
>> </provide>
>>
>> <invoke partnerLink="asyncPartnerLink">
>>
>> <service name="wns:echoService" port="echoInPort"/>
>>
>> </invoke>
>>
>> </process>
>>
>>
>>
>> It seems look like more than DynamicPartnerLink example than to the
>> loan-broker one.
>>
>> I'm sure here comes the problem.
>>
>> Where it is?
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Sunday, March 09, 2008 9:27 AM
>> Subject: Re: Mediator and Services
>>
>>
>> >I really think the problem comes from your wsdls, deploy.xml and bpel.
>> > Being in 2 differents SAs should not change anything and you can test
>> > in a single SA if you prefer. As you have two different processes, I
>> > would
>> > recommend testing them separatly: create one process and deploy some
>> > fake services that will implement the other process wsdl using
>> > servicemix-jsr181
>> > (look at the wsdl-first example and loan-broker). Then do the same
>> with
>> > the
>> > second, without modifying the files for the first one. At the end
>> you
>> > should
>> > be able to deploy the two SAs.
>> >
>> > The main problem imo is that your ODE SU activates some endpoints
>> instead
>> > of just using existing ones: when calling a service outside the bpel,
>> the
>> > bpel
>> > process should not activate any endpoint. ENdpoints need to be
>> activated
>> > when receiving messages, which is what the myRole partnerLink should
>> > indicate.
>> > Have you been able to do that ? You may want to look at the
>> loan-broker
>> > example which activates a BPEL process and call other services.
>> >
>> > On Sun, Mar 9, 2008 at 9:18 AM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> Hi Guillaume,
>> >> I just do what you say, and I've got the problem.
>> >> The call that read use <provide> but the port is realized by
>> echo.wsdl,
>> >> the
>> >> ona that use <invoke> into its configuration file.
>> >> I just thing to this, but the fact that their in two different SA
>> for me
>> >> is
>> >> the core.
>> >> I don't know a way to solve!!
>> >> Do you prefere I past my ode into a mail? Or that I'll send my files
>> to
>> >> the
>> >> community?
>> >> Please help me, I'm coming mad.
>> >>
>> >> Regards,
>> >> Simone
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Saturday, March 08, 2008 10:37 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> > On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta
>> >> <si...@alice.it>
>> >> > wrote:
>> >> >> Hi Guillaume,
>> >> >> your suggest has got sense and I tried to apply it but the
>> >> problem
>> >> >> persists.
>> >> >> In fact the point stands in the creation of a new endpoint while
>> the
>> >> >> system
>> >> >> has to understand that it should use the existing one.
>> >> >> The stack trace is always the same, roles have changed their
>> name
>> >> but as
>> >> >> usual I got the same error.
>> >> >> Now the path is the same but echoPLT.wsdl differs one from
>> another,
>> >> in
>> >> >> the
>> >> >> one putted in the service directory I've got:
>> >> >>
>> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> >> <plnk:role name="consumer" portType="echoOutPortType"/>
>> >> >> </plnk:partnerLinkType>
>> >> >>
>> >> >> and in the mediator one:
>> >> >>
>> >> >> <plnk:partnerLinkType name="readPLT">
>> >> >> <plnk:role name="callReader"
>> portType="echoOutPortType"/>
>> >> >> </plnk:partnerLinkType>
>> >> >>
>> >> >> the deploy.xml files do not change.
>> >> >
>> >> > Well, one is suppose to use a <provide> while the other use
>> <invoke>.
>> >> > Also, one BPEL will have <bpel:partnerLink myRole ../> while the
>> other
>> >> > has <bpel:partnerLink partnerRole />
>> >> >
>> >> > If you do this, it should work.
>> >> >
>> >> >> Then what I have to do? Have you got any Idea?
>> >> >> Please help me, this is a very important point into my thesy's
>> >> stack.
>> >> >>
>> >> >> Regards,
>> >> >> Simone
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> Sent: Friday, March 07, 2008 1:17 PM
>> >> >> Subject: Re: Mediator and Services
>> >> >>
>> >> >>
>> >> >> >I guess you have missed the concept of partner links somehow.
>> >> >> > It is used to indicate how a given service is used: if it is
>> >> consumer
>> >> >> or
>> >> >> > provided. If you want your BPEL processes to communicate
>> >> together.
>> >> >> > it usually means that one process will provide a service that
>> will
>> >> be
>> >> >> > consumed by the other one. This leads to the fact that the
>> >> partner
>> >> >> links
>> >> >> > for the same service definition has to be different for the
>> two
>> >> >> processes.
>> >> >> > That's why i suggested to split the main WSDL from the partner
>> >> links:
>> >> >> > you can reuse the service definition, and externalize the
>> partner
>> >> >> links in
>> >> >> > two different files.
>> >> >> > Makes sense ?
>> >> >> >
>> >> >> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta
>> >> >> <si...@alice.it>
>> >> >> > wrote:
>> >> >> >> No, they are the same file.
>> >> >> >> If I define different file how may hang a single
>> endpoint?
>> >> >> >> You say that I have to define same partnerLinkType with
>> >> different
>> >> >> role
>> >> >> >> to
>> >> >> >> permit my process communicating between them?
>> >> >> >>
>> >> >> >>
>> >> >> >> ----- Original Message -----
>> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >> Sent: Friday, March 07, 2008 12:01 PM
>> >> >> >> Subject: Re: Mediator and Services
>> >> >> >>
>> >> >> >>
>> >> >> >> > So the two echoPLT.wsdl are different, each one having a
>> >> different
>> >> >> >> role ?
>> >> >> >> >
>> >> >> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
>> >> >> >> <si...@alice.it>
>> >> >> >> > wrote:
>> >> >> >> >> Goodmorning Guillame,
>> >> >> >> >> I followed your councile but I'm at the same point of
>> >> >> yesterday,
>> >> >> >> I've
>> >> >> >> >> got same error and my call-sa does not work.
>> >> >> >> >> I split the main file and now my SA are:
>> >> >> >> >>
>> >> >> >> >> +---deploy
>> >> >> >> >> |
>> >> >> >> >> |
>> >> >> >> >> \---echo-jms-sa
>> >> >> >> >> | |
>> >> >> >> >> | |
>> >> >> >> >> | \-----META-INF
>> >> >> >> >> | | |
>> >> >> >> >> | | ---jbi-xml
>> >> >> >> >> | | \
>> >> >> >> >> | \---echo-jms-su
>> >> >> >> >> | | |
>> >> >> >> >> | | |
>> >> >> >> >> | | ---xbean.xml
>> >> >> >> >> | | \
>> >> >> >> >> | \-----echo-ode-su
>> >> >> >> >> | |
>> >> >> >> >> | |
>> >> >> >> >> | +--------echo.wsdl
>> >> >> >> >> | +---------echoPLT.wsdl
>> >> >> >> >> | +---------echo.bpel
>> >> >> >> >> | +---------deploy.xml
>> >> >> >> >> | \
>> >> >> >> >> \---------call-sa
>> >> >> >> >> | |
>> >> >> >> >> | \-----META-INF
>> >> >> >> >> \ |
>> >> >> >> >> |
>> >> >> >> >> \-----call-http-su
>> >> >> >> >> | |
>> >> >> >> >> | +--call.wsdl
>> >> >> >> >> |
>> >> >> >> >> \----call-ode-sa
>> >> >> >> >> | |
>> >> >> >> >> | +-----call.wsdl
>> >> >> >> >> \ +-----echo.wsdl
>> >> >> >> >> +-----echoPLT.wsdl
>> >> >> >> >> +-----call.bpel
>> >> >> >> >> \
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Where echoPLT import echo.wsdl (using the same namespace
>> >> while
>> >> >> >> instead
>> >> >> >> >> there
>> >> >> >> >> are problems referencing endopoint and the module will
>> never
>> >> >> >> activate).
>> >> >> >> >> Again Call is my own Mediator and echo my service.
>> >> >> >> >> My I bypass the needs to activate another endpoijnt and
>> >> using
>> >> >> the
>> >> >> >> >> existing
>> >> >> >> >> one?
>> >> >> >> >> Please gimme a response,
>> >> >> >> >>
>> >> >> >> >> Regards,
>> >> >> >> >> Simone
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> ----- Original Message -----
>> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Sent: Thursday, March 06, 2008 5:40 PM
>> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> > You need to split the wsdl from the partner links. For
>> >> partenr
>> >> >> >> links,
>> >> >> >> >> > define a wsdl
>> >> >> >> >> > and import the main one. That way, you can define
>> >> different
>> >> >> roles
>> >> >> >> for
>> >> >> >> >> > the service
>> >> >> >> >> > and the bpel that calls it.
>> >> >> >> >> >
>> >> >> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
>> >> >> >> >> <si...@alice.it>
>> >> >> >> >> > wrote:
>> >> >> >> >> >> That's true,
>> >> >> >> >> >> In Call echoOut has got myRole role because Call
>> >> reads on
>> >> >> it,
>> >> >> >> I
>> >> >> >> >> have
>> >> >> >> >> >> got
>> >> >> >> >> >> problems deploying Call.
>> >> >> >> >> >> The problem that's that I define the service and the
>> >> port
>> >> >> into
>> >> >> >> Echo
>> >> >> >> >> WSDL
>> >> >> >> >> >> and
>> >> >> >> >> >> not in Call one.
>> >> >> >> >> >> The trace is correct, I'm trying to define a my role
>> on
>> >> a
>> >> >> link
>> >> >> >> where
>> >> >> >> >> I
>> >> >> >> >> >> read
>> >> >> >> >> >> in an asynchronous way, so I need to define a
>> myRole,
>> >> I'm at
>> >> >> >> this
>> >> >> >> >> >> conclusion
>> >> >> >> >> >> in an empyt.
>> >> >> >> >> >> Well, Call is my mediator and Echo my service.
>> >> >> >> >> >> To be clear here is parts of my files:
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> -----------------------echo.wsdl--------------------------
>> >> >> >> >> >> <wsdl:portType name="echoInPortType">
>> >> >> >> >> >>
>> >> >> >> >> >> <wsdl:operation name="echoIn">
>> >> >> >> >> >>
>> >> >> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
>> >> >> >> >> >>
>> >> >> >> >> >> </wsdl:operation>
>> >> >> >> >> >>
>> >> >> >> >> >> </wsdl:portType>
>> >> >> >> >> >>
>> >> >> >> >> >> <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:partnerLinkType>
>> >> >> >> >> >>
>> >> >> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> >> >> >> >>
>> >> >> >> >> >> <plnk:role name="consumer"
>> >> portType="tns:echoOutPortType"/>
>> >> >> >> >> >>
>> >> >> >> >> >> </plnk:partnerLinkType>
>> >> >> >> >> >>
>> >> >> >> >> >> ----------------------echo.bpel-----------------
>> >> >> >> >> >>
>> >> >> >> >> >> <partnerLink
>> >> >> >> >> >>
>> >> >> >> >> >> name="echoInPartnerLink"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
>> >> >> >> >> >>
>> >> >> >> >> >> myRole="provider"/>
>> >> >> >> >> >>
>> >> >> >> >> >> <partnerLink
>> >> >> >> >> >>
>> >> >> >> >> >> name="echoOutPartnerLink"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerRole="consumer"/>
>> >> >> >> >> >>
>> >> >> >> >> >> -------------------------deploy.xml---------------
>> >> >> >> >> echo-su---------[in
>> >> >> >> >> >> echo-sa]
>> >> >> >> >> >>
>> >> >> >> >> >> process name="pns:Echo">
>> >> >> >> >> >> <active>true</active>
>> >> >> >> >> >> <provide
>> partnerLink="echoInPartnerLink">
>> >> >> >> >> >> <service
>> name="wns:echoInService"
>> >> >> >> >> >> port="echoInPort"/>
>> >> >> >> >> >> </provide>
>> >> >> >> >> >> <invoke
>> partnerLink="echoOutPartnerLink">
>> >> >> >> >> >> <service
>> >> name="wns:echoOutService"
>> >> >> >> >> >> port="echoOutPort"/>
>> >> >> >> >> >> </invoke>
>> >> >> >> >> >> </process>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> -----------------------call.bpel--------------------------
>> >> >> >> >> >> <partnerLink
>> >> >> >> >> >>
>> >> >> >> >> >> name="echoIn"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerRole="provider"/>
>> >> >> >> >> >>
>> >> >> >> >> >> <partnerLink
>> >> >> >> >> >>
>> >> >> >> >> >> name="echoOut"
>> >> >> >> >> >>
>> >> >> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
>> >> >> >> >> >>
>> >> >> >> >> >> myRole="consumer"/>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >>
>> >> -------------------------------deploy.xml---------------[call-su
>> >> >> >> in
>> >> >> >> >> >> call-sa]------------------
>> >> >> >> >> >>
>> >> >> >> >> >> <process name="callB:Call">
>> >> >> >> >> >>
>> >> >> >> >> >> <active>true</active>
>> >> >> >> >> >>
>> >> >> >> >> >> <provide partnerLink="callPartnerLink">
>> >> >> >> >> >>
>> >> >> >> >> >> <service name="callW:callService" port="callPort"/>
>> >> >> >> >> >>
>> >> >> >> >> >> </provide>
>> >> >> >> >> >>
>> >> >> >> >> >> <provide partnerLink="echoOut">
>> >> >> >> >> >>
>> >> >> >> >> >> <service name="wns:echoOutService"
>> port="echoOutPort"/>
>> >> >> >> >> >>
>> >> >> >> >> >> </provide>
>> >> >> >> >> >>
>> >> >> >> >> >> <invoke partnerLink="echoIn">
>> >> >> >> >> >>
>> >> >> >> >> >> <service name="wns:echoInService"
>> port="echoInPort"/>
>> >> >> >> >> >>
>> >> >> >> >> >> </invoke>
>> >> >> >> >> >>
>> >> >> >> >> >> </process>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> I think the porblem come from the fact I'm using two
>> >> >> different
>> >> >> >> SA.
>> >> >> >> >> >>
>> >> >> >> >> >> May it be?
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> ----- Original Message -----
>> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
>> >> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> > Could you please raise a JIRA and attach the WSDL,
>> and
>> >> >> >> deploy.xml
>> >> >> >> >> >> files.
>> >> >> >> >> >> > If you look at the stack trace, it clearly shows
>> that
>> >> Ode
>> >> >> is
>> >> >> >> >> condering
>> >> >> >> >> >> > that the endpoint
>> >> >> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> >> >> >> >> >> > has a partner link with a "myRole" role.
>> >> >> >> >> >> >
>> >> >> >> >> >> > See:
>> >> >> >> >> >> > 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)
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> > wrote:
>> >> >> >> >> >> >> I'm sorry I don't understand;
>> >> >> >> >> >> >> this is my background:
>> >> >> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut,
>> each
>> >> one
>> >> >> >> having an
>> >> >> >> >> own
>> >> >> >> >> >> >> partner
>> >> >> >> >> >> >> link type associated echoInPartnerLinkType
>> >> >> >> >> echoOutPartnerLinkType.
>> >> >> >> >> >> >> In the BPEL I define two partner links echoInPL
>> and
>> >> >> >> echoOutPL,
>> >> >> >> >> echo
>> >> >> >> >> >> >> read on
>> >> >> >> >> >> >> echoInPL defining myRole, and write on echoOutPL
>> >> >> defining a
>> >> >> >> >> >> partnerRole.
>> >> >> >> >> >> >> In the deploy Echo provide echoIn and invoke
>> >> echoOut.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> 2) Call use echoInPartnerLink and
>> echoOutPartnerLink
>> >> >> with
>> >> >> >> echoIn
>> >> >> >> >> and
>> >> >> >> >> >> >> echoOut, writeing on the first, partnerRole, and
>> >> reading
>> >> >> on
>> >> >> >> the
>> >> >> >> >> >> second,
>> >> >> >> >> >> >> myRole.
>> >> >> >> >> >> >> In the deploy Call provide echoOut and invoke
>> >> echoIn.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> echoInPort-echoInService and
>> >> echoOutPort-echoOutService
>> >> >> are
>> >> >> >> >> >> activated
>> >> >> >> >> >> >> into
>> >> >> >> >> >> >> Echo WSDL.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> If I change roles in PL description I've got a
>> >> compiler
>> >> >> >> error,
>> >> >> >> >> ODe
>> >> >> >> >> >> says
>> >> >> >> >> >> >> me
>> >> >> >> >> >> >> that my partnerLinks do not define other role[
>> if I
>> >> >> define a
>> >> >> >> my
>> >> >> >> >> role
>> >> >> >> >> >> on
>> >> >> >> >> >> >> writing it says that this link does not define a
>> >> >> >> partnerRole].
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Now, what I have to change?
>> >> >> >> >> >> >> I'm sorry if I may apper insistent, but I want
>> to
>> >> have a
>> >> >> >> clear
>> >> >> >> >> >> picture
>> >> >> >> >> >> >> in a
>> >> >> >> >> >> >> silly example.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Thank you,
>> >> >> >> >> >> >> Regards
>> >> >> >> >> >> >> Simone
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> ----- Original Message -----
>> >> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> >> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> > 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
>> >> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> > 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" <gn...@gmail.com>
>> >> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >> >> >>
>> >> >> >> >> >> >> >>
>> >> >> >> >> >> >> >> 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
>> >> >> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> >> > 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: users@servicemix.apache.org
>> >> >> >> >> >> >> >> >> 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
>> >> >> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> >> >> 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/
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > --
>> >> >> >> >> >> > Cheers,
>> >> >> >> >> >> > Guillaume Nodet
>> >> >> >> >> >> > ------------------------
>> >> >> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Cheers,
>> >> >> >> >> > Guillaume Nodet
>> >> >> >> >> > ------------------------
>> >> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cheers,
>> >> >> >> > Guillaume Nodet
>> >> >> >> > ------------------------
>> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> > ------------------------
>> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> > ------------------------
>> >> > Blog: http://gnodet.blogspot.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
Your deploy.xml looks good, but as I said, they must be correct wrt
the wsdl and
bpel process sections for partnerLinks, especially the myRole info in the bpel
process.
I think there may be a problem, but unrelated to the exception you
pasted earlier.
The problem may be if Ode requires the JBI endpoint to exist at the
time the SU is
started. As you have two BPEL process that call each-other, it would
fail in such
case. But I can't recall if the endpoint is discovered when started
or the first time
it is actually used.
On Sun, Mar 9, 2008 at 9:46 AM, Simone Maletta <si...@alice.it> wrote:
> Hi Guillaume,
> I looed at Loan-Broker BPEL examples but it is very different from my
> own, in fact in my deploy.xml file for echo I write:
> <process name="pns:Echo">
>
> <type>pns:Echo</type>
>
> <provide partnerLink="echoPartnerLink">
>
> <service name="wns:echoService" port="echoInPort"/>
>
> </provide>
>
> <invoke partnerLink="echoPartnerLink">
>
> <service name="wns:echoService" port="echoOutPort"/>
>
> </invoke>
>
>
>
> While in the one for call I've got:
>
>
> <process name="callB:Call">
>
> <active>true</active>
>
> <provide partnerLink="callPartnerLink">
>
> <service name="callW:callService" port="callPort"/>
>
> </provide>
>
> <provide partnerLink="asyncPartnerLink">
>
> <service name="wns:echoService" port="echoOutPort"/>
>
> </provide>
>
> <invoke partnerLink="asyncPartnerLink">
>
> <service name="wns:echoService" port="echoInPort"/>
>
> </invoke>
>
> </process>
>
>
>
> It seems look like more than DynamicPartnerLink example than to the
> loan-broker one.
>
> I'm sure here comes the problem.
>
> Where it is?
>
>
>
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Sunday, March 09, 2008 9:27 AM
> Subject: Re: Mediator and Services
>
>
> >I really think the problem comes from your wsdls, deploy.xml and bpel.
> > Being in 2 differents SAs should not change anything and you can test
> > in a single SA if you prefer. As you have two different processes, I
> > would
> > recommend testing them separatly: create one process and deploy some
> > fake services that will implement the other process wsdl using
> > servicemix-jsr181
> > (look at the wsdl-first example and loan-broker). Then do the same with
> > the
> > second, without modifying the files for the first one. At the end you
> > should
> > be able to deploy the two SAs.
> >
> > The main problem imo is that your ODE SU activates some endpoints instead
> > of just using existing ones: when calling a service outside the bpel, the
> > bpel
> > process should not activate any endpoint. ENdpoints need to be activated
> > when receiving messages, which is what the myRole partnerLink should
> > indicate.
> > Have you been able to do that ? You may want to look at the loan-broker
> > example which activates a BPEL process and call other services.
> >
> > On Sun, Mar 9, 2008 at 9:18 AM, Simone Maletta <si...@alice.it>
> > wrote:
> >> Hi Guillaume,
> >> I just do what you say, and I've got the problem.
> >> The call that read use <provide> but the port is realized by echo.wsdl,
> >> the
> >> ona that use <invoke> into its configuration file.
> >> I just thing to this, but the fact that their in two different SA for me
> >> is
> >> the core.
> >> I don't know a way to solve!!
> >> Do you prefere I past my ode into a mail? Or that I'll send my files to
> >> the
> >> community?
> >> Please help me, I'm coming mad.
> >>
> >> Regards,
> >> Simone
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Saturday, March 08, 2008 10:37 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> > On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta
> >> <si...@alice.it>
> >> > wrote:
> >> >> Hi Guillaume,
> >> >> your suggest has got sense and I tried to apply it but the
> >> problem
> >> >> persists.
> >> >> In fact the point stands in the creation of a new endpoint while the
> >> >> system
> >> >> has to understand that it should use the existing one.
> >> >> The stack trace is always the same, roles have changed their name
> >> but as
> >> >> usual I got the same error.
> >> >> Now the path is the same but echoPLT.wsdl differs one from another,
> >> in
> >> >> the
> >> >> one putted in the service directory I've got:
> >> >>
> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> >> <plnk:role name="consumer" portType="echoOutPortType"/>
> >> >> </plnk:partnerLinkType>
> >> >>
> >> >> and in the mediator one:
> >> >>
> >> >> <plnk:partnerLinkType name="readPLT">
> >> >> <plnk:role name="callReader" portType="echoOutPortType"/>
> >> >> </plnk:partnerLinkType>
> >> >>
> >> >> the deploy.xml files do not change.
> >> >
> >> > Well, one is suppose to use a <provide> while the other use <invoke>.
> >> > Also, one BPEL will have <bpel:partnerLink myRole ../> while the other
> >> > has <bpel:partnerLink partnerRole />
> >> >
> >> > If you do this, it should work.
> >> >
> >> >> Then what I have to do? Have you got any Idea?
> >> >> Please help me, this is a very important point into my thesy's
> >> stack.
> >> >>
> >> >> Regards,
> >> >> Simone
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> Sent: Friday, March 07, 2008 1:17 PM
> >> >> Subject: Re: Mediator and Services
> >> >>
> >> >>
> >> >> >I guess you have missed the concept of partner links somehow.
> >> >> > It is used to indicate how a given service is used: if it is
> >> consumer
> >> >> or
> >> >> > provided. If you want your BPEL processes to communicate
> >> together.
> >> >> > it usually means that one process will provide a service that will
> >> be
> >> >> > consumed by the other one. This leads to the fact that the
> >> partner
> >> >> links
> >> >> > for the same service definition has to be different for the two
> >> >> processes.
> >> >> > That's why i suggested to split the main WSDL from the partner
> >> links:
> >> >> > you can reuse the service definition, and externalize the partner
> >> >> links in
> >> >> > two different files.
> >> >> > Makes sense ?
> >> >> >
> >> >> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta
> >> >> <si...@alice.it>
> >> >> > wrote:
> >> >> >> No, they are the same file.
> >> >> >> If I define different file how may hang a single endpoint?
> >> >> >> You say that I have to define same partnerLinkType with
> >> different
> >> >> role
> >> >> >> to
> >> >> >> permit my process communicating between them?
> >> >> >>
> >> >> >>
> >> >> >> ----- Original Message -----
> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >>
> >> >> >>
> >> >> >> Sent: Friday, March 07, 2008 12:01 PM
> >> >> >> Subject: Re: Mediator and Services
> >> >> >>
> >> >> >>
> >> >> >> > So the two echoPLT.wsdl are different, each one having a
> >> different
> >> >> >> role ?
> >> >> >> >
> >> >> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
> >> >> >> <si...@alice.it>
> >> >> >> > wrote:
> >> >> >> >> Goodmorning Guillame,
> >> >> >> >> I followed your councile but I'm at the same point of
> >> >> yesterday,
> >> >> >> I've
> >> >> >> >> got same error and my call-sa does not work.
> >> >> >> >> I split the main file and now my SA are:
> >> >> >> >>
> >> >> >> >> +---deploy
> >> >> >> >> |
> >> >> >> >> |
> >> >> >> >> \---echo-jms-sa
> >> >> >> >> | |
> >> >> >> >> | |
> >> >> >> >> | \-----META-INF
> >> >> >> >> | | |
> >> >> >> >> | | ---jbi-xml
> >> >> >> >> | | \
> >> >> >> >> | \---echo-jms-su
> >> >> >> >> | | |
> >> >> >> >> | | |
> >> >> >> >> | | ---xbean.xml
> >> >> >> >> | | \
> >> >> >> >> | \-----echo-ode-su
> >> >> >> >> | |
> >> >> >> >> | |
> >> >> >> >> | +--------echo.wsdl
> >> >> >> >> | +---------echoPLT.wsdl
> >> >> >> >> | +---------echo.bpel
> >> >> >> >> | +---------deploy.xml
> >> >> >> >> | \
> >> >> >> >> \---------call-sa
> >> >> >> >> | |
> >> >> >> >> | \-----META-INF
> >> >> >> >> \ |
> >> >> >> >> |
> >> >> >> >> \-----call-http-su
> >> >> >> >> | |
> >> >> >> >> | +--call.wsdl
> >> >> >> >> |
> >> >> >> >> \----call-ode-sa
> >> >> >> >> | |
> >> >> >> >> | +-----call.wsdl
> >> >> >> >> \ +-----echo.wsdl
> >> >> >> >> +-----echoPLT.wsdl
> >> >> >> >> +-----call.bpel
> >> >> >> >> \
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Where echoPLT import echo.wsdl (using the same namespace
> >> while
> >> >> >> instead
> >> >> >> >> there
> >> >> >> >> are problems referencing endopoint and the module will never
> >> >> >> activate).
> >> >> >> >> Again Call is my own Mediator and echo my service.
> >> >> >> >> My I bypass the needs to activate another endpoijnt and
> >> using
> >> >> the
> >> >> >> >> existing
> >> >> >> >> one?
> >> >> >> >> Please gimme a response,
> >> >> >> >>
> >> >> >> >> Regards,
> >> >> >> >> Simone
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> ----- Original Message -----
> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Sent: Thursday, March 06, 2008 5:40 PM
> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> > You need to split the wsdl from the partner links. For
> >> partenr
> >> >> >> links,
> >> >> >> >> > define a wsdl
> >> >> >> >> > and import the main one. That way, you can define
> >> different
> >> >> roles
> >> >> >> for
> >> >> >> >> > the service
> >> >> >> >> > and the bpel that calls it.
> >> >> >> >> >
> >> >> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
> >> >> >> >> <si...@alice.it>
> >> >> >> >> > wrote:
> >> >> >> >> >> That's true,
> >> >> >> >> >> In Call echoOut has got myRole role because Call
> >> reads on
> >> >> it,
> >> >> >> I
> >> >> >> >> have
> >> >> >> >> >> got
> >> >> >> >> >> problems deploying Call.
> >> >> >> >> >> The problem that's that I define the service and the
> >> port
> >> >> into
> >> >> >> Echo
> >> >> >> >> WSDL
> >> >> >> >> >> and
> >> >> >> >> >> not in Call one.
> >> >> >> >> >> The trace is correct, I'm trying to define a my role on
> >> a
> >> >> link
> >> >> >> where
> >> >> >> >> I
> >> >> >> >> >> read
> >> >> >> >> >> in an asynchronous way, so I need to define a myRole,
> >> I'm at
> >> >> >> this
> >> >> >> >> >> conclusion
> >> >> >> >> >> in an empyt.
> >> >> >> >> >> Well, Call is my mediator and Echo my service.
> >> >> >> >> >> To be clear here is parts of my files:
> >> >> >> >> >>
> >> >> >> >>
> >> >> -----------------------echo.wsdl--------------------------
> >> >> >> >> >> <wsdl:portType name="echoInPortType">
> >> >> >> >> >>
> >> >> >> >> >> <wsdl:operation name="echoIn">
> >> >> >> >> >>
> >> >> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
> >> >> >> >> >>
> >> >> >> >> >> </wsdl:operation>
> >> >> >> >> >>
> >> >> >> >> >> </wsdl:portType>
> >> >> >> >> >>
> >> >> >> >> >> <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:partnerLinkType>
> >> >> >> >> >>
> >> >> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> >> >> >> >>
> >> >> >> >> >> <plnk:role name="consumer"
> >> portType="tns:echoOutPortType"/>
> >> >> >> >> >>
> >> >> >> >> >> </plnk:partnerLinkType>
> >> >> >> >> >>
> >> >> >> >> >> ----------------------echo.bpel-----------------
> >> >> >> >> >>
> >> >> >> >> >> <partnerLink
> >> >> >> >> >>
> >> >> >> >> >> name="echoInPartnerLink"
> >> >> >> >> >>
> >> >> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
> >> >> >> >> >>
> >> >> >> >> >> myRole="provider"/>
> >> >> >> >> >>
> >> >> >> >> >> <partnerLink
> >> >> >> >> >>
> >> >> >> >> >> name="echoOutPartnerLink"
> >> >> >> >> >>
> >> >> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
> >> >> >> >> >>
> >> >> >> >> >> partnerRole="consumer"/>
> >> >> >> >> >>
> >> >> >> >> >> -------------------------deploy.xml---------------
> >> >> >> >> echo-su---------[in
> >> >> >> >> >> echo-sa]
> >> >> >> >> >>
> >> >> >> >> >> process name="pns:Echo">
> >> >> >> >> >> <active>true</active>
> >> >> >> >> >> <provide partnerLink="echoInPartnerLink">
> >> >> >> >> >> <service name="wns:echoInService"
> >> >> >> >> >> port="echoInPort"/>
> >> >> >> >> >> </provide>
> >> >> >> >> >> <invoke partnerLink="echoOutPartnerLink">
> >> >> >> >> >> <service
> >> name="wns:echoOutService"
> >> >> >> >> >> port="echoOutPort"/>
> >> >> >> >> >> </invoke>
> >> >> >> >> >> </process>
> >> >> >> >> >>
> >> >> >> >>
> >> >> -----------------------call.bpel--------------------------
> >> >> >> >> >> <partnerLink
> >> >> >> >> >>
> >> >> >> >> >> name="echoIn"
> >> >> >> >> >>
> >> >> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
> >> >> >> >> >>
> >> >> >> >> >> partnerRole="provider"/>
> >> >> >> >> >>
> >> >> >> >> >> <partnerLink
> >> >> >> >> >>
> >> >> >> >> >> name="echoOut"
> >> >> >> >> >>
> >> >> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
> >> >> >> >> >>
> >> >> >> >> >> myRole="consumer"/>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> -------------------------------deploy.xml---------------[call-su
> >> >> >> in
> >> >> >> >> >> call-sa]------------------
> >> >> >> >> >>
> >> >> >> >> >> <process name="callB:Call">
> >> >> >> >> >>
> >> >> >> >> >> <active>true</active>
> >> >> >> >> >>
> >> >> >> >> >> <provide partnerLink="callPartnerLink">
> >> >> >> >> >>
> >> >> >> >> >> <service name="callW:callService" port="callPort"/>
> >> >> >> >> >>
> >> >> >> >> >> </provide>
> >> >> >> >> >>
> >> >> >> >> >> <provide partnerLink="echoOut">
> >> >> >> >> >>
> >> >> >> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
> >> >> >> >> >>
> >> >> >> >> >> </provide>
> >> >> >> >> >>
> >> >> >> >> >> <invoke partnerLink="echoIn">
> >> >> >> >> >>
> >> >> >> >> >> <service name="wns:echoInService" port="echoInPort"/>
> >> >> >> >> >>
> >> >> >> >> >> </invoke>
> >> >> >> >> >>
> >> >> >> >> >> </process>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> I think the porblem come from the fact I'm using two
> >> >> different
> >> >> >> SA.
> >> >> >> >> >>
> >> >> >> >> >> May it be?
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> ----- Original Message -----
> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
> >> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> > Could you please raise a JIRA and attach the WSDL, and
> >> >> >> deploy.xml
> >> >> >> >> >> files.
> >> >> >> >> >> > If you look at the stack trace, it clearly shows that
> >> Ode
> >> >> is
> >> >> >> >> condering
> >> >> >> >> >> > that the endpoint
> >> >> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
> >> >> >> >> >> > has a partner link with a "myRole" role.
> >> >> >> >> >> >
> >> >> >> >> >> > See:
> >> >> >> >> >> > 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)
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> > wrote:
> >> >> >> >> >> >> I'm sorry I don't understand;
> >> >> >> >> >> >> this is my background:
> >> >> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each
> >> one
> >> >> >> having an
> >> >> >> >> own
> >> >> >> >> >> >> partner
> >> >> >> >> >> >> link type associated echoInPartnerLinkType
> >> >> >> >> echoOutPartnerLinkType.
> >> >> >> >> >> >> In the BPEL I define two partner links echoInPL and
> >> >> >> echoOutPL,
> >> >> >> >> echo
> >> >> >> >> >> >> read on
> >> >> >> >> >> >> echoInPL defining myRole, and write on echoOutPL
> >> >> defining a
> >> >> >> >> >> partnerRole.
> >> >> >> >> >> >> In the deploy Echo provide echoIn and invoke
> >> echoOut.
> >> >> >> >> >> >>
> >> >> >> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink
> >> >> with
> >> >> >> echoIn
> >> >> >> >> and
> >> >> >> >> >> >> echoOut, writeing on the first, partnerRole, and
> >> reading
> >> >> on
> >> >> >> the
> >> >> >> >> >> second,
> >> >> >> >> >> >> myRole.
> >> >> >> >> >> >> In the deploy Call provide echoOut and invoke
> >> echoIn.
> >> >> >> >> >> >>
> >> >> >> >> >> >> echoInPort-echoInService and
> >> echoOutPort-echoOutService
> >> >> are
> >> >> >> >> >> activated
> >> >> >> >> >> >> into
> >> >> >> >> >> >> Echo WSDL.
> >> >> >> >> >> >>
> >> >> >> >> >> >> If I change roles in PL description I've got a
> >> compiler
> >> >> >> error,
> >> >> >> >> ODe
> >> >> >> >> >> says
> >> >> >> >> >> >> me
> >> >> >> >> >> >> that my partnerLinks do not define other role[ if I
> >> >> define a
> >> >> >> my
> >> >> >> >> role
> >> >> >> >> >> on
> >> >> >> >> >> >> writing it says that this link does not define a
> >> >> >> partnerRole].
> >> >> >> >> >> >>
> >> >> >> >> >> >> Now, what I have to change?
> >> >> >> >> >> >> I'm sorry if I may apper insistent, but I want to
> >> have a
> >> >> >> clear
> >> >> >> >> >> picture
> >> >> >> >> >> >> in a
> >> >> >> >> >> >> silly example.
> >> >> >> >> >> >>
> >> >> >> >> >> >> Thank you,
> >> >> >> >> >> >> Regards
> >> >> >> >> >> >> Simone
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> ----- Original Message -----
> >> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> >> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> > 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
> >> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> > 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" <gn...@gmail.com>
> >> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >>
> >> >> >> >> >> >> >> 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
> >> >> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> >> > 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: users@servicemix.apache.org
> >> >> >> >> >> >> >> >> 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
> >> >> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> >> >> 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/
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> > Cheers,
> >> >> >> >> >> > Guillaume Nodet
> >> >> >> >> >> > ------------------------
> >> >> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Cheers,
> >> >> >> >> > Guillaume Nodet
> >> >> >> >> > ------------------------
> >> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cheers,
> >> >> >> > Guillaume Nodet
> >> >> >> > ------------------------
> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> > ------------------------
> >> >> > Blog: http://gnodet.blogspot.com/
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
Hi Guillaume,
I looed at Loan-Broker BPEL examples but it is very different from my
own, in fact in my deploy.xml file for echo I write:
<process name="pns:Echo">
<type>pns:Echo</type>
<provide partnerLink="echoPartnerLink">
<service name="wns:echoService" port="echoInPort"/>
</provide>
<invoke partnerLink="echoPartnerLink">
<service name="wns:echoService" port="echoOutPort"/>
</invoke>
While in the one for call I've got:
<process name="callB:Call">
<active>true</active>
<provide partnerLink="callPartnerLink">
<service name="callW:callService" port="callPort"/>
</provide>
<provide partnerLink="asyncPartnerLink">
<service name="wns:echoService" port="echoOutPort"/>
</provide>
<invoke partnerLink="asyncPartnerLink">
<service name="wns:echoService" port="echoInPort"/>
</invoke>
</process>
It seems look like more than DynamicPartnerLink example than to the
loan-broker one.
I'm sure here comes the problem.
Where it is?
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Sunday, March 09, 2008 9:27 AM
Subject: Re: Mediator and Services
>I really think the problem comes from your wsdls, deploy.xml and bpel.
> Being in 2 differents SAs should not change anything and you can test
> in a single SA if you prefer. As you have two different processes, I
> would
> recommend testing them separatly: create one process and deploy some
> fake services that will implement the other process wsdl using
> servicemix-jsr181
> (look at the wsdl-first example and loan-broker). Then do the same with
> the
> second, without modifying the files for the first one. At the end you
> should
> be able to deploy the two SAs.
>
> The main problem imo is that your ODE SU activates some endpoints instead
> of just using existing ones: when calling a service outside the bpel, the
> bpel
> process should not activate any endpoint. ENdpoints need to be activated
> when receiving messages, which is what the myRole partnerLink should
> indicate.
> Have you been able to do that ? You may want to look at the loan-broker
> example which activates a BPEL process and call other services.
>
> On Sun, Mar 9, 2008 at 9:18 AM, Simone Maletta <si...@alice.it>
> wrote:
>> Hi Guillaume,
>> I just do what you say, and I've got the problem.
>> The call that read use <provide> but the port is realized by echo.wsdl,
>> the
>> ona that use <invoke> into its configuration file.
>> I just thing to this, but the fact that their in two different SA for me
>> is
>> the core.
>> I don't know a way to solve!!
>> Do you prefere I past my ode into a mail? Or that I'll send my files to
>> the
>> community?
>> Please help me, I'm coming mad.
>>
>> Regards,
>> Simone
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Saturday, March 08, 2008 10:37 PM
>> Subject: Re: Mediator and Services
>>
>>
>> > On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> Hi Guillaume,
>> >> your suggest has got sense and I tried to apply it but the
>> problem
>> >> persists.
>> >> In fact the point stands in the creation of a new endpoint while the
>> >> system
>> >> has to understand that it should use the existing one.
>> >> The stack trace is always the same, roles have changed their name
>> but as
>> >> usual I got the same error.
>> >> Now the path is the same but echoPLT.wsdl differs one from another,
>> in
>> >> the
>> >> one putted in the service directory I've got:
>> >>
>> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> <plnk:role name="consumer" portType="echoOutPortType"/>
>> >> </plnk:partnerLinkType>
>> >>
>> >> and in the mediator one:
>> >>
>> >> <plnk:partnerLinkType name="readPLT">
>> >> <plnk:role name="callReader" portType="echoOutPortType"/>
>> >> </plnk:partnerLinkType>
>> >>
>> >> the deploy.xml files do not change.
>> >
>> > Well, one is suppose to use a <provide> while the other use <invoke>.
>> > Also, one BPEL will have <bpel:partnerLink myRole ../> while the other
>> > has <bpel:partnerLink partnerRole />
>> >
>> > If you do this, it should work.
>> >
>> >> Then what I have to do? Have you got any Idea?
>> >> Please help me, this is a very important point into my thesy's
>> stack.
>> >>
>> >> Regards,
>> >> Simone
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Friday, March 07, 2008 1:17 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> >I guess you have missed the concept of partner links somehow.
>> >> > It is used to indicate how a given service is used: if it is
>> consumer
>> >> or
>> >> > provided. If you want your BPEL processes to communicate
>> together.
>> >> > it usually means that one process will provide a service that will
>> be
>> >> > consumed by the other one. This leads to the fact that the
>> partner
>> >> links
>> >> > for the same service definition has to be different for the two
>> >> processes.
>> >> > That's why i suggested to split the main WSDL from the partner
>> links:
>> >> > you can reuse the service definition, and externalize the partner
>> >> links in
>> >> > two different files.
>> >> > Makes sense ?
>> >> >
>> >> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta
>> >> <si...@alice.it>
>> >> > wrote:
>> >> >> No, they are the same file.
>> >> >> If I define different file how may hang a single endpoint?
>> >> >> You say that I have to define same partnerLinkType with
>> different
>> >> role
>> >> >> to
>> >> >> permit my process communicating between them?
>> >> >>
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> Sent: Friday, March 07, 2008 12:01 PM
>> >> >> Subject: Re: Mediator and Services
>> >> >>
>> >> >>
>> >> >> > So the two echoPLT.wsdl are different, each one having a
>> different
>> >> >> role ?
>> >> >> >
>> >> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
>> >> >> <si...@alice.it>
>> >> >> > wrote:
>> >> >> >> Goodmorning Guillame,
>> >> >> >> I followed your councile but I'm at the same point of
>> >> yesterday,
>> >> >> I've
>> >> >> >> got same error and my call-sa does not work.
>> >> >> >> I split the main file and now my SA are:
>> >> >> >>
>> >> >> >> +---deploy
>> >> >> >> |
>> >> >> >> |
>> >> >> >> \---echo-jms-sa
>> >> >> >> | |
>> >> >> >> | |
>> >> >> >> | \-----META-INF
>> >> >> >> | | |
>> >> >> >> | | ---jbi-xml
>> >> >> >> | | \
>> >> >> >> | \---echo-jms-su
>> >> >> >> | | |
>> >> >> >> | | |
>> >> >> >> | | ---xbean.xml
>> >> >> >> | | \
>> >> >> >> | \-----echo-ode-su
>> >> >> >> | |
>> >> >> >> | |
>> >> >> >> | +--------echo.wsdl
>> >> >> >> | +---------echoPLT.wsdl
>> >> >> >> | +---------echo.bpel
>> >> >> >> | +---------deploy.xml
>> >> >> >> | \
>> >> >> >> \---------call-sa
>> >> >> >> | |
>> >> >> >> | \-----META-INF
>> >> >> >> \ |
>> >> >> >> |
>> >> >> >> \-----call-http-su
>> >> >> >> | |
>> >> >> >> | +--call.wsdl
>> >> >> >> |
>> >> >> >> \----call-ode-sa
>> >> >> >> | |
>> >> >> >> | +-----call.wsdl
>> >> >> >> \ +-----echo.wsdl
>> >> >> >> +-----echoPLT.wsdl
>> >> >> >> +-----call.bpel
>> >> >> >> \
>> >> >> >>
>> >> >> >>
>> >> >> >> Where echoPLT import echo.wsdl (using the same namespace
>> while
>> >> >> instead
>> >> >> >> there
>> >> >> >> are problems referencing endopoint and the module will never
>> >> >> activate).
>> >> >> >> Again Call is my own Mediator and echo my service.
>> >> >> >> My I bypass the needs to activate another endpoijnt and
>> using
>> >> the
>> >> >> >> existing
>> >> >> >> one?
>> >> >> >> Please gimme a response,
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Simone
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> ----- Original Message -----
>> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >> Sent: Thursday, March 06, 2008 5:40 PM
>> >> >> >> Subject: Re: Mediator and Services
>> >> >> >>
>> >> >> >>
>> >> >> >> > You need to split the wsdl from the partner links. For
>> partenr
>> >> >> links,
>> >> >> >> > define a wsdl
>> >> >> >> > and import the main one. That way, you can define
>> different
>> >> roles
>> >> >> for
>> >> >> >> > the service
>> >> >> >> > and the bpel that calls it.
>> >> >> >> >
>> >> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
>> >> >> >> <si...@alice.it>
>> >> >> >> > wrote:
>> >> >> >> >> That's true,
>> >> >> >> >> In Call echoOut has got myRole role because Call
>> reads on
>> >> it,
>> >> >> I
>> >> >> >> have
>> >> >> >> >> got
>> >> >> >> >> problems deploying Call.
>> >> >> >> >> The problem that's that I define the service and the
>> port
>> >> into
>> >> >> Echo
>> >> >> >> WSDL
>> >> >> >> >> and
>> >> >> >> >> not in Call one.
>> >> >> >> >> The trace is correct, I'm trying to define a my role on
>> a
>> >> link
>> >> >> where
>> >> >> >> I
>> >> >> >> >> read
>> >> >> >> >> in an asynchronous way, so I need to define a myRole,
>> I'm at
>> >> >> this
>> >> >> >> >> conclusion
>> >> >> >> >> in an empyt.
>> >> >> >> >> Well, Call is my mediator and Echo my service.
>> >> >> >> >> To be clear here is parts of my files:
>> >> >> >> >>
>> >> >> >>
>> >> -----------------------echo.wsdl--------------------------
>> >> >> >> >> <wsdl:portType name="echoInPortType">
>> >> >> >> >>
>> >> >> >> >> <wsdl:operation name="echoIn">
>> >> >> >> >>
>> >> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
>> >> >> >> >>
>> >> >> >> >> </wsdl:operation>
>> >> >> >> >>
>> >> >> >> >> </wsdl:portType>
>> >> >> >> >>
>> >> >> >> >> <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:partnerLinkType>
>> >> >> >> >>
>> >> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> >> >> >>
>> >> >> >> >> <plnk:role name="consumer"
>> portType="tns:echoOutPortType"/>
>> >> >> >> >>
>> >> >> >> >> </plnk:partnerLinkType>
>> >> >> >> >>
>> >> >> >> >> ----------------------echo.bpel-----------------
>> >> >> >> >>
>> >> >> >> >> <partnerLink
>> >> >> >> >>
>> >> >> >> >> name="echoInPartnerLink"
>> >> >> >> >>
>> >> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
>> >> >> >> >>
>> >> >> >> >> myRole="provider"/>
>> >> >> >> >>
>> >> >> >> >> <partnerLink
>> >> >> >> >>
>> >> >> >> >> name="echoOutPartnerLink"
>> >> >> >> >>
>> >> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
>> >> >> >> >>
>> >> >> >> >> partnerRole="consumer"/>
>> >> >> >> >>
>> >> >> >> >> -------------------------deploy.xml---------------
>> >> >> >> echo-su---------[in
>> >> >> >> >> echo-sa]
>> >> >> >> >>
>> >> >> >> >> process name="pns:Echo">
>> >> >> >> >> <active>true</active>
>> >> >> >> >> <provide partnerLink="echoInPartnerLink">
>> >> >> >> >> <service name="wns:echoInService"
>> >> >> >> >> port="echoInPort"/>
>> >> >> >> >> </provide>
>> >> >> >> >> <invoke partnerLink="echoOutPartnerLink">
>> >> >> >> >> <service
>> name="wns:echoOutService"
>> >> >> >> >> port="echoOutPort"/>
>> >> >> >> >> </invoke>
>> >> >> >> >> </process>
>> >> >> >> >>
>> >> >> >>
>> >> -----------------------call.bpel--------------------------
>> >> >> >> >> <partnerLink
>> >> >> >> >>
>> >> >> >> >> name="echoIn"
>> >> >> >> >>
>> >> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
>> >> >> >> >>
>> >> >> >> >> partnerRole="provider"/>
>> >> >> >> >>
>> >> >> >> >> <partnerLink
>> >> >> >> >>
>> >> >> >> >> name="echoOut"
>> >> >> >> >>
>> >> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
>> >> >> >> >>
>> >> >> >> >> myRole="consumer"/>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> -------------------------------deploy.xml---------------[call-su
>> >> >> in
>> >> >> >> >> call-sa]------------------
>> >> >> >> >>
>> >> >> >> >> <process name="callB:Call">
>> >> >> >> >>
>> >> >> >> >> <active>true</active>
>> >> >> >> >>
>> >> >> >> >> <provide partnerLink="callPartnerLink">
>> >> >> >> >>
>> >> >> >> >> <service name="callW:callService" port="callPort"/>
>> >> >> >> >>
>> >> >> >> >> </provide>
>> >> >> >> >>
>> >> >> >> >> <provide partnerLink="echoOut">
>> >> >> >> >>
>> >> >> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
>> >> >> >> >>
>> >> >> >> >> </provide>
>> >> >> >> >>
>> >> >> >> >> <invoke partnerLink="echoIn">
>> >> >> >> >>
>> >> >> >> >> <service name="wns:echoInService" port="echoInPort"/>
>> >> >> >> >>
>> >> >> >> >> </invoke>
>> >> >> >> >>
>> >> >> >> >> </process>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> I think the porblem come from the fact I'm using two
>> >> different
>> >> >> SA.
>> >> >> >> >>
>> >> >> >> >> May it be?
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> ----- Original Message -----
>> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
>> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> > Could you please raise a JIRA and attach the WSDL, and
>> >> >> deploy.xml
>> >> >> >> >> files.
>> >> >> >> >> > If you look at the stack trace, it clearly shows that
>> Ode
>> >> is
>> >> >> >> condering
>> >> >> >> >> > that the endpoint
>> >> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> >> >> >> >> > has a partner link with a "myRole" role.
>> >> >> >> >> >
>> >> >> >> >> > See:
>> >> >> >> >> > 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)
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> >> >> >> >> <si...@alice.it>
>> >> >> >> >> > wrote:
>> >> >> >> >> >> I'm sorry I don't understand;
>> >> >> >> >> >> this is my background:
>> >> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each
>> one
>> >> >> having an
>> >> >> >> own
>> >> >> >> >> >> partner
>> >> >> >> >> >> link type associated echoInPartnerLinkType
>> >> >> >> echoOutPartnerLinkType.
>> >> >> >> >> >> In the BPEL I define two partner links echoInPL and
>> >> >> echoOutPL,
>> >> >> >> echo
>> >> >> >> >> >> read on
>> >> >> >> >> >> echoInPL defining myRole, and write on echoOutPL
>> >> defining a
>> >> >> >> >> partnerRole.
>> >> >> >> >> >> In the deploy Echo provide echoIn and invoke
>> echoOut.
>> >> >> >> >> >>
>> >> >> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink
>> >> with
>> >> >> echoIn
>> >> >> >> and
>> >> >> >> >> >> echoOut, writeing on the first, partnerRole, and
>> reading
>> >> on
>> >> >> the
>> >> >> >> >> second,
>> >> >> >> >> >> myRole.
>> >> >> >> >> >> In the deploy Call provide echoOut and invoke
>> echoIn.
>> >> >> >> >> >>
>> >> >> >> >> >> echoInPort-echoInService and
>> echoOutPort-echoOutService
>> >> are
>> >> >> >> >> activated
>> >> >> >> >> >> into
>> >> >> >> >> >> Echo WSDL.
>> >> >> >> >> >>
>> >> >> >> >> >> If I change roles in PL description I've got a
>> compiler
>> >> >> error,
>> >> >> >> ODe
>> >> >> >> >> says
>> >> >> >> >> >> me
>> >> >> >> >> >> that my partnerLinks do not define other role[ if I
>> >> define a
>> >> >> my
>> >> >> >> role
>> >> >> >> >> on
>> >> >> >> >> >> writing it says that this link does not define a
>> >> >> partnerRole].
>> >> >> >> >> >>
>> >> >> >> >> >> Now, what I have to change?
>> >> >> >> >> >> I'm sorry if I may apper insistent, but I want to
>> have a
>> >> >> clear
>> >> >> >> >> picture
>> >> >> >> >> >> in a
>> >> >> >> >> >> silly example.
>> >> >> >> >> >>
>> >> >> >> >> >> Thank you,
>> >> >> >> >> >> Regards
>> >> >> >> >> >> Simone
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> ----- Original Message -----
>> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> > 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
>> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> > 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" <gn...@gmail.com>
>> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> 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
>> >> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> > 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: users@servicemix.apache.org
>> >> >> >> >> >> >> >> 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
>> >> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> >> 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/
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > Cheers,
>> >> >> >> >> > Guillaume Nodet
>> >> >> >> >> > ------------------------
>> >> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cheers,
>> >> >> >> > Guillaume Nodet
>> >> >> >> > ------------------------
>> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> > ------------------------
>> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> > ------------------------
>> >> > Blog: http://gnodet.blogspot.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
I really think the problem comes from your wsdls, deploy.xml and bpel.
Being in 2 differents SAs should not change anything and you can test
in a single SA if you prefer. As you have two different processes, I would
recommend testing them separatly: create one process and deploy some
fake services that will implement the other process wsdl using servicemix-jsr181
(look at the wsdl-first example and loan-broker). Then do the same with the
second, without modifying the files for the first one. At the end you should
be able to deploy the two SAs.
The main problem imo is that your ODE SU activates some endpoints instead
of just using existing ones: when calling a service outside the bpel, the bpel
process should not activate any endpoint. ENdpoints need to be activated
when receiving messages, which is what the myRole partnerLink should indicate.
Have you been able to do that ? You may want to look at the loan-broker
example which activates a BPEL process and call other services.
On Sun, Mar 9, 2008 at 9:18 AM, Simone Maletta <si...@alice.it> wrote:
> Hi Guillaume,
> I just do what you say, and I've got the problem.
> The call that read use <provide> but the port is realized by echo.wsdl, the
> ona that use <invoke> into its configuration file.
> I just thing to this, but the fact that their in two different SA for me is
> the core.
> I don't know a way to solve!!
> Do you prefere I past my ode into a mail? Or that I'll send my files to the
> community?
> Please help me, I'm coming mad.
>
> Regards,
> Simone
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Saturday, March 08, 2008 10:37 PM
> Subject: Re: Mediator and Services
>
>
> > On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta <si...@alice.it>
> > wrote:
> >> Hi Guillaume,
> >> your suggest has got sense and I tried to apply it but the problem
> >> persists.
> >> In fact the point stands in the creation of a new endpoint while the
> >> system
> >> has to understand that it should use the existing one.
> >> The stack trace is always the same, roles have changed their name but as
> >> usual I got the same error.
> >> Now the path is the same but echoPLT.wsdl differs one from another, in
> >> the
> >> one putted in the service directory I've got:
> >>
> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> <plnk:role name="consumer" portType="echoOutPortType"/>
> >> </plnk:partnerLinkType>
> >>
> >> and in the mediator one:
> >>
> >> <plnk:partnerLinkType name="readPLT">
> >> <plnk:role name="callReader" portType="echoOutPortType"/>
> >> </plnk:partnerLinkType>
> >>
> >> the deploy.xml files do not change.
> >
> > Well, one is suppose to use a <provide> while the other use <invoke>.
> > Also, one BPEL will have <bpel:partnerLink myRole ../> while the other
> > has <bpel:partnerLink partnerRole />
> >
> > If you do this, it should work.
> >
> >> Then what I have to do? Have you got any Idea?
> >> Please help me, this is a very important point into my thesy's stack.
> >>
> >> Regards,
> >> Simone
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Friday, March 07, 2008 1:17 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> >I guess you have missed the concept of partner links somehow.
> >> > It is used to indicate how a given service is used: if it is consumer
> >> or
> >> > provided. If you want your BPEL processes to communicate together.
> >> > it usually means that one process will provide a service that will be
> >> > consumed by the other one. This leads to the fact that the partner
> >> links
> >> > for the same service definition has to be different for the two
> >> processes.
> >> > That's why i suggested to split the main WSDL from the partner links:
> >> > you can reuse the service definition, and externalize the partner
> >> links in
> >> > two different files.
> >> > Makes sense ?
> >> >
> >> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta
> >> <si...@alice.it>
> >> > wrote:
> >> >> No, they are the same file.
> >> >> If I define different file how may hang a single endpoint?
> >> >> You say that I have to define same partnerLinkType with different
> >> role
> >> >> to
> >> >> permit my process communicating between them?
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> Sent: Friday, March 07, 2008 12:01 PM
> >> >> Subject: Re: Mediator and Services
> >> >>
> >> >>
> >> >> > So the two echoPLT.wsdl are different, each one having a different
> >> >> role ?
> >> >> >
> >> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
> >> >> <si...@alice.it>
> >> >> > wrote:
> >> >> >> Goodmorning Guillame,
> >> >> >> I followed your councile but I'm at the same point of
> >> yesterday,
> >> >> I've
> >> >> >> got same error and my call-sa does not work.
> >> >> >> I split the main file and now my SA are:
> >> >> >>
> >> >> >> +---deploy
> >> >> >> |
> >> >> >> |
> >> >> >> \---echo-jms-sa
> >> >> >> | |
> >> >> >> | |
> >> >> >> | \-----META-INF
> >> >> >> | | |
> >> >> >> | | ---jbi-xml
> >> >> >> | | \
> >> >> >> | \---echo-jms-su
> >> >> >> | | |
> >> >> >> | | |
> >> >> >> | | ---xbean.xml
> >> >> >> | | \
> >> >> >> | \-----echo-ode-su
> >> >> >> | |
> >> >> >> | |
> >> >> >> | +--------echo.wsdl
> >> >> >> | +---------echoPLT.wsdl
> >> >> >> | +---------echo.bpel
> >> >> >> | +---------deploy.xml
> >> >> >> | \
> >> >> >> \---------call-sa
> >> >> >> | |
> >> >> >> | \-----META-INF
> >> >> >> \ |
> >> >> >> |
> >> >> >> \-----call-http-su
> >> >> >> | |
> >> >> >> | +--call.wsdl
> >> >> >> |
> >> >> >> \----call-ode-sa
> >> >> >> | |
> >> >> >> | +-----call.wsdl
> >> >> >> \ +-----echo.wsdl
> >> >> >> +-----echoPLT.wsdl
> >> >> >> +-----call.bpel
> >> >> >> \
> >> >> >>
> >> >> >>
> >> >> >> Where echoPLT import echo.wsdl (using the same namespace while
> >> >> instead
> >> >> >> there
> >> >> >> are problems referencing endopoint and the module will never
> >> >> activate).
> >> >> >> Again Call is my own Mediator and echo my service.
> >> >> >> My I bypass the needs to activate another endpoijnt and using
> >> the
> >> >> >> existing
> >> >> >> one?
> >> >> >> Please gimme a response,
> >> >> >>
> >> >> >> Regards,
> >> >> >> Simone
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> ----- Original Message -----
> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >>
> >> >> >>
> >> >> >> Sent: Thursday, March 06, 2008 5:40 PM
> >> >> >> Subject: Re: Mediator and Services
> >> >> >>
> >> >> >>
> >> >> >> > You need to split the wsdl from the partner links. For partenr
> >> >> links,
> >> >> >> > define a wsdl
> >> >> >> > and import the main one. That way, you can define different
> >> roles
> >> >> for
> >> >> >> > the service
> >> >> >> > and the bpel that calls it.
> >> >> >> >
> >> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
> >> >> >> <si...@alice.it>
> >> >> >> > wrote:
> >> >> >> >> That's true,
> >> >> >> >> In Call echoOut has got myRole role because Call reads on
> >> it,
> >> >> I
> >> >> >> have
> >> >> >> >> got
> >> >> >> >> problems deploying Call.
> >> >> >> >> The problem that's that I define the service and the port
> >> into
> >> >> Echo
> >> >> >> WSDL
> >> >> >> >> and
> >> >> >> >> not in Call one.
> >> >> >> >> The trace is correct, I'm trying to define a my role on a
> >> link
> >> >> where
> >> >> >> I
> >> >> >> >> read
> >> >> >> >> in an asynchronous way, so I need to define a myRole, I'm at
> >> >> this
> >> >> >> >> conclusion
> >> >> >> >> in an empyt.
> >> >> >> >> Well, Call is my mediator and Echo my service.
> >> >> >> >> To be clear here is parts of my files:
> >> >> >> >>
> >> >> >> >> -----------------------echo.wsdl--------------------------
> >> >> >> >> <wsdl:portType name="echoInPortType">
> >> >> >> >>
> >> >> >> >> <wsdl:operation name="echoIn">
> >> >> >> >>
> >> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
> >> >> >> >>
> >> >> >> >> </wsdl:operation>
> >> >> >> >>
> >> >> >> >> </wsdl:portType>
> >> >> >> >>
> >> >> >> >> <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:partnerLinkType>
> >> >> >> >>
> >> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> >> >> >>
> >> >> >> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
> >> >> >> >>
> >> >> >> >> </plnk:partnerLinkType>
> >> >> >> >>
> >> >> >> >> ----------------------echo.bpel-----------------
> >> >> >> >>
> >> >> >> >> <partnerLink
> >> >> >> >>
> >> >> >> >> name="echoInPartnerLink"
> >> >> >> >>
> >> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
> >> >> >> >>
> >> >> >> >> myRole="provider"/>
> >> >> >> >>
> >> >> >> >> <partnerLink
> >> >> >> >>
> >> >> >> >> name="echoOutPartnerLink"
> >> >> >> >>
> >> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
> >> >> >> >>
> >> >> >> >> partnerRole="consumer"/>
> >> >> >> >>
> >> >> >> >> -------------------------deploy.xml---------------
> >> >> >> echo-su---------[in
> >> >> >> >> echo-sa]
> >> >> >> >>
> >> >> >> >> process name="pns:Echo">
> >> >> >> >> <active>true</active>
> >> >> >> >> <provide partnerLink="echoInPartnerLink">
> >> >> >> >> <service name="wns:echoInService"
> >> >> >> >> port="echoInPort"/>
> >> >> >> >> </provide>
> >> >> >> >> <invoke partnerLink="echoOutPartnerLink">
> >> >> >> >> <service name="wns:echoOutService"
> >> >> >> >> port="echoOutPort"/>
> >> >> >> >> </invoke>
> >> >> >> >> </process>
> >> >> >> >>
> >> >> >> >> -----------------------call.bpel--------------------------
> >> >> >> >> <partnerLink
> >> >> >> >>
> >> >> >> >> name="echoIn"
> >> >> >> >>
> >> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
> >> >> >> >>
> >> >> >> >> partnerRole="provider"/>
> >> >> >> >>
> >> >> >> >> <partnerLink
> >> >> >> >>
> >> >> >> >> name="echoOut"
> >> >> >> >>
> >> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
> >> >> >> >>
> >> >> >> >> myRole="consumer"/>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> -------------------------------deploy.xml---------------[call-su
> >> >> in
> >> >> >> >> call-sa]------------------
> >> >> >> >>
> >> >> >> >> <process name="callB:Call">
> >> >> >> >>
> >> >> >> >> <active>true</active>
> >> >> >> >>
> >> >> >> >> <provide partnerLink="callPartnerLink">
> >> >> >> >>
> >> >> >> >> <service name="callW:callService" port="callPort"/>
> >> >> >> >>
> >> >> >> >> </provide>
> >> >> >> >>
> >> >> >> >> <provide partnerLink="echoOut">
> >> >> >> >>
> >> >> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
> >> >> >> >>
> >> >> >> >> </provide>
> >> >> >> >>
> >> >> >> >> <invoke partnerLink="echoIn">
> >> >> >> >>
> >> >> >> >> <service name="wns:echoInService" port="echoInPort"/>
> >> >> >> >>
> >> >> >> >> </invoke>
> >> >> >> >>
> >> >> >> >> </process>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> I think the porblem come from the fact I'm using two
> >> different
> >> >> SA.
> >> >> >> >>
> >> >> >> >> May it be?
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> ----- Original Message -----
> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> > Could you please raise a JIRA and attach the WSDL, and
> >> >> deploy.xml
> >> >> >> >> files.
> >> >> >> >> > If you look at the stack trace, it clearly shows that Ode
> >> is
> >> >> >> condering
> >> >> >> >> > that the endpoint
> >> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
> >> >> >> >> > has a partner link with a "myRole" role.
> >> >> >> >> >
> >> >> >> >> > See:
> >> >> >> >> > 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)
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
> >> >> >> >> <si...@alice.it>
> >> >> >> >> > wrote:
> >> >> >> >> >> I'm sorry I don't understand;
> >> >> >> >> >> this is my background:
> >> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one
> >> >> having an
> >> >> >> own
> >> >> >> >> >> partner
> >> >> >> >> >> link type associated echoInPartnerLinkType
> >> >> >> echoOutPartnerLinkType.
> >> >> >> >> >> In the BPEL I define two partner links echoInPL and
> >> >> echoOutPL,
> >> >> >> echo
> >> >> >> >> >> read on
> >> >> >> >> >> echoInPL defining myRole, and write on echoOutPL
> >> defining a
> >> >> >> >> partnerRole.
> >> >> >> >> >> In the deploy Echo provide echoIn and invoke echoOut.
> >> >> >> >> >>
> >> >> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink
> >> with
> >> >> echoIn
> >> >> >> and
> >> >> >> >> >> echoOut, writeing on the first, partnerRole, and reading
> >> on
> >> >> the
> >> >> >> >> second,
> >> >> >> >> >> myRole.
> >> >> >> >> >> In the deploy Call provide echoOut and invoke echoIn.
> >> >> >> >> >>
> >> >> >> >> >> echoInPort-echoInService and echoOutPort-echoOutService
> >> are
> >> >> >> >> activated
> >> >> >> >> >> into
> >> >> >> >> >> Echo WSDL.
> >> >> >> >> >>
> >> >> >> >> >> If I change roles in PL description I've got a compiler
> >> >> error,
> >> >> >> ODe
> >> >> >> >> says
> >> >> >> >> >> me
> >> >> >> >> >> that my partnerLinks do not define other role[ if I
> >> define a
> >> >> my
> >> >> >> role
> >> >> >> >> on
> >> >> >> >> >> writing it says that this link does not define a
> >> >> partnerRole].
> >> >> >> >> >>
> >> >> >> >> >> Now, what I have to change?
> >> >> >> >> >> I'm sorry if I may apper insistent, but I want to have a
> >> >> clear
> >> >> >> >> picture
> >> >> >> >> >> in a
> >> >> >> >> >> silly example.
> >> >> >> >> >>
> >> >> >> >> >> Thank you,
> >> >> >> >> >> Regards
> >> >> >> >> >> Simone
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> ----- Original Message -----
> >> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> > 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
> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> > 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" <gn...@gmail.com>
> >> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> 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
> >> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> > 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: users@servicemix.apache.org
> >> >> >> >> >> >> >> 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
> >> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> >> 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/
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Cheers,
> >> >> >> >> > Guillaume Nodet
> >> >> >> >> > ------------------------
> >> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cheers,
> >> >> >> > Guillaume Nodet
> >> >> >> > ------------------------
> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> > ------------------------
> >> >> > Blog: http://gnodet.blogspot.com/
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
Hi Guillaume,
I just do what you say, and I've got the problem.
The call that read use <provide> but the port is realized by echo.wsdl, the
ona that use <invoke> into its configuration file.
I just thing to this, but the fact that their in two different SA for me is
the core.
I don't know a way to solve!!
Do you prefere I past my ode into a mail? Or that I'll send my files to the
community?
Please help me, I'm coming mad.
Regards,
Simone
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Saturday, March 08, 2008 10:37 PM
Subject: Re: Mediator and Services
> On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta <si...@alice.it>
> wrote:
>> Hi Guillaume,
>> your suggest has got sense and I tried to apply it but the problem
>> persists.
>> In fact the point stands in the creation of a new endpoint while the
>> system
>> has to understand that it should use the existing one.
>> The stack trace is always the same, roles have changed their name but as
>> usual I got the same error.
>> Now the path is the same but echoPLT.wsdl differs one from another, in
>> the
>> one putted in the service directory I've got:
>>
>> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> <plnk:role name="consumer" portType="echoOutPortType"/>
>> </plnk:partnerLinkType>
>>
>> and in the mediator one:
>>
>> <plnk:partnerLinkType name="readPLT">
>> <plnk:role name="callReader" portType="echoOutPortType"/>
>> </plnk:partnerLinkType>
>>
>> the deploy.xml files do not change.
>
> Well, one is suppose to use a <provide> while the other use <invoke>.
> Also, one BPEL will have <bpel:partnerLink myRole ../> while the other
> has <bpel:partnerLink partnerRole />
>
> If you do this, it should work.
>
>> Then what I have to do? Have you got any Idea?
>> Please help me, this is a very important point into my thesy's stack.
>>
>> Regards,
>> Simone
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Friday, March 07, 2008 1:17 PM
>> Subject: Re: Mediator and Services
>>
>>
>> >I guess you have missed the concept of partner links somehow.
>> > It is used to indicate how a given service is used: if it is consumer
>> or
>> > provided. If you want your BPEL processes to communicate together.
>> > it usually means that one process will provide a service that will be
>> > consumed by the other one. This leads to the fact that the partner
>> links
>> > for the same service definition has to be different for the two
>> processes.
>> > That's why i suggested to split the main WSDL from the partner links:
>> > you can reuse the service definition, and externalize the partner
>> links in
>> > two different files.
>> > Makes sense ?
>> >
>> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> No, they are the same file.
>> >> If I define different file how may hang a single endpoint?
>> >> You say that I have to define same partnerLinkType with different
>> role
>> >> to
>> >> permit my process communicating between them?
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Friday, March 07, 2008 12:01 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> > So the two echoPLT.wsdl are different, each one having a different
>> >> role ?
>> >> >
>> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
>> >> <si...@alice.it>
>> >> > wrote:
>> >> >> Goodmorning Guillame,
>> >> >> I followed your councile but I'm at the same point of
>> yesterday,
>> >> I've
>> >> >> got same error and my call-sa does not work.
>> >> >> I split the main file and now my SA are:
>> >> >>
>> >> >> +---deploy
>> >> >> |
>> >> >> |
>> >> >> \---echo-jms-sa
>> >> >> | |
>> >> >> | |
>> >> >> | \-----META-INF
>> >> >> | | |
>> >> >> | | ---jbi-xml
>> >> >> | | \
>> >> >> | \---echo-jms-su
>> >> >> | | |
>> >> >> | | |
>> >> >> | | ---xbean.xml
>> >> >> | | \
>> >> >> | \-----echo-ode-su
>> >> >> | |
>> >> >> | |
>> >> >> | +--------echo.wsdl
>> >> >> | +---------echoPLT.wsdl
>> >> >> | +---------echo.bpel
>> >> >> | +---------deploy.xml
>> >> >> | \
>> >> >> \---------call-sa
>> >> >> | |
>> >> >> | \-----META-INF
>> >> >> \ |
>> >> >> |
>> >> >> \-----call-http-su
>> >> >> | |
>> >> >> | +--call.wsdl
>> >> >> |
>> >> >> \----call-ode-sa
>> >> >> | |
>> >> >> | +-----call.wsdl
>> >> >> \ +-----echo.wsdl
>> >> >> +-----echoPLT.wsdl
>> >> >> +-----call.bpel
>> >> >> \
>> >> >>
>> >> >>
>> >> >> Where echoPLT import echo.wsdl (using the same namespace while
>> >> instead
>> >> >> there
>> >> >> are problems referencing endopoint and the module will never
>> >> activate).
>> >> >> Again Call is my own Mediator and echo my service.
>> >> >> My I bypass the needs to activate another endpoijnt and using
>> the
>> >> >> existing
>> >> >> one?
>> >> >> Please gimme a response,
>> >> >>
>> >> >> Regards,
>> >> >> Simone
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> Sent: Thursday, March 06, 2008 5:40 PM
>> >> >> Subject: Re: Mediator and Services
>> >> >>
>> >> >>
>> >> >> > You need to split the wsdl from the partner links. For partenr
>> >> links,
>> >> >> > define a wsdl
>> >> >> > and import the main one. That way, you can define different
>> roles
>> >> for
>> >> >> > the service
>> >> >> > and the bpel that calls it.
>> >> >> >
>> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
>> >> >> <si...@alice.it>
>> >> >> > wrote:
>> >> >> >> That's true,
>> >> >> >> In Call echoOut has got myRole role because Call reads on
>> it,
>> >> I
>> >> >> have
>> >> >> >> got
>> >> >> >> problems deploying Call.
>> >> >> >> The problem that's that I define the service and the port
>> into
>> >> Echo
>> >> >> WSDL
>> >> >> >> and
>> >> >> >> not in Call one.
>> >> >> >> The trace is correct, I'm trying to define a my role on a
>> link
>> >> where
>> >> >> I
>> >> >> >> read
>> >> >> >> in an asynchronous way, so I need to define a myRole, I'm at
>> >> this
>> >> >> >> conclusion
>> >> >> >> in an empyt.
>> >> >> >> Well, Call is my mediator and Echo my service.
>> >> >> >> To be clear here is parts of my files:
>> >> >> >>
>> >> >> >> -----------------------echo.wsdl--------------------------
>> >> >> >> <wsdl:portType name="echoInPortType">
>> >> >> >>
>> >> >> >> <wsdl:operation name="echoIn">
>> >> >> >>
>> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
>> >> >> >>
>> >> >> >> </wsdl:operation>
>> >> >> >>
>> >> >> >> </wsdl:portType>
>> >> >> >>
>> >> >> >> <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:partnerLinkType>
>> >> >> >>
>> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> >> >>
>> >> >> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
>> >> >> >>
>> >> >> >> </plnk:partnerLinkType>
>> >> >> >>
>> >> >> >> ----------------------echo.bpel-----------------
>> >> >> >>
>> >> >> >> <partnerLink
>> >> >> >>
>> >> >> >> name="echoInPartnerLink"
>> >> >> >>
>> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
>> >> >> >>
>> >> >> >> myRole="provider"/>
>> >> >> >>
>> >> >> >> <partnerLink
>> >> >> >>
>> >> >> >> name="echoOutPartnerLink"
>> >> >> >>
>> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
>> >> >> >>
>> >> >> >> partnerRole="consumer"/>
>> >> >> >>
>> >> >> >> -------------------------deploy.xml---------------
>> >> >> echo-su---------[in
>> >> >> >> echo-sa]
>> >> >> >>
>> >> >> >> process name="pns:Echo">
>> >> >> >> <active>true</active>
>> >> >> >> <provide partnerLink="echoInPartnerLink">
>> >> >> >> <service name="wns:echoInService"
>> >> >> >> port="echoInPort"/>
>> >> >> >> </provide>
>> >> >> >> <invoke partnerLink="echoOutPartnerLink">
>> >> >> >> <service name="wns:echoOutService"
>> >> >> >> port="echoOutPort"/>
>> >> >> >> </invoke>
>> >> >> >> </process>
>> >> >> >>
>> >> >> >> -----------------------call.bpel--------------------------
>> >> >> >> <partnerLink
>> >> >> >>
>> >> >> >> name="echoIn"
>> >> >> >>
>> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
>> >> >> >>
>> >> >> >> partnerRole="provider"/>
>> >> >> >>
>> >> >> >> <partnerLink
>> >> >> >>
>> >> >> >> name="echoOut"
>> >> >> >>
>> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
>> >> >> >>
>> >> >> >> myRole="consumer"/>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> -------------------------------deploy.xml---------------[call-su
>> >> in
>> >> >> >> call-sa]------------------
>> >> >> >>
>> >> >> >> <process name="callB:Call">
>> >> >> >>
>> >> >> >> <active>true</active>
>> >> >> >>
>> >> >> >> <provide partnerLink="callPartnerLink">
>> >> >> >>
>> >> >> >> <service name="callW:callService" port="callPort"/>
>> >> >> >>
>> >> >> >> </provide>
>> >> >> >>
>> >> >> >> <provide partnerLink="echoOut">
>> >> >> >>
>> >> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
>> >> >> >>
>> >> >> >> </provide>
>> >> >> >>
>> >> >> >> <invoke partnerLink="echoIn">
>> >> >> >>
>> >> >> >> <service name="wns:echoInService" port="echoInPort"/>
>> >> >> >>
>> >> >> >> </invoke>
>> >> >> >>
>> >> >> >> </process>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> I think the porblem come from the fact I'm using two
>> different
>> >> SA.
>> >> >> >>
>> >> >> >> May it be?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> ----- Original Message -----
>> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
>> >> >> >> Subject: Re: Mediator and Services
>> >> >> >>
>> >> >> >>
>> >> >> >> > Could you please raise a JIRA and attach the WSDL, and
>> >> deploy.xml
>> >> >> >> files.
>> >> >> >> > If you look at the stack trace, it clearly shows that Ode
>> is
>> >> >> condering
>> >> >> >> > that the endpoint
>> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> >> >> >> > has a partner link with a "myRole" role.
>> >> >> >> >
>> >> >> >> > See:
>> >> >> >> > 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)
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> >> >> >> <si...@alice.it>
>> >> >> >> > wrote:
>> >> >> >> >> I'm sorry I don't understand;
>> >> >> >> >> this is my background:
>> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one
>> >> having an
>> >> >> own
>> >> >> >> >> partner
>> >> >> >> >> link type associated echoInPartnerLinkType
>> >> >> echoOutPartnerLinkType.
>> >> >> >> >> In the BPEL I define two partner links echoInPL and
>> >> echoOutPL,
>> >> >> echo
>> >> >> >> >> read on
>> >> >> >> >> echoInPL defining myRole, and write on echoOutPL
>> defining a
>> >> >> >> partnerRole.
>> >> >> >> >> In the deploy Echo provide echoIn and invoke echoOut.
>> >> >> >> >>
>> >> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink
>> with
>> >> echoIn
>> >> >> and
>> >> >> >> >> echoOut, writeing on the first, partnerRole, and reading
>> on
>> >> the
>> >> >> >> second,
>> >> >> >> >> myRole.
>> >> >> >> >> In the deploy Call provide echoOut and invoke echoIn.
>> >> >> >> >>
>> >> >> >> >> echoInPort-echoInService and echoOutPort-echoOutService
>> are
>> >> >> >> activated
>> >> >> >> >> into
>> >> >> >> >> Echo WSDL.
>> >> >> >> >>
>> >> >> >> >> If I change roles in PL description I've got a compiler
>> >> error,
>> >> >> ODe
>> >> >> >> says
>> >> >> >> >> me
>> >> >> >> >> that my partnerLinks do not define other role[ if I
>> define a
>> >> my
>> >> >> role
>> >> >> >> on
>> >> >> >> >> writing it says that this link does not define a
>> >> partnerRole].
>> >> >> >> >>
>> >> >> >> >> Now, what I have to change?
>> >> >> >> >> I'm sorry if I may apper insistent, but I want to have a
>> >> clear
>> >> >> >> picture
>> >> >> >> >> in a
>> >> >> >> >> silly example.
>> >> >> >> >>
>> >> >> >> >> Thank you,
>> >> >> >> >> Regards
>> >> >> >> >> Simone
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> ----- Original Message -----
>> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> >> >> >> Subject: Re: Mediator and Services
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> > 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
>> >> >> >> >> <si...@alice.it>
>> >> >> >> >> > 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" <gn...@gmail.com>
>> >> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> 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
>> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> > 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: users@servicemix.apache.org
>> >> >> >> >> >> >> 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
>> >> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> >> 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/
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Cheers,
>> >> >> >> > Guillaume Nodet
>> >> >> >> > ------------------------
>> >> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> > ------------------------
>> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> > ------------------------
>> >> > Blog: http://gnodet.blogspot.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
On Sat, Mar 8, 2008 at 10:56 AM, Simone Maletta <si...@alice.it> wrote:
> Hi Guillaume,
> your suggest has got sense and I tried to apply it but the problem
> persists.
> In fact the point stands in the creation of a new endpoint while the system
> has to understand that it should use the existing one.
> The stack trace is always the same, roles have changed their name but as
> usual I got the same error.
> Now the path is the same but echoPLT.wsdl differs one from another, in the
> one putted in the service directory I've got:
>
> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> <plnk:role name="consumer" portType="echoOutPortType"/>
> </plnk:partnerLinkType>
>
> and in the mediator one:
>
> <plnk:partnerLinkType name="readPLT">
> <plnk:role name="callReader" portType="echoOutPortType"/>
> </plnk:partnerLinkType>
>
> the deploy.xml files do not change.
Well, one is suppose to use a <provide> while the other use <invoke>.
Also, one BPEL will have <bpel:partnerLink myRole ../> while the other
has <bpel:partnerLink partnerRole />
If you do this, it should work.
> Then what I have to do? Have you got any Idea?
> Please help me, this is a very important point into my thesy's stack.
>
> Regards,
> Simone
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Friday, March 07, 2008 1:17 PM
> Subject: Re: Mediator and Services
>
>
> >I guess you have missed the concept of partner links somehow.
> > It is used to indicate how a given service is used: if it is consumer or
> > provided. If you want your BPEL processes to communicate together.
> > it usually means that one process will provide a service that will be
> > consumed by the other one. This leads to the fact that the partner links
> > for the same service definition has to be different for the two processes.
> > That's why i suggested to split the main WSDL from the partner links:
> > you can reuse the service definition, and externalize the partner links in
> > two different files.
> > Makes sense ?
> >
> > On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta <si...@alice.it>
> > wrote:
> >> No, they are the same file.
> >> If I define different file how may hang a single endpoint?
> >> You say that I have to define same partnerLinkType with different role
> >> to
> >> permit my process communicating between them?
> >>
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Friday, March 07, 2008 12:01 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> > So the two echoPLT.wsdl are different, each one having a different
> >> role ?
> >> >
> >> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
> >> <si...@alice.it>
> >> > wrote:
> >> >> Goodmorning Guillame,
> >> >> I followed your councile but I'm at the same point of yesterday,
> >> I've
> >> >> got same error and my call-sa does not work.
> >> >> I split the main file and now my SA are:
> >> >>
> >> >> +---deploy
> >> >> |
> >> >> |
> >> >> \---echo-jms-sa
> >> >> | |
> >> >> | |
> >> >> | \-----META-INF
> >> >> | | |
> >> >> | | ---jbi-xml
> >> >> | | \
> >> >> | \---echo-jms-su
> >> >> | | |
> >> >> | | |
> >> >> | | ---xbean.xml
> >> >> | | \
> >> >> | \-----echo-ode-su
> >> >> | |
> >> >> | |
> >> >> | +--------echo.wsdl
> >> >> | +---------echoPLT.wsdl
> >> >> | +---------echo.bpel
> >> >> | +---------deploy.xml
> >> >> | \
> >> >> \---------call-sa
> >> >> | |
> >> >> | \-----META-INF
> >> >> \ |
> >> >> |
> >> >> \-----call-http-su
> >> >> | |
> >> >> | +--call.wsdl
> >> >> |
> >> >> \----call-ode-sa
> >> >> | |
> >> >> | +-----call.wsdl
> >> >> \ +-----echo.wsdl
> >> >> +-----echoPLT.wsdl
> >> >> +-----call.bpel
> >> >> \
> >> >>
> >> >>
> >> >> Where echoPLT import echo.wsdl (using the same namespace while
> >> instead
> >> >> there
> >> >> are problems referencing endopoint and the module will never
> >> activate).
> >> >> Again Call is my own Mediator and echo my service.
> >> >> My I bypass the needs to activate another endpoijnt and using the
> >> >> existing
> >> >> one?
> >> >> Please gimme a response,
> >> >>
> >> >> Regards,
> >> >> Simone
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> Sent: Thursday, March 06, 2008 5:40 PM
> >> >> Subject: Re: Mediator and Services
> >> >>
> >> >>
> >> >> > You need to split the wsdl from the partner links. For partenr
> >> links,
> >> >> > define a wsdl
> >> >> > and import the main one. That way, you can define different roles
> >> for
> >> >> > the service
> >> >> > and the bpel that calls it.
> >> >> >
> >> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
> >> >> <si...@alice.it>
> >> >> > wrote:
> >> >> >> That's true,
> >> >> >> In Call echoOut has got myRole role because Call reads on it,
> >> I
> >> >> have
> >> >> >> got
> >> >> >> problems deploying Call.
> >> >> >> The problem that's that I define the service and the port into
> >> Echo
> >> >> WSDL
> >> >> >> and
> >> >> >> not in Call one.
> >> >> >> The trace is correct, I'm trying to define a my role on a link
> >> where
> >> >> I
> >> >> >> read
> >> >> >> in an asynchronous way, so I need to define a myRole, I'm at
> >> this
> >> >> >> conclusion
> >> >> >> in an empyt.
> >> >> >> Well, Call is my mediator and Echo my service.
> >> >> >> To be clear here is parts of my files:
> >> >> >>
> >> >> >> -----------------------echo.wsdl--------------------------
> >> >> >> <wsdl:portType name="echoInPortType">
> >> >> >>
> >> >> >> <wsdl:operation name="echoIn">
> >> >> >>
> >> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
> >> >> >>
> >> >> >> </wsdl:operation>
> >> >> >>
> >> >> >> </wsdl:portType>
> >> >> >>
> >> >> >> <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:partnerLinkType>
> >> >> >>
> >> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> >> >>
> >> >> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
> >> >> >>
> >> >> >> </plnk:partnerLinkType>
> >> >> >>
> >> >> >> ----------------------echo.bpel-----------------
> >> >> >>
> >> >> >> <partnerLink
> >> >> >>
> >> >> >> name="echoInPartnerLink"
> >> >> >>
> >> >> >> partnerLinkType="test:echoInPartnerLinkType"
> >> >> >>
> >> >> >> myRole="provider"/>
> >> >> >>
> >> >> >> <partnerLink
> >> >> >>
> >> >> >> name="echoOutPartnerLink"
> >> >> >>
> >> >> >> partnerLinkType="test:echoOutPartnerLinkType"
> >> >> >>
> >> >> >> partnerRole="consumer"/>
> >> >> >>
> >> >> >> -------------------------deploy.xml---------------
> >> >> echo-su---------[in
> >> >> >> echo-sa]
> >> >> >>
> >> >> >> process name="pns:Echo">
> >> >> >> <active>true</active>
> >> >> >> <provide partnerLink="echoInPartnerLink">
> >> >> >> <service name="wns:echoInService"
> >> >> >> port="echoInPort"/>
> >> >> >> </provide>
> >> >> >> <invoke partnerLink="echoOutPartnerLink">
> >> >> >> <service name="wns:echoOutService"
> >> >> >> port="echoOutPort"/>
> >> >> >> </invoke>
> >> >> >> </process>
> >> >> >>
> >> >> >> -----------------------call.bpel--------------------------
> >> >> >> <partnerLink
> >> >> >>
> >> >> >> name="echoIn"
> >> >> >>
> >> >> >> partnerLinkType="echo:echoInPartnerLinkType"
> >> >> >>
> >> >> >> partnerRole="provider"/>
> >> >> >>
> >> >> >> <partnerLink
> >> >> >>
> >> >> >> name="echoOut"
> >> >> >>
> >> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
> >> >> >>
> >> >> >> myRole="consumer"/>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> -------------------------------deploy.xml---------------[call-su
> >> in
> >> >> >> call-sa]------------------
> >> >> >>
> >> >> >> <process name="callB:Call">
> >> >> >>
> >> >> >> <active>true</active>
> >> >> >>
> >> >> >> <provide partnerLink="callPartnerLink">
> >> >> >>
> >> >> >> <service name="callW:callService" port="callPort"/>
> >> >> >>
> >> >> >> </provide>
> >> >> >>
> >> >> >> <provide partnerLink="echoOut">
> >> >> >>
> >> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
> >> >> >>
> >> >> >> </provide>
> >> >> >>
> >> >> >> <invoke partnerLink="echoIn">
> >> >> >>
> >> >> >> <service name="wns:echoInService" port="echoInPort"/>
> >> >> >>
> >> >> >> </invoke>
> >> >> >>
> >> >> >> </process>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> I think the porblem come from the fact I'm using two different
> >> SA.
> >> >> >>
> >> >> >> May it be?
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> ----- Original Message -----
> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >>
> >> >> >>
> >> >> >> Sent: Thursday, March 06, 2008 4:52 PM
> >> >> >> Subject: Re: Mediator and Services
> >> >> >>
> >> >> >>
> >> >> >> > Could you please raise a JIRA and attach the WSDL, and
> >> deploy.xml
> >> >> >> files.
> >> >> >> > If you look at the stack trace, it clearly shows that Ode is
> >> >> condering
> >> >> >> > that the endpoint
> >> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
> >> >> >> > has a partner link with a "myRole" role.
> >> >> >> >
> >> >> >> > See:
> >> >> >> > 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)
> >> >> >> >
> >> >> >> >
> >> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
> >> >> >> <si...@alice.it>
> >> >> >> > wrote:
> >> >> >> >> I'm sorry I don't understand;
> >> >> >> >> this is my background:
> >> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one
> >> having an
> >> >> own
> >> >> >> >> partner
> >> >> >> >> link type associated echoInPartnerLinkType
> >> >> echoOutPartnerLinkType.
> >> >> >> >> In the BPEL I define two partner links echoInPL and
> >> echoOutPL,
> >> >> echo
> >> >> >> >> read on
> >> >> >> >> echoInPL defining myRole, and write on echoOutPL defining a
> >> >> >> partnerRole.
> >> >> >> >> In the deploy Echo provide echoIn and invoke echoOut.
> >> >> >> >>
> >> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with
> >> echoIn
> >> >> and
> >> >> >> >> echoOut, writeing on the first, partnerRole, and reading on
> >> the
> >> >> >> second,
> >> >> >> >> myRole.
> >> >> >> >> In the deploy Call provide echoOut and invoke echoIn.
> >> >> >> >>
> >> >> >> >> echoInPort-echoInService and echoOutPort-echoOutService are
> >> >> >> activated
> >> >> >> >> into
> >> >> >> >> Echo WSDL.
> >> >> >> >>
> >> >> >> >> If I change roles in PL description I've got a compiler
> >> error,
> >> >> ODe
> >> >> >> says
> >> >> >> >> me
> >> >> >> >> that my partnerLinks do not define other role[ if I define a
> >> my
> >> >> role
> >> >> >> on
> >> >> >> >> writing it says that this link does not define a
> >> partnerRole].
> >> >> >> >>
> >> >> >> >> Now, what I have to change?
> >> >> >> >> I'm sorry if I may apper insistent, but I want to have a
> >> clear
> >> >> >> picture
> >> >> >> >> in a
> >> >> >> >> silly example.
> >> >> >> >>
> >> >> >> >> Thank you,
> >> >> >> >> Regards
> >> >> >> >> Simone
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> ----- Original Message -----
> >> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> >> >> >> Subject: Re: Mediator and Services
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> > 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
> >> >> >> >> <si...@alice.it>
> >> >> >> >> > 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" <gn...@gmail.com>
> >> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> 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
> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> > 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: users@servicemix.apache.org
> >> >> >> >> >> >> 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
> >> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> >> 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/
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > Cheers,
> >> >> >> > Guillaume Nodet
> >> >> >> > ------------------------
> >> >> >> > Blog: http://gnodet.blogspot.com/
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> > ------------------------
> >> >> > Blog: http://gnodet.blogspot.com/
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
Hi Guillaume,
your suggest has got sense and I tried to apply it but the problem
persists.
In fact the point stands in the creation of a new endpoint while the system
has to understand that it should use the existing one.
The stack trace is always the same, roles have changed their name but as
usual I got the same error.
Now the path is the same but echoPLT.wsdl differs one from another, in the
one putted in the service directory I've got:
<plnk:partnerLinkType name="echoOutPartnerLinkType">
<plnk:role name="consumer" portType="echoOutPortType"/>
</plnk:partnerLinkType>
and in the mediator one:
<plnk:partnerLinkType name="readPLT">
<plnk:role name="callReader" portType="echoOutPortType"/>
</plnk:partnerLinkType>
the deploy.xml files do not change.
Then what I have to do? Have you got any Idea?
Please help me, this is a very important point into my thesy's stack.
Regards,
Simone
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Friday, March 07, 2008 1:17 PM
Subject: Re: Mediator and Services
>I guess you have missed the concept of partner links somehow.
> It is used to indicate how a given service is used: if it is consumer or
> provided. If you want your BPEL processes to communicate together.
> it usually means that one process will provide a service that will be
> consumed by the other one. This leads to the fact that the partner links
> for the same service definition has to be different for the two processes.
> That's why i suggested to split the main WSDL from the partner links:
> you can reuse the service definition, and externalize the partner links in
> two different files.
> Makes sense ?
>
> On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta <si...@alice.it>
> wrote:
>> No, they are the same file.
>> If I define different file how may hang a single endpoint?
>> You say that I have to define same partnerLinkType with different role
>> to
>> permit my process communicating between them?
>>
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Friday, March 07, 2008 12:01 PM
>> Subject: Re: Mediator and Services
>>
>>
>> > So the two echoPLT.wsdl are different, each one having a different
>> role ?
>> >
>> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> Goodmorning Guillame,
>> >> I followed your councile but I'm at the same point of yesterday,
>> I've
>> >> got same error and my call-sa does not work.
>> >> I split the main file and now my SA are:
>> >>
>> >> +---deploy
>> >> |
>> >> |
>> >> \---echo-jms-sa
>> >> | |
>> >> | |
>> >> | \-----META-INF
>> >> | | |
>> >> | | ---jbi-xml
>> >> | | \
>> >> | \---echo-jms-su
>> >> | | |
>> >> | | |
>> >> | | ---xbean.xml
>> >> | | \
>> >> | \-----echo-ode-su
>> >> | |
>> >> | |
>> >> | +--------echo.wsdl
>> >> | +---------echoPLT.wsdl
>> >> | +---------echo.bpel
>> >> | +---------deploy.xml
>> >> | \
>> >> \---------call-sa
>> >> | |
>> >> | \-----META-INF
>> >> \ |
>> >> |
>> >> \-----call-http-su
>> >> | |
>> >> | +--call.wsdl
>> >> |
>> >> \----call-ode-sa
>> >> | |
>> >> | +-----call.wsdl
>> >> \ +-----echo.wsdl
>> >> +-----echoPLT.wsdl
>> >> +-----call.bpel
>> >> \
>> >>
>> >>
>> >> Where echoPLT import echo.wsdl (using the same namespace while
>> instead
>> >> there
>> >> are problems referencing endopoint and the module will never
>> activate).
>> >> Again Call is my own Mediator and echo my service.
>> >> My I bypass the needs to activate another endpoijnt and using the
>> >> existing
>> >> one?
>> >> Please gimme a response,
>> >>
>> >> Regards,
>> >> Simone
>> >>
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Thursday, March 06, 2008 5:40 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> > You need to split the wsdl from the partner links. For partenr
>> links,
>> >> > define a wsdl
>> >> > and import the main one. That way, you can define different roles
>> for
>> >> > the service
>> >> > and the bpel that calls it.
>> >> >
>> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
>> >> <si...@alice.it>
>> >> > wrote:
>> >> >> That's true,
>> >> >> In Call echoOut has got myRole role because Call reads on it,
>> I
>> >> have
>> >> >> got
>> >> >> problems deploying Call.
>> >> >> The problem that's that I define the service and the port into
>> Echo
>> >> WSDL
>> >> >> and
>> >> >> not in Call one.
>> >> >> The trace is correct, I'm trying to define a my role on a link
>> where
>> >> I
>> >> >> read
>> >> >> in an asynchronous way, so I need to define a myRole, I'm at
>> this
>> >> >> conclusion
>> >> >> in an empyt.
>> >> >> Well, Call is my mediator and Echo my service.
>> >> >> To be clear here is parts of my files:
>> >> >>
>> >> >> -----------------------echo.wsdl--------------------------
>> >> >> <wsdl:portType name="echoInPortType">
>> >> >>
>> >> >> <wsdl:operation name="echoIn">
>> >> >>
>> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
>> >> >>
>> >> >> </wsdl:operation>
>> >> >>
>> >> >> </wsdl:portType>
>> >> >>
>> >> >> <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:partnerLinkType>
>> >> >>
>> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >> >>
>> >> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
>> >> >>
>> >> >> </plnk:partnerLinkType>
>> >> >>
>> >> >> ----------------------echo.bpel-----------------
>> >> >>
>> >> >> <partnerLink
>> >> >>
>> >> >> name="echoInPartnerLink"
>> >> >>
>> >> >> partnerLinkType="test:echoInPartnerLinkType"
>> >> >>
>> >> >> myRole="provider"/>
>> >> >>
>> >> >> <partnerLink
>> >> >>
>> >> >> name="echoOutPartnerLink"
>> >> >>
>> >> >> partnerLinkType="test:echoOutPartnerLinkType"
>> >> >>
>> >> >> partnerRole="consumer"/>
>> >> >>
>> >> >> -------------------------deploy.xml---------------
>> >> echo-su---------[in
>> >> >> echo-sa]
>> >> >>
>> >> >> process name="pns:Echo">
>> >> >> <active>true</active>
>> >> >> <provide partnerLink="echoInPartnerLink">
>> >> >> <service name="wns:echoInService"
>> >> >> port="echoInPort"/>
>> >> >> </provide>
>> >> >> <invoke partnerLink="echoOutPartnerLink">
>> >> >> <service name="wns:echoOutService"
>> >> >> port="echoOutPort"/>
>> >> >> </invoke>
>> >> >> </process>
>> >> >>
>> >> >> -----------------------call.bpel--------------------------
>> >> >> <partnerLink
>> >> >>
>> >> >> name="echoIn"
>> >> >>
>> >> >> partnerLinkType="echo:echoInPartnerLinkType"
>> >> >>
>> >> >> partnerRole="provider"/>
>> >> >>
>> >> >> <partnerLink
>> >> >>
>> >> >> name="echoOut"
>> >> >>
>> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
>> >> >>
>> >> >> myRole="consumer"/>
>> >> >>
>> >> >>
>> >> >>
>> >> >> -------------------------------deploy.xml---------------[call-su
>> in
>> >> >> call-sa]------------------
>> >> >>
>> >> >> <process name="callB:Call">
>> >> >>
>> >> >> <active>true</active>
>> >> >>
>> >> >> <provide partnerLink="callPartnerLink">
>> >> >>
>> >> >> <service name="callW:callService" port="callPort"/>
>> >> >>
>> >> >> </provide>
>> >> >>
>> >> >> <provide partnerLink="echoOut">
>> >> >>
>> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
>> >> >>
>> >> >> </provide>
>> >> >>
>> >> >> <invoke partnerLink="echoIn">
>> >> >>
>> >> >> <service name="wns:echoInService" port="echoInPort"/>
>> >> >>
>> >> >> </invoke>
>> >> >>
>> >> >> </process>
>> >> >>
>> >> >>
>> >> >>
>> >> >> I think the porblem come from the fact I'm using two different
>> SA.
>> >> >>
>> >> >> May it be?
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> Sent: Thursday, March 06, 2008 4:52 PM
>> >> >> Subject: Re: Mediator and Services
>> >> >>
>> >> >>
>> >> >> > Could you please raise a JIRA and attach the WSDL, and
>> deploy.xml
>> >> >> files.
>> >> >> > If you look at the stack trace, it clearly shows that Ode is
>> >> condering
>> >> >> > that the endpoint
>> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> >> >> > has a partner link with a "myRole" role.
>> >> >> >
>> >> >> > See:
>> >> >> > 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)
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> >> >> <si...@alice.it>
>> >> >> > wrote:
>> >> >> >> I'm sorry I don't understand;
>> >> >> >> this is my background:
>> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one
>> having an
>> >> own
>> >> >> >> partner
>> >> >> >> link type associated echoInPartnerLinkType
>> >> echoOutPartnerLinkType.
>> >> >> >> In the BPEL I define two partner links echoInPL and
>> echoOutPL,
>> >> echo
>> >> >> >> read on
>> >> >> >> echoInPL defining myRole, and write on echoOutPL defining a
>> >> >> partnerRole.
>> >> >> >> In the deploy Echo provide echoIn and invoke echoOut.
>> >> >> >>
>> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with
>> echoIn
>> >> and
>> >> >> >> echoOut, writeing on the first, partnerRole, and reading on
>> the
>> >> >> second,
>> >> >> >> myRole.
>> >> >> >> In the deploy Call provide echoOut and invoke echoIn.
>> >> >> >>
>> >> >> >> echoInPort-echoInService and echoOutPort-echoOutService are
>> >> >> activated
>> >> >> >> into
>> >> >> >> Echo WSDL.
>> >> >> >>
>> >> >> >> If I change roles in PL description I've got a compiler
>> error,
>> >> ODe
>> >> >> says
>> >> >> >> me
>> >> >> >> that my partnerLinks do not define other role[ if I define a
>> my
>> >> role
>> >> >> on
>> >> >> >> writing it says that this link does not define a
>> partnerRole].
>> >> >> >>
>> >> >> >> Now, what I have to change?
>> >> >> >> I'm sorry if I may apper insistent, but I want to have a
>> clear
>> >> >> picture
>> >> >> >> in a
>> >> >> >> silly example.
>> >> >> >>
>> >> >> >> Thank you,
>> >> >> >> Regards
>> >> >> >> Simone
>> >> >> >>
>> >> >> >>
>> >> >> >> ----- Original Message -----
>> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> >> >> Subject: Re: Mediator and Services
>> >> >> >>
>> >> >> >>
>> >> >> >> > 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
>> >> >> >> <si...@alice.it>
>> >> >> >> > 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" <gn...@gmail.com>
>> >> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> 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
>> >> >> >> >> <si...@alice.it>
>> >> >> >> >> > 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: users@servicemix.apache.org
>> >> >> >> >> >> 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
>> >> >> >> >> <si...@alice.it>
>> >> >> >> >> >> 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/
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Cheers,
>> >> >> > Guillaume Nodet
>> >> >> > ------------------------
>> >> >> > Blog: http://gnodet.blogspot.com/
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> > ------------------------
>> >> > Blog: http://gnodet.blogspot.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
I guess you have missed the concept of partner links somehow.
It is used to indicate how a given service is used: if it is consumer or
provided. If you want your BPEL processes to communicate together.
it usually means that one process will provide a service that will be
consumed by the other one. This leads to the fact that the partner links
for the same service definition has to be different for the two processes.
That's why i suggested to split the main WSDL from the partner links:
you can reuse the service definition, and externalize the partner links in
two different files.
Makes sense ?
On Fri, Mar 7, 2008 at 12:11 PM, Simone Maletta <si...@alice.it> wrote:
> No, they are the same file.
> If I define different file how may hang a single endpoint?
> You say that I have to define same partnerLinkType with different role to
> permit my process communicating between them?
>
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Friday, March 07, 2008 12:01 PM
> Subject: Re: Mediator and Services
>
>
> > So the two echoPLT.wsdl are different, each one having a different role ?
> >
> > On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta <si...@alice.it>
> > wrote:
> >> Goodmorning Guillame,
> >> I followed your councile but I'm at the same point of yesterday, I've
> >> got same error and my call-sa does not work.
> >> I split the main file and now my SA are:
> >>
> >> +---deploy
> >> |
> >> |
> >> \---echo-jms-sa
> >> | |
> >> | |
> >> | \-----META-INF
> >> | | |
> >> | | ---jbi-xml
> >> | | \
> >> | \---echo-jms-su
> >> | | |
> >> | | |
> >> | | ---xbean.xml
> >> | | \
> >> | \-----echo-ode-su
> >> | |
> >> | |
> >> | +--------echo.wsdl
> >> | +---------echoPLT.wsdl
> >> | +---------echo.bpel
> >> | +---------deploy.xml
> >> | \
> >> \---------call-sa
> >> | |
> >> | \-----META-INF
> >> \ |
> >> |
> >> \-----call-http-su
> >> | |
> >> | +--call.wsdl
> >> |
> >> \----call-ode-sa
> >> | |
> >> | +-----call.wsdl
> >> \ +-----echo.wsdl
> >> +-----echoPLT.wsdl
> >> +-----call.bpel
> >> \
> >>
> >>
> >> Where echoPLT import echo.wsdl (using the same namespace while instead
> >> there
> >> are problems referencing endopoint and the module will never activate).
> >> Again Call is my own Mediator and echo my service.
> >> My I bypass the needs to activate another endpoijnt and using the
> >> existing
> >> one?
> >> Please gimme a response,
> >>
> >> Regards,
> >> Simone
> >>
> >>
> >>
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Thursday, March 06, 2008 5:40 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> > You need to split the wsdl from the partner links. For partenr links,
> >> > define a wsdl
> >> > and import the main one. That way, you can define different roles for
> >> > the service
> >> > and the bpel that calls it.
> >> >
> >> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
> >> <si...@alice.it>
> >> > wrote:
> >> >> That's true,
> >> >> In Call echoOut has got myRole role because Call reads on it, I
> >> have
> >> >> got
> >> >> problems deploying Call.
> >> >> The problem that's that I define the service and the port into Echo
> >> WSDL
> >> >> and
> >> >> not in Call one.
> >> >> The trace is correct, I'm trying to define a my role on a link where
> >> I
> >> >> read
> >> >> in an asynchronous way, so I need to define a myRole, I'm at this
> >> >> conclusion
> >> >> in an empyt.
> >> >> Well, Call is my mediator and Echo my service.
> >> >> To be clear here is parts of my files:
> >> >>
> >> >> -----------------------echo.wsdl--------------------------
> >> >> <wsdl:portType name="echoInPortType">
> >> >>
> >> >> <wsdl:operation name="echoIn">
> >> >>
> >> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
> >> >>
> >> >> </wsdl:operation>
> >> >>
> >> >> </wsdl:portType>
> >> >>
> >> >> <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:partnerLinkType>
> >> >>
> >> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >> >>
> >> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
> >> >>
> >> >> </plnk:partnerLinkType>
> >> >>
> >> >> ----------------------echo.bpel-----------------
> >> >>
> >> >> <partnerLink
> >> >>
> >> >> name="echoInPartnerLink"
> >> >>
> >> >> partnerLinkType="test:echoInPartnerLinkType"
> >> >>
> >> >> myRole="provider"/>
> >> >>
> >> >> <partnerLink
> >> >>
> >> >> name="echoOutPartnerLink"
> >> >>
> >> >> partnerLinkType="test:echoOutPartnerLinkType"
> >> >>
> >> >> partnerRole="consumer"/>
> >> >>
> >> >> -------------------------deploy.xml---------------
> >> echo-su---------[in
> >> >> echo-sa]
> >> >>
> >> >> process name="pns:Echo">
> >> >> <active>true</active>
> >> >> <provide partnerLink="echoInPartnerLink">
> >> >> <service name="wns:echoInService"
> >> >> port="echoInPort"/>
> >> >> </provide>
> >> >> <invoke partnerLink="echoOutPartnerLink">
> >> >> <service name="wns:echoOutService"
> >> >> port="echoOutPort"/>
> >> >> </invoke>
> >> >> </process>
> >> >>
> >> >> -----------------------call.bpel--------------------------
> >> >> <partnerLink
> >> >>
> >> >> name="echoIn"
> >> >>
> >> >> partnerLinkType="echo:echoInPartnerLinkType"
> >> >>
> >> >> partnerRole="provider"/>
> >> >>
> >> >> <partnerLink
> >> >>
> >> >> name="echoOut"
> >> >>
> >> >> partnerLinkType="echo:echoOutPartnerLinkType"
> >> >>
> >> >> myRole="consumer"/>
> >> >>
> >> >>
> >> >>
> >> >> -------------------------------deploy.xml---------------[call-su in
> >> >> call-sa]------------------
> >> >>
> >> >> <process name="callB:Call">
> >> >>
> >> >> <active>true</active>
> >> >>
> >> >> <provide partnerLink="callPartnerLink">
> >> >>
> >> >> <service name="callW:callService" port="callPort"/>
> >> >>
> >> >> </provide>
> >> >>
> >> >> <provide partnerLink="echoOut">
> >> >>
> >> >> <service name="wns:echoOutService" port="echoOutPort"/>
> >> >>
> >> >> </provide>
> >> >>
> >> >> <invoke partnerLink="echoIn">
> >> >>
> >> >> <service name="wns:echoInService" port="echoInPort"/>
> >> >>
> >> >> </invoke>
> >> >>
> >> >> </process>
> >> >>
> >> >>
> >> >>
> >> >> I think the porblem come from the fact I'm using two different SA.
> >> >>
> >> >> May it be?
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> Sent: Thursday, March 06, 2008 4:52 PM
> >> >> Subject: Re: Mediator and Services
> >> >>
> >> >>
> >> >> > Could you please raise a JIRA and attach the WSDL, and deploy.xml
> >> >> files.
> >> >> > If you look at the stack trace, it clearly shows that Ode is
> >> condering
> >> >> > that the endpoint
> >> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
> >> >> > has a partner link with a "myRole" role.
> >> >> >
> >> >> > See:
> >> >> > 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)
> >> >> >
> >> >> >
> >> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
> >> >> <si...@alice.it>
> >> >> > wrote:
> >> >> >> I'm sorry I don't understand;
> >> >> >> this is my background:
> >> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one having an
> >> own
> >> >> >> partner
> >> >> >> link type associated echoInPartnerLinkType
> >> echoOutPartnerLinkType.
> >> >> >> In the BPEL I define two partner links echoInPL and echoOutPL,
> >> echo
> >> >> >> read on
> >> >> >> echoInPL defining myRole, and write on echoOutPL defining a
> >> >> partnerRole.
> >> >> >> In the deploy Echo provide echoIn and invoke echoOut.
> >> >> >>
> >> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn
> >> and
> >> >> >> echoOut, writeing on the first, partnerRole, and reading on the
> >> >> second,
> >> >> >> myRole.
> >> >> >> In the deploy Call provide echoOut and invoke echoIn.
> >> >> >>
> >> >> >> echoInPort-echoInService and echoOutPort-echoOutService are
> >> >> activated
> >> >> >> into
> >> >> >> Echo WSDL.
> >> >> >>
> >> >> >> If I change roles in PL description I've got a compiler error,
> >> ODe
> >> >> says
> >> >> >> me
> >> >> >> that my partnerLinks do not define other role[ if I define a my
> >> role
> >> >> on
> >> >> >> writing it says that this link does not define a partnerRole].
> >> >> >>
> >> >> >> Now, what I have to change?
> >> >> >> I'm sorry if I may apper insistent, but I want to have a clear
> >> >> picture
> >> >> >> in a
> >> >> >> silly example.
> >> >> >>
> >> >> >> Thank you,
> >> >> >> Regards
> >> >> >> Simone
> >> >> >>
> >> >> >>
> >> >> >> ----- Original Message -----
> >> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >>
> >> >> >>
> >> >> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> >> >> Subject: Re: Mediator and Services
> >> >> >>
> >> >> >>
> >> >> >> > 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
> >> >> >> <si...@alice.it>
> >> >> >> > 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" <gn...@gmail.com>
> >> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> 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
> >> >> >> >> <si...@alice.it>
> >> >> >> >> > 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: users@servicemix.apache.org
> >> >> >> >> >> 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
> >> >> >> >> <si...@alice.it>
> >> >> >> >> >> 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/
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> > ------------------------
> >> >> > Blog: http://gnodet.blogspot.com/
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
No, they are the same file.
If I define different file how may hang a single endpoint?
You say that I have to define same partnerLinkType with different role to
permit my process communicating between them?
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Friday, March 07, 2008 12:01 PM
Subject: Re: Mediator and Services
> So the two echoPLT.wsdl are different, each one having a different role ?
>
> On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta <si...@alice.it>
> wrote:
>> Goodmorning Guillame,
>> I followed your councile but I'm at the same point of yesterday, I've
>> got same error and my call-sa does not work.
>> I split the main file and now my SA are:
>>
>> +---deploy
>> |
>> |
>> \---echo-jms-sa
>> | |
>> | |
>> | \-----META-INF
>> | | |
>> | | ---jbi-xml
>> | | \
>> | \---echo-jms-su
>> | | |
>> | | |
>> | | ---xbean.xml
>> | | \
>> | \-----echo-ode-su
>> | |
>> | |
>> | +--------echo.wsdl
>> | +---------echoPLT.wsdl
>> | +---------echo.bpel
>> | +---------deploy.xml
>> | \
>> \---------call-sa
>> | |
>> | \-----META-INF
>> \ |
>> |
>> \-----call-http-su
>> | |
>> | +--call.wsdl
>> |
>> \----call-ode-sa
>> | |
>> | +-----call.wsdl
>> \ +-----echo.wsdl
>> +-----echoPLT.wsdl
>> +-----call.bpel
>> \
>>
>>
>> Where echoPLT import echo.wsdl (using the same namespace while instead
>> there
>> are problems referencing endopoint and the module will never activate).
>> Again Call is my own Mediator and echo my service.
>> My I bypass the needs to activate another endpoijnt and using the
>> existing
>> one?
>> Please gimme a response,
>>
>> Regards,
>> Simone
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Thursday, March 06, 2008 5:40 PM
>> Subject: Re: Mediator and Services
>>
>>
>> > You need to split the wsdl from the partner links. For partenr links,
>> > define a wsdl
>> > and import the main one. That way, you can define different roles for
>> > the service
>> > and the bpel that calls it.
>> >
>> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> That's true,
>> >> In Call echoOut has got myRole role because Call reads on it, I
>> have
>> >> got
>> >> problems deploying Call.
>> >> The problem that's that I define the service and the port into Echo
>> WSDL
>> >> and
>> >> not in Call one.
>> >> The trace is correct, I'm trying to define a my role on a link where
>> I
>> >> read
>> >> in an asynchronous way, so I need to define a myRole, I'm at this
>> >> conclusion
>> >> in an empyt.
>> >> Well, Call is my mediator and Echo my service.
>> >> To be clear here is parts of my files:
>> >>
>> >> -----------------------echo.wsdl--------------------------
>> >> <wsdl:portType name="echoInPortType">
>> >>
>> >> <wsdl:operation name="echoIn">
>> >>
>> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
>> >>
>> >> </wsdl:operation>
>> >>
>> >> </wsdl:portType>
>> >>
>> >> <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:partnerLinkType>
>> >>
>> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>> >>
>> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
>> >>
>> >> </plnk:partnerLinkType>
>> >>
>> >> ----------------------echo.bpel-----------------
>> >>
>> >> <partnerLink
>> >>
>> >> name="echoInPartnerLink"
>> >>
>> >> partnerLinkType="test:echoInPartnerLinkType"
>> >>
>> >> myRole="provider"/>
>> >>
>> >> <partnerLink
>> >>
>> >> name="echoOutPartnerLink"
>> >>
>> >> partnerLinkType="test:echoOutPartnerLinkType"
>> >>
>> >> partnerRole="consumer"/>
>> >>
>> >> -------------------------deploy.xml---------------
>> echo-su---------[in
>> >> echo-sa]
>> >>
>> >> process name="pns:Echo">
>> >> <active>true</active>
>> >> <provide partnerLink="echoInPartnerLink">
>> >> <service name="wns:echoInService"
>> >> port="echoInPort"/>
>> >> </provide>
>> >> <invoke partnerLink="echoOutPartnerLink">
>> >> <service name="wns:echoOutService"
>> >> port="echoOutPort"/>
>> >> </invoke>
>> >> </process>
>> >>
>> >> -----------------------call.bpel--------------------------
>> >> <partnerLink
>> >>
>> >> name="echoIn"
>> >>
>> >> partnerLinkType="echo:echoInPartnerLinkType"
>> >>
>> >> partnerRole="provider"/>
>> >>
>> >> <partnerLink
>> >>
>> >> name="echoOut"
>> >>
>> >> partnerLinkType="echo:echoOutPartnerLinkType"
>> >>
>> >> myRole="consumer"/>
>> >>
>> >>
>> >>
>> >> -------------------------------deploy.xml---------------[call-su in
>> >> call-sa]------------------
>> >>
>> >> <process name="callB:Call">
>> >>
>> >> <active>true</active>
>> >>
>> >> <provide partnerLink="callPartnerLink">
>> >>
>> >> <service name="callW:callService" port="callPort"/>
>> >>
>> >> </provide>
>> >>
>> >> <provide partnerLink="echoOut">
>> >>
>> >> <service name="wns:echoOutService" port="echoOutPort"/>
>> >>
>> >> </provide>
>> >>
>> >> <invoke partnerLink="echoIn">
>> >>
>> >> <service name="wns:echoInService" port="echoInPort"/>
>> >>
>> >> </invoke>
>> >>
>> >> </process>
>> >>
>> >>
>> >>
>> >> I think the porblem come from the fact I'm using two different SA.
>> >>
>> >> May it be?
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Thursday, March 06, 2008 4:52 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> > Could you please raise a JIRA and attach the WSDL, and deploy.xml
>> >> files.
>> >> > If you look at the stack trace, it clearly shows that Ode is
>> condering
>> >> > that the endpoint
>> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> >> > has a partner link with a "myRole" role.
>> >> >
>> >> > See:
>> >> > 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)
>> >> >
>> >> >
>> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> >> <si...@alice.it>
>> >> > wrote:
>> >> >> I'm sorry I don't understand;
>> >> >> this is my background:
>> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one having an
>> own
>> >> >> partner
>> >> >> link type associated echoInPartnerLinkType
>> echoOutPartnerLinkType.
>> >> >> In the BPEL I define two partner links echoInPL and echoOutPL,
>> echo
>> >> >> read on
>> >> >> echoInPL defining myRole, and write on echoOutPL defining a
>> >> partnerRole.
>> >> >> In the deploy Echo provide echoIn and invoke echoOut.
>> >> >>
>> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn
>> and
>> >> >> echoOut, writeing on the first, partnerRole, and reading on the
>> >> second,
>> >> >> myRole.
>> >> >> In the deploy Call provide echoOut and invoke echoIn.
>> >> >>
>> >> >> echoInPort-echoInService and echoOutPort-echoOutService are
>> >> activated
>> >> >> into
>> >> >> Echo WSDL.
>> >> >>
>> >> >> If I change roles in PL description I've got a compiler error,
>> ODe
>> >> says
>> >> >> me
>> >> >> that my partnerLinks do not define other role[ if I define a my
>> role
>> >> on
>> >> >> writing it says that this link does not define a partnerRole].
>> >> >>
>> >> >> Now, what I have to change?
>> >> >> I'm sorry if I may apper insistent, but I want to have a clear
>> >> picture
>> >> >> in a
>> >> >> silly example.
>> >> >>
>> >> >> Thank you,
>> >> >> Regards
>> >> >> Simone
>> >> >>
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> >> Subject: Re: Mediator and Services
>> >> >>
>> >> >>
>> >> >> > 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
>> >> >> <si...@alice.it>
>> >> >> > 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" <gn...@gmail.com>
>> >> >> >> To: <us...@servicemix.apache.org>
>> >> >> >>
>> >> >> >>
>> >> >> >> 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
>> >> >> >> <si...@alice.it>
>> >> >> >> > 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: users@servicemix.apache.org
>> >> >> >> >> 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
>> >> >> >> <si...@alice.it>
>> >> >> >> >> 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/
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >> > ------------------------
>> >> > Blog: http://gnodet.blogspot.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
So the two echoPLT.wsdl are different, each one having a different role ?
On Fri, Mar 7, 2008 at 11:30 AM, Simone Maletta <si...@alice.it> wrote:
> Goodmorning Guillame,
> I followed your councile but I'm at the same point of yesterday, I've
> got same error and my call-sa does not work.
> I split the main file and now my SA are:
>
> +---deploy
> |
> |
> \---echo-jms-sa
> | |
> | |
> | \-----META-INF
> | | |
> | | ---jbi-xml
> | | \
> | \---echo-jms-su
> | | |
> | | |
> | | ---xbean.xml
> | | \
> | \-----echo-ode-su
> | |
> | |
> | +--------echo.wsdl
> | +---------echoPLT.wsdl
> | +---------echo.bpel
> | +---------deploy.xml
> | \
> \---------call-sa
> | |
> | \-----META-INF
> \ |
> |
> \-----call-http-su
> | |
> | +--call.wsdl
> |
> \----call-ode-sa
> | |
> | +-----call.wsdl
> \ +-----echo.wsdl
> +-----echoPLT.wsdl
> +-----call.bpel
> \
>
>
> Where echoPLT import echo.wsdl (using the same namespace while instead there
> are problems referencing endopoint and the module will never activate).
> Again Call is my own Mediator and echo my service.
> My I bypass the needs to activate another endpoijnt and using the existing
> one?
> Please gimme a response,
>
> Regards,
> Simone
>
>
>
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Thursday, March 06, 2008 5:40 PM
> Subject: Re: Mediator and Services
>
>
> > You need to split the wsdl from the partner links. For partenr links,
> > define a wsdl
> > and import the main one. That way, you can define different roles for
> > the service
> > and the bpel that calls it.
> >
> > On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta <si...@alice.it>
> > wrote:
> >> That's true,
> >> In Call echoOut has got myRole role because Call reads on it, I have
> >> got
> >> problems deploying Call.
> >> The problem that's that I define the service and the port into Echo WSDL
> >> and
> >> not in Call one.
> >> The trace is correct, I'm trying to define a my role on a link where I
> >> read
> >> in an asynchronous way, so I need to define a myRole, I'm at this
> >> conclusion
> >> in an empyt.
> >> Well, Call is my mediator and Echo my service.
> >> To be clear here is parts of my files:
> >>
> >> -----------------------echo.wsdl--------------------------
> >> <wsdl:portType name="echoInPortType">
> >>
> >> <wsdl:operation name="echoIn">
> >>
> >> <wsdl:input name="inMex" message="tns:echoMessage"/>
> >>
> >> </wsdl:operation>
> >>
> >> </wsdl:portType>
> >>
> >> <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:partnerLinkType>
> >>
> >> <plnk:partnerLinkType name="echoOutPartnerLinkType">
> >>
> >> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
> >>
> >> </plnk:partnerLinkType>
> >>
> >> ----------------------echo.bpel-----------------
> >>
> >> <partnerLink
> >>
> >> name="echoInPartnerLink"
> >>
> >> partnerLinkType="test:echoInPartnerLinkType"
> >>
> >> myRole="provider"/>
> >>
> >> <partnerLink
> >>
> >> name="echoOutPartnerLink"
> >>
> >> partnerLinkType="test:echoOutPartnerLinkType"
> >>
> >> partnerRole="consumer"/>
> >>
> >> -------------------------deploy.xml--------------- echo-su---------[in
> >> echo-sa]
> >>
> >> process name="pns:Echo">
> >> <active>true</active>
> >> <provide partnerLink="echoInPartnerLink">
> >> <service name="wns:echoInService"
> >> port="echoInPort"/>
> >> </provide>
> >> <invoke partnerLink="echoOutPartnerLink">
> >> <service name="wns:echoOutService"
> >> port="echoOutPort"/>
> >> </invoke>
> >> </process>
> >>
> >> -----------------------call.bpel--------------------------
> >> <partnerLink
> >>
> >> name="echoIn"
> >>
> >> partnerLinkType="echo:echoInPartnerLinkType"
> >>
> >> partnerRole="provider"/>
> >>
> >> <partnerLink
> >>
> >> name="echoOut"
> >>
> >> partnerLinkType="echo:echoOutPartnerLinkType"
> >>
> >> myRole="consumer"/>
> >>
> >>
> >>
> >> -------------------------------deploy.xml---------------[call-su in
> >> call-sa]------------------
> >>
> >> <process name="callB:Call">
> >>
> >> <active>true</active>
> >>
> >> <provide partnerLink="callPartnerLink">
> >>
> >> <service name="callW:callService" port="callPort"/>
> >>
> >> </provide>
> >>
> >> <provide partnerLink="echoOut">
> >>
> >> <service name="wns:echoOutService" port="echoOutPort"/>
> >>
> >> </provide>
> >>
> >> <invoke partnerLink="echoIn">
> >>
> >> <service name="wns:echoInService" port="echoInPort"/>
> >>
> >> </invoke>
> >>
> >> </process>
> >>
> >>
> >>
> >> I think the porblem come from the fact I'm using two different SA.
> >>
> >> May it be?
> >>
> >>
> >>
> >>
> >>
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Thursday, March 06, 2008 4:52 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> > Could you please raise a JIRA and attach the WSDL, and deploy.xml
> >> files.
> >> > If you look at the stack trace, it clearly shows that Ode is condering
> >> > that the endpoint
> >> > {urn:/echo.wsdl}echoOutService:echoOutPort
> >> > has a partner link with a "myRole" role.
> >> >
> >> > See:
> >> > 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)
> >> >
> >> >
> >> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
> >> <si...@alice.it>
> >> > wrote:
> >> >> I'm sorry I don't understand;
> >> >> this is my background:
> >> >> 1) Echo Expose two ports, echoIn and echoOut, each one having an own
> >> >> partner
> >> >> link type associated echoInPartnerLinkType echoOutPartnerLinkType.
> >> >> In the BPEL I define two partner links echoInPL and echoOutPL, echo
> >> >> read on
> >> >> echoInPL defining myRole, and write on echoOutPL defining a
> >> partnerRole.
> >> >> In the deploy Echo provide echoIn and invoke echoOut.
> >> >>
> >> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
> >> >> echoOut, writeing on the first, partnerRole, and reading on the
> >> second,
> >> >> myRole.
> >> >> In the deploy Call provide echoOut and invoke echoIn.
> >> >>
> >> >> echoInPort-echoInService and echoOutPort-echoOutService are
> >> activated
> >> >> into
> >> >> Echo WSDL.
> >> >>
> >> >> If I change roles in PL description I've got a compiler error, ODe
> >> says
> >> >> me
> >> >> that my partnerLinks do not define other role[ if I define a my role
> >> on
> >> >> writing it says that this link does not define a partnerRole].
> >> >>
> >> >> Now, what I have to change?
> >> >> I'm sorry if I may apper insistent, but I want to have a clear
> >> picture
> >> >> in a
> >> >> silly example.
> >> >>
> >> >> Thank you,
> >> >> Regards
> >> >> Simone
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> >> Subject: Re: Mediator and Services
> >> >>
> >> >>
> >> >> > 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
> >> >> <si...@alice.it>
> >> >> > 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" <gn...@gmail.com>
> >> >> >> To: <us...@servicemix.apache.org>
> >> >> >>
> >> >> >>
> >> >> >> 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
> >> >> >> <si...@alice.it>
> >> >> >> > 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: users@servicemix.apache.org
> >> >> >> >> 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
> >> >> >> <si...@alice.it>
> >> >> >> >> 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/
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> > ------------------------
> >> > Blog: http://gnodet.blogspot.com/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
Goodmorning Guillame,
I followed your councile but I'm at the same point of yesterday, I've
got same error and my call-sa does not work.
I split the main file and now my SA are:
+---deploy
|
|
\---echo-jms-sa
| |
| |
| \-----META-INF
| | |
| | ---jbi-xml
| | \
| \---echo-jms-su
| | |
| | |
| | ---xbean.xml
| | \
| \-----echo-ode-su
| |
| |
| +--------echo.wsdl
| +---------echoPLT.wsdl
| +---------echo.bpel
| +---------deploy.xml
| \
\---------call-sa
| |
| \-----META-INF
\ |
|
\-----call-http-su
| |
| +--call.wsdl
|
\----call-ode-sa
| |
| +-----call.wsdl
\ +-----echo.wsdl
+-----echoPLT.wsdl
+-----call.bpel
\
Where echoPLT import echo.wsdl (using the same namespace while instead there
are problems referencing endopoint and the module will never activate).
Again Call is my own Mediator and echo my service.
My I bypass the needs to activate another endpoijnt and using the existing
one?
Please gimme a response,
Regards,
Simone
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Thursday, March 06, 2008 5:40 PM
Subject: Re: Mediator and Services
> You need to split the wsdl from the partner links. For partenr links,
> define a wsdl
> and import the main one. That way, you can define different roles for
> the service
> and the bpel that calls it.
>
> On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta <si...@alice.it>
> wrote:
>> That's true,
>> In Call echoOut has got myRole role because Call reads on it, I have
>> got
>> problems deploying Call.
>> The problem that's that I define the service and the port into Echo WSDL
>> and
>> not in Call one.
>> The trace is correct, I'm trying to define a my role on a link where I
>> read
>> in an asynchronous way, so I need to define a myRole, I'm at this
>> conclusion
>> in an empyt.
>> Well, Call is my mediator and Echo my service.
>> To be clear here is parts of my files:
>>
>> -----------------------echo.wsdl--------------------------
>> <wsdl:portType name="echoInPortType">
>>
>> <wsdl:operation name="echoIn">
>>
>> <wsdl:input name="inMex" message="tns:echoMessage"/>
>>
>> </wsdl:operation>
>>
>> </wsdl:portType>
>>
>> <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:partnerLinkType>
>>
>> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>>
>> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
>>
>> </plnk:partnerLinkType>
>>
>> ----------------------echo.bpel-----------------
>>
>> <partnerLink
>>
>> name="echoInPartnerLink"
>>
>> partnerLinkType="test:echoInPartnerLinkType"
>>
>> myRole="provider"/>
>>
>> <partnerLink
>>
>> name="echoOutPartnerLink"
>>
>> partnerLinkType="test:echoOutPartnerLinkType"
>>
>> partnerRole="consumer"/>
>>
>> -------------------------deploy.xml--------------- echo-su---------[in
>> echo-sa]
>>
>> process name="pns:Echo">
>> <active>true</active>
>> <provide partnerLink="echoInPartnerLink">
>> <service name="wns:echoInService"
>> port="echoInPort"/>
>> </provide>
>> <invoke partnerLink="echoOutPartnerLink">
>> <service name="wns:echoOutService"
>> port="echoOutPort"/>
>> </invoke>
>> </process>
>>
>> -----------------------call.bpel--------------------------
>> <partnerLink
>>
>> name="echoIn"
>>
>> partnerLinkType="echo:echoInPartnerLinkType"
>>
>> partnerRole="provider"/>
>>
>> <partnerLink
>>
>> name="echoOut"
>>
>> partnerLinkType="echo:echoOutPartnerLinkType"
>>
>> myRole="consumer"/>
>>
>>
>>
>> -------------------------------deploy.xml---------------[call-su in
>> call-sa]------------------
>>
>> <process name="callB:Call">
>>
>> <active>true</active>
>>
>> <provide partnerLink="callPartnerLink">
>>
>> <service name="callW:callService" port="callPort"/>
>>
>> </provide>
>>
>> <provide partnerLink="echoOut">
>>
>> <service name="wns:echoOutService" port="echoOutPort"/>
>>
>> </provide>
>>
>> <invoke partnerLink="echoIn">
>>
>> <service name="wns:echoInService" port="echoInPort"/>
>>
>> </invoke>
>>
>> </process>
>>
>>
>>
>> I think the porblem come from the fact I'm using two different SA.
>>
>> May it be?
>>
>>
>>
>>
>>
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Thursday, March 06, 2008 4:52 PM
>> Subject: Re: Mediator and Services
>>
>>
>> > Could you please raise a JIRA and attach the WSDL, and deploy.xml
>> files.
>> > If you look at the stack trace, it clearly shows that Ode is condering
>> > that the endpoint
>> > {urn:/echo.wsdl}echoOutService:echoOutPort
>> > has a partner link with a "myRole" role.
>> >
>> > See:
>> > 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)
>> >
>> >
>> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta
>> <si...@alice.it>
>> > wrote:
>> >> I'm sorry I don't understand;
>> >> this is my background:
>> >> 1) Echo Expose two ports, echoIn and echoOut, each one having an own
>> >> partner
>> >> link type associated echoInPartnerLinkType echoOutPartnerLinkType.
>> >> In the BPEL I define two partner links echoInPL and echoOutPL, echo
>> >> read on
>> >> echoInPL defining myRole, and write on echoOutPL defining a
>> partnerRole.
>> >> In the deploy Echo provide echoIn and invoke echoOut.
>> >>
>> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
>> >> echoOut, writeing on the first, partnerRole, and reading on the
>> second,
>> >> myRole.
>> >> In the deploy Call provide echoOut and invoke echoIn.
>> >>
>> >> echoInPort-echoInService and echoOutPort-echoOutService are
>> activated
>> >> into
>> >> Echo WSDL.
>> >>
>> >> If I change roles in PL description I've got a compiler error, ODe
>> says
>> >> me
>> >> that my partnerLinks do not define other role[ if I define a my role
>> on
>> >> writing it says that this link does not define a partnerRole].
>> >>
>> >> Now, what I have to change?
>> >> I'm sorry if I may apper insistent, but I want to have a clear
>> picture
>> >> in a
>> >> silly example.
>> >>
>> >> Thank you,
>> >> Regards
>> >> Simone
>> >>
>> >>
>> >> ----- Original Message -----
>> >> From: "Guillaume Nodet" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> Sent: Thursday, March 06, 2008 4:24 PM
>> >> Subject: Re: Mediator and Services
>> >>
>> >>
>> >> > 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
>> >> <si...@alice.it>
>> >> > 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" <gn...@gmail.com>
>> >> >> To: <us...@servicemix.apache.org>
>> >> >>
>> >> >>
>> >> >> 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
>> >> >> <si...@alice.it>
>> >> >> > 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: users@servicemix.apache.org
>> >> >> >> 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
>> >> >> <si...@alice.it>
>> >> >> >> 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/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
You need to split the wsdl from the partner links. For partenr links,
define a wsdl
and import the main one. That way, you can define different roles for
the service
and the bpel that calls it.
On Thu, Mar 6, 2008 at 5:10 PM, Simone Maletta <si...@alice.it> wrote:
> That's true,
> In Call echoOut has got myRole role because Call reads on it, I have got
> problems deploying Call.
> The problem that's that I define the service and the port into Echo WSDL and
> not in Call one.
> The trace is correct, I'm trying to define a my role on a link where I read
> in an asynchronous way, so I need to define a myRole, I'm at this conclusion
> in an empyt.
> Well, Call is my mediator and Echo my service.
> To be clear here is parts of my files:
>
> -----------------------echo.wsdl--------------------------
> <wsdl:portType name="echoInPortType">
>
> <wsdl:operation name="echoIn">
>
> <wsdl:input name="inMex" message="tns:echoMessage"/>
>
> </wsdl:operation>
>
> </wsdl:portType>
>
> <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:partnerLinkType>
>
> <plnk:partnerLinkType name="echoOutPartnerLinkType">
>
> <plnk:role name="consumer" portType="tns:echoOutPortType"/>
>
> </plnk:partnerLinkType>
>
> ----------------------echo.bpel-----------------
>
> <partnerLink
>
> name="echoInPartnerLink"
>
> partnerLinkType="test:echoInPartnerLinkType"
>
> myRole="provider"/>
>
> <partnerLink
>
> name="echoOutPartnerLink"
>
> partnerLinkType="test:echoOutPartnerLinkType"
>
> partnerRole="consumer"/>
>
> -------------------------deploy.xml--------------- echo-su---------[in
> echo-sa]
>
> process name="pns:Echo">
> <active>true</active>
> <provide partnerLink="echoInPartnerLink">
> <service name="wns:echoInService" port="echoInPort"/>
> </provide>
> <invoke partnerLink="echoOutPartnerLink">
> <service name="wns:echoOutService" port="echoOutPort"/>
> </invoke>
> </process>
>
> -----------------------call.bpel--------------------------
> <partnerLink
>
> name="echoIn"
>
> partnerLinkType="echo:echoInPartnerLinkType"
>
> partnerRole="provider"/>
>
> <partnerLink
>
> name="echoOut"
>
> partnerLinkType="echo:echoOutPartnerLinkType"
>
> myRole="consumer"/>
>
>
>
> -------------------------------deploy.xml---------------[call-su in
> call-sa]------------------
>
> <process name="callB:Call">
>
> <active>true</active>
>
> <provide partnerLink="callPartnerLink">
>
> <service name="callW:callService" port="callPort"/>
>
> </provide>
>
> <provide partnerLink="echoOut">
>
> <service name="wns:echoOutService" port="echoOutPort"/>
>
> </provide>
>
> <invoke partnerLink="echoIn">
>
> <service name="wns:echoInService" port="echoInPort"/>
>
> </invoke>
>
> </process>
>
>
>
> I think the porblem come from the fact I'm using two different SA.
>
> May it be?
>
>
>
>
>
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Thursday, March 06, 2008 4:52 PM
> Subject: Re: Mediator and Services
>
>
> > Could you please raise a JIRA and attach the WSDL, and deploy.xml files.
> > If you look at the stack trace, it clearly shows that Ode is condering
> > that the endpoint
> > {urn:/echo.wsdl}echoOutService:echoOutPort
> > has a partner link with a "myRole" role.
> >
> > See:
> > 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)
> >
> >
> > On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta <si...@alice.it>
> > wrote:
> >> I'm sorry I don't understand;
> >> this is my background:
> >> 1) Echo Expose two ports, echoIn and echoOut, each one having an own
> >> partner
> >> link type associated echoInPartnerLinkType echoOutPartnerLinkType.
> >> In the BPEL I define two partner links echoInPL and echoOutPL, echo
> >> read on
> >> echoInPL defining myRole, and write on echoOutPL defining a partnerRole.
> >> In the deploy Echo provide echoIn and invoke echoOut.
> >>
> >> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
> >> echoOut, writeing on the first, partnerRole, and reading on the second,
> >> myRole.
> >> In the deploy Call provide echoOut and invoke echoIn.
> >>
> >> echoInPort-echoInService and echoOutPort-echoOutService are activated
> >> into
> >> Echo WSDL.
> >>
> >> If I change roles in PL description I've got a compiler error, ODe says
> >> me
> >> that my partnerLinks do not define other role[ if I define a my role on
> >> writing it says that this link does not define a partnerRole].
> >>
> >> Now, what I have to change?
> >> I'm sorry if I may apper insistent, but I want to have a clear picture
> >> in a
> >> silly example.
> >>
> >> Thank you,
> >> Regards
> >> Simone
> >>
> >>
> >> ----- Original Message -----
> >> From: "Guillaume Nodet" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> Sent: Thursday, March 06, 2008 4:24 PM
> >> Subject: Re: Mediator and Services
> >>
> >>
> >> > 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
> >> <si...@alice.it>
> >> > 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" <gn...@gmail.com>
> >> >> To: <us...@servicemix.apache.org>
> >> >>
> >> >>
> >> >> 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
> >> >> <si...@alice.it>
> >> >> > 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: users@servicemix.apache.org
> >> >> >> 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
> >> >> <si...@alice.it>
> >> >> >> 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/
> >>
> >>
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
That's true,
In Call echoOut has got myRole role because Call reads on it, I have got
problems deploying Call.
The problem that's that I define the service and the port into Echo WSDL and
not in Call one.
The trace is correct, I'm trying to define a my role on a link where I read
in an asynchronous way, so I need to define a myRole, I'm at this conclusion
in an empyt.
Well, Call is my mediator and Echo my service.
To be clear here is parts of my files:
-----------------------echo.wsdl--------------------------
<wsdl:portType name="echoInPortType">
<wsdl:operation name="echoIn">
<wsdl:input name="inMex" message="tns:echoMessage"/>
</wsdl:operation>
</wsdl:portType>
<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:partnerLinkType>
<plnk:partnerLinkType name="echoOutPartnerLinkType">
<plnk:role name="consumer" portType="tns:echoOutPortType"/>
</plnk:partnerLinkType>
----------------------echo.bpel-----------------
<partnerLink
name="echoInPartnerLink"
partnerLinkType="test:echoInPartnerLinkType"
myRole="provider"/>
<partnerLink
name="echoOutPartnerLink"
partnerLinkType="test:echoOutPartnerLinkType"
partnerRole="consumer"/>
-------------------------deploy.xml--------------- echo-su---------[in
echo-sa]
process name="pns:Echo">
<active>true</active>
<provide partnerLink="echoInPartnerLink">
<service name="wns:echoInService" port="echoInPort"/>
</provide>
<invoke partnerLink="echoOutPartnerLink">
<service name="wns:echoOutService" port="echoOutPort"/>
</invoke>
</process>
-----------------------call.bpel--------------------------
<partnerLink
name="echoIn"
partnerLinkType="echo:echoInPartnerLinkType"
partnerRole="provider"/>
<partnerLink
name="echoOut"
partnerLinkType="echo:echoOutPartnerLinkType"
myRole="consumer"/>
-------------------------------deploy.xml---------------[call-su in
call-sa]------------------
<process name="callB:Call">
<active>true</active>
<provide partnerLink="callPartnerLink">
<service name="callW:callService" port="callPort"/>
</provide>
<provide partnerLink="echoOut">
<service name="wns:echoOutService" port="echoOutPort"/>
</provide>
<invoke partnerLink="echoIn">
<service name="wns:echoInService" port="echoInPort"/>
</invoke>
</process>
I think the porblem come from the fact I'm using two different SA.
May it be?
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Thursday, March 06, 2008 4:52 PM
Subject: Re: Mediator and Services
> Could you please raise a JIRA and attach the WSDL, and deploy.xml files.
> If you look at the stack trace, it clearly shows that Ode is condering
> that the endpoint
> {urn:/echo.wsdl}echoOutService:echoOutPort
> has a partner link with a "myRole" role.
>
> See:
> 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)
>
>
> On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta <si...@alice.it>
> wrote:
>> I'm sorry I don't understand;
>> this is my background:
>> 1) Echo Expose two ports, echoIn and echoOut, each one having an own
>> partner
>> link type associated echoInPartnerLinkType echoOutPartnerLinkType.
>> In the BPEL I define two partner links echoInPL and echoOutPL, echo
>> read on
>> echoInPL defining myRole, and write on echoOutPL defining a partnerRole.
>> In the deploy Echo provide echoIn and invoke echoOut.
>>
>> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
>> echoOut, writeing on the first, partnerRole, and reading on the second,
>> myRole.
>> In the deploy Call provide echoOut and invoke echoIn.
>>
>> echoInPort-echoInService and echoOutPort-echoOutService are activated
>> into
>> Echo WSDL.
>>
>> If I change roles in PL description I've got a compiler error, ODe says
>> me
>> that my partnerLinks do not define other role[ if I define a my role on
>> writing it says that this link does not define a partnerRole].
>>
>> Now, what I have to change?
>> I'm sorry if I may apper insistent, but I want to have a clear picture
>> in a
>> silly example.
>>
>> Thank you,
>> Regards
>> Simone
>>
>>
>> ----- Original Message -----
>> From: "Guillaume Nodet" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> Sent: Thursday, March 06, 2008 4:24 PM
>> Subject: Re: Mediator and Services
>>
>>
>> > 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
>> <si...@alice.it>
>> > 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" <gn...@gmail.com>
>> >> To: <us...@servicemix.apache.org>
>> >>
>> >>
>> >> 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
>> >> <si...@alice.it>
>> >> > 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: users@servicemix.apache.org
>> >> >> 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
>> >> <si...@alice.it>
>> >> >> 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/
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
Could you please raise a JIRA and attach the WSDL, and deploy.xml files.
If you look at the stack trace, it clearly shows that Ode is condering
that the endpoint
{urn:/echo.wsdl}echoOutService:echoOutPort
has a partner link with a "myRole" role.
See:
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)
On Thu, Mar 6, 2008 at 4:44 PM, Simone Maletta <si...@alice.it> wrote:
> I'm sorry I don't understand;
> this is my background:
> 1) Echo Expose two ports, echoIn and echoOut, each one having an own partner
> link type associated echoInPartnerLinkType echoOutPartnerLinkType.
> In the BPEL I define two partner links echoInPL and echoOutPL, echo read on
> echoInPL defining myRole, and write on echoOutPL defining a partnerRole.
> In the deploy Echo provide echoIn and invoke echoOut.
>
> 2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
> echoOut, writeing on the first, partnerRole, and reading on the second,
> myRole.
> In the deploy Call provide echoOut and invoke echoIn.
>
> echoInPort-echoInService and echoOutPort-echoOutService are activated into
> Echo WSDL.
>
> If I change roles in PL description I've got a compiler error, ODe says me
> that my partnerLinks do not define other role[ if I define a my role on
> writing it says that this link does not define a partnerRole].
>
> Now, what I have to change?
> I'm sorry if I may apper insistent, but I want to have a clear picture in a
> silly example.
>
> Thank you,
> Regards
> Simone
>
>
> ----- Original Message -----
> From: "Guillaume Nodet" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> Sent: Thursday, March 06, 2008 4:24 PM
> Subject: Re: Mediator and Services
>
>
> > 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 <si...@alice.it>
> > 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" <gn...@gmail.com>
> >> To: <us...@servicemix.apache.org>
> >>
> >>
> >> 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
> >> <si...@alice.it>
> >> > 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: users@servicemix.apache.org
> >> >> 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
> >> <si...@alice.it>
> >> >> 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/
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
I'm sorry I don't understand;
this is my background:
1) Echo Expose two ports, echoIn and echoOut, each one having an own partner
link type associated echoInPartnerLinkType echoOutPartnerLinkType.
In the BPEL I define two partner links echoInPL and echoOutPL, echo read on
echoInPL defining myRole, and write on echoOutPL defining a partnerRole.
In the deploy Echo provide echoIn and invoke echoOut.
2) Call use echoInPartnerLink and echoOutPartnerLink with echoIn and
echoOut, writeing on the first, partnerRole, and reading on the second,
myRole.
In the deploy Call provide echoOut and invoke echoIn.
echoInPort-echoInService and echoOutPort-echoOutService are activated into
Echo WSDL.
If I change roles in PL description I've got a compiler error, ODe says me
that my partnerLinks do not define other role[ if I define a my role on
writing it says that this link does not define a partnerRole].
Now, what I have to change?
I'm sorry if I may apper insistent, but I want to have a clear picture in a
silly example.
Thank you,
Regards
Simone
----- Original Message -----
From: "Guillaume Nodet" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
Sent: Thursday, March 06, 2008 4:24 PM
Subject: Re: Mediator and Services
> 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 <si...@alice.it>
> 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" <gn...@gmail.com>
>> To: <us...@servicemix.apache.org>
>>
>>
>> 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
>> <si...@alice.it>
>> > 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: users@servicemix.apache.org
>> >> 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
>> <si...@alice.it>
>> >> 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/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <si...@alice.it> 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" <gn...@gmail.com>
> To: <us...@servicemix.apache.org>
>
>
> 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 <si...@alice.it>
> > 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: users@servicemix.apache.org
> >> 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 <si...@alice.it>
> >> 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/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
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" <gn...@gmail.com>
To: <us...@servicemix.apache.org>
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 <si...@alice.it>
> 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: users@servicemix.apache.org
>> 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 <si...@alice.it>
>> 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/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <si...@alice.it> 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: users@servicemix.apache.org
> 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 <si...@alice.it> 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/
Re: Mediator and Services
Posted by Simone Maletta <si...@alice.it>.
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: users@servicemix.apache.org
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 <si...@alice.it> 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/
Re: Mediator and Services
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <si...@alice.it> 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/