You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "David Carver (JIRA)" <ji...@apache.org> on 2010/05/19 18:11:53 UTC

[jira] Updated: (ODE-827) Better Error Messages for incorrect PortType/Operation on Invoke

     [ https://issues.apache.org/jira/browse/ODE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Carver updated ODE-827:
-----------------------------

    Affects Version/s: 1.3.3
                       1.3.2
                       1.3.4
             Priority: Minor  (was: Major)
          Component/s: BPEL Compilation/Parsing

> Better Error Messages for incorrect PortType/Operation on Invoke
> ----------------------------------------------------------------
>
>                 Key: ODE-827
>                 URL: https://issues.apache.org/jira/browse/ODE-827
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Compilation/Parsing
>    Affects Versions: 1.3.2, 1.3.3, 1.3.4
>            Reporter: David Carver
>            Priority: Minor
>
> The following is an example 
> The operation "Received___Cost_Booking___details" is not declared on portType "{http://example.com/Process/Blah}ForProcess_call". SomeBPELProcess.bpel Some/build/Process line 1113 
> The problem here is that with out the information on what PartnerLink is being invoked it makes it more difficult to know without examining the BPEL what could be he cause.    So something along the lines of:
> SomePartnerLink does not have the operation SomeOperation declared on portType SomePortType:ForPrecess_Call ("{http://example.com/Process/Blah}ForProcess_call") at SomeBPELProcess.bpel Some/build/Process line 1113.
> Could help in tracking down the actual cause.  In this case the BPEL had been requesting the wrong partnerlink to be invoked.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.