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

Similar Messages

  • 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.

  • Urgent - please help with osb-service bus schema validation.

    I have a proxyService runing on osb service bus, when I send wrong input to my proxyservices it react correctly by rejecting it, becuase the requestion is not conform to the schema, but I only get the error message saying that
    the Input is does not much, is there a way to get more info about the error ?
    like witch fields that cause the error ?

    The fault variable in your stage error handler will have the approariate information. Just add a stage error handler in the stage you are doing schema validation (make sure that in validate action you are selecting "raise Error on validation failure") and the error handler log the $fault
    Also refer -
    Re: Validate each xml element against XML schema
    Regards,
    Anuj

  • OSB: strict xsd validation

    Hi guys,
    I'm trying to validate an XML inside the OSB with this schema:
    <xsd:complexType name="GenericMessage">
    <xsd:sequence>
    <xsd:element name="generic_header" type="gm:GenericHeader">
    </xsd:element>
    <xsd:any maxOccurs="unbounded">
    </xsd:any>
    </xsd:sequence>
    </xsd:complexType>
    and the message:
    xmlns:doc="http://www.namespaces.com/schema/Document/v1"
    <gm:generic_header>
    </gm:generic_header>
    <doc:document>
    </doc:document >
    I can validate this message with the Oracle Workshop but when I send it to the OSB I always get this error:
    Element not allowed (strict wildcard, and no definition found): document@http://www.namespaces.com/schema/Document/v1
    I thought that maybe it weren't finding the schemaLocation so I tried to add it as a relative and/or absolute url:
    schemaLocation=” http://www.namespaces.com/schema/Document/v1 http://localhost:7010/sbresource?SCHEMA/...../Document” (this address works in a browser)
    But it didn't work either.
    Do you know if there is a bug or what I'm doing wrong?
    PS: I can't change the strict any element to a lax one.
    Thank you!
    Edited by: user10791025 on 21-oct-2011 2:46

    Hi ,
    As u said after take off <xsd:any> its working fine....
    Is tat xsd is valid one..????
    If ur using validate action it check and validate your input payload against the xsd ..let say for ex: xsd element excepts Boolean value but while testing the proxy input payload if we gave 13123 (numeric value) it through error..
    if it troughs error while validating in OSB server ..something wrong with validate action elements .
    Chck xpath------xsd element
    In variable --body
    against resouce ----xsd element or wsdl elemnt

  • OSB: Payload validation required for empty elements inside OSB process.

    Hello
    I need to validate the payload for non-empty elements. If the payload is completely empty then OSB should throw an error that the submitted payload is empty.
    If the payload contains at least one element then it should pass through.
    As in process to test this particular one, i have tried with the following code to generally validate for an element.
    xquery version "1.0" encoding "Cp1252";
    (:: pragma bea:global-element-parameter parameter="$inputParameters1" element="ns0:InputParameters" location="../adapter/StoreProcDB/xsd/StoreProcDBService_sp.xsd" ::)
    (:: pragma bea:schema-type-return type="ns1:Validation" location="../xsd/validation.xsd" ::)
    declare namespace xf = "http://tempuri.org/StoreProc_osb/transformation/PayloadValidation/";
    declare namespace ns1 = "http://www.sigmainfo.com/validation";
    declare namespace ns0 = "http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService";
    declare function xf:PayloadValidation($inputParameters1 as element(ns0:InputParameters))
    as element()
    <ns1:Validation>
              <ns1:Payload>{$inputParameters1/.}</ns1:Payload>
              <ns1:ValidationErrorList>
                   (: BEGIN - Required Field Validations :)
              (:     if (empty($inputParameters1/ns0:ACCOUNTNUMBER/text())) then
                        <ns1:ValidationError>
                             <ns1:code>1</ns1:code>
                             <ns1:message>ACCOUNTNUMBER: Required Field</ns1:message>
                        </ns1:ValidationError> :)
                   if (empty($inputParameters1/ns0:AUDITUSER/text())) then
                        <ns1:ValidationError>
                             <ns1:code>1</ns1:code>
                             <ns1:message>AUDITUSER: Required Field</ns1:message>
                        </ns1:ValidationError>
                   else ''
                   (: END - Required Field Validations :)
    </ns1:ValidationErrorList>
         </ns1:Validation>
    declare variable $inputParameters1 as element(ns0:InputParameters) external;
    xf:PayloadValidation($inputParameters1)
    But it throws the following error:
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    REQUEST DOCUMENT:
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    <soapenv:Body>
    <stor:InputParameters
    xmlns:stor="http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService">
    <!--Optional:-->
    <stor:P_ACCOUNTNUMBER>00101</stor:P_ACCOUNTNUMBER>
    <!--Optional:-->
    <stor:P_AUDITUSER>venkat</stor:P_AUDITUSER>
    </stor:InputParameters>
    </soapenv:Body>
    </soapenv:Envelope>
    RESPONSE DOCUMENT:
    The invocation resulted in an error: . <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-382505: OSB Validate action failed validation</faultstring><detail><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>
    Incompatible elements: expected an XML instance of name "{http://xmlns.oracle.com/pcbpel/adapter/db/sp/StoreProcDBService}InputParameters", but found an XML instance of name "{http://schemas.xmlsoap.org/soap/envelope/}Body".
    </con1:message>
    <con1:xmlLocation/>
    </con1:ValidationFailureDetail>
    </con:details>
    <con:location>
    <con:node>PipelinePairNode1</con:node>
    <con:pipeline>PipelinePairNode1_request</con:pipeline>
    <con:stage>stage1</con:stage>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    </detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    But this is not the way it should be done as i progress.
    Please suggest a simple way to have a pragma with sample and complete validation for the input payload.
    Appreciate your help in advance
    Regards
    Venkat

    Venkat,
    Find below url's for implementing security policies in OSB
    http://docs.oracle.com/cd/E17904_01/doc.1111/e15866/owsm.htm#CHDEEGJI
    http://docs.oracle.com/cd/E17904_01/doc.1111/e15866/owsm.htm#CHDBIJHD
    http://niallcblogs.blogspot.in/2010/07/osb-11g-and-wsm.html
    http://biemond.blogspot.in/2009/06/ws-security-in-osb.html
    Regards,
    Abhinav

  • OSB: xs:base64 and MTOM - validation

    Hi,
    I have a xs:base64 that I would like to transfer on OSB using MTOM with include binary data by reference.
    I'm required to walidate the response before sending.
    Now the problem is, I get the schema validation error on this element. It says "did not expect the ctx:binary-content" in my xs:base64 element.
    Help please?

    It is very simple and the thread you are referring to describes that in full detail - just use Java Callout with javax.activation.DataSource as a return value. In Java Callout, you assign return value (your binary data) to a new OSB variable. Then use Replace action to put your variable into any other variable.

  • Validation of SOA Suite / OSB / SAP Adapter install

    We will be doing a clustered install of SOA Suite 11g, OSB and the SAP Adapter at a customer next week.
    I was wondering if anyone has any validation scripts/tests that I might use to test basic functionality and connectivity after the install.
    When we deployed into DEV (a single node) environment, we wrote a simple HelloWorld test. I thought I'd check here to see if anyone has something they use to validate their installs.
    We will be installing SOA Suite 11gPS2, OSB 11g and the SAP Adapter (PS1) into SOA Suite. The OS is RedHat Linux 5.5.
    If there is a better place for me to ask this question, please direct me there.
    Thanks,
    Mike

    Hi,
    When I checked the diagnostic logs I can see the following type of messages:
    [2012-02-08T13:33:35.702+00:00] [osb_server2] [TRACE] [] [] [tid: [STUCK].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <WLS Kernel>] [ecid: 0000JLS^rAUEoI05nzk3yZ1FC_AW000002,0] [SRC_CLASS: org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor] [APP: JCA Transport Provider] [dcid: 49e003eb77940676:13e96fa:1355c9322e6:-7fd8-0000000000000002] [SRC_METHOD: basicExecuteCall] SELECT Batch_Date, Update_Flag FROM dbo.amr_temp_update
    Is there any problem because of which the thread is getting stuck. Is there any parameter for the DB adapter which can be changed to fix this problem.
    Thanks,
    Sanjay

  • 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?

  • Validation failed for ArchiveClassLoaderDerivedType- Java callouts from OSB

    Even though jar file for java classes are present, I am receiving the following error sometimes:
    com.bea.wli.config.component.NotFoundException: Validation failed for ArchiveClassLoaderDerivedType ..Referenced component (ArchiveClassLoaderDerivedType ../../Java/.._ArchiveClassLoaderDerivedType) not found.
    When I bounce the server then it works, but I can't bounce the server in production. Do anybody know why this is happening?

    Unfortunately ALSB/OSB does not seem to honour JAR files packaged in your JAR and referenced by the manifest Class-Path attribute. As well, the JAR files deployed into a project cannot reference each other. As such, you either have to open the library JAR and stick it into the one you are deploying or to put it on the server classpath via the domain lib (you do not need to edit the start scripts). This is definitely a hole in the capabilities of OSB.

  • XML Schema dependencies is not valid in osb 11g version

    Hi,
    I'm working in osb 11.1.1.5 version.I have to import the 10g project in 11g server, but in my 10g project some schemas are included in another schemas.When i'm trying to export the resources in the 10g console and importing it in the 11g console i'm getting the errors. XML Schema dependencies is not valid in osb 11g version.Is there any alternative to import the 10g project in 11g in this case?Please suggest.
    Thanks in advance!

    while running the proxy in the eclipse i'm getting the error
    servicebus:/XMLSchema/HistoricLoadService/Schemas/CCD/datatypes-base:998:2: error: derivation-ok-restriction.5.3a: A type with a mixed content model can only restrict another type with a mixed content model. at poc_ccd.xsd
    When i'm trying to export the project from 10g console and importing it from osb 11g console I'm getting the conflicts like
    servicebus:/XMLSchema/HistoricLoadService/Schemas/CCD/datatypes-base:289:2: error: derivation-ok-restriction.5.3: Must be a valid restriction.
    Resource XMLSchema HistoricLoadService/Schemas/CCD/ poc_ccd forms a cyclic reference

  • [OSB] SOAP Validation

    Hello,
    I have a proxy with service type "Any SOAP". Is there a way to validate the SOAP request?
    For example:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:op="http://www.op.org/">
    <soapenv:Header/>
    <soapenv:Body>
    <op:baja>
    <op:id>2231</op:id>
    </op:baja_ERROR>
    </soapenv:Body>
    </soapenv:Envelope>
    or with wrong/inexistent namespace
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:op="http://www.op.org/">
    <soapenv:Header/>
    <soapenv:Body>
    <op:baja>
    <opINEXISTENT:id>2231</opINEXISTENT:id>
    </op:baja>
    </soapenv:Body>
    </soapenv:Envelope>
    or without Body:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:op="http://www.op.org/">
    <soapenv:Header/>
    </soapenv:Envelope>
    is possible check this?
    Thanks.

    There is no out of the box way to do that. However you can try following:
    Instead of defining a Any SOAP type service, create a dummy WSDL with AnyType request and response. In the Proxy Service configuration enable the WS-I compliance checkmark and it will validate the structure of SOAP Envelope for you.
    The problem is that WS-I compliance is available for only WSDL based web services hence you will need the workaround.
    You can find more details here:
    http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1076699

  • How to get invalid message in OSB?

    Hi,
    I have OSB Proxy Service which reads XML messages from JMS Queue.
    Is it possible to handle non xml bad messages in my proxy service ? I want to get them, write into log
    and put it another queue which contains all buggy messages? I use validate, but non XML messages don't fall
    into my Proxy Service from JMS, and stay in jms queue.

    Create the messaging type proxy service with input type as "Text" to read messages from JMS queue. Then in it's message flow route the message to your existing proxy. In the route node of first proxy put an error handler and add a check for XML validation failure. From inside the error handler call a business service which will put that message into buggy queue. You may also log the message in error handler.
    Regards,
    Anuj

  • OSB Global settings corrupt

    When I create a simple proxy service containing only one report task I get the following error:
    java.lang.IllegalStateException: com.bea.wli.config.component.NotFoundException: Validation failed for Operations System/Operator Settings/GlobalOperationalSettings: Referenced component (Operations System/Operator Settings/GlobalOperationalSettings) not found.
    at com.bea.wli.sb.resources.globaloperations.GlobalOperationsRepository.isDomainReportingEnabled(GlobalOperationsRepository.java:123)
    at stages.logging.runtime.ReportRuntimeStep.processMessage(ReportRuntimeStep.java:68)
    When I did some research I found out the Global settings of the OSB are not working anymore. When I open that page in the OSB Console I get the same (kind of) error. Futhermore I found out that the file /apps/bea/domains/<MYDOMAIN>/osb/config/core/System/Operator Settings/GlobalOperationalSettings.xml was missing in my domain. But how did this happen?
    Placing a copy of this file back does not seem to make any difference. It still cannot find anything.
    A thing to notice is I have two OSBs (AdminServers) running on one Linux Machine. Both of them in a different domain with their own oracle XE Database Schema for reporting. One of the OSBs is working and one is not working. But I cannot think of a reason why this would cause a problem.
    Does anyone know what to do?

    Hi there!
    Add this to the import.py script
              operationMap = alsbImportPlan.getOperations()
              # We want to avoid to delete the GlobalOperationalSettings which the JAR packaged using the
              # ant tasks seem to automatically do.
              # So we go look for the 'System/Operator Settings/GlobalOperationalSettings' reference
              # in the operations map
              globalOp = findRefInOperationMap(operationMap, 'System/Operator Settings/GlobalOperationalSettings')
              if (globalOp != None):
                   print 'Removing delete operation on the GlobalOperationalSettings'
                   alsbImportPlan.removeOperation(globalOp)
    Just after
              # Getting the default import plan from the upload jar file
              alsbJarInfo = ALSBConfigurationMBean.getImportJarInfo()
              alsbImportPlan = alsbJarInfo.getDefaultImportPlan()
    Regards,
    Knut

  • JCA Error while calling Stored Procedure containing cursors in BPEL/OSB

    Hi,
    I created JCA DBAdapter in Jdeveloper for calling remote stored procedure which contains cursors as OUT parameters.
    I'm getting below exception when i try to call the database via BPEL/OSB.the same remote procedure call is working on Invoking with WLI .
    Kindly sugggest !!!
    The invocation resulted in an error: I*nvoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/ServiceBus/BusinessServices/IsdnSiebelConn [ IsdnSiebelConn_ptt::IsdnSiebelConn(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'IsdnSiebelConn' failed due to: Get object error.*
    Error retrieving the value of a parameter R_NON_CNF_ATTR_CURSOR.
    An error occurred when retrieving the value of parameter R_NON_CNF_ATTR_CURSOR after invoking the SIEBEL.ISDN_OBT_INS_DET.OBTAINASSETDETAILS API. Cause: java.sql.SQLException: Cursor is closed.
    *; nested exception is:*
    BINDING.JCA-11810
    Get object error.
    Error retrieving the value of a parameter R_NON_CNF_ATTR_CURSOR.
    An error occurred when retrieving the value of parameter R_NON_CNF_ATTR_CURSOR after invoking the SIEBEL.ISDN_OBT_INS_DET.OBTAINASSETDETAILS API. Cause: java.sql.SQLException: Cursor is closed.
    Check to ensure that the parameter has been correctly registered as a valid IN/OUT or OUT parameter of the API. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/ServiceBus/BusinessServices/IsdnSiebelConn [ IsdnSiebelConn_ptt::IsdnSiebelConn(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'IsdnSiebelConn' failed due to: Get object error.
    Error retrieving the value of a parameter R_NON_CNF_ATTR_CURSOR.
    An error occurred when retrieving the value of parameter R_NON_CNF_ATTR_CURSOR after invoking the SIEBEL.ISDN_OBT_INS_DET.OBTAINASSETDETAILS API. Cause: java.sql.SQLException: Cursor is closed.
    ; nested exception is:
    BINDING.JCA-11810
    Get object error.
    Error retrieving the value of a parameter R_NON_CNF_ATTR_CURSOR.
    An error occurred when retrieving the value of parameter R_NON_CNF_ATTR_CURSOR after invoking the SIEBEL.ISDN_OBT_INS_DET.OBTAINASSETDETAILS API. Cause: java.sql.SQLException: Cursor is closed.
    Check to ensure that the parameter has been correctly registered as a valid IN/OUT or OUT parameter of the API. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers.
    at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
    at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
    at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:571)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
    at $Proxy127.sendMessageAsync(Unknown Source)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:603)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:538)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:558)
    at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:426)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:377)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
    at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
    at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
    at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
    at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
    at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
    at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
    at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
    at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
    at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
    at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
    at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    You need to open all the cursors in the PLSQL ie., cursors should be initialized in your PLSQL package. JCA DB Adapter tries to open the cursor without checking whether its there or not..If you cant change the PLSQL package, raise a SR with Oracle for a patch.This would be considered as Enhancement Request.
    Regards
    Sesha

  • Consuming URL renames XSD and WSDL files in OSB

    We try to define a proxy service in the OSB 11g by consuming an URL.
    We have all our WSDLs, XSDs etc online available, that is references like import of include in a WSDL uses URLs to identify other WSDLs or XSDs. In fact a webservice has a concrete WSDL which imports an abstract WSDL. The abstract WSDL imports XSD's. The XSD's file can import another XSD's as well. It is more or less a tree structure of XML documents.
    When we try to define a proxy or business service on the concrete WSDL in Eclipse by consuming the URL ending on ?wsdl, all meaningfull names of XSD's are replaced by generated names i.e. common.xsd becomes xml_1233.xsd. And all URL references are replaced by file references. The depencency tree is preserved, everthing is still valid however the names are no longer human readable.
    Is there any way to preserve the filenames of XML documents?
    With kinds regards,
    Jornica

    Hi Anuj,
    I followed this link to create the MDS connection and local MDS repository, should I create an empty composite project and place the
    zip file of my xsd's in this and bundle that in to an MAR file? Are there any documents that talks about MAR creation?
    Thanks,
    Jai.

Maybe you are looking for

  • I want to always be able to page down using space bar, but some web pages seem to disable this.

    I often use the space bar to page down in web pages rather than scrolling with the mouse or arrow keys, but in the last few months I've encountered a number of pages that don't seem to allow this browser feature to work. For instance, space bar doesn

  • New Hard Drive Woes!

    I replaced the 500 GB optical hd in my macbook pro with a 1TB SSD after the optical drive crapped out. I put in the startup disc and went through the steps twice using my TimeCapsule to restoremy settings and files. But both times my login password w

  • Add event cases to an event structure using scripting

    Hello, Iam trying to (using scripting) update an event structure (add event cases) on a vi that is not on memory. i get error 1054 The specified object was not found. here is a picture of it. any help in this will be greatly apreaciated. Solved! Go t

  • Thre was a problem when installing InDesign CC

    Getting below error when installing inDesign CC "Installation Failed "  Unable to Extract to temp library.  Pls contact customer support |(EX11)

  • DM Is Not Responding

    I have DM 5.0, and am running Windows 7 OS on my laptop. I cannot get my DM to run properly. I have uninstalled & reinstalled it twice with no luck. It boots up properly, and asks for my device password (8900 running 5.0 OS). Once I enter it, the DM