Easy-BPEL

Error with onMessage for generated BPEL processes

Details

  • Type: Bug Bug
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When we generate a BPEL skeleton from a WSDL definition, each service operation results in an "onMessage", mark-up, associated with the name space "http://docs.oasis-open.org/wsbpel/2.0/process/executable". If we try to add a child to this element, we got an error from EasyBPEL.

    [BPEL engine restriction] Sorry, but a child activity inside the onMessage for operation null is unrecognized or not supported by Bpel Engine for the moment or is null

    If I change the prefix to associate it with "http://docs.oasis-open.org/wsbpel/2.0/process/abstract", then it is validated.
    I have not tested with the runtime.

    My point is: if onMessage does not work, do not generate such mark-ups. Generating something that is not validated is useless.
    The generation should be updated in consequence.

    Show
    When we generate a BPEL skeleton from a WSDL definition, each service operation results in an "onMessage", mark-up, associated with the name space "http://docs.oasis-open.org/wsbpel/2.0/process/executable". If we try to add a child to this element, we got an error from EasyBPEL.
    [BPEL engine restriction] Sorry, but a child activity inside the onMessage for operation null is unrecognized or not supported by Bpel Engine for the moment or is null
    If I change the prefix to associate it with "http://docs.oasis-open.org/wsbpel/2.0/process/abstract", then it is validated. I have not tested with the runtime. My point is: if onMessage does not work, do not generate such mark-ups. Generating something that is not validated is useless. The generation should be updated in consequence.
  • Environment:
    Windows XP

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:39:14 +0200

OK. In fact, it seems to be a problem with the BPEL designer.
When it finds the abstract BPEL name space, it considers it abstract and makes the things messy.
This bug should be updated as follows:

  • Change it from "bug" to "improvement".
  • Change its title into "Remove the abstract BPEL name space from the BPEL generation".

Thanks.

Show
Vincent Zurczak added a comment - Tue, 14 Sep 2010 - 19:39:14 +0200 OK. In fact, it seems to be a problem with the BPEL designer. When it finds the abstract BPEL name space, it considers it abstract and makes the things messy. This bug should be updated as follows:
  • Change it from "bug" to "improvement".
  • Change its title into "Remove the abstract BPEL name space from the BPEL generation".
Thanks.

People

Dates

  • Created:
    Tue, 14 Sep 2010 - 18:07:23 +0200
    Updated:
    Tue, 14 Sep 2010 - 19:39:14 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.