I may have misleaded you in my previous mail.
Looking at your message, the root element of the soap body is
  im:EchoOperation
The effect is that the OperationName of the jbi exchange will be set
to this QName.  That's good, because the bpel engine can now find the
receive operation of the process.
The problem is that your message no more conforms to the wsdl and the
xpath in your copy will certainly fails because of this element.

Try something like that:
<SOAP-ENV:Envelope
        xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
        xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
  <SOAP-ENV:Header>
    <wsa:Action>
      http://it.imolinfo.demo/DoubleEcho/EchoOperation
    </wsa:Action>
  </SOAP-ENV:Header>
        <SOAP-ENV:Body>
                <typens:EchoRequest 
xmlns:typens="http://it.imolinfo.demo.types";>
                        <typens:msg1>Hello</typens:msg1>
                        <typens:msg2>World</typens:msg2>
                </typens:EchoRequest>
        </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Cheers,
Guillaume Nodet


On 3/31/06, Raffaele Spazzoli <[EMAIL PROTECTED]> wrote:
> thanks for the quick reply. Frankly I don't undestandan exactly what is
> going on, but with a manually constructed message the process starts.
> Now I'm stuck again in assign phase. It seems that I'm not using XPATH
> correctly. I know this is not a mailing list about bpel and XPATH but I
> try.
> The following is the exception  I receive. I attach the message and the
> bpel process. Thanks.
> Raffaele
>
> ---------------------exception------------------------------------
>
> SEVERE: Native Exception: ResolverException. Native Message:
> org.apache.ode.bpe.interaction.NonExistentNodeException: Node null not
> found.  Check the associated business process to ensure that the source
> variable has been initialized and check runtime data to ensure that the
> requested element exists in the source variable.
> org.apache.ode.bpe.util.BPException: Native Exception:
> ResolverException. Native Message:
> org.apache.ode.bpe.interaction.NonExistentNodeException: Node null not
> found.  Check the associated business process to ensure that the source
> variable has been initialized and check runtime data to ensure that the
> requested element exists in the source variable.
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolveBPContext(ContextResolver.java:158)
>         at
> org.apache.ode.bpe.action.bpel.CopyAction.execute(CopyAction.java:104)
>         at
> org.apache.ode.bpe.engine.ProcessInstance.executeActions(ProcessInstance.java:359)
>         at
> org.apache.ode.bpe.engine.ProcessInstance.evaluate(ProcessInstance.java:325)
>         at
> org.apache.ode.bpe.engine.ProcessInstance.evaluate(ProcessInstance.java:414)
>         at
> org.apache.ode.bpe.engine.ProcessInstance.processInternalEvent(ProcessInstance.java:254)
>         at
> org.apache.ode.bpe.engine.ProcessInstance.processEvent(ProcessInstance.java:209)
>         at
> org.apache.ode.bpe.correlation.CorrelationService.createInstanceAndRoute(CorrelationService.java:230)
>         at
> org.apache.ode.bpe.correlation.CorrelationService.correlateEvent(CorrelationService.java:337)
>         at
> org.apache.ode.bpe.bped.unmanaged.EventDirectorSLImpl.sendEvent(EventDirectorSLImpl.java:116)
>         at
> org.apache.servicemix.bpe.BPEEndpoint.process(BPEEndpoint.java:99)
>         at
> org.apache.servicemix.common.BaseLifeCycle.processExchange(BaseLifeCycle.java:374)
>         at org.apache.servicemix.common.BaseLifeCycle
> $2.run(BaseLifeCycle.java:240)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
> $Worker.runTask(ThreadPoolExecutor.java:650)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
> $Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.ode.bpe.context.resolver.ResolverException:
> org.apache.ode.bpe.interaction.NonExistentNodeException: Node null not
> found.  Check the associated business process to ensure that the source
> variable has been initialized and check runtime data to ensure that the
> requested element exists in the source variable.
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolve(ContextResolver.java:265)
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolve(ContextResolver.java:201)
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolve(ContextResolver.java:191)
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolveBPContext(ContextResolver.java:156)
>         ... 15 more
> Caused by: org.apache.ode.bpe.interaction.NonExistentNodeException: Node
> null not found.  Check the associated business process to ensure that
> the source variable has been initialized and check runtime data to
> ensure that the requested element exists in the source variable.
>         at
> org.apache.ode.bpe.interaction.operations.GetTextValueOperation.execute(GetTextValueOperation.java:40)
>         at
> org.apache.ode.bpe.interaction.operations.DocumentOperation.execute(DocumentOperation.java:62)
>         at
> org.apache.ode.bpe.interaction.Invocation.execute(Invocation.java:79)
>         at
> org.apache.ode.bpe.interaction.BaseInteraction.invoke(BaseInteraction.java:41)
>         at
> org.apache.ode.bpe.interaction.BaseInteraction.invoke(BaseInteraction.java:77)
>         at
> org.apache.ode.bpe.context.resolver.ContextResolver.resolve(ContextResolver.java:252)
>         ... 18 more
> Mar 31, 2006 9:52:59 AM org.apache.ode.bpe.action.bpel.CopyAction
> execute
>
> ---------------------exception------------------------------------
>
>
> On Thu, 2006-03-30 at 17:15 +0200, Guillaume Nodet wrote:
> > Just thought that this attribute should also be used for soap consumer
> > endpoints.  I will fix that asap.
> >
> > Guillaume
> >
> > On 3/30/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > > I think the problem comes from the fact that the operation defined on
> > > the exchange is {http://it.imolinfo.demo.types}EchoRequest.  It have
> > > to be {http://it.imolinfo.demo.types}EchoOperation.
> > >
> > > Try using the defaultOperation attribute on your http consumer
> > > endpoint (if it is not a soap endpoint) else use wsa:Action soap
> > > header (see http://servicemix.org/servicemix-http).
> > > If none is specified, he operation defaults to the qname of the root
> > > xml content.
> > >
> > > Cheers,
> > > Guillaume Nodet
> > >
> > > On 3/30/06, Raffaele Spazzoli <[EMAIL PROTECTED]> wrote:
> > > > Hi, I'm trying to launch a simple process with bpe. My configuration is
> > > > the following
> > > >
> > > > SOAP/HTTP client <---> servicemix-http <---> servicemix-bpe <- ... the
> > > > bpe process link interal endpoint ->
> > > >
> > > > The process seems to deploy correctly, launching the process I receive
> > > > the following error:
> > > >
> > > > DEBUG - BaseLifeCycle.processExchange(362) | Received exchange: status:
> > > > Active, role: Provider
> > > > ERROR - BaseLifeCycle$2.run(242) | Error processing exchange
> > > > [EMAIL PROTECTED]
> > > > org.apache.ode.bpe.correlation.CorrelationServiceException: An error
> > > > occurred when attempting to route the service request for operation:
> > > > EchoRequest, port type: DoubleEcho, target namespace
> > > > http://it.imolinfo.demo, correlation key(s):  to a business process
> > > > instance.  The correlation definition for this operation is as
> > > > follows: .  Inspect the business process design and verify that a
> > > > business process instance is waiting for this request to be sent.
> > > >         at
> > > > org.apache.ode.bpe.correlation.CorrelationService.correlateEvent(CorrelationService.java:361)
> > > >         at
> > > > org.apache.ode.bpe.bped.unmanaged.EventDirectorSLImpl.sendEvent(EventDirectorSLImpl.java:116)
> > > >         at 
> > > > org.apache.servicemix.bpe.BPEEndpoint.process(BPEEndpoint.java:99)
> > > >         at
> > > > org.apache.servicemix.common.BaseLifeCycle.processExchange(BaseLifeCycle.java:374)
> > > >         at org.apache.servicemix.common.BaseLifeCycle
> > > > $2.run(BaseLifeCycle.java:240)
> > > >         at 
> > > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
> > > > $Worker.runTask(ThreadPoolExecutor.java:650)
> > > >         at 
> > > > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
> > > > $Worker.run(ThreadPoolExecutor.java:675)
> > > >         at java.lang.Thread.run(Thread.java:595)
> > > > DEBUG - DeliveryChannelImpl.traceMessageExchange(342) | Sent:
> > > > MessageExchange[
> > > >   id: ID:raffaele-32840-1143727115057-9:0
> > > >   status: Error
> > > >   role: provider
> > > >   service: {http://it.imolinfo.demo}DoubleEcho
> > > >   endpoint: DoubleEchoJBIPort
> > > >   operation: {http://it.imolinfo.demo.types}EchoRequest
> > > >   in: <?xml version="1.0" encoding="UTF-8"?><m:EchoRequest
> > > > xmlns:m="http://it.imolinfo.demo.types";
> > > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
> > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><msg1>Hello</msg1><msg2>World</msg2></m:EchoRequest>
> > > >   error: An error occurred when attempting to route the service request
> > > > for operation: EchoRequest, port type: DoubleEcho, target namespace
> > > > http://it.imolinfo.demo, correlation key(s):  to a business process
> > > > instance.  The correlation definition for this operation is as
> > > > follows: .  Inspect the business process design and verify that a
> > > > business process instance is waiting for this request to be sent.
> > > > ]
> > > >
> > > > I'm not an expert of bpel but it looks like bpe is looking for an
> > > > existing instance of a process wich is not what I expect because the
> > > > process is just starting. I attach the content of the bpe service unit.
> > > >
> > > > thanks
> > > > Raffaele
> > > >
> > > >
> > > >
> > >
> >
>
>
>

Reply via email to