OSB : BEA-382510: OSB Assign action failed updating variable

Hi all,
I just started learning OSB and created a simple process .
This is my request :
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soap:Header      xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
     </soap:Header>
     <soapenv:Body>
     <hel:getGreeting      xmlns:hel="http://hello.alsb.com/">
     <!--Optional:-->
     <arg0>string</arg0>
     </hel:getGreeting>
     </soapenv:Body>
     </soapenv:Envelope>
im getting a error response in Assign:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
     <soapenv:Fault>
     <faultcode>soapenv:Server</faultcode>
     <faultstring>
     BEA-382510: OSB Assign action failed updating variable "Test": weblogic.xml.query.exceptions.XQueryTypeException: {err}XP0006: "element return { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type {http://www.w3.org/2001/XMLSchema}string
     </faultstring>
     <detail>
     <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382510</con:errorCode>
     <con:reason>
     OSB Assign action failed updating variable "Test": weblogic.xml.query.exceptions.XQueryTypeException: {err}XP0006: "element return { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type {http://www.w3.org/2001/XMLSchema}string
     </con:reason>
     <con:location>
     <con:node>RouteTo_HelloWorldBiz</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>
     </soapenv:Envelope>
This is my Xquery:
xquery version "1.0" encoding "Cp1252";
declare namespace xf = "http://tempuri.org/GoodbyeWorld_SB/XQuery/Hello_to_GoodBye/";
declare function xf:Hello_to_GoodBye($helloStr as xs:string)
as xs:string {
replace($helloStr, 'HELLO', 'Goodbye')
declare variable $helloStr as xs:string external;
xf:Hello_to_GoodBye($helloStr)
in my message response pipeln of the proxy service:
i have added the assign and given the expression : $body/hel:getGreetingResponse/return
var :Test
After the assign: i have given a replace activity:
xpath: ./hel:getGreetingResponse/return
varabile : body
Expression : string($Test)
when i test in OSB console:
im getting this error:
<soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
     <soapenv:Fault>
     <faultcode>soapenv:Server</faultcode>
     <faultstring>
     BEA-382510: OSB Assign action failed updating variable "Test": weblogic.xml.query.exceptions.XQueryTypeException: {err}XP0006: "element return { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type {http://www.w3.org/2001/XMLSchema}string
     </faultstring>
     <detail>
     <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382510</con:errorCode>
     <con:reason>
     OSB Assign action failed updating variable "Test": weblogic.xml.query.exceptions.XQueryTypeException: {err}XP0006: "element return { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type {http://www.w3.org/2001/XMLSchema}string
     </con:reason>
     <con:location>
     <con:node>RouteTo_HelloWorldBiz</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>
     </soapenv:Envelope>
aany suggestions on where the issue is.
im totaly stuck here:
TIA,
karthik

it is not clear at which point you are invoking Hello_to_GoodBye, and using which argument
anyway it's likely that you are passing an Xml element (a node, something like <hello>Charlie</hello>) instead of a simple type (a string, like "Charlie")
you should use the function data($body/bla) or text ($body/bla/text() ) to extract the value (Charlie) of your element

Similar Messages

  • MQ:OSB Assign action failed updating variable "ServiceRequest"

    Hi
    We have a problem with the MQ adapters in Oracle Service Bus.
    If we (by accident/break testing) put messages on the queue that are invalid XML (such as "Banana" as plain text), the OSB goes into an infinte loop with this message, as it can never be dequeued due to:
    <BEA-381901> <Exception in MQ Inbound Request: TransportException EndPoint: T20230_GoodsEvent/ProxyServices/T20230_G
    oodsEvent, com.bea.wli.sb.transports.TransportException: OSB Assign action failed updating variable "ServiceRequest": com.bea.wli.common.xquery.XQueryException: Error parsing XML: {err}FORG0
    005: expected exactly one item, got 0 items
    com.bea.wli.sb.transports.TransportException: OSB Assign action failed updating variable "ServiceRequest": com.bea.wli.common.xquery.XQueryException: Error parsing XML: {err}FORG0005: expect
    ed exactly one item, got 0 itemsThis even prevents the message from being put on the dead letter queue.
    Any hints?

    Correct, but we have tried switching to Text to no avail.

  • I need helop with my ALSB Replace action failed updating variable

    System Error Handler
    $fault:      
         <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-382513</con:errorCode>
         <con:reason>
         ALSB Replace action failed updating variable "body": Error parsing XML: {err}XP0006: "element {http://rep.oio.dk/tinglysning.dk/svarservice/message/anmeldelse/1/}AndelsbogAnmaerkningStatusModtag { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type element {http://rep.oio.dk/tinglysning.dk/schema/anmeldelse/1/}AndelsbogAnmaerkningStatus { {http://www.w3.org/2001/XMLSchema}anyType }
         </con:reason>
         <con:location>
         <con:node>PipelinePairNode1</con:node>
         <con:pipeline>PipelinePairNode1_response</con:pipeline>
         <con:stage>stage1</con:stage>
         <con:path>response-pipeline</con:path>
         </con:location>
         </con:fault>
    Edited by: user543916 on Jun 28, 2011 2:28 AM

    you should report also the content of the variable you were trying to assign to $body, and which element in $body you were trying to modify.

  • Getting --BEA-382510: OSB Assign fails.

    Hi I have exposed an EJB as a Business Service though OSB.
    Above this business Service sits a Proxy Service which is called the Data Service and Over the Data Service Sits the actual Proxy Service which is exposed to the clients.
    While testing the data service, the flow always fails when the response from the business service to the data service.
    "OSB Assign action failed updating variable "responseParam": weblogic.xml.query.exceptions.XQueryDynamicException: {err}FORG0005: expected exactly one item, got 0 items"
    The response from the EJB is being returned as expected but when the response reaches the response pipeline (where i have put a transformation) it fails with the above error.
    Individual queries and transformation are working fine when tested discreetly, but when the flow is triggered end to end it fails
    Can some body please help. I am completely stuck.
    Edited by: sgupta2 on Jul 15, 2009 1:40 PM

    This is one of the very basic errors in XQuery and XPath. This is thrown where an XPath is supposed to return a node but it can not retrieve one at runtime. There can be many reasons for this.
    For ex. your Xpath may be wrong, source XML does not contain the element which you are looking for, providing incorrect namespaces of the element. You can log the input XML to verify that the element your XPath is referring to is present. Then you can separately test the XPath/XQuery to validate its correctness.

  • Xquery exception: BEA-382510

    Experts,
    I am facing this weird issue in OSB, the explanation for the issue is:
    Whenever the mange instances gets overloaded or even some time when they are running fine, I get this exception BEA-382510 from the message flow.
    There is no problem with any xqueries or xpath or namespace. Everything is fine.
    The issue gets resolved when i restart the mange instances.
    There is no particular pattern which i could trace for the occurence of the issue. It is random in nature.
    This is happening sometimes even in production and i am unable to figure out the root cause.
    It would be great if any expert can throw more light on this.
    Regards,
    Deepak.

    Hi,
    I am getting the same issue on our OSB. Is there information about the reason of this issue? Any results of the investigation?
    We are using Service Bus 11gR1. Using XQuery, transformation. I did few tests with a default xml messages, they failed with the same error. But the first time after editing and activating the service bus, the first message handled without error!!
    The second attempt with the exact message result in error.
    OSB Assign action failed updating variable "transformOutput":
         com.bea.wli.common.xquery.XQueryException:
         Error parsing XML: {bea-err}TYPE003: Runtime Type Mismatch
    If you have any advice or the results of the investigation, will appreciate it.
    thanks.
    Regards,
    B. Al Soufi

  • Error BEA-382510 bad value for type node

    Hi,
    We have a requirement to read the xpath from the resource file placed in project folder in OSB and use that xpath to generate the report. For this I have done the following:
    1) Made the xpath entry to properties file as <xpath>$body/*/*/EMPTYPE/EMPDATA/EMPNO</xpath>
    2) Created a variable to fetch the xpath value from property file, say xpathvar
    3) Created another variable, say reportvar which will have the contents: <report>{$xpathvar/text()}</report>. This should fetch the xpath from the variable and replace it in the calling part to fetch the value of the xpath.
    4) For report generation the in key value it is ./text() from variable reportvar.
    When I test this it throws error:
    <con:errorCode>BEA-382510</con:errorCode>
    <con:reason>
    OSB Assign action failed updating variable "reportxpath": com.bea.wli.common.xquery.XQueryException: Error parsing XML: line 1, column 19: {err}XP0006: "$body/*/*/EMPTYPE/EMPDATA/EMPNO ({http://www.w3.org/2001/XMLSchema}string)": bad value for type node
    </con:reason>
    Any pointers will be highly appreciated.
    Thanks!

    I think you cant substitute xpath as you have did.
    As shown in the blog which you mentioned in the other post you may need to have a xslt transformation with xalan:evaluate to correctly process the xpath read from the properties file.
    <report>{$xpathvar/text()}</report>. Here $xpathvar having the value '$body/*/*/EMPTYPE/EMPDATA/EMPNO' will be treated as string type (this will be string as you have read from the properties file as string) and not node. And you are trying to apply the text() function on a string instead of node which is resulting in that error.

  • BEA-382513: OSB Replace action failed: bad value for type element anyType

    Hello, in OSB I get this strange error message on my XQUERY TRANSFORMATION.
    *<faultstring>BEA-382513: OSB Replace action failed updating variable "response":*
    com.bea.wli.common.xquery.XQueryException:
    *Error parsing XML: {err}XP0006: "*
    *element {http://xmlns.oracle.com/pcbpel/adapter/db/top/CS2AdapterSelectOffenePosten_v0_5}Cs2DebitorOpVieCollection*
    *{ {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }":*
    bad value for type element
    *{http://xmlns.oracle.com/pcbpel/adapter/db/top/CS2AdapterSelectOffenePosten_v0_5}cs2RechungungenResponse*
    *{ {http://www.w3.org/2001/XMLSchema}anyType }*
    *</faultstring>*
    I'm a pl/sql developer and I have no idea what this error message is telling me.
    In this forum I'v read someting about a wrong namespace declaration. I can't see any wrong value on my xml (ok, I'm not the specialist here...)
    Maybe someone of you xquey cracks might have a look at my code?
    This is what I have:
    _1.) a XQuery variable called cs2RechnungenResponse with this content:_
    <cs2:Cs2DebitorOpVieCollection
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:cs2="http://xmlns.oracle.com/pcbpel/adapter/db/top/CS2AdapterSelectOffenePosten_v0_5">
         <cs2:Cs2DebitorOpVie>
              <cs2:f40Konto>333</cs2:f40Konto>
              <cs2:AMT_BEZEICHNUNG>Amt für Gesundheit</cs2:AMT_BEZEICHNUNG>
              <cs2:f40Belnr>555</cs2:f40Belnr>
              <cs2:f40Sohab>S</cs2:f40Sohab>
              <cs2:f40Dmbet>100</cs2:f40Dmbet>
              <cs2:f40Fadat>2011-05-05T00:00:00.000+02:00</cs2:f40Fadat>
              <cs2:f40Valut>2011-05-05T00:00:00.000+02:00</cs2:f40Valut>
              <cs2:f40Mahns/>
              <cs2:f40F40Sj>0</cs2:f40F40Sj>
         </cs2:Cs2DebitorOpVie>
    </cs2:Cs2DebitorOpVieCollection>
    _2. a xquery with this code:_
    (:: pragma bea:global-element-parameter parameter="$cs2RechnungenResponse" element="ns2:cs2RechnungenResponse" location="../adapters/cs2_adapters/xsd/CS2AdapterSelectOffenePosten_v0_5_table.xsd" ::)
    (:: pragma bea:global-element-return element="ns0:getDebitorRechnungResponse" location="../../interfaces/RechnungServiceTypes_v0_6.xsd" ::)
    declare namespace ns3 = "http://www.llv.li/common/types/v1";
    declare namespace ns2 = "http://xmlns.oracle.com/pcbpel/adapter/db/top/CS2AdapterSelectOffenePosten_v0_5";
    declare namespace ns1 = "http://www.llv.li/fin/types/v1";
    declare namespace ns0 = "http://www.llv.li/fin/services/rechnungService/v1";
    declare namespace xf = "http://tempuri.org/fin_sb/RechnungsService/transformations/CARI_CS_2DBAdpter_to_RechnungsServiceGetOffenePosten_v0_5/";
    declare function xf:CARI_CS_2DBAdpter_to_RechnungsServiceGetOffenePosten_v1_0($cs2RechnungenResponse as element(ns2:cs2RechnungenResponse))
    as element(ns0:getDebitorRechnungenResponse) {
    <ns0:getDebitorRechnungenResponse schemaVersion="0.6">
              if ($cs2RechnungenResponse/ns2:Cs2DebitorOpVie) then
              <ns0:debitorRechnungList>
         for $Cs2DebitorOpVie in $cs2RechnungenResponse/ns2:Cs2DebitorOpVie
         return
         <ns0:debitorRechnung>
              <ns1:peid>0</ns1:peid>
              <ns1:rechnungsnummer>{ data($Cs2DebitorOpVie/ns2:f40Belnr) }</ns1:rechnungsnummer>
              <ns1:rechnungsdatum>{ xs:date(fn-bea:remove-timezone-from-dateTime(data($Cs2DebitorOpVie/ns2:f40Fadat))) }</ns1:rechnungsdatum>
              <ns1:faelligAm>{ xs:date(fn-bea:remove-timezone-from-dateTime(data($Cs2DebitorOpVie/ns2:f40Valut))) }</ns1:faelligAm>
         <ns1:behoerde>{ data($Cs2DebitorOpVie/ns2:AMT_BEZEICHNUNG) }</ns1:behoerde>
         <ns1:positionList>
              <ns1:position>
                   <ns1:positionsnummer>1</ns1:positionsnummer>
                                                 <ns1:betrag>{ data($Cs2DebitorOpVie/ns2:f40Dmbet) }</ns1:betrag>
                                                 <ns1:waehrung>
                                                      <ns1:isoCode>CHF</ns1:isoCode>
                                                      <ns1:bezeichnung>Schweizer Franken</ns1:bezeichnung>
                                                 </ns1:waehrung>
              </ns1:position>
              </ns1:positionList>
         <ns1:status>offen</ns1:status>
              if ($Cs2DebitorOpVie/ns2:f40Mahns/text() > "") then
                   <ns1:mahnstufe>{ xs:int(data($Cs2DebitorOpVie/ns2:f40Mahns)) }</ns1:mahnstufe>
              else ()
         </ns0:debitorRechnung>
         </ns0:debitorRechnungList>
         else ()
    <ns0:resultatStatus>
         <ns3:code>Erfolgreich</ns3:code>
         <ns3:beschreibung>Rechnungen aus MFK fehlen</ns3:beschreibung>
    </ns0:resultatStatus>     
    </ns0:getDebitorRechnungenResponse>
    declare variable $cs2RechnungenResponse as element(ns2:cs2RechnungenResponse) external;
    xf:CARI_CS_2DBAdpter_to_RechnungsServiceGetOffenePosten_v1_0($cs2RechnungenResponse)
    _3. this should result in this response, but it doesn't_
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soap-env:Body xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    <v1:getDebitorRechnungenResponse schemaVersion="0.6" xmlns:v1="http://www.llv.li/fin/services/rechnungService/v1">
    <v1:debitorRechnungList>
    <v1:debitorRechnung>
    <v11:peid xmlns:v11="http://www.llv.li/fin/types/v1">333</v11:peid>
    <v11:rechnungsnummer xmlns:v11="http://www.llv.li/fin/types/v1">555</v11:rechnungsnummer>
    <v11:rechnungsdatum xmlns:v11="http://www.llv.li/fin/types/v1">2011-05-05</v11:rechnungsdatum>
    <v11:faelligAm xmlns:v11="http://www.llv.li/fin/types/v1">2011-05-05</v11:faelligAm>
    <v11:behoerde xmlns:v11="http://www.llv.li/fin/types/v1">Amt für Gesundheit</v11:behoerde>
    <v11:positionList xmlns:v11="http://www.llv.li/fin/types/v1">
    <v11:position>
    <v11:positionsnummer>1</v11:positionsnummer>
    <v11:betrag>100</v11:betrag>
    <v11:waehrung>
    <v11:isoCode>CHF</v11:isoCode>
    <v11:bezeichnung>Schweizer Franken</v11:bezeichnung>
    </v11:waehrung>
    </v11:position>
    </v11:positionList>
    <v11:status xmlns:v11="http://www.llv.li/fin/types/v1">offen</v11:status>
    </v1:debitorRechnung>
    </v1:debitorRechnungList>
    <v1:resultatStatus>
    <v11:code xmlns:v11="http://www.llv.li/common/types/v1">Erfolgreich</v11:code>
    <v11:beschreibung xmlns:v11="http://www.llv.li/common/types/v1">Rechnungen aus MFK fehlen</v11:beschreibung>
    </v1:resultatStatus>
    </v1:getDebitorRechnungenResponse>
    </soap-env:Body>
    </soapenv:Envelope>
    But I do not get this expectet result, all I get is the BEA-382513: OSB Replace action failed: bad value for type element anyType?
    Any help would be appreciated.
    Thanks
    Best regards
    rk

    cs2RechungungenResponse or cs2RechnungenResponse ? the error message says cs2RechungungenResponse, but the actual element is cs2RechnungenResponse (one less "u")

  • OSB replace action failed..

    very urgent help needed.
    Scenario:
    1. My proxy service (new wsdl based) calls business (legacy wsdl based).
    2. I want to transform input format from new format schema to legacy format schema.
    3. I write a Xquery and Replace ./* in variable body with Xquery. Binding variable is accepted as $body.
    4. Individually tested, works like a charm; but when proxy is exected-throws following error:
    BEA-382513: OSB Replace action failed updating variable "body": line 29, column 1: {err}XP0006: "element {http://schemas.xmlsoap.org/soap/envelope/}Body { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type element {http://myURL}SwapnilRequest { {http://www.w3.org/2001/XMLSchema}anyType }
    here myURL is namespace defined for input format "SwapnilRequest".
    In short, the content of variable "body" are not changed even after transformation.
    Please help.
    Thanks and Regards,
    Swapnil Kharwadkar.

    Dear Eric,
    Following is Xquery:
    (:: pragma bea:global-element-parameter parameter="$aMA_UpdateRQ1" element="ns0:AMA_UpdateRQ" location="AMA_UpdateRQ.xsd" ::)
    (:: pragma bea:schema-type-return type="ns1:ListOfAyLoyMemberPortalProspectTopElmt" location="AY%20LOY%20Member%20Portal%20Prospect_blore.wsdl" ::)
    declare namespace ay = "http://www.siebel.com/xml/AYRES%20Member%20Information%20–%20Long%20Portal";
    declare namespace com = "http://com.finnair";
    declare namespace asi = "http://siebel.com/asi/";
    declare namespace xf = "http://tempuri.org/GetNewCard_WithSiebel_XQuery/A_getProfile_Xquery/newResponse/";
    declare namespace pros="http://com.finnair/prospectProcessing/";
    declare function xf:A_blore_QueryByExample_Request($AMA_UpdateRQ as element(com:AMA_UpdateRQ))
    as element(asi:ListOfAyLoyMemberPortalProspectTopElmt) {
    let $AMA_UpdateRQ := $AMA_UpdateRQ
    return
    <asi:ListOfAyLoyMemberPortalProspectTopElmt>
    <ay:ListOfAyLoyMemberPortalProspect>
    <ay:Contact>
    <ay:Id>{ data($AMA_UpdateRQ/com:UniqueID/@ID) }</ay:Id>
    <ay:ContactId>{ data($AMA_UpdateRQ/com:UniqueID/@ID) }</ay:ContactId>
    </ay:Contact>
    </ay:ListOfAyLoyMemberPortalProspect>
    </asi:ListOfAyLoyMemberPortalProspectTopElmt>
    declare variable $AMA_UpdateRQ as element() external;
    xf:A_blore_QueryByExample_Request($AMA_UpdateRQ)

  • OSB Validate action failed validation

    Hi All,
    I'm trying to convert non-xml to xml by using XqueryTransformation source as an HL7 and target as an CCD schema.When validating the against the schema I got the following exception.
    Please provide any suggestions.
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-382505</con:errorCode>
    <con:reason>OSB Validate action failed validation</con:reason>
    <con:details>
    <con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
    <con1:message>
    string value '' does not match pattern for cs in namespace urn:hl7-org:v3
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    <con1:message>
    Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
    </con1:message>
    <con1:xmlLocation>
    <ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
    </con1:xmlLocation>
    </con1:ValidationFailureDetail>
    </con:details>
    Thanks
    Mani

    Hi Anuj,
    I tried doing that but in Response, it is echoing back the request after the statement:
    The invocation resulted in an error: .
    And now it shows:
    Stage Error Handler
    $fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-382505</con:errorCode>
    <con:reason>OSB Validate action failed validation</con:reason>
    <con:details>
    <con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
    <con1:message>
    string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
    </con1:message>
    <con1:xmlLocation>
    <abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
    </con1:xmlLocation>
    </con1:ValidationFailureDetail>
    </con:details>
    <con:location>
    <con:node>PipelinePairNode1</con:node>
    <con:pipeline>PipelinePairNode1_request</con:pipeline>
    <con:stage>request xml validation</con:stage>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    System Error Handler
    $fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>402</con:errorCode>
    <con:reason>
    Validation Failed. Please enter proper values.
    </con:reason>
    <con:details>
    <con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
    <con1:message>
    string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
    </con1:message>
    <con1:xmlLocation>
    <abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
    </con1:xmlLocation>
    </con1:ValidationFailureDetail>
    </con:details>
    <con:location>
    <con:node>PipelinePairNode1</con:node>
    <con:pipeline>PipelinePairNode1_request</con:pipeline>
    <con:stage>request xml validation</con:stage>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    Is there any way by which only the customized error can be seen & not the OSB errors?

  • OSB Assign Action

    Hi:
    I have created a service in OSB, which has two Business service and a proxy service.
    One Business service uses JCA Binding which gets the value from DataBase and another Business service posts data into a queue.
    In my proxy service message flow, i am using these two business Service by means of service callout.
    Firstly the business Service with JCA binding is invoked and the output from it will be like
    <get:SampleCollection      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:get="http://xmlns.oracle.com/pcbpel/adapter/db/top/Get_Sample">
         <get:Sample>
         <get:type>Testing</get:type>
         <get:status>Success</get:status>
         <get:mailto>[email protected]</get:mailto>
         <get:cc>[email protected]</get:cc>
         <get:bcc>[email protected]</get:bcc>
         </get:Sample>
         </get:SampleCollection>
    And i have assigned it to a variable called DBOutput in ServiceCallout.
    Now to my second business service, some input need to be taken from the output of my first business service, so i am trying to use the below expression to get the values from DBOutput variable and assign to a variable called TestingDBVariable
    $DBOutput/*:SampleCollection/*:Sample/*:mailto/text()
    But after testing the proxyservice, variable "TestingDBVariable" itself is not reflecting, am i missing something here?
    OSB: 11.1.1.4
    Regards,
    RK

    You should investigate it at two levels:
    1. Check if your business service is indeed returning the "mailto" field properly. To verify this test the business service directly from sbconsole. If business service is not returning the mailto value then it may be because table metadata was changed after you created the JCA DB Adapter. Try creating it again and updating business service.
    2. If your business service is indeed returning the "mailto" field then there is some problem with mapping of the field while populating request for second business service. Try $DBOutput//*:mailto/text() once instead of whole XPath. Depending on how you have assigned the output of first BS to the variable, one of the following should be the right Xpath:
    $DBOutput/*:SampleCollection/*:Sample/*:mailto/text()
    or
    $DBOutput/*:Sample/*:mailto/text()

  • OSB Validate action fails even an element is nillable="true"

    Hi,
    I have declared two elements in my inline schema nillable="true":
    <xsd:element name="Skip_CreditChk" nillable="true" type="xsd:boolean" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="Observation_End_Date" nillable="true" type="xsd:date" minOccurs="0" maxOccurs="1"/>
    In my OSB message flow, my first action is a Validate action.
    When I test the proxy service in the OSB Console and input the following elements I encounter an OSB validate action failed error even when those fields below are declared as nillable in the schema. Anyone got an idea regarding this issue?
    <Skip_CreditChk/>
    <Observation_End_Date/>

    Please check W3C recommendation -
    http://www.w3.org/TR/xmlschema-0/ (section 2.9 Nil Values)
    Your input should be like -
    <Skip_CreditChk xsi:nil="true"></Skip_CreditChk>
    <Observation_End_Date xsi:nil="true"></Observation_End_Date>
    Regards,
    Anuj

  • OSB- BEA-380000 - com.bea.wli.sb.pipeline.PipelineException in OSB 11.1

    Hi,
      My test case is a simple one. JMS Proxy (Publish with QOS- exactly once) --> http Proxy (Publish with QOS- Best Effort)--> http BS. Am getting a BEA-380000 - com.bea.wli.sb.pipeline.PipelineException error while testing from JMS proxy in test console. However, the test is successful while testing from http Proxy.
    I saw one of the threads OSB - BEA-380000 - com.bea.wli.sb.pipeline.PipelineException   but it didn't solve my issue.
    Please advise if anyone has a solution.
    Thanks,
    Nikhil

    Hi All,
    I found these are the observations when ever this error occured.
    1) name space issue, un used namspaces are giving conflict, two namespaces with different uri's, out of which one is no more required, that will give problem.
    2) Copying any stage from route node to the other stages ( it will add few extra namespaces).
    3) Using un-reachable variables in the failed stage.
    Thanks.
    Edited by: user12679330 on 07-Oct-2011 02:19

  • Bea-inlinedxml + OSB 11.1.1.7

    Hi-
    Looks like bea-inlinedxml() is not working as expected on 11.1.1.7
    I used to use bea-inlinedxml() to return a CDATA into a XML node but now OSB is returning it empty.
    OSB 11.1.1.7 ChangeLog shows:
    +13902323 - The bea-inlinedxml() function trims whitespace when parsing text to XML+
    Assign Activity Produces an Empty Message Body if a New Line Character Exists
    Bug: 16205232
    Added: 07-March-2013
    Platform: All
    The resulting message body is empty if a proxy service processes an XML string with a newline character after the XML declaration (<?xml version="1.0" encoding="UTF-8"?>), the message flow includes an Assign activity that uses fn-bea:inlinedXML() to assign that XML string to a variable, and the message flow uses the variable to replace the contents of $body. This is related to issue 13902323, caused by the fn-bea:inlinedxml() function trimming whitespace when parsing text to XML.
    Maybe this fix broke inlinedXML behavior??
    Please help.

    Hi,
    We are also facing the same issue. Do we have any suggested patch from Oracle yet ?
    In the mean time, we have worked around the issue by doing the following
    <soap-env:Body>{fn-bea:inlinedXML($xmlParseResult)}</soap-env:Body>
    regards.

  • OSB/RMAN to tape it's failed (hang)

    We are trying to backup ODA RAC database to SL150 tape library, backup hangs with no errors. Oracle support was trying to solve the problem with no luck. any help please:
    n summary:
    OSB/RMAN to disk it's OK
    OSB/RMAN to fake tape it's OK
    OSB/filesystem to tape it's OK
    OSB/RMAN to tape it's failed (hang)
    we have checked permission devices, RMAN parameters all seems to be ok.

    There's not enough information here to begin. Please supply full "obtool lsdev -lvg" output and also the full log files from the jobs.
    Thanks
    Rich

  • How to use one Assign action to create multiple context variables

    Hello, everyone.
    I read some tips from Oracle documentation that said:
    Avoid creating many OSB context variables that are used just once within another XQuery
    Context variables created using an Assign action are converted to XmlBeans and then reverted to the native XQuery format for the next XQuery. Multiple "Assign" actions can be collapsed into a single Assign action using a FLWOR expression. Intermediate values can be created using "let" statements. Avoiding redundant context variable creation eliminates overheads associated with internal data format conversions. This benefit has to be balanced against visibility of the code and reuse of the variables.
    Oracle® Fusion Middleware Performance and Tuning Guide
    +11g Release 1 (11.1.1)+
    Part Number E10108-03
    But I don't know how to do that. Can you show me ?
    Thank in advance
    Edited by: Doubt_Man on Aug 17, 2011 3:30 PM

    if you return sequences, you can declare the return type of your xquery as xs:double*
    (notice the asterix at the end)
    but I have the impression that in the assign action only the first element will be assigned to the context variable
    (correct me if I am wrong)
    So in fact you might indeed have to transform the sequence into a element()*, or concatenate it into a CVS string - for instance using string-join
    http://www.xqueryfunctions.com/xq/fn_string-join.html

Maybe you are looking for

  • Safari 5.1.2 not working with USPS Click-N-Ship Label Printing

    I use the USPS Click-N-Ship for printing postage labels. Prior to this update the behavior was: I'd enter the label information, check out and click the print button. The labels would be generated and downloaded to my downloads folder and Preview wou

  • Problem in credit control area

    Hi Gurus, We  have configured credit control area using Static Credit check. We have assigned the same to order type and delivery type also. While creating sales order, even though the total value is crossing the credit limit which is set in FD32. th

  • Sleep issues

    My mac mini sleeps when I turn off my TV though it's preferences are set to not sleep. How can I change this, what com.plist do I have to delete? This is something new that just started on Monday. I swear the thing has a mind of it's own. I would lik

  • Need help for connecting Ms Acces with java Swing in Mac OS

    Hi all, i need to connect to Ms Access in MAc os through my java swing program. Is it possible for accessing Ms access through dsn in Mac OS. If Possible which driver shall i use for Establishing Connection with MS Access in Mac OS. Suggestion is nee

  • Trouble activating OIAACCGI structure in upgrade process, fields repeated

    Hi community, I'm working in an upgrade process from 4.6 to ECC 6 versions. In the activation step some errors have arisen and many of that have been solved but still there is an error with the OIAACCGI structure. the trouble is that this structure h