Forum Stats

  • 3,768,005 Users
  • 2,252,739 Discussions
  • 7,874,407 Comments

Discussions

Categories

Oracle BPM 12c: URL Error/String Index Out of Range Creating Business Rules with Input

Ethan Pilot
Ethan Pilot Member Posts: 4
edited May 7, 2018 2:26PM in Business Process Management Suite

Hello Everyone
While attempting to create a business rule, every time I attempt to add inputs/outputs at time of creations, I encounter an unhandled error.  Even after wiping my project and starting over I still encountered this error and I was not able to find anything relevant online.
Is this perhaps a bug or just a configuration issue on my workstation?

Stack trace is below; in my log this same error was repeatedly emitted a number of times, perhaps form the software attempting the action a number of times after failure

if the any other details or the whole couple hundred line log would be helpful please let me know.

exception.code:36353exception.type: ERRORexception.severity: 2exception.name: URL error while reading XSD.exception.description: The data model failed to read the XSD businessCatalog/HelloTypes/HelloObject.xsd because of a URL error.exception.fix: Check the underlying exception and correct the error.  at oracle.bpel.services.rules.util.XSDGenerator.getLocalPart(XSDGenerator.java:847)  at oracle.bpel.services.rules.util.XSDGenerator.addSchemaImportToSchema(XSDGenerator.java:798)  at oracle.bpel.services.rules.util.XSDGenerator.addArgumentSequenceSchemaElement(XSDGenerator.java:718)  at oracle.bpel.services.rules.util.XSDGenerator.createParameterListElement(XSDGenerator.java:382)  at oracle.bpel.services.rules.util.XSDGenerator.createMessageElements(XSDGenerator.java:625)  at oracle.bpel.services.rules.util.XSDGenerator.createDecisionServiceTypesDocument(XSDGenerator.java:256)  at oracle.bpel.services.rules.util.XSDGenerator.createDecisionServiceMessageTypesFile(XSDGenerator.java:187)  at oracle.bpel.services.rules.util.WSDLGenerator.createTypes(WSDLGenerator.java:1334)  at oracle.bpel.services.rules.util.WSDLGenerator.createDefinition(WSDLGenerator.java:1154)  at oracle.bpel.services.rules.util.WSDLGenerator.createWSDL(WSDLGenerator.java:1003)  at oracle.bpel.services.rules.util.WSDLGenerator.createWSDLDefinitionForSCAComponent(WSDLGenerator.java:368)  at oracle.bpel.services.rules.util.DecisionServiceBuilder.createWSDLForService(DecisionServiceBuilder.java:1946)  at oracle.bpel.services.rules.util.DecisionServiceBuilder.createWSDLDoc(DecisionServiceBuilder.java:937)  at oracle.bpel.services.rules.util.DecisionServiceBuilder.createDecisionServiceComponent(DecisionServiceBuilder.java:910)  at oracle.bpel.services.rules.util.DecisionServiceBuilder.createDecisionServiceComponent(DecisionServiceBuilder.java:727)  at oracle.bpel.services.rules.util.DecisionServiceBuilder.createDecisionServiceComponent(DecisionServiceBuilder.java:651)  at oracle.tip.tools.ide.rules.editor.services.util.DecisionServiceUtil.createService(DecisionServiceUtil.java:181)  at oracle.tip.tools.ide.rules.dictionarybuilder.jdev.JDevDictionaryFileBuilder.createRuleDictionary(JDevDictionaryFileBuilder.java:472)  at oracle.tip.tools.ide.rules.dictionarybuilder.RulesCreationDialog$2.run(RulesCreationDialog.java:109)  at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1  at java.lang.String.substring(String.java:1967)  at oracle.bpel.services.rules.util.XSDGenerator.getLocalPart(XSDGenerator.java:837)  ... 19 more
· Share on TwitterShare on Facebook

Best Answer

  • Ethan Pilot
    Ethan Pilot Member Posts: 4
    edited May 7, 2018 9:26AM Accepted Answer

    Hey Dan,

    I replaced the XSD files with the modified ones you posted and still got an identical error, "The data model failed to read the XSD businessCatalog/HelloTypes/HelloObject.xsd because of a URL error.", leading me to think I may have some kind of configuration issues. I'm running JDeveloper on Win 10 Pro, dont know if this is a JDeveloper config issue or a windows one, but I've never gotten file system errors with any other development software/servers during my 2 years using this computer.

    Let me know if I left anything out.
    Thanks,

    Ethan

    · Share on TwitterShare on Facebook

Answers

  • Dan Atwood
    Dan Atwood Member Posts: 2,313
    edited May 4, 2018 4:47PM

    What does your XSD look like?

    What version of 12c are you on?

    It does not sound like it, but are you creating two process data objects (based on XSDs with different namespaces) and using those for the input and output of the rule?

    · Share on TwitterShare on Facebook
  • Ethan Pilot
    Ethan Pilot Member Posts: 4
    edited May 4, 2018 5:01PM

    Hi Dan,

    I'm on version 12.2.1.3.0.  The XSDs were both generated by JDeveloper, I have attached them here.  I have encountered this error both when creating the rule from inside my process and referencing the process data objects and also when I create this from the composite editor and reference these items from the business catalogue as shown in some of the 11g oracle tutorials I have seen.
    Input schema

    <?xml version="1.0" encoding="UTF-8"?>

    <?bpmo version="12.1.3" build="00.00" fullName="HelloTypes.HelloObject" modifiers="[public]"?>

    <!--########################################################################################-->

    <!--####                                                                                ####-->

    <!--####          THIS IS AN AUTO GENERATED FILE. PLEASE DO NOT MANUALLY MODIFY         ####-->

    <!--#### CHANGES TO THIS FILE MAY PRODUCE UNEXPECTED BEHAVIOR AND WOULD BE OVERWRITTEN  ####-->

    <!--####                                                                                ####-->

    <!--########################################################################################-->

    <xs:schema targetNamespace="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/HelloObject" elementFormDefault="qualified" xmlns="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/HelloObject"  xmlns:xs="http://www.w3.org/2001/XMLSchema"  xmlns:bpmo="http://xmlns.oracle.com/bpm/bpmobject/" >

        <xs:complexType name="HelloObjectType">

            <xs:sequence>

                <xs:element name="date" nillable="true" type="xs:time"/>

                <xs:element name="greeting" nillable="true" type="xs:string"/>

                <xs:element name="message" nillable="true" type="xs:string"/>

            </xs:sequence>

        </xs:complexType>

        <xs:element name="HelloObject" type="HelloObjectType"/>

    </xs:schema>


    output object

    <?xml version="1.0" encoding="UTF-8"?>

    <?bpmo version="12.1.3" build="00.00" fullName="HelloTypes.ReviewObject" modifiers="[public]"?>

    <!--########################################################################################-->

    <!--####                                                                                ####-->

    <!--####          THIS IS AN AUTO GENERATED FILE. PLEASE DO NOT MANUALLY MODIFY         ####-->

    <!--#### CHANGES TO THIS FILE MAY PRODUCE UNEXPECTED BEHAVIOR AND WOULD BE OVERWRITTEN  ####-->

    <!--####                                                                                ####-->

    <!--########################################################################################-->

    <xs:schema targetNamespace="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/ReviewObject" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"  xmlns="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/ReviewObject"  xmlns:bpmo="http://xmlns.oracle.com/bpm/bpmobject/" >

        <xs:complexType name="ReviewObjectType">

            <xs:sequence>

                <xs:element name="review" nillable="true" type="xs:string"/>

                <xs:element name="reason" nillable="true" type="xs:string"/>

            </xs:sequence>

        </xs:complexType>

        <xs:element name="ReviewObject" type="ReviewObjectType"/>

    </xs:schema>

    · Share on TwitterShare on Facebook
  • Dan Atwood
    Dan Atwood Member Posts: 2,313
    edited May 5, 2018 9:45AM

    Try these two XSDs.   Changes made primarily because my XSDs work and what you are using is not.  Testing using these XSDs would let you see if it is your XSDs that are causing the issue:  Changes were:

    • I've never used nillable as XSD inputs to Business Rules so changed them to minOccurs="0"
    • Removed the clutter at the top

    input XSD:

    <?xml version="1.0" encoding="UTF-8"?>

    <xs:schema targetNamespace="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/HelloObject" elementFormDefault="qualified" xmlns="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/HelloObject"  xmlns:xs="http://www.w3.org/2001/XMLSchema"  xmlns:bpmo="http://xmlns.oracle.com/bpm/bpmobject/" >

        <xs:complexType name="HelloObjectType">

            <xs:sequence>

                <xs:element name="date" minOccurs="0" type="xs:time"/>

                <xs:element name="greeting" minOccurs="0" type="xs:string"/>

                <xs:element name="message" minOccurs="0" type="xs:string"/>

            </xs:sequence>

        </xs:complexType>

        <xs:element name="HelloObject" type="HelloObjectType"/>

    </xs:schema>

    output XSD:

    <?xml version="1.0" encoding="UTF-8"?>

    <xs:schema targetNamespace="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/ReviewObject" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"  xmlns="http://xmlns.oracle.com/bpm/bpmobject/HelloTypes/ReviewObject"  xmlns:bpmo="http://xmlns.oracle.com/bpm/bpmobject/" >

        <xs:complexType name="ReviewObjectType">

            <xs:sequence>

                <xs:element name="review" minOccurs="0" type="xs:string"/>

                <xs:element name="reason" minOccurs="0" type="xs:string"/>

            </xs:sequence>

        </xs:complexType>

        <xs:element name="ReviewObject" type="ReviewObjectType"/>

    </xs:schema>

    Hope this helps,

    Dan

    · Share on TwitterShare on Facebook
  • Ethan Pilot
    Ethan Pilot Member Posts: 4
    edited May 7, 2018 9:26AM Accepted Answer

    Hey Dan,

    I replaced the XSD files with the modified ones you posted and still got an identical error, "The data model failed to read the XSD businessCatalog/HelloTypes/HelloObject.xsd because of a URL error.", leading me to think I may have some kind of configuration issues. I'm running JDeveloper on Win 10 Pro, dont know if this is a JDeveloper config issue or a windows one, but I've never gotten file system errors with any other development software/servers during my 2 years using this computer.

    Let me know if I left anything out.
    Thanks,

    Ethan

    · Share on TwitterShare on Facebook
  • Dan Atwood
    Dan Atwood Member Posts: 2,313
    edited May 7, 2018 10:49AM

    Hi Ethan,

    I'm not sure what is going on, but believe you've eliminated the simple stuff.

    I won't be available after this week, but I'll be glad to work with you directly some time this week if you'd like.  Just click my name and all of my contact information is available there.

    Thanks,

    Dan

    Ethan Pilot
    · Share on TwitterShare on Facebook
  • Ethan Pilot
    Ethan Pilot Member Posts: 4
    edited May 7, 2018 2:26PM

    Leaving this here for posterity, issue seems to have been related to a somehow corrupted project.  Started over and created a new project and no issues were encountered.

    · Share on TwitterShare on Facebook
This discussion has been closed.