Petals SE BPEL

Unable to invoke autogenerated endpoint

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.1
  • Fix Version/s: 1.2.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    From the BPEL, the following error occurs invoking an auto-generated endpoint:

    Caused by: com.ebmwebsourcing.easybpel.model.bpel.api.BPELException: endpoint ({http://esb.mediation.archi.acoss.fr/services/echo/1.0}EchoService-autogenerate) not found in the JBI environment
    	at org.ow2.petals.bpel.engine.util.Sender.resolveEndPoint(Sender.java:410)
    	at org.ow2.petals.bpel.engine.util.Sender.send(Sender.java:163)
    	at org.ow2.petals.bpel.engine.env.JBISenderImpl.sendSyncTo(JBISenderImpl.java:183)

    If the endpoint name is 'autogenerate', it has not to be set in the message exchange. The Petals kernel will resolve it according to the interface and service names

    Note: the endpoint name can be 'autogenerate' because it should be extracted from WSDL of partner link

    Show
    From the BPEL, the following error occurs invoking an auto-generated endpoint:
    Caused by: com.ebmwebsourcing.easybpel.model.bpel.api.BPELException: endpoint ({http://esb.mediation.archi.acoss.fr/services/echo/1.0}EchoService-autogenerate) not found in the JBI environment
    	at org.ow2.petals.bpel.engine.util.Sender.resolveEndPoint(Sender.java:410)
    	at org.ow2.petals.bpel.engine.util.Sender.send(Sender.java:163)
    	at org.ow2.petals.bpel.engine.env.JBISenderImpl.sendSyncTo(JBISenderImpl.java:183)
    If the endpoint name is 'autogenerate', it has not to be set in the message exchange. The Petals kernel will resolve it according to the interface and service names Note: the endpoint name can be 'autogenerate' because it should be extracted from WSDL of partner link
  • Environment:
    -

Activity

Christophe DENEUX made changes - Tue, 8 Jan 2013 - 09:10:47 +0100
Field Original Value New Value
Fix Version/s 1.2.0 [ 10344 ]
Priority Blocker [ 1 ]
Description From the BPEL, the following error occurs invoking an auto-generated endpoint:
{code}
Caused by: com.ebmwebsourcing.easybpel.model.bpel.api.BPELException: endpoint ({http://esb.mediation.archi.acoss.fr/services/echo/1.0}EchoService-autogenerate) not found in the JBI environment
at org.ow2.petals.bpel.engine.util.Sender.resolveEndPoint(Sender.java:410)
at org.ow2.petals.bpel.engine.util.Sender.send(Sender.java:163)
at org.ow2.petals.bpel.engine.env.JBISenderImpl.sendSyncTo(JBISenderImpl.java:183)
{code}
If the endpoint name is '{{autogenerate}}', it has not to be set in the message exchange. The Petals kernel will resolve it according to the interface and service names
From the BPEL, the following error occurs invoking an auto-generated endpoint:
{code}
Caused by: com.ebmwebsourcing.easybpel.model.bpel.api.BPELException: endpoint ({http://esb.mediation.archi.acoss.fr/services/echo/1.0}EchoService-autogenerate) not found in the JBI environment
at org.ow2.petals.bpel.engine.util.Sender.resolveEndPoint(Sender.java:410)
at org.ow2.petals.bpel.engine.util.Sender.send(Sender.java:163)
at org.ow2.petals.bpel.engine.env.JBISenderImpl.sendSyncTo(JBISenderImpl.java:183)
{code}
If the endpoint name is '{{autogenerate}}', it has not to be set in the message exchange. The Petals kernel will resolve it according to the interface and service names

Note: the endpoint name can be '{{autogenerate}}' because it should be extracted from WSDL of partner link
Christophe DENEUX made changes - Tue, 8 Jan 2013 - 09:10:56 +0100
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Tue, 8 Jan 2013 - 09:10:58 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 8 Jan 2013 - 09:32:52 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Tue, 8 Jan 2013 - 09:09:05 +0100
    Updated:
    Tue, 8 Jan 2013 - 09:32:52 +0100
    Resolved:
    Tue, 8 Jan 2013 - 09:32:52 +0100