Ignoring namespace in OSB validation action

Hi,
I want my namespace to be ignored while doing validation of my XML against an XSD, by default OSB does not allow us to do this, is their a way around?

Unfortunately XMLs are strongly defined with namespaces. If your schema has a nmespace then validation will also include namespace validation and without it traversing through the XML document will also not be possible even for the validation engine.
Alternative is to define a duplicate schema without a namespace and validate against it.
If a different namespace coming in the XML document then write a simple XQuery to remove namespace before validation, do the validation against the duplicate schema. But this approach is just a work around and heavy on performance so its not usually recommended. I suggest keeping the normal validation with namespace and asking the consumer applications to send XMLs with proper namespace. Validation are intended to keep such bad XML requests getting processed and it makes sense to have namespaces validated as well.

Similar Messages

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 Validate action problem with xs:short datatype

Hi,
In the XSD, intPayment is defined as xs:short.
We have the validate action in OSB proxy.
If we pass below, everything is fine : (correct)
<intPayment>96</intPayment>
If we pass below, OSB is throwing a validate error indicating fractional digits after decimal point. (correct)
<intPayment>96.01</intPayment>
But if we pass below, OSB validate action is not catching :
<intPayment>96.00</intPayment>
I am assuming that OSB validate action should throw an error that 96.00 is not a valid value. (xs:short restricts any fractional digits after decimal point).
Can you pl help me?
Thanks,
S
Edited by: user13058197 on Jan 13, 2011 10:29 AM
Edited by: user13058197 on Jan 13, 2011 12:16 PM

I am assuming that OSB validate action should throw an error that 96.00 is not a valid value. (xs:short restricts any fractional digits after decimal point). Your assumption is incorrect and OSB is working as designed (actually as per XML standard). Actually short datatype is derived from int, int is derived from long, long is derived from integer and integer is derived from decimal.
Definition of Integer (http://www.w3.org/TR/xmlschema-2/#integer) says -
[Definition:] integer is ·derived· from decimal by fixing the value of ·fractionDigits· to be 0and disallowing the trailing decimal point. This results in the standard mathematical concept of the integer numbers. The ·value space· of integer is the infinite set {...,-2,-1,0,1,2,...}. The ·base type· of integer is decimal. And hence xs:short accepts 96.00 but does not accept 96.01
Regards,
Anuj

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 : 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/">
     
     <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

OSB Validate action

As I have just started working in OSB, so my query is whether I can get a proper error message from OSB validate action against the particular attribute in an XML which is having the wrong input.
Example : Suppose in my XSD i have defined student's id as integer but in below XML it is coming with a string. So can I get the exact error message stating like attribute 'id' is having a wrong value and so validation failed.
<Class>
<student id="123"/>
</Class>
Please help.

The attribute level validation was done through java call out. Had to use sax parser for this..
here is the code :
public class XMLValidator {
static boolean success = true;
static private String errorMsg = "";
static String msg = "";
* @param xsdPath
* @param payload
* @return
public static String XMLValidator(String xsdPath, String payload) {
String status = "";
try {
System.out.println("XSD Path: " + xsdPath);
System.out.println("Payload: " + payload);
status = ValidateXML(new URL(xsdPath), payload);
} catch (MalformedURLException e) {
return (e.getMessage());
return (status);
public static String ValidateXML(URL xsdUrl, String xmlFile) {
success = true;
errorMsg = "";
SAXParser saxParser = new SAXParser();
saxParser.setValidationMode(XMLParser.SCHEMA_VALIDATION);
String xmlFilePayload = xmlFile;
XSDBuilder builder;
try {
builder = new XSDBuilder();
URL url = xsdUrl;
//System.out.println(url.getPath());
XMLSchema schemadoc = (XMLSchema)builder.build(url);
saxParser.setXMLSchema(schemadoc);
Validator handler = new Validator();
saxParser.setErrorHandler(handler);
// saxParser.parse(new FileInputStream(new File(xmlFilePayload)));
InputStream inputStream =
new ByteArrayInputStream(xmlFilePayload.getBytes("UTF-8"));
saxParser.parse(inputStream);
if (success) {
msg = "Successfully Validated";
} else {
/* writeLogFile(logFileName,
"[" + counter + "]. " + xmlFileName + "\n" +
"------------------------------------------------------------------------------------------------------\n" +
errorMsg + "\n\n\n", true);*/
msg = errorMsg;
} catch (XSDException f) {
System.out.println("XSDException : " + f.getMessage());
//System.out.println("XSDException : " + f.getMessage());
} catch (FileNotFoundException f) {
System.out.println("FileNotFoundException : " + f.getMessage());
} catch (SAXException f) {
System.out.println("SAXException : " + f.getMessage());
} catch (IOException f) {
System.out.println("IOException : " + f.getMessage());
catch (Exception f) {
System.out.println("IOException : " + f.getMessage());
return (msg);
public static class Validator implements ErrorHandler {
public void error(SAXParseException exception) {
success = false;
int separator = exception.getMessage().indexOf(")");
System.out.println("index "+separator);
String st = exception.getMessage().substring(separator+1);
errorMsg = errorMsg + "Error : " + st + "\n";
//System.out.println("error: " + exception.getMessage());
public void fatalError(SAXParseException exception) {
success = false;
errorMsg =
errorMsg + "Fatal Error : " + exception.getMessage() + "\n";
// System.out.println("fatalError: " + exception.getMessage());
public void warning(SAXParseException exception) {
success = false;
errorMsg = errorMsg + "Warning : " + exception.getMessage() + "\n";
//System.out.println("warning: " + exception.getMessage());
}

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")

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.

"There is no valid action to be performed" error message when using free-form approvals

Hi all,
I'm using free-form approval template with no owners and reviewers assigned, just security filters are applied on Entity dim.
I have started all entityes and they are in "First Pass" stauts. And now I'm not able to change status on a planning unit and I'm getting following error message:
There is no valid action that can be performed on the selected Planning Unit.
Why I'm not able to change status? Could anyone help me out of this?
BR
Vlado

when the user id created in solman was P0041, and hence the BP was created assigned to this ID.
at some stage of time, a request came to change delete P0041 and recreate as ALMA41 to maintain the standards.
but it was missed to change the P0041 in the BP to reflect ALMA41.
Daher Abdeen.

"AstService namespace is not valid" error when querying CCM 4.1 when Axis

Hi,
I'm trying to query a CCM with the Axis Java Soap API and I'm receiving a Fault response saying "AstService namespace is not valid"
I have tried with SAAJ API from Sun (similar to Axis) and it works fine.
What's wrong ?
Thanks
Seb

Could you trace the soap exchange and post it here? You obviously have a namespace issue.. also, the code how you set up your service endpoint might be of use, too. I have AXL working via AXIS (but I'm using handwritten XML since AXL just doesn't work without hacking WSDLs and I have better things to do than worry about breaking apps when installing a ccm patch) so we could compare the code.

WebDynpro Action Types : Validating vs Non Validating Action Types

Hi
Can someone tell me the difference between Validating and Non Validating Action Types in webdynpro. I read it through, but its not very clear.
regards
Saurabh

HI Maksim,
Thanx it helped !!
I need some more help. I have a PAR file which displays an employees CV in an IView. I want to print only the content in the iView (i.e the CV) not the complete page with Roles and worksets, is there some code that can do this.
I need to place a button on the CV (in the iView) and on the click of the button the CV (iView) gets printed.
A workaround for this is that I open the CV (from the iView Personalization ) in a new window and then from the File menu of the new window fire the Print option. But I dont want to do it this way.
I want to Print the CV from the parent window only.
Plz suggest !!
Regards
Saurabh

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

Replacing default namespace in OSB message flow

I'm in the process of setting up a simple OSB proxy and could use some help figuring out how to change a default namespace in the response from the business service.
The proxy and business service use different namespaces which we'll call "http://foo.com/namespace/proxy" and "http://foo.com/namespace/business". In my routing request message flow, the contents of $body look like this and I'm able to use a Rename action with XQuery expression "./sof:*" to change "http://foo.com/namespace/proxy" to "http://foo.com/namespace/business":
<sof:Execute xmlns:sof="http://foo.com/namespace/proxy">
<sof:adminName>MyAdaptor</sof:adminName>
<sof:request>
[escaped payload omitted]
</sof:request>
</sof:Execute>
This works fine, but in the response message flow, I need to revert the namespace and am having difficulty because the response uses a default namespace instead of using a prefix:
<ExecuteResponse xmlns="http://foo.com/namespace/business">
<ExecuteResult>
[escaped payload omitted]
</ExecuteResult>
</ExecuteResponse>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
Can anyone tell me what I'm doing wrong, or suggest a different approach? Assume that changing the calling application or business service is not an option.
Thanks!

>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
>
You pattern "./P2L:\*" matches just one element so it's ok that the payload's namespace wasn't touched. If you want to rename namespace for all elements try "//P2L:*". However, I'm not sure whether this is what you want. Try do describe what you do, what you want and what you get instead.
>
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
>
I think it's not a good approach to replace content of xmlns as this attribute is not a common xml attribute.

OSB: Validation

hi
OSB has by default provided validate action. It has syntax as "validate <xpath> in {variable} against {schema/wsdl}".
Can i decide at schema/wsdl at run time? This scenario is similar with that of using a dynamic xquery.
Regards,
Swapnil Kharwadkar

thanks,
first option is not available in this case because xml schemas are constantly being added to OSB project.
I tried second option, however performance was not very good.
after some experimenting, I implemented like this:
     public static String validate(XmlObject body, String schemaLocation) {
        try {
             //remove <xml-fragment>
             XmlOptions opts = new XmlOptions();
             opts.setSaveOuter();
             SchemaFactory sf = SchemaFactory.newInstance("http://www.w3.org/2001/XMLSchema");
            // Handle validation
            Schema schema = sf.newSchema(new URL(schemaLocation));
            Validator validator = schema.newValidator();
            validator.validate(new StreamSource(new StringReader(body.xmlText(opts))));
            return null;
        } catch (IOException ex) {
            return ex.getMessage();
        } catch (SAXException ex) {
            return ex.getMessage();
     }there is some type conversations, but I am not sure if there is better way

OSB - Publish action - Request action message enrich/ tranformation impact

Hi ,
Today I came across an analysis on how the performance of thread is impacted if we have these two scenarios.
1. A stage containing all the pre enrichment and validation and transformation to the input message to construct the request message for Publish action(to BS)
2. A Publish action - Request action - sub activities / actions containing the enrichment, validation and transformation to construct the request message from input message
An expert advice is expected to see if there is any significant impact in performance and thread analysis. This cal has to be made on entire implementation which has almost 70+ services.
Thanks for quick reply.

Enable tracing in osb console, and for debugging try adding routing options in publish node and change the quality of service to exactky once. You will then eb able to see the error.
Also if you do not require your ps2 to be accessed outside the jvm consider making the ps2 a local proxy service.

Ignoring namespace in OSB validation action

Similar Messages

Maybe you are looking for