Hi Herve,
Most likely this is due to the format of the message coming from the
FilePoler. When you say "I am sending exactly what the WSDL partner
expects", what do you mean exactly? What's the format of the message on the
JBI bus?
As for deploy.xml, do you have a specific question? The deployment
descriptor simply binds partnerlinks to their respective (JBI) endpoints
with a service qname and a port name.
alex
On 3/12/07, kermitt <[EMAIL PROTECTED]> wrote:
Hello,
I am trying to integrate ODE and Servicemix:
The BPEL process answers and responses to a web service deployed within
servicemix as an http endpoint.
In this BPEL process I am calling an asynchronious service.
Interface of this service is designed with file endpoints.The BPEL invoke
a
service to write a file in a IN directory.
After using a pick, I wait a message from a file poller on an OUT
directory.
There is a timer that time out the BPEL wait.
Execution is doing ok, BPEL process is triggered when sending a SOAP
mesasge, a file is created within my IN directory. If I wait, the time out
occurs and the process responds with a time out message to my initial web
service.
My issue is when I put a file in the OUT directory I get the following
message:
org.apache.ode.jbi.msgmap.MessageTranslationException: Could not find a
mapper for request message for JBI MEX ID:MYCOMP-1653-1173689518233-3:7
; ODE MEX 5636113 is failed.
at org.apache.ode.jbi.OdeService.invokeOde(OdeService.java:239)
at
org.apache.ode.jbi.OdeService.onJbiMessageExchange(OdeService.java:147)
at
org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(
JbiMessageExchangeEventRouter.java:47)
at org.apache.ode.jbi.Receiver$1.run(Receiver.java:190)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:675)
at java.lang.Thread.run(Thread.java:595)
previous post said that is was an issue with the content of the message
but
here I am sending exactly what the WSDL partner expects.
any ideas?
Could you please also provide a documentation for the deploy.xml?
http://www.nabble.com/file/7092/InvoiceProcess.bpel InvoiceProcess.bpel
http://www.nabble.com/file/7093/CXmlService.wsdl CXmlService.wsdl
http://www.nabble.com/file/7094/InvoiceService.wsdl InvoiceService.wsdl
http://www.nabble.com/file/7095/deploy.xml deploy.xml
thx
--
View this message in context:
http://www.nabble.com/callback-issue-tf3388687.html#a9432333
Sent from the Apache Ode User mailing list archive at Nabble.com.
