Fault Bindings using BPEL.xml

Hi
I have a peculiar problem with fault bindings. I have a webservice from target application hosting two different operations. I need to have the fault policy being applied to one operation and the other operation should not have any fault policy defined on it.
I tried in the following way.
Approach 1. In Fault Bindings.xml i have added the entry for the operation for which policy needs to be applied.
This is working fine as expected.
Approach 2. I have added the entries in bpel.xml and fault-bindings does not contain any entries related to this operation. In this approach the problem am facing is for both the operations the policy is getting applied.
I need to go with the second option as all my bpel processes have fault policies at the bpel level instead of domain level.
Can any one give me some clue on this
Thanks
Vamsi

Entries in BPEL.XML file
<faultPolicyBindings>
<partnerLink faultPolicy="EAIFaultPolicy"/>
<name>BSNLUpdateCollectionStatus</name>
<portType xmlns:CollectionProvCreateSO="http://siebel.com/asi/">CollectionProvCreateSO:BSNLUpdateCollectionStatus</portType>
Entries in Fault Binding.xml has been removed for this
One observation i had is both the WSDLs has same SOAP Address location but the operation names are different.
Does this have any impact for this kind of behaviour
Thanks
Vamsi

Similar Messages

Fault handling using BPEL

Good, I'm working on a research project and I have been assigned the task of processing errors in SOAP BPEL.
I've been searching on Internet and the most commonly methodology used is soap-fault with throwing and catching exceptions in BPEL process.
I wonder if I can do it in a more proactive and comprehensive way, catching those exceptions through a web service, and if possible, how can the BPEL process send the information encapsulated in the soap-fault to the web service?
If there is another way of treating errors or someone can suggest me another way, I would be very grateful.

I am not clear on your objective, but in so far as BPEL SE Component of Open-ESB Project, running on JBI is concerned you can read more about Fault handling and other features of BPELSE here at http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSE. Also, you can find some working examples on this page http://wiki.open-esb.java.net/Wiki.jsp?page=HowToDo
- Malkit

Fault handling in 11g - fault-bindings.xml for a partnerLink

I'm using 11g and I'm trying to use the fault handling framework for a specific partner link. In fault-bindings.xml I have:
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<partnerLink faultPolicy="GetDateFaultPolicy">
<name>GetDateService</name>
</partnerLink>
</faultPolicyBindings>
I have a partner link named GetDateService in the bpel that I'd like to defin a policy for, but when I try to compile, I get:
Warning(3,58): Schema validation failed for fault-bindings.xml<Line 3, Column 58>: XML-24534: (Error) Element 'partnerLink' not expected.
Does the framework still allow partnerlinks granularity, it says it does in the docs?
Thanks

Maybe I should have looked at the new schema first.... : }
It's now reference:
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicyBindings version="2.0.1" xmlns="http://schemas.oracle.com/bpel/faultpolicy">
*<reference faultPolicy="GetDateFaultPolicy">*
<name>GetDateService</name>
*</reference>*
</faultPolicyBindings>
Edited by: Brutus35 on Sep 16, 2010 10:42 AM

SaxParser error while using WSIF bindings in BPEL

Hi All,
I am using WSIF bindings in BPEL to invoke a java class.
This java classs is using Jersey Client. For this I have imported relevant jersey jar files version 1.1.4.1.
My java class is getting invoked and even the jersey client jars are also recognized by my project.
But I am getiing the following SAX parser error:
*Operation failed!; nested exception is: javax.ws.rs.WebApplicationException: javax.xml.bind.JAXBException: Error creating SAXSource - with linked exception: [org.xml.sax.SAXNotSupportedException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.]*
I found the following details when checked the logs.
JAXP feature XMLConstants.FEATURE_SECURE_PROCESSING cannot be set on a SAXParserFactory. External general entity processing is disbaled but other potential securty related features will not be enabled.
Please let me know what should be done in order to solve this issue.
Thanks in advance!!!

I am having the same problem in a non-BPEL application. I am using Oracle MDS in an application that is also using Jersey 1.1.4.1 and it blows up Jersey 1.1.4.1 in the same way.
Oracle MDS has a dependency on Oracle XDK, an XML parser (xmlparserv2.jar). xmlparserv2.jar registers Oracle's oracle.xml.jaxp.JXSAXParserFactory using the Java ServiceLoader API (by using the file META-INF/javax.xml.parsers.SAXParserFactory.
Jersey doesn't like Oracle's JXSAXParserFactory, as you can see. From what I've found so far, it seems that the Oracle SAXParserFactory is clamped down for security and Jersey will not work with it. Here is a more complete stack trace that I have:
[org.xml.sax.SAXNotSupportedException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.]
at com.sun.jersey.core.provider.jaxb.AbstractJAXBProvider.getSAXSource(AbstractJAXBProvider.java:178)
at com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider.readFrom(XMLRootElementProvider.java:110)
at com.sun.jersey.core.provider.jaxb.AbstractRootElementProvider.readFrom(AbstractRootElementProvider.java:105)
Caused by: org.xml.sax.SAXNotSupportedException: SAX feature 'http://xml.org/sax/features/external-general-entities' not supported.
at oracle.xml.parser.v2.NonValidatingParser.setFeature(NonValidatingParser.java:1974)
at oracle.xml.parser.v2.SAXParser.setFeature(SAXParser.java:270)
at oracle.xml.jaxp.JXSAXParserFactory.newSAXParser(JXSAXParserFactory.java:92)
at com.sun.jersey.core.provider.jaxb.AbstractJAXBProvider.getSAXSource(AbstractJAXBProvider.java:174)
In my case, Jersey seems to ignore the system property that I set with -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
I am trying to figure out a way to satisfy the dependency that my app has on Oracle's XDK (xmlparserv2.jar) without having its SAXParserFactory take over Jersey.
I'll try to post here if I ever solve my problem because it sounds the same as yours.

Purchase Order to Purchase Order using BPEL and/or XML Gateway

Hi,
Is there a way to do create a duplicate Purchase Order in another instance using BPEL and/or XML Gateway? We're looking to do A2A transactions, namely duplicating data from one instance to another (of course the functional setups would have to be the same). Thanks!!

this is the perfect usace for the upcoming ESB (shuffling data with transforming from A to B) - but this can be done with BPEL too .. there are some solutions to this
1) on a database level (db to db)
2) having events setup'ed in the master instance, that fire a process that get's the data
3) and then using the functions from iRep
hth clemens

Using BPEL console testing with XML attributes

I'm having trouble with using an XML attribute in my BPEL process. When I put an attribute on my input element, the BPEL Console test page no longer works. Here's what I'm doing:
I create a synchronous new BPEL project in JDeveloper using the default input and output XSDs, and add a simple assign to assign the input to the output. When I deploy this and look at it in BPEL console, I can see the input field and enter my value to test.
Now I go back into JDeveloper and add an attribute to the input element, and then redeploy my process. Now when I go into BPEL console, the Initiate tab no longer has any field for me to enter my value. Clicking the XML Source radio button doesn't help either. (I also tried invoking the BPEL process web service through the app server control - same issue.)
I'm using JDeveloper 10.1.3.3 with App Server 10.1.3.3.0. Does anyone know how to make the BPEL Console testing work with XSDs that contain attributes?
Thanks,
Skip

A bit more info on this. It doesn't appear that the problem is limited to the console tester. I created another BPEL process which calls my original process, and attempted to set the attribute on the input using the Assign activity. JDeveloper generated this:
<assign name="Assign_1">
<copy>
<from variable="inputVariable" part="payload"
query="/client:TestAttributes2ProcessRequest/client:input"/>
<to variable="Invoke_1_process_InputVariable" part="payload"
query="/ns1:TestAttributesProcessRequest/ns1:input"/>
</copy>
<copy>
<from expression="'bob'"/>
<to variable="Invoke_1_process_InputVariable" part="payload"
query="/ns1:TestAttributesProcessRequest/ns1:input/@attribute1"/>
</copy>
</assign>
As you can see this is mapping a variable into the /TestAttributesProcessRequest/input element and then attempting to set the attribute of that element to the value 'bob'. This compiles just fine but when this code is executed, this error occurs:
Error in <assign> expression: <to> value is empty at line "87". The XPath expression : "" returns zero node, when applied to document shown below:
oracle.xml.parser.v2.XMLElement@7efe7efe
(Line 87 is query="/ns1:TestAttributesProcessRequest/ns1:input/@attribute1"/>)
Is there something wrong with this generated code? Do I need to do some kind of custom code to set attributes, instead of using the graphical tools in JDeveloper?

How to add XML attribute to an Element using BPEL assign

I have a request xml to a bpel process that does not contain a attribute.
After some process I need to create this missing attribute and set a value.
I tried using the XML fragment in the Assign Activity. But how can I create a attribute?
This XML node to which I am trying to create an attribute is a very huge node with lot of dynamic typing(xsi:type). I can just re-create the complete xml with required nodes.
Does any one know how I can create a xml attribute using the BPEL assign? I do not want to use the Java code in my process.
Thanks.

I'm bit confused about what exact problem you are facing with attributes.
You can check accessing XML attributes in BPEL Assign @ http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/manipdoc.htm#BABIHDHI from the page http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/manipdoc.htm.
I suppose your source input has no attributes and destination has to be an xml with attribute of type xsi:type. You can use the assign activity as mentioned in above document to assign your type structure to type attribute.

RejectedMessageHandlers property, can we use it 2 times in bpel.xml file

hi'
I have a XML file to read, if the file is incorrect then I am calling another BPEL process to catch the error by the below code
inside the bpel.xml file
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="TestFileRead" src="TestFileRead.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="ReadFile">
<property name="wsdlLocation">ReadFile.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="ReadFile">
<property name="portType">Read_ptt</property>
*<property name="rejectedMessageHandlers">bpel://default|GetRejectedMessageBPEL|initiate|payload</property>*
*<property name="rejectedMessageHandlers">file:///abc/test/fail</property>*
</activationAgent>
</activationAgents>
</BPELProcess>
</BPELSuitcase>
Now what I want to do is, I also want to move the rejected file to different directory something like this,
*<property name="rejectedMessageHandlers">file:///abc/test/fail</property>*
however If I put both the property inside the bpel.xml file then only one is working which is the later one i.e. it simply ignores the first one. My requirement is, I also want to move the rejected file to different directory, please tell me how this can be achieved, where I want to move the error file to other directory and pass the error details to other BPEL process.
thanks
Yatan

If that is the case...
do what you are doing in second BPEL in first BPEL catch block and use the property to move the file to folder.
Ohhhh... Sorry.... It will not go to catch right....
Regards
PavanKumar.M
Edited by: pavan4s on Sep 2, 2010 12:25 AM

AP Invoices via XML Gateway using BPEL

Experts,
I am trying to create a process that loads an invoice into 11i Accounts Payables using the XML Gateway. I have done this manually, uploading a piece of XML using the Oracle Transport Agent Send Inbound html page and it works fine. I believe my applications environment is working correctly. However, when I attempt to leverage the XML Gateway adapter for invoices in BPEL 10.1.2.02 I am getting errors.
For some reason I am not able to add one xml node (which processes the invoice) as a child of another (the entire xml message sent to the gateway).
I'm trying to assign a piece of an xml doc to the message for AP/XML Gateway:
<copy>
<from variable="Invoke_AP_Invoice_Enqueue_InputVariable" part="PROCESS_INVOICE_002"/>
<to variable="Invoke_1_ReceiveDocument_InputVariable" part="body" query="/ns5:ReceiveDocument[1]"/>
</copy>
What I am expecting is:
<Invoke_1_ReceiveDocument_InputVariable>
<part name="header" >
<XMLGateway_Header>
<MESSAGE_TYPE>XML</MESSAGE_TYPE>
<MESSAGE_STANDARD>OAG</MESSAGE_STANDARD>
<TRANSACTION_TYPE>INVOICE</TRANSACTION_TYPE>
<TRANSACTION_SUBTYPE>PROCESS</TRANSACTION_SUBTYPE>
<DOCUMENT_NUMBER>1</DOCUMENT_NUMBER>
<PARTY_ID>1</PARTY_ID>
<PARTY_SITE_ID>OSO</PARTY_SITE_ID>
<USERNAME>SYSADMIN</USERNAME>
<PASSWORD>SYSADMIN</PASSWORD>
</XMLGateway_Header>
</part>
<part name="body" >
<ReceiveDocument>
<PROCESS_INVOICE_002>
<CNTROLAREA>...
What I get is:
<Invoke_1_ReceiveDocument_InputVariable>
<part name="header" >
<XMLGateway_Header>
<MESSAGE_TYPE>XML</MESSAGE_TYPE>
<MESSAGE_STANDARD>OAG</MESSAGE_STANDARD>
<TRANSACTION_TYPE>INVOICE</TRANSACTION_TYPE>
<TRANSACTION_SUBTYPE>PROCESS</TRANSACTION_SUBTYPE>
<DOCUMENT_NUMBER>1</DOCUMENT_NUMBER>
<PARTY_ID>1</PARTY_ID>
<PARTY_SITE_ID>OSO</PARTY_SITE_ID>
<USERNAME>SYSADMIN</USERNAME>
<PASSWORD>SYSADMIN</PASSWORD>
</XMLGateway_Header>
</part>
<part name="body" >
<ReceiveDocument>
<CNTROLAREA>...
As you will notice the <PROCESS_INVOICE_002> tag is missing. Everytime I assign it, the <PROCESS_INVOICE_002> will not show up. What am I doing incorrectly? btw - I'm not on this list so any (please!) responses will have to be copied to me.
Thanks,
Mark W

We have exactly the same problem. The guides are not up to date and we can't find where to find information about accepting and processing inbound Advanced Shipment Notifications (ASN) through XML Gateway.

Get Custom SOAP Header Value in SOA Suite 11.1.1.6 using BPEL 1.1

Hi Experts,
We are using SOA Suite 11.1.1.6 and in one of the projects we have requirement to retrieve custom SOAP header value.
This is enhancement to existing process which is developed using BPEL 1.1 and deployed to Production. So we cannot convert this now to BPEL 2.0
We suggested to use custom XML element in Header the definition of which will be defined in custom XSD and stored in common location. However the 3rd party who are invoking this service will not be able to do any customization in their process to pass custom XML header.
Please can you help me in providing any approach through which we can retrieve custom Header value from SOAP header using BPEL 1.1
I have read some blogs for retrieving the custom XML header but they are using BPEL 2.0. I would like achieve this functionality using BPEL 1.1
Appreciate your inputs.
Thanks in Advance - RK

Hello RK,
Have you've tried to put the bpex:outputHeaderVariable on the invoke activity of the invoked service.
<invoke name="Invoke"
bpelx:outputHeaderVariable="HeaderVariable"/>
Where the "HeaderVariable" reflects the XSD Datastructure of the received header.
This is also specified here in section 6.19.1 How to Receive SOAP Headers in BPEL
Please note that the exact header must be specified in the WSDL of the invoked service.
Also note that in case of a soap fault. No header will be returned from the invoked service but only a /soap/body/fault part.
Good luck!
Melvin

Trying to throw fault from one BPEL process to another

We are trying to throw a fault from one BPEL process to another and apparently are experiencing a common problem. That is, the invoking process times out and never receives the fault.
Likely a beginner's mistake is at fault (pun intended).
Below are samples of a simple "Hello World" process that tries to throw the fault.
snippet of pbel file....
<process name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns1="http://helloworldjavaproject/"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<faultHandlers>
<catchAll>
<sequence name="Sequence_1">
<assign name="Assign_3">
<copy>
<from expression="12345"/>
<to variable="FaultVar" part="code"/>
</copy>
<copy>
<from expression="'Hello fault summary'"/>
<to variable="FaultVar" part="summary"/>
</copy>
<copy>
<from expression="'Hello test detail'"/>
<to variable="FaultVar" part="detail"/>
</copy>
</assign>
<throw name="Throw_2" faultName="client:myFault"
faultVariable="FaultVar"/>
</sequence>
HelloJavaWorldSynchronous.wsdl file
<definitions
name="HelloJavaWorldSynchronous"
targetNamespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/HelloJavaWorldSynchronous"
>
<import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl";/>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/HelloJavaWorldSynchronous" schemaLocation="HelloJavaWorldSynchronous.xsd";/>
</schema>
</types>
<message name="HelloJavaWorldSynchronousRequestMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessRequest"/>
</message>
<message name="HelloJavaWorldSynchronousResponseMessage">
<part name="payload" element="client:HelloJavaWorldSynchronousProcessResponse"/>
</message>
<portType name="HelloJavaWorldSynchronous">
<operation name="process">
<input message="client:HelloJavaWorldSynchronousRequestMessage"/>
<output message="client:HelloJavaWorldSynchronousResponseMessage"/>
<fault name="myFault" message="ns1:RuntimeFaultMessage"/>
</operation>
</portType>
<plnk:partnerLinkType name="HelloJavaWorldSynchronous">
<plnk:role name="HelloJavaWorldSynchronousProvider">
<plnk:portType name="client:HelloJavaWorldSynchronous"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The standard RuntimeFault.wsdl file (RuntimeFaultMessage message is defined in here, so I don't need a message in HelloJavaWorldSynchronous.wsdl. Do I?)
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="RuntimeFault"
targetNamespace="http://schemas.oracle.com/bpel/extension"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<message name="RuntimeFaultMessage">
<part name="code" type="xsd:string"/>
<part name="summary" type="xsd:string"/>
<part name="detail" type="xsd:string"/>
</message>
</definitions>
But when we invoke the process, after the standard 45 seconds timeout, we still get...
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is f290d62d2ad31aa6:-49eb76f4:124eb51622a:-7c91. Please check the process instance for detail.</faultstring>
</Fault>
The console audit below might hold a clue. I noticed the mesage BPELFault" has not been caught by a catch block at the end.
<catchAll>
<sequence>
Assign_3
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</part>
</FaultVar>
[2009/11/13 11:18:32] Updated variable "FaultVar" More...
-<FaultVar>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</FaultVar>
Throw_2 (faulted)
[2009/11/13 11:18:32] "{http://xmlns.oracle.com/HelloJavaWorldSynchronous}myFault" has been thrown. More...
-<myFault xmlns="http://xmlns.oracle.com/HelloJavaWorldSynchronous">
-<part name="code">
<code xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">12345
</code>
</part>
-<part name="summary">
<summary xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello fault summary
</summary>
</part>
-<part name="detail">
<detail xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Hello test detail
</detail>
</part>
</myFault>
</sequence>
</catchAll>
[2009/11/13 11:18:32] "BPELFault" has not been caught by a catch block.
[2009/11/13 11:18:32] BPEL process instance "570162" cancelled

Thanks very much for this answer. It was right on.
You wanted to know "how (I) get on". Funny you should ask. Believe it or not, I had figured out the problem on my own just about the time you were posting your reply (of course, this is a bit too convenient. No one will ever believe me).
But the answer leads to another question. What is the Throw activity for, if not to throw an error to the calling process? Is it only used to throw within scope of the process its self?
I am probably biased by the Java world I am coming from, but Throw feels like it should terminate the process (without side effects like a big red mark in the console) bubble up the fault to the calling process who can catch it (if so desired). Using the reply we must explicitly Terminate (which includes that unsightly red mark).
Is there any way to get this behavior from the Throw, or should we just reprogram the "wetware" and learn a new paradigm?
Is there any way to end a process without marking it with a red flag that suggests something went wrong?

XML in Payload, fault returned. -org.xml.sax.SAXException: SimpleDeserializ

I'M getting the following fault msg returned -
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
         <soapenv:Fault>
            <faultcode>soapenv:Server.userException</faultcode>
            <faultstring>org.xml.sax.SAXException: SimpleDeserializer
encountered a child element, which is NOT expected, in something it
was trying to deserialize.</faultstring>
            <detail/>
         </soapenv:Fault>
      </soapenv:Body>
   </soapenv:Envelope>
WHEN I send over this SOAP Msg in my document style web service:
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
         <CATALOG xmlns="http://mywroxexample/axis/catalog">
            <DOCUMENTINFO>
               <DATE>02/15/2004</DATE>
            </DOCUMENTINFO>
            <SUPPLERDETAILS>
               <SUPPLIERID>1234</SUPPLIERID>
               <SUPPLIERCONTACTEMAIL>[email protected]</SUPPLIERCONTACTEMAIL>
            </SUPPLERDETAILS>
            <PRODUCTLIST>
               <PRODUCT>
                  <SUPPLIER-PRODUCTSKU>SKU 123</SUPPLIER-PRODUCTSKU>
               </PRODUCT>
            </PRODUCTLIST>
         </CATALOG>
      </soapenv:Body>
   </soapenv:Envelope>
I'm using apache axis with tomcat.
Any advice regarding what this fault msg means or how to fix my
problem is appreciated.
org.xml.sax.SAXException: SimpleDeserializer encountered a child
element, which is NOT expected, in something it was trying to
deserialize.

Fixed my own problem.
I should of declared the WS to be of type 'message' instead of document.

Error in Parsing XML using fx:XML/ [Error- 1090: XML parser failure: element is malformed]

Hi All,
I am getting error while loading XML in <fx:XML> tag.
Error:
TypeError: Error #1090: XML parser failure: element is malformed.
MXML Code:
<fx:Declarations>
<fx:XML id="xmlSource2" source="sample.xml"/>
</fx:Declarations>
Sample XML Used: (sample.xml)
<?xml version="1.0" encoding="UTF-8"?>
<File>
    <Chemical id="000035676" displayFormula="C39-H45-N2-O6"
        displayName="Dimethyltubocurarine">
        <NameList>
            <NameOfSubstance>
                Dimethyltubocurarine
                <SourceList>
                    <Source>MESH</Source>
                </SourceList>
            </NameOfSubstance>
            <SystematicName>
                Tubocuraranium, 6,6',7',12'-tetramethoxy-2,2',2'-trimethyl-
                <SourceList>
                    <Source>NLM</Source>
                </SourceList>
            </SystematicName>
            <Synonyms>
                Dimethyltubocurarine
                <SourceList>
                    <Source>NLM</Source>
                </SourceList>
            </Synonyms>
            <Synonyms>
                Dimethyltubocurarinium
                <SourceList>
                    <Source>NLM</Source>
                </SourceList>
            </Synonyms>
            <Synonyms>
                Methyltubocurarinum
                <SourceList>
                    <Source>NLM</Source>
                </SourceList>
            </Synonyms>
        </NameList>
        <NumberList>
            <CASRegistryNumber>
                35-67-6
                <SourceList></SourceList>
            </CASRegistryNumber>
            <RelatedRegistryNumber>
                518-26-3 (iodide.hydriodide)
                <SourceList>
                    <Source>MESH</Source>
                </SourceList>
            </RelatedRegistryNumber>
        </NumberList>
        <ClassificationList>
            <ClassificationCode>
                Neuromuscular nondepolarizing agents
                <SourceList>
                    <Source>MESH</Source>
                </SourceList>
            </ClassificationCode>
        </ClassificationList>
        <FormulaList>
            <MolecularFormula>
                C39-H45-N2-O6
                <SourceList>
                    <Source>NLM</Source>
                </SourceList>
            </MolecularFormula>
        </FormulaList>
        <FormulaFragmentList></FormulaFragmentList>
        <NoteList></NoteList>
        <LocatorList>
            <FileLocator
                url="http://cnetdb.nci.nih.gov/cgi-bin/srchcgi.exe?DBID=****3&SFMT=****_basic%2F10%2F0%2F0&TYPE=search&SRCHFORM=passthru%3D%Asrchform%3ASRCH%3A&FIELD_001=[CAS]35-67-6&GoButton=Search&FIELD_001_CTL=EXPR&FIELD_908=&FIELD908_CTL=HASABSTRACT&FIELD_903=&FIELD_903_CTL=YEARFORE&DOCPAGE=10">CANCERLIT</FileLocator>
            <FileLocator
                url="http://toxnet.nlm.nih.gov/cgi-bin/sis/search/r?dbs+toxline:@and+@term+@rn+35-67-6+@term+@org+DART">DART/ETIC</FileLocator>
            <FileLocator
                url="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=search&db=PubMed&term=35-67-6[ECNO]+OR+"~"[MH]">MEDLINE</FileLocator>
            <FileLocator
                url="http://www.nlm.nih.gov/cgi/mesh/2K/MB_cgi?term=35-67-6&rn=1">MESH</FileLocator>
            <FileLocator
                url="http://toxnet.nlm.nih.gov/cgi-bin/sis/search/r?dbs+toxline:@term+@rn+35-67-6+@OR+@mh+""">TOXLINE</FileLocator>
        </LocatorList>
    </Chemical>
</File>
Also, when I am using HttpService to load same XML I am getting no such error!!
<s:HTTPService id="employeeService"
                       url="sample.xml"
                       result="employeeService_resultHandler(event)"
                       fault="employeeService_faultHandler(event)"/>
Please help!!
Thanks.
Abhinav

I think url in XML is creating problem here.
<FileLocator
                url="http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=search&db=PubMed&term=23-95-0[ECNO]+OR+"~"[MH]">MEDLINE</FileLocator>
Is there any way to parse this XML using <fx:XML/> ??
Thanks.

Error logging in using BPEL Console

Hi
When I try to login using BPEL Console, I get following error:
"No domains accessible to the user logged in"
I tried link "Goto BPEL Admin". I found no domains there. I am unable to add new domain also.
Can anyone let me know if I need to change any configuration to make this work?
Thanks

Hi Badri,
Check 1:
First checkpoint where we can identify the detail of error description is checking the following log files;
Domain Log: $SOA_Home\bpel\domains\default\logs\domain.log ('default' is the default domain name)
- This log file will be created everytime the SOA service is started and will log any domain level startup issues
OPMN Log: $SOA_Home\opmn\logs\OC4J~oc4j_soa~default_group~1.log
- This log file will log all the BPEL process specific logs (creation/termination)
System Log: $SOA_Home\bpel\system\logs\orabpel.log
- System level logging is provided for infrastructure, AXIS, and WSIF issues
All these log files should give a clear picture about the error which might be causing this issue, based on which you can take necessary actions.
Check 2:
Check whether the database on top of which Oracle SOA suite was installed is up & running. If not, ensure the RDBMS listener is running & restart SOA service.
Check 3:
The Oracle SOA suite will be installed on top of a database (Oracle Lite/external Oracle DB), where three schemas would have been created during installation namely Orabpel, Oraesb, Orawsm. These schemas might have got corrupted (or) their passwords might have got changed which throws "No domains accessible to the user logged in." error in Oracle BPEL console. Ensure all 3 schemas are present in the database and their passwords are intact as specified in the datasources.xml/during installation and restart SOA service after corrections.
Check 4:
If any class files have been added in the SOA suite, ensure they are properly compiled and deployed @ $SOA_Home\bpel\system\classes.
Check 5:
If you have added any custom xpath functions for use in the BPEL process, you might have added entries in the $SOA_Home/bpel/system/config/xpath-functions.xml. Ensure that this file is well formed.
Check 6:
If you have deployed any BPEL process recently after which the Oracle BPEL console throws this error, there might be high chance for issues in the deployed BPEL process.
All deployed BPEL processes will be picked up from the following location. Take backup of the existing processes, delete all entries and then restart SOA service.
$SOA_Home\bpel\domains\default\tmp ('default' is the default domain name)
Refer : http://sathyam-soa.blogspot.com/2009/01/oracle-bpel-console-throws-no-domains.html
Hope this helps!
Cheers
Anirudh Pucha

Fault Handling in BPEL process

hi
We have to develop an application which involves several BPEL processes and proxy service(OSB) and JMS queue etc.
What is the difference between Fault Management Framework in SOA11g and normal fault handling(using catch and throw activities)?
which one we should prefer for fault handling in our application n why?
Plz help thanks in advance.

Hi-
In Normal Fault handling process, you will be able to catch the faluts only but in Fault Management Framework if a fault occurs the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity. You can also have a human intervention prescribed in it, where you perform recovery actions from Enterprise Manager.
Pls go throgh the below post for detailed description
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_faults.htm
Fault Management Framework and non BPEL soap faults
Edited by: 333333 on Mar 23, 2011 5:01 PM

Fault Bindings using BPEL.xml

Similar Messages

Maybe you are looking for