Exception - Cannot Build Schema (Question)

Friends,
I have a quick question which is driving me crazy. New to SOA, please help.
I defined a variable of type "element" by refering it to an pre-existing xsd. I know the xsd is valid. When I try to use the variable in an assign activiity it does not show the child element and gives error "Exception - Cannot build Schema". While creating variable I refer to element "FetchCustomerInfoResponse".
Following is the xsd for your reference :-
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.example.org"
targetNamespace="http://www.example.org"
elementFormDefault="qualified">
<xsd:element name="FetchCustomerInfoResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="XYX_ONT_ACCOUNT_ORDERS">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="XYZ_ONT_ACCOUNT_ORDER" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="ordered_date" type="xsd:string"/>
<xsd:attribute name="cust_po_number" type="xsd:string"/>
<xsd:attribute name="order_number" type="xsd:integer"/>
<xsd:attribute name="header_id" type="xsd:integer"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

Hi,
using the schema you gave, i was able to create a variable inside the BPEL by referring to the FetchCustomerInfoResponse element, and also i was able to do the copy operation inside the assign activity.
Please try the same again, may be create the variable again...it should work...
Thanks
N

Similar Messages

Exception:Problem building schema

Hi all,
I want to make a web service call to a service deployed in weblogic, I copied the wsdl to a local file and I created a PartnerLink referring to the wsdl in my local file. I put an Invoke action, create an input variable, everything work fine. However when I try to explore the input variable I got exception:Problem building schema.
Is there anything wrong with the WSDL? I've validate it and it was ok.
Thanks in advance,
santoso
Here is the WSDL of the service:
<?xml version='1.0' encoding='UTF-8'?>
<definitions name="ProposalWSServiceDefinitions" targetNamespace="http://com/my/ws" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://com/my/ws" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.my.com/opl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://com/my/ws" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.my.com/opl">
<complexType name="Proposal">
<sequence>
<element name="id" type="int"/>
<element name="title" type="string"/>
<element name="creator" type="string"/>
<element name="status" type="string"/>
<element name="customerId" type="int"/>
</sequence>
</complexType>
<element name="ProposalData" type="tns:Proposal"/>
</schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://com/my/ws" xmlns:s0="http://com/my/ws" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="insertProposal">
<xs:complexType>
<xs:sequence>
<xs:element name="proposal" type="opl:Proposal" xmlns:opl="http://www.my.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="insertProposal">
<part element="s0:insertProposal" name="parameters"/>
</message>
<portType name="ProposalWS">
<operation name="insertProposal" parameterOrder="parameters">
<input message="s0:insertProposal"/>
</operation>
</portType>
<binding name="ProposalWSServiceSoapBinding" type="s0:ProposalWS">
<s1:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="insertProposal">
<s1:operation soapAction="" style="document"/>
<input>
<s1:body parts="parameters" use="literal"/>
</input>
</operation>
</binding>
<service name="ProposalWSService">
<port binding="s0:ProposalWSServiceSoapBinding" name="ProposalWSSoapPort">
<s1:address location="http://172.16.208.45:7001/SBSWebService/ProposalWS"/>
</port>
</service>
</definitions>

I've solved it just by upgrading to BPEL 10.1.3.1 (was 10.1.2.0)

"Problem building schema" exception in BPEL Designer

Hi all,
I use BPEL Designer 10.1.2.0.2 and encounter the following problem:
I built a web service based on the Oracle Toplink How To demo. The web service has one published method that returns a custom 'Customer' object.
I deployed the web service on my localhost (AS 10.1.3)
In my BPEL process, I create a partnerlink based on the WSDL that was generated by JDeveloper and let BPEL Designer create a local copy.
Then I created an invoke and had the wizard create in- and output variables for the invoke.
When I select either the input- or output variable in the structure pane, I get an error message when I click on the 'parameters' entry. The message shown is 'Exception - problem building schema!'
When I check the 'show detailed node information' box no additional info is shown!
Any Idea what might go wrong?
The WSDL looks as follows:
<definitions
name="updCustWS"
targetNamespace="http://examples.ox.model/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://examples.ox.model/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://examples.ox.model/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns1="http://www.oracle.com/webservices/internal/literal"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="urn:customer-example" schemaLocation="Customer.xsd"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://examples.ox.model/types/"
elementFormDefault="qualified" xmlns:tns="http://examples.ox.model/types/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
<import namespace="http://www.oracle.com/webservices/internal/literal"/>
<import namespace="urn:customer-example" schemaLocation="Customer.xsd"/>
<complexType name="getCust">
<sequence>
<element name="cust" type="tns:Customer" nillable="true"/>
</sequence>
</complexType>
<complexType name="Customer">
<sequence>
<element name="gender" type="string" nillable="true"/>
<element name="dateOfBirth" type="dateTime" nillable="true"/>
<element name="phoneNumbers" type="ns1:vector" nillable="true"/>
<element name="shippingAddress" type="tns:Address" nillable="true"/>
<element name="billingAddress" type="tns:Address" nillable="true"/>
<element name="firstName" type="string" nillable="true"/>
<element name="lastName" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="Address">
<sequence>
<element name="postalCode" type="string" nillable="true"/>
<element name="suite" type="string" nillable="true"/>
<element name="street" type="string" nillable="true"/>
<element name="province" type="string" nillable="true"/>
<element name="city" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="getCustResponse">
<sequence>
<element name="result" type="tns:Customer" nillable="true"/>
</sequence>
</complexType>
<complexType name="version">
<sequence/>
</complexType>
<complexType name="versionResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<element name="getCustElement" type="tns:getCust"/>
<element name="getCustResponseElement" type="tns:getCustResponse"/>
<element name="versionElement" type="tns:version"/>
<element name="versionResponseElement" type="tns:versionResponse"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.oracle.com/webservices/internal/literal"
elementFormDefault="qualified" xmlns:tns="http://www.oracle.com/webservices/internal/literal"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<import namespace="http://examples.ox.model/types/"/>
<import namespace="urn:customer-example" schemaLocation="Customer.xsd"/>
<complexType name="vector">
<complexContent>
<extension base="tns:list">
<sequence/>
</extension>
</complexContent>
</complexType>
<complexType name="list">
<complexContent>
<extension base="tns:collection">
<sequence/>
</extension>
</complexContent>
</complexType>
<complexType name="collection">
<sequence>
<element name="item" type="anyType" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
</schema>
</types>
<message name="UpdCustWS_getCust">
<part name="parameters" element="tns0:getCustElement"/>
</message>
<message name="UpdCustWS_getCustResponse">
<part name="parameters" element="tns0:getCustResponseElement"/>
</message>
<message name="UpdCustWS_version">
<part name="parameters" element="tns0:versionElement"/>
</message>
<message name="UpdCustWS_versionResponse">
<part name="parameters" element="tns0:versionResponseElement"/>
</message>
<portType name="updCustWS">
<operation name="getCust">
<input message="tns:UpdCustWS_getCust"/>
<output message="tns:UpdCustWS_getCustResponse"/>
</operation>
<operation name="version">
<input message="tns:UpdCustWS_version"/>
<output message="tns:UpdCustWS_versionResponse"/>
</operation>
</portType>
<binding name="updCustWSSoapHttp" type="tns:updCustWS">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getCust">
<soap:operation soapAction="http://examples.ox.model//getCust"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
<operation name="version">
<soap:operation soapAction="http://examples.ox.model//version"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<service name="updCustWS">
<port name="updCustWSSoapHttpPort" binding="tns:updCustWSSoapHttp">
<soap:address location="http://localhost:7780/toplinkDemo-toplink-context-root/updCustWSSoapHttpPort"/>
</port>
</service>
</definitions>
any help would be greatly appreciated!
Thanks in advance,
Rob

Hi
I know it's an old thread, but I'm having the same issue.
I have created an EJB3 web service that returns an object with 2 nested objects. The autogenerated WSDL looks something like this:
<?xml version = '1.0' encoding = 'UTF-8'?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns0="http://www.oracle.com/webservices/internal/literal" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://smbc.crm.persistence.services/" name="CRMBusinessWSService" targetNamespace="http://smbc.crm.persistence.services/">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.oracle.com/webservices/internal/literal" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://smbc.crm.persistence.services/" elementFormDefault="qualified">
<import namespace="http://www.oracle.com/webservices/internal/literal"/>
<complexType name="Businesses">
<sequence>
<element name="partyId" type="long" nillable="true"/>
<element name="businessContactPoints" type="ns1:list" nillable="true"/>
<element name="businessAddresses" type="ns1:list" nillable="true"/>
</sequence>
</complexType>
<complexType name="BusinessAddresses">
<sequence>
<element name="locality" type="string" nillable="true"/>
<element name="paon" type="string" nillable="true"/>
<element name="siteUseType" type="string" nillable="true"/>
<element name="locationId" type="long" nillable="true"/>
<element name="townName" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="BusinessContactPoints">
<sequence>
<element name="telCountryCode" type="string" nillable="true"/>
<element name="partyId" type="long" nillable="true"/>
<element name="telAreaCode" type="string" nillable="true"/>
</sequence>
</complexType>
<element name="queryBusinessesFindByPartyId" type="tns:queryBusinessesFindByPartyId"/>
<complexType name="queryBusinessesFindByPartyId">
<sequence>
<element name="int_1" type="int"/>
</sequence>
</complexType>
<element name="queryBusinessesFindByPartyIdResponse" type="tns:queryBusinessesFindByPartyIdResponse"/>
<complexType name="queryBusinessesFindByPartyIdResponse">
<sequence>
<element name="return" type="tns:Businesses" nillable="true"/>
</sequence>
</complexType>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.oracle.com/webservices/internal/literal" targetNamespace="http://www.oracle.com/webservices/internal/literal" elementFormDefault="qualified">
<import namespace="http://smbc.crm.persistence.services/"/>
<complexType name="list">
<complexContent>
<extension base="tns:collection">
<sequence/>
</extension>
</complexContent>
</complexType>
<complexType name="collection">
<sequence>
<element name="item" type="anyType" minOccurs="0" maxOccurs="unbounded"/>
</sequence>
</complexType>
</schema>
</types>
<message name="CRMBusinessWS_queryBusinessesFindByPartyId">
<part name="parameters" element="tns:queryBusinessesFindByPartyId"/>
</message>
<message name="CRMBusinessWS_queryBusinessesFindByPartyIdResponse">
<part name="parameters" element="tns:queryBusinessesFindByPartyIdResponse"/>
</message>
<portType name="CRMBusinessWS">
<operation name="queryBusinessesFindByPartyId">
<input message="tns:CRMBusinessWS_queryBusinessesFindByPartyId"/>
<output message="tns:CRMBusinessWS_queryBusinessesFindByPartyIdResponse"/>
</operation>
</portType>
<binding name="CRMBusinessWSSoapHttp" type="tns:CRMBusinessWS">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="queryBusinessesFindByPartyId">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="CRMBusinessWSService">
<port name="CRMBusinessSessionEJB" binding="tns:CRMBusinessWSSoapHttp">
<soap:address location="http://blah.solihull.gov.uk:1234/crm-ws/CRMBusinessSessionEJB"/>
</port>
</service>
</definitions>
The web service runs fine and returns a valid XML document (like below):
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://smbc.crm.persistence.services/"
xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
<env:Body>
<ns0:queryBusinessesFindByPartyIdResponse>
<ns0:return>
<ns0:turnover xsi:nil="1"/>
<ns0:partyId>551837</ns0:partyId>
<ns0:employeesLocal xsi:nil="1"/>
<ns0:employeesNational xsi:nil="1"/>
<ns0:businessName xsi:nil="1"/>
<ns0:classificationSic xsi:nil="1"/>
<ns0:registeredBusinessName>Bob The Builder</ns0:registeredBusinessName>
<ns0:classificationLacors xsi:nil="1"/>
<ns0:sbaLinkNumber xsi:nil="1"/>
<ns0:legalStatus xsi:nil="1"/>
<ns0:localAuthority xsi:nil="1"/>
<ns0:bpa>560950</ns0:bpa>
<ns0:dateCommencedTrading xsi:nil="1"/>
<ns0:businessDirectoryListing xsi:nil="1"/>
<ns0:businessStage xsi:nil="1"/>
<ns0:classificationBcl xsi:nil="1"/>
<ns0:employeesGlobal xsi:nil="1"/>
<ns0:descriptionOfBusiness xsi:nil="1"/>
<ns0:businessContactPoints xsi:type="ns1:vector">
<ns1:item xsi:type="ns0:BusinessContactPoints">
<ns0:telCountryCode xsi:nil="1"/>
<ns0:partyId>551837</ns0:partyId>
<ns0:contactPointType>EMAIL</ns0:contactPointType>
<ns0:contactTelephoneNumber xsi:nil="1"/>
<ns0:bpa>560950</ns0:bpa>
<ns0:contactPointId>76330</ns0:contactPointId>
<ns0:telExtensionNumber xsi:nil="1"/>
<ns0:contactEmailAddress>[email protected]</ns0:contactEmailAddress>
<ns0:registeredBusinessName>Bob The Builder</ns0:registeredBusinessName>
<ns0:telAreaCode xsi:nil="1"/>
</ns1:item>
<ns1:item xsi:type="ns0:BusinessContactPoints">
<ns0:telCountryCode>44</ns0:telCountryCode>
<ns0:partyId>551837</ns0:partyId>
<ns0:contactPointType>PHONE</ns0:contactPointType>
<ns0:contactTelephoneNumber>323233</ns0:contactTelephoneNumber>
<ns0:bpa>560950</ns0:bpa>
<ns0:contactPointId>76329</ns0:contactPointId>
<ns0:telExtensionNumber xsi:nil="1"/>
<ns0:contactEmailAddress xsi:nil="1"/>
<ns0:registeredBusinessName>Bob The Builder</ns0:registeredBusinessName>
<ns0:telAreaCode>123</ns0:telAreaCode>
</ns1:item>
</ns0:businessContactPoints>
<ns0:businessAddresses xsi:type="ns1:vector">
<ns1:item xsi:type="ns0:BusinessAddresses">
<ns0:partyId>551837</ns0:partyId>
<ns0:locality>Kingshurst</ns0:locality>
<ns0:paon>20</ns0:paon>
<ns0:siteUseType>HEADQUATERS_FOR</ns0:siteUseType>
<ns0:locationId>34380</ns0:locationId>
<ns0:townName>Birmingham</ns0:townName>
<ns0:registeredBusinessName>Bob The Builder</ns0:registeredBusinessName>
<ns0:saon xsi:nil="1"/>
<ns0:bpa>560950</ns0:bpa>
<ns0:country>GB</ns0:country>
<ns0:uprn>100070950848</ns0:uprn>
<ns0:dateOfOccupancyAtthisaddr xsi:nil="1"/>
<ns0:streetDescriptor>Acacia Avenue</ns0:streetDescriptor>
<ns0:postcode>B37 6AQ</ns0:postcode>
<ns0:countyName xsi:nil="1"/>
<ns0:usrn xsi:nil="1"/>
</ns1:item>
</ns0:businessAddresses>
</ns0:return>
</ns0:queryBusinessesFindByPartyIdResponse>
</env:Body>
</env:Envelope>
The problem is that I'm trying to transform this message in BPEL/ESB but the mapper does not understand the schema as described in the WSDL and will not let me do 'for-each' or 'if' actions on the collections of addresses for example.
I've tried injecting my own WSDL into the EJB3 web service through annotations, but it will not compile....
Can anybody help????
Thanks
Chris

Exception building schema because of different namespace

Hi all,
I have a wsdl that define a schema having different namespace from the service itself. When I create an Invoke activity and the input/output variables, everything went ok. However if I try to explore the newly created input/output variables an exception (Problem building schema) is thrown.
If I use the same namespace for the service and the schema defined in it, everything is okay.
Could anybody explain to me why I should set it to the same namespace to get it to work?
Is it a mistake to use different namespace?
Thanks in advance,
santoso
Below is the wsdl :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="ProposalWSServiceDefinitions4" targetNamespace="http://www.test.com/service" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://www.test.com/service" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/opl" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.test.com/opl">
<complexType name="TProposal">
<sequence>
<element name="id" type="int"/>
<element name="title" type="string"/>
<element name="creator" type="string"/>
<element name="status" type="string"/>
<element name="customerId" type="int"/>
</sequence>
</complexType>
<element name="Proposal" type="tns:TProposal"/>
</schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="insertProposal">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="insertProposalResponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="insertProposal">
<part element="s0:insertProposal" name="parameters"/>
</message>
<message name="insertProposalResponse">
<part element="s0:insertProposalResponse" name="parameters"/>
</message>
<portType name="ProposalWS">
<operation name="insertProposal" parameterOrder="parameters">
<input message="s0:insertProposal"/>
<output message="s0:insertProposalResponse"/>
</operation>
</portType>
<binding name="ProposalWSServiceSoapBinding" type="s0:ProposalWS">
<s1:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="insertProposal">
<s1:operation soapAction="" style="document"/>
<input>
<s1:body parts="parameters" use="literal"/>
</input>
<output>
<s1:body parts="parameters" use="literal"/>
</output>
</operation>
</binding>
<service name="ProposalWSService">
<port binding="s0:ProposalWSServiceSoapBinding" name="ProposalWSSoapPort">
<s1:address location="http://localhost:7021/Proposal"/>
</port>
</service>
</definitions>

Hi,
The problem is when I use the wsdl in a bpel process project, the variable created can't be explored.
However, I've found the solution by adding import namespace.
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.test.com/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://www.test.com/opl" />
<xs:element name="insertProposal">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="insertProposalResponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="opl:Proposal" xmlns:opl="http://www.test.com/opl"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

Problem building schema - Siebel OnDemand Web Services

I'm trying to call a Siebel OnDemand Web Service from BPEL.
I've downloaded the Contact.wsdl from OnDemand and imported it into my project.
I've created a partner link and created variables for the input and output.
The problem is that JDeveloper cannot build the schemas defined in the wsdl.
If you try to copy a value to the Input variable, JDeveloper gives the error:
Exception - Problem building schema!
You cannot navigate the schema path.
Does anyone know why this is happening?

I'm also trying to do this.
Some info from the Siebel web services guide:-
"The login request is an HTTPS request to instantiate a session and obtain a session ID. A client invokes login by sending an HTTP GET request to a URL like the following:
https://secure.crmondemand.com/Services/Integration?command=login
NOTE: The login parameter value is case sensitive.
■ Login input. The input to login is provided in the URL parameters and the HTTP headers, as follows:
■ The only URL parameter to be set is command. This parameter value is login.
Two HTTP headers, UserName and Password, must be set with the appropriate values for your system. For example:
❏ UserName: [email protected]
❏ Password: mypass
■ Login output. The login command returns the following items:
■ A session cookie, jsessionid. The client must use this cookie when submitting subsequent requests, including logoff requests.
■ A status code of 200, if the session does not encounter any errors. This indicates that the request succeeded.
Then to get data out ....
Integration request input. The jsessionid returned to the client during login must be included with the request. The request must contain the jsessionid either as a cookie or as a URL parameter, as follows:
https://secure.crmondemand.com/Services/Integration/object;jsessionid=xyZ12489w3482413
Does anyone have any ideas on how we might do this using the Oracle BPEL PM?
Thanks in advance.

Bpel variables return Http 503 (problem building schema) error

First of all if I have posted this in the wrong forum, I apologise in advance.
I have recently installed the Oracle SOA suite and I have downloaded JDeveloper 10.1.3.3, I am running the (http://download.oracle.com/otndocs/products/bpel/orderbooking.pdf) Oracle® BPEL Process Manager Tutorial and when attempting to create a copy rule I have noticed that some of my variables return the following error:
Exception - Problem building schema
expanded error:
Exception: Server returned HTTP response code: 503 for URL: http://MYID.MYDOMAIN.com:80/orabpel/default/CreditRatingService/CreditRatingService?wsdl
I can access the WSDL directly and it is visible in my Bpel console window too, yet JDeveloper seems to be having trouble with it. I have setup an integration server connection to the BPEL server and from there, when I attempt to validate WSDL I don't get any problems.
I was wondering if anyone could help as this has got me stuck and I can't continue any further.
Edited by: Saheem on Jun 8, 2009 3:33 PM

Disable the proxy settings in JDeveloper.
Marc

Problem building schema for return type as custom object

Hi i am invoking a web service through a partner link. But when i expand the invoke variables( in structure tab ), it shows Exception- Problem building schema.
Response is of type java:Customer which is a custom object having mobile_no, name, compname.
Error is--
Invalid reference: 'java:customobjectproject:Customer'
wsdl file:
<?xml version='1.0' encoding='UTF-8'?>
<definitions name="CustomerDetailServiceDefinitions" targetNamespace="http://customobjectproject" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://customobjectproject" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://customobjectproject" xmlns:s0="http://customobjectproject" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="getCustomer">
<xs:complexType>
<xs:sequence>
<xs:element name="mobileNo" type="xs:int"/>
<xs:element name="name" type="xs:string"/>
<xs:element name="compName" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getCustomerResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" type="java:Customer" xmlns:java="java:customobjectproject"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:customobjectproject" xmlns:s0="http://customobjectproject" xmlns:s1="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="Customer">
<xs:sequence>
<xs:element minOccurs="1" name="Mobile_no" nillable="false" type="xs:int"/>
<xs:element minOccurs="1" name="Name" nillable="true" type="xs:string"/>
<xs:element minOccurs="1" name="CompName" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
</types>
<message name="getCustomer">
<part element="s0:getCustomer" name="parameters"/>
</message>
<message name="getCustomerResponse">
<part element="s0:getCustomerResponse" name="parameters"/>
</message>
<portType name="CustomerDetail">
<operation name="getCustomer" parameterOrder="parameters">
<input message="s0:getCustomer"/>
<output message="s0:getCustomerResponse"/>
</operation>
</portType>
<binding name="CustomerDetailServiceSoapBinding" type="s0:CustomerDetail">
<s1:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getCustomer">
<s1:operation soapAction="" style="document"/>
<input>
<s1:body parts="parameters" use="literal"/>
</input>
<output>
<s1:body parts="parameters" use="literal"/>
</output>
</operation>
</binding>
<service name="CustomerDetailService">
<port binding="s0:CustomerDetailServiceSoapBinding" name="CustomerDetailSoapPort">
<s1:address location="http://localhost:7030/CustomerDetail/CustomerDetail"/>
</port>
</service>
</definitions>
I am using jdeveloper 10.1.3.3.0. Please help..
Thanks.

Well, the problem is caused by the fact that BPEL does not yet support soapenc:Array types. We've created a workaround by defining two Services, one that has only single returntypes and one that has the multiple returntypes (which are defined using soapenc:Array). There are other solutions, but those are very complicated. Hope this helps!

I am getting read WSDL errors for WSDLS and Exception building schema in the assign activity schema

Hi All,
1 st error: Even though I had added the URLs related to Webservice WSDLs that composite and BPEL have to load,I am getting 'read WSDL' errors when I open the composite.Sometimes it is loading properly and sometimes it is not loading properly.I restarted the system and I had aslo put webbrowser and proxy unchecked still I am facing that issue
2 nd error: As I any schema node in assign activity I am getting 'Exception building schema' errors.
What I feel I had set some memory settings so that wsdls and schemas will load properly.
Please do the needful to resolve these issues as I have to work on some production issues urgently.

Maybe you can use the MDS to decouple your development environment with your runtime environment.
Put you're WSDLs/XSDs in a local MDS that you then sync with your runtime environment.
Instead of referencing to the life WSDL you reference to a oramds:// url.
Check out my two-part blogpost about it:
(1/2) Using the MetaData Services (MDS) in a SOA environment
(2/2) Using the MetaData Services (MDS) in a SOA environment

Error "Problem building schema" while invoking external webservice

Hi,
I have following problem:
I created 2 BPEL processes.
One of these processes should be called from the other as a partnerlink.
When I create the partnerlink, pointing to the deployed wsdl, I get following error "Problem building schema" when I try to access the input variable that was created by the invoke activity.
I have tried a lot of things but keep on getting this error.
When I create a new, empty BPEL process, and do exactly the same it does work!
any help would be greatly appreciated.....

Hi,
I have given this URL 'http://ws.cdyne.com/WeatherWS/Weather.asmx?WSDL'.
Now it is showing the following error
Exception occured in library handler.Not implemented.
Exception of class CX_SIDL_INTERNAL_ERROR
Please have a look into it
Regards,
Dhana

Error : Old and new exceptions cannot be used at the same time.

HI ALL,
i build a new exception class with message class and i want to replace the
old exception that i had in the method ,what i did is delete the exception from the method
signature and add the exception class .
the problem is that when i try to activate the method i get error :
Old and new exceptions cannot be used at the same time.
CALL FUNCTION 'CALCULATE_HASH_FOR_CHAR'
      EXPORTING
        alg            = 'MD5'
        data           = iv_iss
      IMPORTING
        hash           = lv_issu
      EXCEPTIONS
        unknown_alg    = 1
        param_error    = 2
        internal_error = 3
        OTHERS         = 4.
    IF sy-subrc <> 0.
      RAISE EXCEPTION TYPE cx_user_mng EXPORTING
      textid = cx_user_mng=>wrong_isrs.
    ENDIF.
I want to use the new exception class ,
how can i avoid this error ?
Best Regards
Edited by: Joy Stpr on Jul 22, 2009 2:56 PM
Edited by: Joy Stpr on Jul 22, 2009 3:16 PM

Hi Joy,
Check this link.
[Old and New Exceptions Cannot be used at same time|Urgent problem, give me a hand;
Old and new exceptions cannot be used the same time, what does this mean???
Regards,
Lakshman.

Problem in building schema when try to invoke the another BPEL service

Hi all,
Whenever try to Invoke a another BPEL service using the Invoke activiy and Partnerlink, we need to create a variable structure similar to the providing service.
For this I used create Auto Varible option available in the invoke activity. But after creating the variable, I tried to expand the variable for the copy operation, the error iam getting is Problem in building schema.
This error never happened to me before. I have no clue.
Jdev version:10.1.3.3.0
Soa version:10.1.3.3.0
Please help me on this.
Thanks.

Hi Lokesh,
Iam not able to understand what you are trying to say. But my Input variable and Invoke Input variable are compatible, no problem on this. I got some clue from your reply.
Finally I got it worked by doing it in another way.
In my Invoking BPEL Process(ie. BPEL Process is trying to invoke the another BPEL Process using Partnerlink) wsdl I imported the partnerlink BPEL schema and it get solved my problem.
eg) <import namespace="http://xmlns.oracle.com/BpelProcessname" schemaLocation="ParnerLinkBPELSchema.xsd"/>
This can be usefull for others and I never did this to import the schema manually before, but it works without any errors.
Now only it causing this problem, whether it is any Jdeveloper issue.
And i tryed this using Jdev version 10.1.3.4.0, but still the same exception.
This workaround will usefull for others.
Thanks for your reply.
bye.....

Error building schema

Hi Gurus,
I am trying to create a simple synchronous BPEL process from which I am invoking a external webservice deployed on a local oc4j container in my laptop.My external webservice operation takes a complex type as input and returns a complex type as output.I have created a partner link for my external webservice and an invoke activity for the calling the partner link.
When I try to expand the Input/Output variables created for the invoke activity,I get the following error
Error building schema
Exception: Connection timed out: connect
I have the correct proxy settings in my JDeveloper and I am able to access my webservice port from my browser.Please let me know where I am going wrong.
Thanks In Advance,
Prasanna

Hi, just a try:
"In obsetenv.bat you can specify the proxy to be used for outbound soap/http.
Make sure it is set if there is a proxy between the bpel server and the webservice you are trying to call."
In case it works: Thanks to Mark :-)
Regards,
Hansi

Problem building schema on WSDL for Partnerlink

Hi,
We use PL/SQL webservices, which are being generated with JDeveloper. As long as it contains single Object Types, there's no problem with defining the WS as Partnerlink and using it.
However, we've made one service that returns several occurrences (array). That shouldn't be a problem. But, ... I can define the partnerlink on the basis of the WSDL, but when I try to access the variables it generates with it, i get an exception with the following message: Problem building schema. Detailed node information shows: 'Invalid reference: 'http://schemas.xmlsoap.org/soap/encoding/:Array'


     <definitions name="aanvraagWS" targetNamespace="http://nl/nak/aanvraagService/aanvraagWS.wsdl">
     <types>
     <schema targetNamespace="http://nl.nak.services/AanvraagWS.xsd">
     <complexType name="nl_nak_services_AvrgAvrgOtUser" jdev:packageName="nl.nak.services">
     <all>
<element name="id" type="decimal"/>
<element name="oogstjaar" type="decimal"/>
<element name="aanvraagNummer" type="decimal"/>
<element name="rleId" type="decimal"/>
<element name="kotId" type="decimal"/>
<element name="aantalVerpakkingen" type="decimal"/>
<element name="verpakkingsvorm" type="string"/>
<element name="totaalGewicht" type="decimal"/>
<element name="indBemonsterdNaDrogen" type="string"/>
<element name="partijnummerHandelaar" type="string"/>
<element name="opmerkingen" type="string"/>
<element name="datumBemonstering" type="dateTime"/>
<element name="plombenummer" type="string"/>
<element name="indSpoedonderzoek" type="string"/>
<element name="bemonsterdDoor" type="string"/>
<element name="pdtId" type="decimal"/>
<element name="procesInstanceId" type="decimal"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_addaanvraag_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="paanvraagotInout" type="ns1:nl_nak_services_AvrgAvrgOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AvrgServiceBerichtOtUser" jdev:packageName="nl.nak.services">
     <all>
<element name="serviceCode" type="decimal"/>
<element name="serviceBericht" type="string"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_getaanvraag_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="paanvraagotOut" type="ns1:nl_nak_services_AvrgAvrgOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_findaanvraag_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="paanvraagotOut" type="ns1:nl_nak_services_AvrgAvrgOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AvrgWngOtUser" jdev:packageName="nl.nak.services">
     <all>
<element name="id" type="decimal"/>
<element name="wmrId" type="decimal"/>
<element name="prrId" type="decimal"/>
<element name="avrgId" type="decimal"/>
<element name="waardeNumeriek" type="decimal"/>
<element name="waardeAlfanumeriek" type="string"/>
<element name="datumUitvoering" type="dateTime"/>
<element name="uitvoerder" type="string"/>
<element name="istId" type="decimal"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_addwaarneming_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="pwaarnemingotInout" type="ns1:nl_nak_services_AvrgWngOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_getwaarneming_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="pwaarnemingotOut" type="ns1:nl_nak_services_AvrgWngOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_findwaarneming_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="pwaarnemingotInout" type="ns1:nl_nak_services_AvrgWngOtUser"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_listwaarnemingperaanvraag_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="pwaarnemingctOut" type="ns1:nl_nak_services_AvrgWngCt"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
     <complexType name="nl_nak_services_AvrgWngCt" jdev:packageName="nl.nak.services">
     <all>
<element name="array" type="ns1:ArrayOfnl_nak_services_AvrgWngOtUser"/>
</all>
</complexType>
     <complexType name="ArrayOfnl_nak_services_AvrgWngOtUser">
     <complexContent>
     <restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:nl_nak_services_AvrgWngOtUser[]"/>
</restriction>
</complexContent>
</complexType>
     <complexType name="nl_nak_services_AanvraagWSImpl_listwaarnemingperwerkmonster_Out" jdev:packageName="nl.nak.services">
     <all>
<element name="pwaarnemingctOut" type="ns1:nl_nak_services_AvrgWngCt"/>
<element name="pserviceberichttypeOut" type="ns1:nl_nak_services_AvrgServiceBerichtOtUser"/>
</all>
</complexType>
</schema>
</types>
     <message name="addaanvraag0Request">
<part name="xxpAanvraagOt_inoutxx" type="ns1:nl_nak_services_AvrgAvrgOtUser"/>
</message>
     <message name="addaanvraag0Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_addaanvraag_Out"/>
</message>
     <message name="getaanvraag1Request">
<part name="pAanvraagid" type="xsd:decimal"/>
</message>
     <message name="getaanvraag1Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_getaanvraag_Out"/>
</message>
     <message name="findaanvraag2Request">
<part name="pOogstjaar" type="xsd:decimal"/>
<part name="pAanvraagNummer" type="xsd:decimal"/>
</message>
     <message name="findaanvraag2Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_findaanvraag_Out"/>
</message>
     <message name="addwaarneming3Request">
<part name="xxpWaarnemingOt_inoutxx" type="ns1:nl_nak_services_AvrgWngOtUser"/>
</message>
     <message name="addwaarneming3Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_addwaarneming_Out"/>
</message>
     <message name="getwaarneming4Request">
<part name="pWerkmonsterId" type="xsd:decimal"/>
<part name="pAanvraagId" type="xsd:decimal"/>
<part name="pBepalingId" type="xsd:decimal"/>
</message>
     <message name="getwaarneming4Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_getwaarneming_Out"/>
</message>
     <message name="findwaarneming5Request">
<part name="xxpWaarnemingOt_inoutxx" type="ns1:nl_nak_services_AvrgWngOtUser"/>
</message>
     <message name="findwaarneming5Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_findwaarneming_Out"/>
</message>
     <message name="listwaarnemingperaanvraag6Request">
<part name="pAanvraagId" type="xsd:decimal"/>
</message>
     <message name="listwaarnemingperaanvraag6Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_listwaarnemingperaanvraag_Out"/>
</message>
     <message name="listwaarnemingperwerkmonster7Request">
<part name="pWerkmonsterId" type="xsd:decimal"/>
</message>
     <message name="listwaarnemingperwerkmonster7Response">
<part name="return" type="ns1:nl_nak_services_AanvraagWSImpl_listwaarnemingperwerkmonster_Out"/>
</message>
     <portType name="AanvraagWSPortType">
     <operation name="addaanvraag">
<input name="addaanvraag0Request" message="tns:addaanvraag0Request"/>
<output name="addaanvraag0Response" message="tns:addaanvraag0Response"/>
</operation>
     <operation name="getaanvraag">
<input name="getaanvraag1Request" message="tns:getaanvraag1Request"/>
<output name="getaanvraag1Response" message="tns:getaanvraag1Response"/>
</operation>
     <operation name="findaanvraag">
<input name="findaanvraag2Request" message="tns:findaanvraag2Request"/>
<output name="findaanvraag2Response" message="tns:findaanvraag2Response"/>
</operation>
     <operation name="addwaarneming">
<input name="addwaarneming3Request" message="tns:addwaarneming3Request"/>
<output name="addwaarneming3Response" message="tns:addwaarneming3Response"/>
</operation>
     <operation name="getwaarneming">
<input name="getwaarneming4Request" message="tns:getwaarneming4Request"/>
<output name="getwaarneming4Response" message="tns:getwaarneming4Response"/>
</operation>
     <operation name="findwaarneming">
<input name="findwaarneming5Request" message="tns:findwaarneming5Request"/>
<output name="findwaarneming5Response" message="tns:findwaarneming5Response"/>
</operation>
     <operation name="listwaarnemingperaanvraag">
<input name="listwaarnemingperaanvraag6Request" message="tns:listwaarnemingperaanvraag6Request"/>
<output name="listwaarnemingperaanvraag6Response" message="tns:listwaarnemingperaanvraag6Response"/>
</operation>
     <operation name="listwaarnemingperwerkmonster">
<input name="listwaarnemingperwerkmonster7Request" message="tns:listwaarnemingperwerkmonster7Request"/>
<output name="listwaarnemingperwerkmonster7Response" message="tns:listwaarnemingperwerkmonster7Response"/>
</operation>
</portType>
     <binding name="AanvraagWSBinding" type="tns:AanvraagWSPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
     <operation name="addaanvraag">
<soap:operation soapAction="" style="rpc"/>
     <input name="addaanvraag0Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="addaanvraag0Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="getaanvraag">
<soap:operation soapAction="" style="rpc"/>
     <input name="getaanvraag1Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="getaanvraag1Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="findaanvraag">
<soap:operation soapAction="" style="rpc"/>
     <input name="findaanvraag2Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="findaanvraag2Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="addwaarneming">
<soap:operation soapAction="" style="rpc"/>
     <input name="addwaarneming3Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="addwaarneming3Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="getwaarneming">
<soap:operation soapAction="" style="rpc"/>
     <input name="getwaarneming4Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="getwaarneming4Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="findwaarneming">
<soap:operation soapAction="" style="rpc"/>
     <input name="findwaarneming5Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="findwaarneming5Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="listwaarnemingperaanvraag">
<soap:operation soapAction="" style="rpc"/>
     <input name="listwaarnemingperaanvraag6Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="listwaarnemingperaanvraag6Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
     <operation name="listwaarnemingperwerkmonster">
<soap:operation soapAction="" style="rpc"/>
     <input name="listwaarnemingperwerkmonster7Request">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
     <output name="listwaarnemingperwerkmonster7Response">
<soap:body use="encoded" namespace="aanvraagWS" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
     <service name="aanvraagWS">
     <port name="AanvraagWSPort" binding="tns:AanvraagWSBinding">
<soap:address location="http://nak3.nak.nl:7779/aanvraagService/AanvraagWS"/>
</port>
</service>
</definitions>

Well, the problem is caused by the fact that BPEL does not yet support soapenc:Array types. We've created a workaround by defining two Services, one that has only single returntypes and one that has the multiple returntypes (which are defined using soapenc:Array). There are other solutions, but those are very complicated. Hope this helps!

Cannot build form off from view?

Is this true because when I try to Add a Page to a new application I dont seem to be able to see any of my views on the list of values but my tables. Opened up a TAR and here was the response
To implement the solution, please execute the following steps:
Use workaround listed in Bug 4719289 - CANNOT BUILD FORM OFF FROM VIEW
1. Create Application
2. Give Application a name, the "From Scratch" option is selected, our
desired
schema is selected.
3. Add Blank Page, select theme, etc, application is created.
4. From Blank page, Add Form Region based on existing table, followed the
resulting steps in the Wizard, etc.

Please share your first name and put it into your profile to help us.
You can create a form based on ("off from") a view after an application is created using the create page or create region wizards.
Scott

Cannot build aggregates

Hi,
For which chars we cannot build aggregates.

Hello,
In general, you can create aggregates on any characteristics defined in the InfoCube.
the following documents can clarify your questions,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cbd2d390-0201-0010-8eab-a8a9269a23c2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
Assign points if helpful.
Regards,
karthik

Exception - Cannot Build Schema (Question)

Similar Messages

Maybe you are looking for