Forum Stats

  • 3,769,478 Users
  • 2,252,969 Discussions
  • 7,875,044 Comments

Discussions

Error(59): [Error ORABPEL-10007]: unresolved messageType [Description]:

662666
662666 Member Posts: 49
edited Oct 13, 2008 10:23AM in BPEL
Hi guys,

I am trying to catch remote and binding faults these error messages are coming please help me.

Error(59):
[Error ORABPEL-10007]: unresolved messageType
[Description]: in line 59 of "C:\jdevstudio10131\jdev\mywork\TraxtoE1\ediasnf5547372\bpel\ediasnf5547372.bpel", WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" of variable "RemoteFaultVar" is not defined in any of the WSDL files.
[Potential fix]: Make sure the WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" is defined in one of the WSDLs referenced by the deployment descriptor.


Error(61):
[Error ORABPEL-10007]: unresolved messageType
[Description]: in line 61 of "C:\jdevstudio10131\jdev\mywork\TraxtoE1\ediasnf5547372\bpel\ediasnf5547372.bpel", WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" of variable "BindingFaultVar" is not defined in any of the WSDL files.
[Potential fix]: Make sure the WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" is defined in one of the WSDLs referenced by the deployment descriptor.


Regards
janardhan

Answers

  • Have you imported the RuntimeFault.wsdl into your bpel process.

    1. import orabpel/xmllib/RuntimeFault.wsdl into your process.wsdl
    2. add the namespace xmlns:bpelx="http://schemas.oracle.com/bpel/extension" to the process
    3. create a variable based upon the messagetype RuntimeFaultMessage in this wsdl
    4. add a catch branch to your process or Scope
    5. in this catch branch use the RuntimeFaultMessage as the Fault Variable
    6. You can then use this variable to extract the info you want

    cheers
    James

    process.wsdl

    <import namespace="http://schemas.oracle.com/bpel/extension" location="http://localhost:9700/orabpel/xmllib/RuntimeFault.wsdl"/>


    process.bpel

    <variables>
    <variable name="RuntimeFault" messageType="bpelx:RuntimeFaultMessage"/>
    </variables>


    process.bpel

    <faultHandlers>
    <catch faultName="bpelx:bindingFault" faultVariable="RuntimeFault">
    <assign name="errorOutput">
    <copy>
    <from expression="bpws:getVariableData('RuntimeFault','summary')"/>
    <to variable="outputVariable" part="payload"
    query="/ns3:error_response"/>
    </copy>
    </catch>
  • 662666
    662666 Member Posts: 49
    thank you buddy
  • 644760
    644760 Member Posts: 5
    Hi:

    I have followed the exact procedure defined, and I still receive the same error.

    process.bpel
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension"

    <variable name="FaultVar" messageType="bpelx:RuntimeFaultMessage"/>


    process.wsdl
    <import namespace="http://schemas.oracle.com/bpel/extension" location="http://localhost:9700/orabpel/xmllib/RuntimeFault.wsdl"/>



    ERROR:
    Error(101):
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 101 of "C:\ORACLEFUSION\JDeveloper\jdev\mywork\CheckConnection\CheckPasswordExpiry\bpel\CheckPasswordExpiry.bpel", WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" of variable "FaultVar" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage" is defined in one of the WSDLs referenced by the deployment descriptor.


    Thanks
    Praveen
This discussion has been closed.