XSD encoding
I am uploading an XSD into an external definition. In the XSD the encoding is specified as UTF-8. In the external definition it has changed to ISO-8859-1. This seems to be messing up my output XML. Any ideas on why and how the encoding changed from XSD to external definition? Is this a setting somewhere?
Regards
Anthony
Hi Stephan
I checked and see that it is only used for display. The problem I'm having is this:
The sample XML from my partner looks like this:
<cmt:Store>
<cmt:AddressLine1>1 main street</cmt:AddressLine1>
My generated XML looks like this:
<ns0:Store>
<ns0:AddressLine1>1 main street</ns0:AddressLine1>
In the tags cmt has changed to ns0.
The XSD starts like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cmt="http://www.trimble.com/tms/XMLSchema/1.0" xmlns:exds="http://www.trimble.com/tms/XMLSchema/ExtendedDataSchema/2.0" targetNamespace="http://www.trimble.com/tms/XMLSchema/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
Hope this helps.
Anthony
Similar Messages
-
DISPLAYNAME_CONVERSION_ERROR in XML DB
Hello,
After I have installed Oracle 10g Release 2 patchetset 1 (10.2.0.2.0), I have created a new database (the previous one was disabled after the update process, I suppose I did not make all steps well). This new database has the NLS parameters following:
nls_language: SPANISH
nls_territory: SPAIN
Database Characterset: WE8ISO8859P1
National Characterset: AL16UTF16
OK!, now I have registered my schema (encoding='ISO8859-1') and I uploaded some examples files based in this XSD (encoding='ISO8859-1') to the XML DB Repository through WebDAV.
After this, I have closed the WebDAV session and I opened a new session with the File Manager. When I access to the folder that it contain the files, Oracle show a DISPLAYNAME_CONVERSION_ERROR. I have detected that this error is showed when the file contain 'ñ' character.
If I make the connection with a Web Browser (iExplorer or Firefox) all files names are showed correctly.
With Windows FTP Client, the 'ñ' is showed as '±'.
I tried the same with a commercial FTP Client and the names are showed correctly.
I was thinking a database characterset based in ISO-8859-1 will be a better standard option than others.
I must delete the current database and to create another with a database characterset based in WE8MSWIN1252 (or similar) or there is an easy way to solve this problem?.
In my previous configuration (10.2.0.1) all was working fine based in WE8WIN1252.
The operating system is Windows XP Service Pack 2.
Thanks in advanced,
David.
Mensaje editado por:
David2005There does not appear to be a fast, support way to change the database character set. However I was under the impression you were creating a new database anyway in which case I would recommend selecting the AL32UTF8 character set.
-
How change the encoding of xsd?
Hi.
I have an xsd file that has as encoding the ISO-8859-7. When importing it into XI the encoding is changed to ISO-8859-1.
To be more specific the
<?xml version="1.0" encoding="ISO-8859-7"?>
is converted to
<?xml version="1.0" encoding="ISO-8859-1"?>
How can I change this one?Hi,
Re: How to change the incoming xml to a different namespace -
Using the Soap Encoding schema within an XSD
Hi,
I am trying to create some XSDs based on the types from the auto-generated WSDLs in JDeveloper. However, I find that while the Array type works fine in the WSDL, I cannot seem to get it validate correctly in my XML schemas, possibly due to some namespace error.
The current code in the XSD is given as:
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/"/>
<xsd:complexType name="VesselQueryResult">
<xsd:all>
<xsd:element name="vesselNames" type="ArrayOfjava_lang_String"/>
</xsd:all>
</xsd:complexType>
<xsd:complexType name="ArrayOfjava_lang_String">
<xsd:complexContent>
<xsd:restriction base="SOAP-ENC:Array">
<xsd:attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:string[]"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
When I tried to add this XSD using as a user schema, however, below validation error is being displayed:
Error: Line 0, Column 0: Invalid reference: 'http://schemas.xmlsoap.org/soap/encoding/:Array'
I tried to qualify the SOAP-ENC namespace with the schemaLocation, but another error was displayed:
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/"
schemaLocation="http://schemas.xmlsoap.org/soap/encoding/"/>
oracle.xml.parser.schema.XSDException: Server returned HTTP response code: 407 for URL: http://schemas.xmlsoap.org/soap/encoding/
I am wondering how JDeveloper supports the SOAP-ENC schema for use in XSDs. Do I need to add the Soap Encoding schema as a user schema, or is there a way I might reference it similar to the way that auto-generated WSDLs seem to deal with it? Any information regarding this would be greatly appreciated.
Thank you and regards.I deleted the two lines of coding below:
utl_http.set_proxy('www-proxy', NULL);
utl_http.set_persistent_conn_support(TRUE);
and then I set the utl_http.set_persistent_conn_support() to False to get that error message. Seems like the website in question doesnt have the webservice anymore because the error has to do with the parsing of the WSDL file.... which probrably doesnt exist.
Im just trying to get a working example of using a third party webservice to return a value to be displayed in the database.... know of any good examples? The ones im using seem to be pretty out dated... the barnes and nobles example just times out.... -
Issue in Conversion of String to XML (xsd) elements.
Hi All,
Please help in resolving the below issue.Please help me ASAP
I am getting a strng value from Db adapter String= Mike,3453,USA
I need to convert the data into xml by using below xsd.
<?xml version="1.0" encoding='UTF-8' ?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.uss.com/htr/IHCM204/MainRec"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://www.uss.com/htr/IHCM204/MainRec"
attributeFormDefault="unqualified" nxsd:version="NXSD"
nxsd:stream="chars" nxsd:encoding="US-ASCII">
<element name="MainOutput">
<complexType>
<sequence>
<element name="Target" maxOccurs="unbounded">
<complexType>
<sequence>
<element name="name" type="string" nxsd:style="terminated" nxsd:terminatedBy="," />
<element name="sal" type="string" nxsd:style="terminated" nxsd:terminatedBy="," />
<element name="add" type="string" nxsd:style="terminated" nxsd:terminatedBy="," />
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
Regards,
AnaSay, for Example
If you are getting response from db adapter as abc,def,ghi then use an transform activity to split the string.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oraext="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<xsl:template match="/">
<ns:StringParsing>
<ns:Name>
<xsl:value-of select='substring(/ns:simpleelement/ns:dbString,1.0, oraext:last-index-within-string(/ns:simpleelement/ns:dbString,",") + 0.0)'/>
</ns:Name>
<ns:Address>
<xsl:value-of select='substring(/ns:simpleelement/ns:dbString,oraext:last-index-within-string(/ns:simpleelement/ns:dbString,",") + 2.0)'/>
</ns:Address>
</ns:StringParsing>
</xsl:template>
</xsl:stylesheet>
Let me know if it helps you.
Edited by: BK574 on May 14, 2013 11:31 AM
Edited by: BK574 on May 14, 2013 11:55 AM
Edited by: BK574 on May 14, 2013 12:48 PM -
Issue with xsd Data type mapping for collection of user defined data type
Hi,
I am facing a issue with wsdl for xsd mapping for collection of user defined data type.
Here is the code snippet.
sample.java
@WebMethod
public QueryPageOutput AccountQue(QueryPageInput qpInput)
public class QueryPageInput implements Serializable, Cloneable
protected Account_IO fMessage = null;
public class QueryPageOutput implements Serializable, Cloneable
protected Account_IO fMessage = null;
public class Account_IO implements Serializable, Cloneable {
protected ArrayList <AccountIC> fintObjInst = null;
public ArrayList<AccountIC>getfintObjInst()
return (ArrayList<AccountIC>)fintObjInst.clone();
public void setfintObjInst(AccountIC val)
fintObjInst = new ArrayList<AccountIC>();
fintObjInst.add(val);
Public class AccountIC
protected String Name;
protected String Desc;
public String getName()
return Name;
public void setName(String name)
Name = name;
For the sample.java code, the wsdl generated is as below:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions
name="SimpleService"
targetNamespace="http://example.org"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://example.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
>
<wsdl:types>
<xs:schema version="1.0" targetNamespace="http://examples.org" xmlns:ns1="http://example.org/types"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.org/types"/>
<xs:element name="AccountWSService" type="ns1:accountEMRIO"/>
</xs:schema>
<xs:schema version="1.0" targetNamespace="http://example.org/types" xmlns:ns1="http://examples.org"
xmlns:tns="http://example.org/types" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://examples.org"/>
<xs:complexType name="queryPageOutput">
<xs:sequence>
<xs:element name="fSiebelMessage" type="tns:accountEMRIO" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="accountEMRIO">
<xs:sequence>
<xs:element name="fIntObjectFormat" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageType" type="xs:string" minOccurs="0"/>
<xs:element name="fMessageId" type="xs:string" minOccurs="0"/>
<xs:element name="fIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fOutputIntObjectName" type="xs:string" minOccurs="0"/>
<xs:element name="fintObjInst" type="xs:anyType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="queryPageInput">
<xs:sequence>
<xs:element name="fPageSize" type="xs:string" minOccurs="0"/>
<xs:element name="fSiebelMessage" type="tns:accountEMRIO" minOccurs="0"/>
<xs:element name="fStartRowNum" type="xs:string" minOccurs="0"/>
<xs:element name="fViewMode" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://example.org" xmlns:ns1="http://example.org/types">
<import namespace="http://example.org/types"/>
<xsd:complexType name="AccountQue">
<xsd:sequence>
<xsd:element name="arg0" type="ns1:queryPageInput"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AccountQue" type="tns:AccountQue"/>
<xsd:complexType name="AccountQueResponse">
<xsd:sequence>
<xsd:element name="return" type="ns1:queryPageOutput"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="AccountQueResponse" type="tns:AccountQueResponse"/>
</schema>
</wsdl:types>
<wsdl:message name="AccountQueInput">
<wsdl:part name="parameters" element="tns:AccountQue"/>
</wsdl:message>
<wsdl:message name="AccountQueOutput">
<wsdl:part name="parameters" element="tns:AccountQueResponse"/>
</wsdl:message>
<wsdl:portType name="SimpleService">
<wsdl:operation name="AccountQue">
<wsdl:input message="tns:AccountQueInput" xmlns:ns1="http://www.w3.org/2006/05/addressing/wsdl"
ns1:Action=""/>
<wsdl:output message="tns:AccountQueOutput" xmlns:ns1="http://www.w3.org/2006/05/addressing/wsdl"
ns1:Action=""/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SimpleServiceSoapHttp" type="tns:SimpleService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="AccountQue">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port name="SimpleServicePort" binding="tns:SimpleServiceSoapHttp">
<soap:address location="http://localhost:7101/WS-Project1-context-root/SimpleServicePort"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
In the above wsdl the collection of fintObjInst if of type xs:anytype. From the wsdl, I do not see the xsd mapping for AccountIC which includes Name and Desc. Due to which, when invoking the web service from a different client like c#(by creating proxy business service), I am unable to set the parameters for AccountIC. I am using JAX-WS stack and WLS 10.3. I have already looked at blog http://weblogs.java.net/blog/kohlert/archive/2006/10/jaxws_and_type.html but unable to solve this issue. However, at run time using a tool like SoapUI, when this wsdl is imported, I am able to see all the params related to AccountIC class.
Can some one help me with this.
Thanks,
Sudha.Did you try adding the the XmlSeeAlso annotation to the webservice
@XmlSeeAlso({<package.name>.AccountIC.class})
This will add the schema for the data type (AccountIC) to the WSDL.
Hope this helps.
-Ajay -
Need help in creating XSD for a WSDL file to tranform given XML
Hi,
Please let me knoe if this is the right forum to post the query below:
We are trying to transform a XML output from a webservice using a XSD file. But we are facing problem as the XML output has some namespace issue and schema due to which transformation is not working fine. I am pasting the files below:
WSDL file used is
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/Projectix20/SOAPAccess" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/Projectix20/SOAPAccess" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/Projectix20/SOAPAccess">
<s:element name="ExecuteSQLToXML">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SQL" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="GUID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="ExecuteSQLToXMLResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLToXMLResult">
<s:complexType mixed="true">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="NewDataSet">
<s:complexType>
<s:choice>
<s:element minOccurs="0" maxOccurs="unbounded" name="Table1">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="10" name="FName" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:choice>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetDataTablePage">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SQL" type="s:string" />
<s:element minOccurs="1" maxOccurs="1" name="PageNumber" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="RecordsPerPage" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="GUID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetDataTablePageResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="GetDataTablePageResult">
<s:complexType mixed="true">
<s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetRecordCount">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="SQL" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="GUID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="GetRecordCountResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="GetRecordCountResult" type="s:int" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="UploadCanAtt">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="CanID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="Filename" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="bytesData" type="s:base64Binary" />
<s:element minOccurs="0" maxOccurs="1" name="GUID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="UploadCanAttResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="UploadCanAttResult" type="s:int" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DownloadCanAtt">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="CanAttID" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="GUID" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Password" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DownloadCanAttResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="DownloadCanAttResult" type="s:base64Binary" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="ExecuteSQLToXMLSoapIn">
<wsdl:part name="parameters" element="tns:ExecuteSQLToXML" />
</wsdl:message>
<wsdl:message name="ExecuteSQLToXMLSoapOut">
<wsdl:part name="parameters" element="tns:ExecuteSQLToXMLResponse" />
</wsdl:message>
<wsdl:message name="GetDataTablePageSoapIn">
<wsdl:part name="parameters" element="tns:GetDataTablePage" />
</wsdl:message>
<wsdl:message name="GetDataTablePageSoapOut">
<wsdl:part name="parameters" element="tns:GetDataTablePageResponse" />
</wsdl:message>
<wsdl:message name="GetRecordCountSoapIn">
<wsdl:part name="parameters" element="tns:GetRecordCount" />
</wsdl:message>
<wsdl:message name="GetRecordCountSoapOut">
<wsdl:part name="parameters" element="tns:GetRecordCountResponse" />
</wsdl:message>
<wsdl:message name="UploadCanAttSoapIn">
<wsdl:part name="parameters" element="tns:UploadCanAtt" />
</wsdl:message>
<wsdl:message name="UploadCanAttSoapOut">
<wsdl:part name="parameters" element="tns:UploadCanAttResponse" />
</wsdl:message>
<wsdl:message name="DownloadCanAttSoapIn">
<wsdl:part name="parameters" element="tns:DownloadCanAtt" />
</wsdl:message>
<wsdl:message name="DownloadCanAttSoapOut">
<wsdl:part name="parameters" element="tns:DownloadCanAttResponse" />
</wsdl:message>
<wsdl:portType name="SOAPAccessSoap">
<wsdl:operation name="ExecuteSQLToXML">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Executes a SQL statement and returns a generic XML document with results from SQL statement.</documentation>
<wsdl:input message="tns:ExecuteSQLToXMLSoapIn" />
<wsdl:output message="tns:ExecuteSQLToXMLSoapOut" />
</wsdl:operation>
<wsdl:operation name="GetDataTablePage">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Executes a SQL statement and returns a generic XML document with results from SQL statement.</documentation>
<wsdl:input message="tns:GetDataTablePageSoapIn" />
<wsdl:output message="tns:GetDataTablePageSoapOut" />
</wsdl:operation>
<wsdl:operation name="GetRecordCount">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Executes a SQL statement and returns a generic XML document with results from SQL statement.</documentation>
<wsdl:input message="tns:GetRecordCountSoapIn" />
<wsdl:output message="tns:GetRecordCountSoapOut" />
</wsdl:operation>
<wsdl:operation name="UploadCanAtt">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Uploads a text or binary attachment file for a Candidate record.</documentation>
<wsdl:input message="tns:UploadCanAttSoapIn" />
<wsdl:output message="tns:UploadCanAttSoapOut" />
</wsdl:operation>
<wsdl:operation name="DownloadCanAtt">
<documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Uploads a text or binary attachment file for a Candidate record.</documentation>
<wsdl:input message="tns:DownloadCanAttSoapIn" />
<wsdl:output message="tns:DownloadCanAttSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SOAPAccessSoap" type="tns:SOAPAccessSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="ExecuteSQLToXML">
<soap:operation soapAction="http://tempuri.org/Projectix20/SOAPAccess/ExecuteSQLToXML" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetDataTablePage">
<soap:operation soapAction="http://tempuri.org/Projectix20/SOAPAccess/GetDataTablePage" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetRecordCount">
<soap:operation soapAction="http://tempuri.org/Projectix20/SOAPAccess/GetRecordCount" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="UploadCanAtt">
<soap:operation soapAction="http://tempuri.org/Projectix20/SOAPAccess/UploadCanAtt" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="DownloadCanAtt">
<soap:operation soapAction="http://tempuri.org/Projectix20/SOAPAccess/DownloadCanAtt" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SOAPAccess">
<wsdl:port name="SOAPAccessSoap" binding="tns:SOAPAccessSoap">
<soap:address location="http://sales.projectix.com:81/customer/SOAPAccess.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
XSD file used for transformation is:
<?xml version = '1.0' encoding = 'UTF-8'?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" >
<xs:element name="ExecuteSQLToXMLResponse">
<xs:complexType>
<xs:sequence>
<xs:element ref="ExecuteSQLToXMLResult"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="parameters">
<xs:complexType>
<xs:sequence>
<xs:element ref="ExecuteSQLToXMLResponse"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ExecuteSQLToXMLResult">
<xs:complexType>
<xs:sequence>
<xs:element ref="NewDataSet"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="FNAME" type="xs:string"/>
<xs:element name="Table1">
<xs:complexType>
<xs:sequence>
<xs:element ref="FNAME"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="NewDataSet">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" ref="Table1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
XML Output from webservice call that we are trying to tranform using above XSD is:
<parameters >
<ExecuteSQLToXMLResponse xmlns = "http://tempuri.org/Projectix20/SOAPAccess" >
<ExecuteSQLToXMLResult >
<NewDataSet xmlns = "" >
<xs:schema xmlns:xs = "http://www.w3.org/2001/XMLSchema" xmlns:msdata = "urn:schemas-microsoft-com:xml-msdata" >
<xs:element name = "NewDataSet" msdata:IsDataSet = "true" >
<xs:complexType >
<xs:choice maxOccurs = "unbounded" >
<xs:element name = "Table1" >
<xs:complexType >
<xs:sequence >
<xs:element name = "FNAME" type = "xs:string" minOccurs = "0" ></xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
<Table1 >
<FNAME >
JOHN
</FNAME>
</Table1>
<Table1 >
<FNAME >
John
</FNAME>
</Table1>
<Table1 >
<FNAME >
John
</FNAME>
</Table1>
<Table1 >
<FNAME >
JOHN
</FNAME>
</Table1>
<Table1 >
<FNAME >
John
</FNAME>
</Table1>
</NewDataSet>
</ExecuteSQLToXMLResult>
</ExecuteSQLToXMLResponse>
</parameters>
I am not sure what we are missing in XSD file that the XML output is not getting transformed correctly...although we tried transforming the XML output by removing some information in XML output above and it was getting trasformed properly..
We remove
1. xmlns = "http://tempuri.org/Projectix20/SOAPAccess" from <ExecuteSQLToXMLResponse xmlns = "http://tempuri.org/Projectix20/SOAPAccess" >
2. xmlns = "" from <NewDataSet xmlns = "" >
3 remove <parameters > and </parameters > tags from output and the XML Output is getting tranformed correctly.
Please let us know if we can transform the XML Output without requiring these removals.
Thanks,
PawanCould you clarify some things? You are saying you are trying to transform the xml output of a webservice with an xsd, but an xsd is a schema that describes the allowed format of a xml file. If you want to transform xml from one format to an other (from one xsd to an other) you have to use a xsl file. You can make and test this with JDeveloper. Are you calling the webservice from esb or bpel?
Kind Regards,
Andre -
Question regarding xsd and shredding
All,
I have the following xsd and xml file, I register the xsd in xmldb and create a resource from the xml file. Upon registration of the xsd, the proper (I think) tables are created and upon creating the resource the primary table seems to have a row in it. I am having a problem trying to figure out how to get the values out of the types that have the enumeration values. Any help would be appreciated.
$sqlplus / as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Tue Aug 28 10:40:41 2012
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
SQL> select * from V$VERSION
2 /
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for HPUX: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
SQL>
xsd:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:storeVarrayAsTable="true">
<xs:element name="ITEMS" xdb:defaultTable="TMP_ITEMS">
<xs:complexType xdb:SQLType="TMP_ITEMS_T" xdb:maintainDOM="false">
<xs:sequence>
<xs:element name="ITEM_GROUP" xdb:SQLCollType="ITEM_GROUP_ROW_NTT">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="GROUP_A"/>
<xs:enumeration value="GROUP_B"/>
<xs:enumeration value="GROUP_C"/>
<xs:enumeration value="GROUP_D"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element ref="ITEM" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ITEM" xdb:defaultTable="TMP_ITEM" xdb:SQLType="TMP_ITEM_T" xdb:maintainDOM="false">
<xs:complexType>
<xs:sequence>
<xs:element name="ITEM_NUMBER" type="xs:string"/>
<xs:element name="ITEM_STATUS">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="ACTIVE"/>
<xs:enumeration value="INACTIVE"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ITEM_DATE" type="xs:string"/>
<xs:element name="ITEM_ID" type="xs:string"/>
<xs:element ref="ITEM_SUBGROUP_1" maxOccurs="unbounded"/>
<xs:element ref="ITEM_SUBGROUP_2" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ITEM_SUBGROUP_1" xdb:defaultTable="TMP_ITEM_SUBGROUP_1" xdb:SQLType="TMP_ITEM_SUBGROUP_1_T" xdb:maintainDOM="false">
<xs:complexType>
<xs:sequence>
<xs:element name="SUBGROUP_1_ID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ITEM_SUBGROUP_2" xdb:defaultTable="TMP_ITEM_SUBGROUP_2" xdb:SQLType="TMP_ITEM_SUBGROUP_2_T" xdb:maintainDOM="false">
<xs:complexType>
<xs:sequence>
<xs:element name="SUBGROUP_2_ID" type="xs:string"/>
<xs:element name="SUBGROUP_2_TYPE">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SUBGROUP_TYPE_2_TYPE_A"/>
<xs:enumeration value="SUBGROUP_TYPE_2_TYPE_B"/>
<xs:enumeration value="SUBGROUP_TYPE_2_TYPE_C"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>xml:
<?xml version="1.0"?>
<ITEMS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="tmp_items.xsd">
<ITEM_GROUP>GROUP_A</ITEM_GROUP>
<ITEM>
<ITEM_NUMBER>1</ITEM_NUMBER>
<ITEM_STATUS>ACTIVE</ITEM_STATUS>
<ITEM_ID>0000000123</ITEM_ID>
<ITEM_SUBGROUP_1>
<SUBGROUP_1_ID>SG1_000000987</SUBGROUP_1_ID>
</ITEM_SUBGROUP_1>
<ITEM_SUBGROUP_2>
<SUBGROUP_2_ID>SG2_000000987</SUBGROUP_2_ID>
<SUBGROUP_2_TYPE>SUBGROUP_TYPE_2_TYPE_A</SUBGROUP_2_TYPE>
</ITEM_SUBGROUP_2>
</ITEM>
<ITEM>
<ITEM_NUMBER>2</ITEM_NUMBER>
<ITEM_STATUS>INACTIVE</ITEM_STATUS>
<ITEM_ID>0000000456</ITEM_ID>
<ITEM_SUBGROUP_1>
<SUBGROUP_1_ID>SG1_000000654</SUBGROUP_1_ID>
</ITEM_SUBGROUP_1>
<ITEM_SUBGROUP_2>
<SUBGROUP_2_ID>SG2_000000654</SUBGROUP_2_ID>
<SUBGROUP_2_TYPE>SUBGROUP_TYPE_2_TYPE_A</SUBGROUP_2_TYPE>
</ITEM_SUBGROUP_2>
</ITEM>
</ITEMS>registration of xsd:
BEGIN
IF DBMS_XDB.CREATERESOURCE(
abspath => '/public/tmp/tmp_items.xsd',
data => BFILENAME ('XSD_DIR','tmp_items.xsd')
THEN
DBMS_XMLSCHEMA.REGISTERSCHEMA(
schemaurl => 'tmp_items.xsd',
schemadoc => sys.UriFactory.getUri('/public/tmp/tmp_items.xsd')
COMMIT;
END IF;
END;creation on xml resource:
declare
v_return BOOLEAN;
BEGIN
v_return := DBMS_XDB.CREATERESOURCE(abspath => '/public/tmp/tmp_items.xml', data => BFILENAME('XML_DIR', 'tmp_items.xml'));
END;query the high level:
select xml.item_number as item_number,
extractvalue(value(i),'/ITEMS/ITEM_GROUP') item_status
from tmp_items i,
table(i.xmldata.item) xmlquery the sub_group for one high level:
select *
from table(
select xml.ITEM_SUBGROUP_2
from tmp_items i,
table(i.xmldata.item) xml
where xml.item_number = '1')When I execute the above query, I can't seem to extract the value out of the subgroup_2_type element. I used the extractvalue function to get it out of the high level, but can't seem to get it right here.
Thanks
Eric
Edited by: Eric Schrauth on Aug 28, 2012 8:39 AMHave to create a base view on the elements that will always be there and other views on the items that might not and query them appropriately. Right?Not necessarily.
The usual approach is to use an OUTER JOIN :
SELECT x1.item_number
, x1.item_status
, x2.*
FROM tmp_items t
, XMLTable(
'/ITEMS/ITEM'
passing t.object_value
columns item_number varchar2(15) path 'ITEM_NUMBER'
, item_status varchar2(15) path 'ITEM_STATUS'
, item_subgroup_2 xmltype path 'ITEM_SUBGROUP_2'
) x1
, XMLTable(
'/ITEM_SUBGROUP_2'
passing x1.item_subgroup_2
columns subgroup_2_id varchar2(15) path 'SUBGROUP_2_ID'
, subgroup_2_type varchar2(15) path 'SUBGROUP_2_TYPE'
) (+) x2
;Or the equivalent with ANSI JOIN :
SELECT x1.item_number
, x1.item_status
, x2.*
FROM tmp_items t
, XMLTable(
'/ITEMS/ITEM'
passing t.object_value
columns item_number varchar2(15) path 'ITEM_NUMBER'
, item_status varchar2(15) path 'ITEM_STATUS'
, item_subgroup_2 xmltype path 'ITEM_SUBGROUP_2'
) x1
LEFT OUTER JOIN
XMLTable(
'/ITEM_SUBGROUP_2'
passing x1.item_subgroup_2
columns subgroup_2_id varchar2(15) path 'SUBGROUP_2_ID'
, subgroup_2_type varchar2(15) path 'SUBGROUP_2_TYPE'
) x2
ON 1 = 1
; -
Transformation issue with EDI 841 xsd generated by document editor
Hi,
I was trying to create a B2B Outbound interface with Doc Standard as EDI X12. When our custom payload for item is being mapped to the xsd of doc type 841 (generated using standard ecs with Oracle Doc Editor), the xengine is behaving a little weird. It's generating a file in the output directory for sure, but it's not having all the data I mapped. For Example, I wanted to have a datafile as below:
ST~841~000000001
SPI~00~~~~~~04~MF
AMT~LI~0
HL~1~~I~0
SPI~ZZ
LIN~~PN~ABC
MSG~ABC
PID~F~~~~ABC
REF~ZZ~BaseUOMCode~EA~ZZ>EACH
SE~38~000000001
For which I mapped in xslt quite a few elements and corresponding payload that is coming in the console application message is as below:
<?xml version = '1.0' encoding = 'UTF-8'?>
<Transaction-841 xmlns:ns10="urn:oracle:b2b:X12/V4010/841" Standard="X12"
xmlns="urn:oracle:b2b:X12/V4010/841">
<ns10:Segment-ISA>
<ns10:Element-I12/>
</ns10:Segment-ISA>
<ns10:Segment-GS>
<ns10:Element-28/>
</ns10:Segment-GS>
<ns10:Segment-ST>
<ns10:Element-143>841</ns10:Element-143>
<ns10:Element-329>1</ns10:Element-329>
</ns10:Segment-ST>
<ns10:Loop-HL>
<ns10:Segment-HL>
<ns10:Element-628>1</ns10:Element-628>
<ns10:Element-735>I</ns10:Element-735>
<ns10:Element-736>0</ns10:Element-736>
</ns10:Segment-HL>
<ns10:Loop-SPI>
<ns10:Segment-SPI>
<ns10:Element-786>ZZ</ns10:Element-786>
</ns10:Segment-SPI>
<ns10:Segment-LIN>
<ns10:Element-235>PN</ns10:Element-235>
<ns10:Element-234>ABC</ns10:Element-234>
</ns10:Segment-LIN>
<ns10:Segment-MSG>
<ns10:Element-933>ABC</ns10:Element-933>
</ns10:Segment-MSG>
</ns10:Loop-SPI>
<ns10:Loop-PID>
<ns10:Segment-PID>
<ns10:Element-349>F</ns10:Element-349>
<ns10:Element-352>ABC</ns10:Element-352>
</ns10:Segment-PID>
</ns10:Loop-PID>
<ns10:Loop-REF>
<ns10:Segment-REF>
<ns10:Element-128>ZZ</ns10:Element-128>
<ns10:Element-127>BaseUOMCode</ns10:Element-127>
<ns10:Element-352>Ea</ns10:Element-352>
<ns10:Composite-C040>
<ns10:Element-128>ZZ</ns10:Element-128>
<ns10:Element-127>Each</ns10:Element-127>
</ns10:Composite-C040>
</ns10:Segment-REF>
</ns10:Loop-REF>
</ns10:Loop-HL>
<ns10:Segment-SE>
<ns10:Element-96>38</ns10:Element-96>
<ns10:Element-329>1</ns10:Element-329>
</ns10:Segment-SE>
<ns10:Segment-GE>
<ns10:Element-28/>
</ns10:Segment-GE>
<ns10:Segment-IEA>
<ns10:Element-I12/>
</ns10:Segment-IEA>
</Transaction-841>
However when the file is getting generated, the content misses the LIN Segment and below REF segment. It comes as below:
ISA~00~ ~00~ ~ZZ~079763140 ~ZZ~V1 ~140901~1118~U~00401~100000012~1~T~>
GS~GS~079763140~V1~20140901~1118~1012~X~004010
ST~841~000000001
SPI~00~~~~~~04~MF
AMT~LI~0
HL~1~~I~0
SE~38~000000001
GE~1~1012
IEA~1~100000012
Below are missing:
SPI~ZZ
LIN~~PN~ABC
MSG~ABC
PID~F~~~~ABC
REF~ZZ~BaseUOMCode~EA~ZZ>EACH
We are on 11G. What could go wrong here? Any help is appreciated.
Regards,
SubhadeepThe problem is resolved after re-upload of ecs and xsd. There was a version mismatch and keeping validation off was generating half cooked file. Thanks for reading.
Regards,
Subhadeep -
XSD OTD compilefailure String literal not properly closed by double-quote
Java CAPS 5.1.3
I have created a XSD to describe a simple XML file. After this I created an OTD from the exported XSD file.
This OTD is being used in a JCD. During the build of the Deployment Profile I get the error: :Compile failed: xsd.XSD_MB235401907.X_all_B: Line 69: String literal is not properly closed by a double-quote
All steps have been preferformed within the same eDesigner and the same repository.
I have verified the XSD file with netbeans and can not see a problem with the file itself.
Any ideas to resolve this compile failure?
The XSD is:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://ams1saa011:12000/repository/repository/Recieve/MessageBroker/WISE_WTE/repository1423024:117d46f486a:-8000/XSDDefinition1" targetNamespace="http://ams1saa011:12000/repository/repository/Recieve/MessageBroker/WISE_WTE/repository1423024:117d46f486a:-8000/XSDDefinition1">
<xsd:element name="MessageBroker">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="IN" maxOccurs="unbounded">
<xsd:complexType>
<xsd:all>
<xsd:element name="MSGFN" type="xsd:string" default="IN"/>
<xsd:element name="DIR" type="xsd:string" default="\"/>
<xsd:element name="FILEMASK"
type="xsd:string" default="*.DAT"/>
<xsd:element name="MAPID" type="xsd:string" default="MS000"/>
<xsd:element name="RCVPRN" type="xsd:string"/>
<xsd:element name="RCVPRT" type="xsd:string"/>
<xsd:element name="RCVPFC" type="xsd:string"/>
<xsd:element name="SNDPRN" type="xsd:string"/>
<xsd:element name="SNDPRT" type="xsd:string"/>
<xsd:element name="MESTYP" type="xsd:string"/>
<xsd:element name="MESCOD" type="xsd:string"/>
<xsd:element name="MESFCT" type="xsd:string"/>
<xsd:element name="TEST" type="xsd:boolean" nillable="true"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="dateTime" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
</xsd:schema>The complete error stack trace is:
com.stc.codegen.framework.model.CodeGenException: error generating otd for CMap1_jcdMB_Recieve_SAP_Inbound1:Compile failed: xsd.XSD_MB235401907.X_all_B: Line 69: String literal is not properly closed by a double-quote
at com.stc.codegen.OTDImpl.model.OTDCodeletFactory$OTDCodelet.postFileGeneration(OTDCodeletFactory.java:767)
at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.processCodelets(CodeGenFrameworkImpl.java:653)
at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.process(CodeGenFrameworkImpl.java:1544)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:405)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:308)
at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.traverseDeployment(DeploymentVisitorImpl.java:268)
at com.stc.codegen.driver.module.DeploymentBuildAction.loadCodeGen(DeploymentBuildAction.java:923)
at com.stc.codegen.driver.module.DeploymentBuildAction.access$1000(DeploymentBuildAction.java:174)
at com.stc.codegen.driver.module.DeploymentBuildAction$1.run(DeploymentBuildAction.java:599)
at org.openide.util.Task.run(Task.java:136)
at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:599)
Caused by: java.lang.RuntimeException: Compile failed: xsd.XSD_MB235401907.X_all_B: Line 69: String literal is not properly closed by a double-quote
at com.stc.javac.Javac.compile(Javac.java:227)
at com.stc.otd.codegen.BaseXsdDtdGenerator.compileFromJarfile(BaseXsdDtdGenerator.java:254)
at com.stc.otd.codegen.BaseXsdDtdGenerator.compile(BaseXsdDtdGenerator.java:52)
at com.stc.otd.xsd.codegen.XsdParserGenerator.compile(XsdParserGenerator.java:182)
at com.stc.otd.codegen.BaseXsdDtdGenerator.generate(BaseXsdDtdGenerator.java:166)
at com.stc.otd.codegen.BaseXsdDtdGenerator.generate(BaseXsdDtdGenerator.java:90)
at com.stc.codegen.OTDImpl.model.CollabOTDGenerator.generateCollabOTDJavaFiles(CollabOTDGenerator.java:233)
at com.stc.codegen.OTDImpl.model.OTDCodeletFactory$OTDCodelet.processOTDJars(OTDCodeletFactory.java:861)
at com.stc.codegen.OTDImpl.model.OTDCodeletFactory$OTDCodelet.postFileGeneration(OTDCodeletFactory.java:666)
... 10 moreYou may need to escape the default slash "\\".
I'd suggest importing the xsd into the jcaps xml schema editor and verifying that way and then creating the otd by node export.
Regards,
Rupert -
To generate xml code in encoding as specified in system profile options
Hi,
i have a customer bug wherein the report page which is generated after a particular process, which is a .xml file, does not open because we have special characters which are not getting encoded properly!..
the probable solution to this would be to encode the .xml file in the encoding format specified in system profile options.
After the content generation the following code is used to generate the tags and the .xml page:
DBMS_XMLGEN.setRowSetTag(l_qryCtx,'INVOICE_SET');
DBMS_XMLGEN.setRowTag(l_qryCtx, 'INVOICE_RECORD');
DBMS_XMLGEN.setBindValue(l_qryCtx,'BATCH_ID', p_batch_id);
DBMS_XMLGEN.setBindValue(l_qryCtx,'SUPPLIER_ID', rec.supplier_id);
DBMS_XMLGEN.setBindValue(l_qryCtx,'SITE_ID', rec.site_id);
l_result_clob :=DBMS_XMLGEN.GETXML(l_qryCtx);
l_result_clob := substr(l_result_clob,instr(l_result_clob,'>')+1);
l_temp_invoice_count := DBMS_XMLGEN.getNumRowsProcessed(l_qryCtx);
l_invoice_count := l_invoice_count + l_temp_invoice_count;
DBMS_XMLGEN.closeContext(l_qryCtx);
clob_to_file(l_result_clob);
here we have a transaction type in portugese like Nota de Crédito
and the issue summary is as follows
It contains some foreign language symbols which are not encoded in UTF-8 format hence IE is showing the error. Even though in mozilla the file is completely opened but the same foreign language symbol is not shown. So the error exists in all the browsers.
can you please suggest how the encoding maybe done so as to avoid the above problem!...
and also how to include the encoding as per mentioned in the system profile options.Hi,
>>>The XSD doesn't have any messages only simple and complex types - I can't seem to relate (via drag and drop) them to a data or message type to generate the required objects.
maybe it has some reference inside to some other types which you did not get?
if so you need to import into IR/ESR all files and put the correct reference (external archives)
this would be the proper way to get the file generated according to the xml schema
Regards,
Michal Krawczyk -
Exception While importing or unable to browse the xsd to a BPEL Project
Dear All..,
I am having an issue wjile importing the schema to a BPEL project. It says that unable to load the schema.
Even When I try to choose the schema through edit variable option, and to mention the URI of schema location, on click of the search button, the Jdev hangs for ever. Why this scenario is happening.
I replaced the JDEV copy i have, still its shows the same issue. Is it a problem from the OS. The Jdev Version is 1.3.4.1
Please update...
Many Thanks in advance...
Edited by: santark on May 7, 2009 12:38 PMThank you for your immediate resposne...
Please find the xsd below:
<?xml version="1.0" encoding="Windows-1252"?>
<xsd:schema xmlns="http://xmlns.hdnl.com/EnterpriseObject/Core/DiaryCancellation"
elementFormDefault="qualified"
targetNamespace="http://xmlns.hdnl.com/EnterpriseObject/Core/DiaryCancellation"
xmlns:types="http://xmlns.hdnl.com/EnterpriseObject/Core/Types"
xmlns:comm="http://xmlns.hdnl.com/EnterpriseObject/Core/CommonTypes"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import schemaLocation="DataTypes.xsd"
namespace="http://xmlns.hdnl.com/EnterpriseObject/Core/CommonTypes"/>
<xsd:import schemaLocation="CommonTypes.xsd"
namespace="http://xmlns.hdnl.com/EnterpriseObject/Core/Types"/>
<xsd:complexType name="DiaryCancellationRequestType">
<xsd:sequence>
<xsd:element name="BookingId" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="types:StringType">
<xsd:maxLength value="32"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="UserId" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="types:StringType">
<xsd:maxLength value="32"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="DiaryCancellationResponseType">
<xsd:sequence>
<xsd:element name="BookingId" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="types:StringType">
<xsd:maxLength value="32"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element minOccurs="0" name="ErrorInfo" type="comm:ErrorType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="DiaryCancellationRequest" type="DiaryCancellationRequestType"/>
<xsd:element name="DiaryCancellationResponse"
type="DiaryCancellationResponseType"/>
</xsd:schema>
I have the DataTypes.xsd and CommonTypes.xsd are there in the same location
Please update... -
How to handle rpc/encoded style messages using BizTalk?
I am integrating with a lot of services and one of our customers has a service with rpc/encoded style
I could consume and generate schema from their wsdl file via BizTalk consume WCF wizard.
Once I am trying to call the service with request message that generated from the schema, it is giving an error that can not desterilize the first element of the message.
No Deserializer found to deserialize a 'FieldName' using encoding style 'null'
I compared the stub xml request message from SaopUI and I noticed that the xml expecting the data type with the element like this .
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<sozlesmeNo xsi:type="xsd:string">?</sozlesmeNo>
<bankaKodu xsi:type="xsd:string">?</bankaKodu>
<anahtar xsi:type="xsd:string">?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
On the other hand, I got the request of the message from Fiddler using the BizTalk , and the generate xml of the BizTalk schema without the data type.
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama>
<sozlesmeNo>?</sozlesmeNo>
<bankaKodu>?</bankaKodu>
<anahtar>?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
In SoapUi, if I remove a datatype from the message, I will get same error from the BizTalk request.
I read some articles that rpc/encoded style are not supported but I am not sure and these articles are not clear.
I also read that it was supported with Soap adapter but now it is deprecated.
So, Is there any one has an experience in rpc/encoded style messages and how to handle these message in BizTalk or is there any work around to handle these messages?
Your inputs really appreciate it.
Thanks in advance,
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As AnswerHi,
Please refer to the document which might help you:
#RPC/Encoded Style
http://www.c-sharpcorner.com/UploadFile/martinkropp/DesigningInteroperableWebService11232005044847AM/DesigningInteroperableWebService.aspx -
JDev generated webservices encodes XML output from PL/SQL procedure
I have a PL/SQL packaged procedure which takes some input parameters and produces one output parameter. The output parameter is of type CLOB and after the procedure has run, it contains a big piece of XML data.
Using JDeveloper 10.1.3.1, I've published this packaged procedure as a webservice. The generated webservice is fine and works, except for one tiny little issue: the XML that is taken from the output parameter is encoded.
Here is an example of the SOAP message that the webservice returns:
<?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://gbv0300u/GBV0300U.wsdl/types/"><env:Body><ns0:gbv0300uResponse
Element><ns0:result><ns0:obvglijstOut> & gt;type>GBV0001& gt ;/type& lt;
& gt;diensten& lt;
& gt;dienst>some value& gt;/dienst& lt;
& gt;/diensten& lt;
</ns0:obvglijstOut></ns0:result></ns0:gbv0300uResponseElement></env:Body></env:Envelope>
(I've manually added an extra space between the & and lt; or gt; to make sure a browser will not translate it into a < or >!)
The contents of the <ns0:obvglijstOut> element are filled with the output parameter from the PL/SQL package.
How can I change the generated webservice, so the output from the PL/SQL package is used as is instead of being encoded?Update: I've tested a bit more by adding some output statements to the java code that JDeveloper generated. I'm now 100% sure the PL/SQL code gives the XML data correctly to the webservice.
At this moment my guess is that somewhere in the WSDL definition there is something that enables the encoding of the data. But I'm not sure.
Any help is greatly appreciated. -
Can I use Non-standard XSD Data Types in my XSD; if so how?
Please help if you can, this is a complex question, so bear with me.
Also note that I am in Livecycle 8.2 ES (not ES2 or higher).
I am working on creating XSD schemas to map to form objects.
I have created one master schema document that is wired into multiple forms, and I have one separate schema for reusable form objects, that I refer to as a "common node".
All of my individual form schemas are brought together in this one Master Schema via the use of include statements.
EXAMPLE: This is like my Master Schema
<?xml version="1.0" encoding="UTF-8"?>
<!--W3C Schema written by Benjamin P. Lyons - Twin Technologies July 2010-->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" >
<xs:include schemaLocation="./commonElementsNode.xsd" />
<xs:include schemaLocation="./form1111.xsd" />
<xs:include schemaLocation="./form2222.xsd" />
<xs:include schemaLocation="./form3333.xsd" />
<xs:element name="form">
<xs:complexType>
<xs:sequence>
<xs:element ref="commonElementsNode" />
<xs:element ref="form1111" />
<xs:element ref="form2222" />
<xs:element ref="form3333" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
This works fine.
I can load this up in Designer in the Data View and everything appears in the Data View hierarchy correctly, with "form" as the top node.
And as long as I use standard "xs:" data types - everything works great. So if I go into LiveCycle Designer and I go to File --> Form Properties --> Preview --> Generate Preview Data and generate dummy XML data - it respects my XSD conventions.
Now here is where the problem arises:
In these schemas, I need to define the data types.
The client I am working for needs me to use their data types.
These data types are not standard xs: data types, like "xs:string" or "xs:date".
Rather, the data types are ones that have been defined in other schemas and reserved to a namespace.
For instance, rather than use xs:date I need to use something like: "myns:DateType"
This "myns:DateType" is defined as:
<xs:complexType name="DateType">
<xs:simpleContent>
<xs:extension base="xs:date">
<xs:attribute name="format" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation xml:lang="en">
<mydoc:Name>Date Format Text</mydoc:Name>
<mydoc:Definition>The format of the date content</mydoc:Definition>
<mydoc:PrimitiveType>string</mydoc:PrimitiveType>
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
Note that I have redacted this data type slightly and changed the namespace to protect the anonymity of my client, but we can assume that their data type is valid and currently in use with other systems.
It conforms to W3 standards.
Note also how this type is an enumeration of the base type "xs:date".
This is defined in a schema called something like "MyCoreTypes.xsd"
There is a namespace reservation in this file that looks something like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"
xmlns:myns="http://clinetname.com/schemas/mycoretypes" >
So there is a name space reservation there.
In my aforementioned "Master Schema" file, I have an include statement that looks like this:
<xs:include namespace="http://clinetname.com/schemas/mycoretypes" schemaLocation="./MyCoreTypes.xsd" />
(let's assume that the schema is in the same folder, as the Master Schema, so we can use the "./" relative path.)
Now the problems is that in all my forms, where I have a myns:DateType (e.g.: in form1111, a "Date of Birth" element that looks like this: <xs:element name="OwnerBirthDt" type="myns:DateType"/> ) the XSD is not respected when the XML dummy data is generated in LiveCycle Designer implying that the XSD's data types are not being recognized properly.
Has anyone had this problem before?
Is there a solution?
Is it even possible to use these kind of include or import references in LiveCycle to define a data type other that the standard "xs:" data types?
Please let me know - it would be greatly appreciated.
I am more than willing to clarify the question further if others are willing to help.
Thanks -
Ben Lyonsprf.kishorekumar wrote:
i came here with a hope that I would definitely get some help.
pls.. some one reply1) You got some help. No where do I see thanks or acknowledgment for the information given.
2) Please remember that people on the forum help others voluntarily, it's not their job.
3) Google can often help you here if the forum can't. Using Google I found this interesting link:
http://today.java.net/pub/a/today/2004/05/24/html-pt1.html
It discusses the Swing HTML EditorKit as well as some other free HTML renderers.
Edited by: petes1234 on Oct 24, 2007 7:29 PM
Maybe you are looking for
-
How do I make my accordion spry not "jump" or "hiccup" in IE??
Ok, sorry you guys, I'm a newbie. It seems that no matter what I do, I can't get the accordion to co-operate with Internet Explorer. It has always jumped when tabs are clicked and then settles down. It's rather irritating and I would like to fix it.
-
I am trying to load an external library with about 700 gigs of music into iTunes on my mac, but of course my mac's inter hard drive is much less than that. Is there a way I can load the music onto iTunes without importing it into my computer? I use t
-
Work path of 'hollow' characters?
How do I make a work path of a character that consists of a loop (letters O, O, and P in LOOP for example) so that i get the inner and outer walls of a character, take O for example, instead of a solid O? O (the black area of the O should be filled w
-
Errors while compiling AIA project in Jdeveloper 11.1.1.5.0
Hi I am using JDeveloper 11.1.1.5.0 for my AIA project. I created one ReqABCS using ServiceConstuctor in Jdev and at time of deployment I got the following errors. [scac] error: in SyncItemLotEbizReqABCSImplProcess.bpel(81): XML element "{http://xmln
-
Frieght charges include for particular customer and also include in invoice
Hi, How to include frieght charges for the particular customers towards freight charges recovered from them. Credit into Freight Charges received (GL account No: 310010 ). Frieght amount should shown in invoice also. How to do that above issue. Pleas