Validating WSDL with schema imports
Hello,
i'm trying to validate a WSDL that uses a schema import construction, like
<wsdl:types>
<xsd:schema>
<!-- import foo.xsd which defines BarType-->
<xsd:import namespace="http://foo" schemaLocation="http://localhost/foo.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="MyMessage">
<wsdl:part name="bar" type="foo:BarType"/>
</wsdl:message>
I keep getting the error :
Validating foo.wsdl
Schema type not found: QName(http://foo, BarType)
Validate WSDL: has errors.If I paste the content of foo.xsd inline in the wsdl file, it works ok.
The wsdl file validates in XMLSpy; it can even successfully generate SOAP requests from it.
Am I wrong somewhere ?
Did anyone succeed in importing an external schema inside a wsdl file with JDev ?
thx.
Does anyone know if this is working in JDeveloper 10.1.3?
Another (relared) question: we use multiple wsdl files to define our web services (according to the Venetian Blind design). Since the project uses WebLogic as AS we used their mechanism to generate the webservice. The only thing is that generating a stub via WebLogic JAX-RPC fails due to namespace errors.
When I try to generate a stub based on the JDeveloper 10.1.3 wizards using the top-level wsdl (the one importing other wsdl's) I get an invalid wsdl message and the options in the wizard are disabled. Anyone know whether multiple wsdl's are supported in JDeveloper 10.1.3?
Ronald
Similar Messages
-
Problem Import WSDL with XSD import Schema
Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
<xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
<xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
</xsd:schema>
</wsdl:types>
<wsdl:message name="iVistaHO_AddItemHO_InputMessage">
<wsdl:part name="parameters" element="tns:AddItemHO" />
</wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards -
Lax validation errors on schema import ('version' exceeds maximum length)
I have a schema as per below. I'm trying to import it into Oracle 10.2.0.2.0. However, I'm getting the following lax validation error:
Error loading ora_business_rule.xsd:ORA-30951: Element or attribute at Xpath /schema[@version] exceeds maximum length
I can fix it by modifying the attribute and shortening it but I'd like to know why it's occuring. Insofar as I can tell there is no imposed limit on the size of schema attributes according to the W3C standard. Which then makes me wonder: does Oracle impose limits on the length of all attributes or is this specific to 'version' ? If there is a limit, what is the upper bound (in bytes) ? Where is this documented?
Cheers,
Daniel
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:br="http://foo.com/BusinessRule_PSG_V001" targetNamespace="http://foo.com/BusinessRule_PSG_V001" elementFormDefault="qualified" attributeFormDefault="unqualified" version="last committed on $LastChangedDate: 2006-05-19 11:00:52 +1000 (Fri, 19 May 2006) $">
<xs:element name="edit">
<xs:complexType>
<xs:sequence>
<xs:element name="edit_id" type="xs:string"/>
<xs:element ref="br:business_rule"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="derivation">
<xs:complexType>
<xs:sequence>
<xs:element name="derivation_id" type="xs:string"/>
<xs:element ref="br:derivation_type"/>
<xs:element ref="br:business_rule"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="derivation_type">
<xs:simpleType>
<xs:restriction base="xs:NMTOKENS">
<xs:enumeration value="complex"/>
<xs:enumeration value="format"/>
<xs:enumeration value="formula"/>
<xs:enumeration value="recode"/>
<xs:enumeration value="SAS code"/>
<xs:enumeration value="transfer"/>
<xs:enumeration value="count"/>
<xs:enumeration value="sum"/>
<xs:enumeration value="max"/>
<xs:enumeration value="min"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="business_rule"></xs:element>
</xs:schema>Opps -- Sorry it's a decision we took when looking at Version
When we registered the Schema for Schemas during XDB bootstrap the Version attriubte was mapped to varchar2(12).
SQL> desc xdb.xdb$schema_T
Name Null? Type
SCHEMA_URL VARCHAR2(700)
TARGET_NAMESPACE VARCHAR2(2000)
VERSION VARCHAR2(12)
NUM_PROPS NUMBER(38)
FINAL_DEFAULT XDB.XDB$DERIVATIONCHOICE
BLOCK_DEFAULT XDB.XDB$DERIVATIONCHOICE
ELEMENT_FORM_DFLT XDB.XDB$FORMCHOICE
ATTRIBUTE_FORM_DFLT XDB.XDB$FORMCHOICE
ELEMENTS XDB.XDB$XMLTYPE_REF_LIST_T
SIMPLE_TYPE XDB.XDB$XMLTYPE_REF_LIST_T
COMPLEX_TYPES XDB.XDB$XMLTYPE_REF_LIST_T
ATTRIBUTES XDB.XDB$XMLTYPE_REF_LIST_T
IMPORTS XDB.XDB$IMPORT_LIST_T
INCLUDES XDB.XDB$INCLUDE_LIST_T
FLAGS RAW(4)
SYS_XDBPD$ XDB.XDB$RAW_LIST_T
ANNOTATIONS XDB.XDB$ANNOTATION_LIST_T
MAP_TO_NCHAR RAW(1)
MAP_TO_LOB RAW(1)
GROUPS XDB.XDB$XMLTYPE_REF_LIST_T
ATTRGROUPS XDB.XDB$XMLTYPE_REF_LIST_T
ID VARCHAR2(256)
VARRAY_AS_TAB RAW(1)
SCHEMA_OWNER VARCHAR2(30)
NOTATIONS XDB.XDB$NOTATION_LIST_T
LANG VARCHAR2(4000)
SQL> -
IllegalArgumentException - error validating xml with schema
I'm trying to validate an XML document using the following:
JAXP 1.2
Xerces 1.4.4
JDK 1.4.1
The xml is valid and I can confirm it with XML Spy when I point it to the schema definition. But, I get an IllegalArgumentException when I try to do it in my class.
Here's the code...
public static final String JAXP_SCHEMA_LANGUAGE = "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
public static final String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";
public static final String CIS_SCHEMA = "D:\\dev\\xml\\cis.xsd";
public static final String[] SCHEMAS = { W3C_XML_SCHEMA, CIS_SCHEMA };
private static DocumentBuilderFactory dbf;
private static DocumentBuilder db;
try {
dbf.setNamespaceAware(true);
dbf.setValidating(true);
dbf.setAttribute(JAXP_SCHEMA_LANGUAGE, SCHEMAS);
} (catch ...) {
I get the following error:
java.lang.IllegalArgumentException: http://java.sun.com/xml/jaxp/properties/schemaLanguage
Any ideas?When I tried this with Xerces SAX, I got---
org.xml.sax.SAXNotRecognizedException: http://java.sun.com/xml/jaxp/properties/schemaLanguage
Maybe Xerces has not implemented the schemaLanguage property.
I have been successfully using Xerces-dependent properties to do validation:
XMLReader parser = saxParser.getXMLReader();
parser.setFeature( "http://xml.org/sax/features/validation", true);
parser.setFeature( "http://xml.org/sax/features/namespaces", true);
parser.setFeature( "http://apache.org/xml/features/validation/schema", true);
parser.setFeature( "http://apache.org/xml/features/validation/schema-full-checking", true);
if (noNamespaceSchemaLocation!=null) {
parser.setProperty(
"http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",
noNamespaceSchemaLocation);
if (schemaLocation!=null) {
parser.setProperty(
"http://apache.org/xml/properties/schema/external-schemaLocation",
schemaLocation);
Also, as DrClap pointed out, for the schema location I use URIs.
Please let me know if you got the jaxp schemaLocation property to work and how you did it. -
Define Web Service as WSDL with Schemas
Dear All,
I would like to define Web Services by using XI/PI expose to consumer. Is it possible to define or separate the data type as schema (.xsd) from wsdl?
Thank you.
Regards,
Wenga single data type will refer to multiple data types data.
You can refer one Data type in other Data Type but it wont be available under a different root node.....the root node will the the DT name under which you are referring the other DTs......you can do this by:
DT --> Give the appropriate name to a node --> While selecting the Type for this node select Data types --> select the DT from the list available....for this you should first include all the schemas in IR i.e. you should first create individual DTs by importing the schema (DT --> XSD --> Import Data Type Definition from File)
You have a huge list of schemas!
Regards,
Abhishek. -
Importing WSDLs with references to schema
Hi all,
I am trying to invoke a webservice from PI and have imported the WSDLs for the same. But i couldn't see the various data types.
When i noticed that wsdl, i could see that there are rexternal references with relative path.
schemaLocation="..\External\external-common.xsd"/>
So i have a doubt about how to bring these references to PI. Since these are relative path, do i need to change them to absolute path?
If yes, how?
Thanks and best regards,
KulwantHi Kulwant,
The schema files should always be present at the relative paths.
You try out by importing these schema files also under External Definitions along with the main WSDL and check whether they are referenced.
OR
Manipulate the WSDL in any of XML editior and to Include the schema files into the main WSDL. and then import the WSDL.
Regards,
AshwinM -
Xsl schema import from within a wsdl file
I have a namespace conflict issue validating a bpel process.
The message error is as follow:
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
// Here the BPEL file (SMSMulticast2.bpel)
<pre>
<!-- SMSMulticast2 BPEL Process [Generated by the Oracle BPEL Designer] -->
<process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
<!-- ================================================================= -->
<!-- PARTNERLINKS -->
<!-- List of services participating in this BPEL process -->
<!-- ================================================================= -->
<partnerLinks>
<!--
The 'client' role represents the requester of this service. It is
used for callback. The location and correlation information associated
with the client role are automatically set using WS-Addressing.
-->
<partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
<partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
<partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
</partnerLinks>
<!-- ================================================================= -->
<!-- VARIABLES -->
<!-- List of messages and XML documents used within this BPEL process -->
<!-- ================================================================= -->
<variables>
<!-- Reference to the message passed as input during initiation -->
<variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
<!-- Reference to the message that will be sent back to the
requester during callback
-->
<variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
<variable name="count" type="xsd:integer"/>
<variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
<variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
<variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
<variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
</variables>
<!-- ================================================================= -->
<!-- ORCHESTRATION LOGIC -->
<!-- Set of activities coordinating the flow of messages across the -->
<!-- services integrated within this business process -->
<!-- ================================================================= -->
<sequence name="main">
<!-- Receive input from requestor.
Note: This maps to operation defined in SMSMulticast2.wsdl
-->
<receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
<!-- Asynchronous callback to the requester.
Note: the callback location and correlation id is transparently handled
using WS-addressing.
-->
<assign name="setProperties">
<copy>
<from expression="5"></from>
<to variable="count"/>
</copy>
<copy>
<from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
<to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
</copy>
<copy>
<from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
<to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
</copy>
</assign>
<while name="foreach" condition="bpws:getVariableData('count') > 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
<assign name="decrease"><copy>
<from expression="bpws:getVariableData('count') - 1"></from>
<to variable="count"/>
</copy>
</assign>
</sequence>
</while>
<!--invoke name="callbackClient" partnerLink="client" portType="tns:SMSMulticast2Callback" operation="onResult" inputVariable="output"/-->
<reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
</sequence>
</process>
// Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
name="SMSSenderEnablerSEI"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:complexType name="InvocationContext">
<xsd:sequence>
<xsd:element
maxOccurs="unbounded"
name="properties"
nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EnablerException">
<xsd:sequence>
<xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
<xsd:element name="errorCode" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:element name="sendSMS">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotification">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="sendSMSWithNotificationToAliasReturn"
nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:complexType name="SMSMessageETO">
<xsd:sequence>
<xsd:element name="content" nillable="true" type="xsd:string"/>
<xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
<xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
<xsd:element name="priority" nillable="true" type="xsd:string"/>
<xsd:element name="recipient" nillable="true" type="xsd:string"/>
<xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
<xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
<xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
<xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<xsd:complexType name="SMSException">
<xsd:sequence>
<xsd:element name="errorCode" type="xsd:int"/>
<xsd:element name="message" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="sendSMSRequest">
<wsdl:part element="impl:sendSMS" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasResponse">
<wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnablerException">
<wsdl:part element="tns2:EnablerException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasRequest">
<wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasRequest">
<wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasResponse">
<wsdl:part
element="impl:sendSMSWithNotificationToAliasResponse"
name="parameters"/>
</wsdl:message>
<wsdl:message name="SMSException">
<wsdl:part element="tns4:SMSException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationResponse">
<wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationRequest">
<wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSResponse">
<wsdl:part element="impl:sendSMSResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="SMSSenderEnablerRemote">
<wsdl:operation name="sendSMS">
<wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
<wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdl:input
message="impl:sendSMSWithNotificationRequest"
name="sendSMSWithNotificationRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationResponse"
name="sendSMSWithNotificationResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
<wsdl:output
message="impl:sendSMSToAliasResponse"
name="sendSMSToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdl:input
message="impl:sendSMSWithNotificationToAliasRequest"
name="sendSMSWithNotificationToAliasRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationToAliasResponse"
name="sendSMSWithNotificationToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding
name="SMSSenderEnablerRemoteSoapBinding"
type="impl:SMSSenderEnablerRemote">
<wsdlsoap:binding
style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendSMS">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SMSSenderEnablerRemoteService">
<wsdl:port
binding="impl:SMSSenderEnablerRemoteSoapBinding"
name="SMSSenderEnablerRemote">
<wsdlsoap:address
location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
<plnk:role name="SMSSenderEnablerRemoteProvider">
<plnk:portType name="impl:SMSSenderEnablerRemote"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
Many Thanks
GuillaumeYou need to use the XSLT before you do assignment to achieve this, to
change the message to the correct namespace.
Please refer to sample at
"orabpel\samples\tutorials\114.XSLTTransformations" which talks about
how to use XSLT transformation.
And please refer to
"orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
especially "InvToPo.xslt" which talks about doing transformations
between 2 structures pointing to different namespaces. -
Error validating xml with xsd schema on JSDK 1.4
Hi All,
Asked to me do it a Web Service client in Java and validate its xml answer with an xsd file using 1.4 plataform.
I googled and I saw many samples to 1.5 plataform, and few samples to 1.4, but anyway I tried to do what they asked to me.
I got connect with service, got the response and so I went to validate that xml with an xsd file.
But I got an error on that task. The error occurs in the following line
"Schema schema = factory.getSchema();"
Bellow my code
final String JAXP_SCHEMA_LANGUAGE = "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
final String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";
final String schemaSource = "C:\\GetAuthorizationServiceOutput.xsd";
final String JAXP_SCHEMA_SOURCE = "http://java.sun.com/xml/jaxp/properties/schemaSource";
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
try {
factory.setAttribute(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
factory.setAttribute(JAXP_SCHEMA_SOURCE,new File(source));
catch (IllegalArgumentException x) {
System.out.println(x.getMessage());
DocumentBuilder builder = null;
Document document = null;
try {
builder = factory.newDocumentBuilder();
document = builder.parse(new InputSource(new StringReader(ret.toString())));
} catch (ParserConfigurationException e) {
e.printStackTrace();
} catch (SAXException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
**Schema schema = factory.getSchema();**
Validator validator = schema.newValidator();
try {
validator.validate(new DOMSource(document));
} catch (SAXException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
and here is the exception :
Caused by: java.lang.NoSuchMethodError: javax.xml.parsers.DocumentBuilderFactory.getSchema()Ljavax/xml/validation/Schema;
Method onLinkClicked of interface wicket.markup.html.link.ILinkListener targeted at component [MarkupContainer [Component id = btBack, page = br.com.weev.finan.mkb_er.extranet.view.relations.RelationsDetails, path = 30:form:btBack.RelationsDetails$4, isVisible = true, isVersioned = true]] threw an exception
wicket.WicketRuntimeException: Method onLinkClicked of interface wicket.markup.html.link.ILinkListener targeted at component [MarkupContainer [Component id = btBack, page = br.com.weev.finan.mkb_er.extranet.view.relations.RelationsDetails, path = 30:form:btBack.RelationsDetails$4, isVisible = true, isVersioned = true]] threw an exception
at wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:198)
at wicket.request.target.component.listener.ListenerInterfaceRequestTarget.processEvents(ListenerInterfaceRequestTarget.java:74)
at wicket.request.compound.DefaultEventProcessorStrategy.processEvents(DefaultEventProcessorStrategy.java:65)
at wicket.request.compound.AbstractCompoundRequestCycleProcessor.processEvents(AbstractCompoundRequestCycleProcessor.java:57)
at wicket.RequestCycle.doProcessEventsAndRespond(RequestCycle.java:896)
at wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:929)
at wicket.RequestCycle.step(RequestCycle.java:1010)
at wicket.RequestCycle.steps(RequestCycle.java:1084)
at wicket.RequestCycle.request(RequestCycle.java:454)
at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:219)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:187)
... 39 more
Caused by: java.lang.NoSuchMethodError: javax.xml.parsers.DocumentBuilderFactory.getSchema()Ljavax/xml/validation/Schema;
at br.com.weev.finan.mkb_er.business.manager.impl.RelationManagerImpl.getAuthorizationService(RelationManagerImpl.java:152)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy22.getAuthorizationService(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at wicket.proxy.LazyInitProxyFactory$JdkHandler.invoke(LazyInitProxyFactory.java:377)
at wicket.proxy.$Proxy39.getAuthorizationService(Unknown Source)
at br.com.weev.finan.mkb_er.extranet.view.relations.RelationsDetails$4.onClick(RelationsDetails.java:125)
at wicket.markup.html.link.Link.onLinkClicked(Link.java:254)
... 43 more
It's my first time doing that, so I'm confuse to do it.
Thank you
Juliano.This is how.
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.dom.DOMResult;
import javax.xml.transform.dom.DOMSource;
import javax.xml.validation.Schema;
import javax.xml.validation.SchemaFactory;
import javax.xml.validation.Validator;
DocumentBuilderFactory dbfac = DocumentBuilderFactory.newInstance();
dbfac.setNamespaceAware(true);
SchemaFactory factory1 = SchemaFactory
.newInstance("http://www.w3.org/2001/XMLSchema");
Schema schema = factory1.newSchema(new File("person.xsd"));
dbfac.setSchema(schema);
DocumentBuilder dbparser1 = dbfac.newDocumentBuilder();
Document doc1 = dbparser1.parse(new File("person.xml"));
Validator validator1 = schema.newValidator();
DOMSource dm1 = new DOMSource(doc1);
DOMResult domresult1 = new DOMResult();
validator1.validate(dm1, domresult1); -
Create a wsdl file - with schemas inline - in JDeveloper
Hi,
We are trying to create a wsdl file using schemas in jdeveloper 11.1.1.3. We could generate the wsdl file using options available in jdeveloper, but the wsdl generated contains <types> element that has schemas referenced by only an "import" statement as below.
<types>
<xsd:schema>
<xsd:import schemaLocation="../../../Test.xsd" namespace="http://www.openuri.org"/>
</xsd:schema>
</types>
But, I would like get the schemas inlined or embedded within the wsdl instead of just an import statement.. This helps me in using the wsdl anywhere (creating webservices or use in my applications or give it to some one to use) without worrying about the actual schema definition files. The <types> element within the wsdl must have the schemas embedded, something like below.
<types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://testWSDLproject/type" elementFormDefault="qualified">
<xsd:element name="testIn">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="value" type="xsd:integer"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</types>
Is there any way forward, with the Jdeveloper to create wsdl files with schemas inline ?Hi Vohra,
The schema snippet pasted previously was just a sample.
In actual, there are mulitple cross referencing xsd files that must be embedded within my wsdl file. Sometimes, such manual editing of wsdl (embedding so many schema definitions) is prone to errors.
If there is an option in Jdeveloper which automatically does this embedding for us, then it becomes more handy. Have you come across any such options ? -
WSDL validation problem with WS-I
I created a WSDL with jDeveloper 10.1.3.2 following the Oracle Tutorial
http://www.oracle.com/technology/obe/obe1013jdev/wstopdown/wstopdown.htm
At the point where i have to validate the WSDL with the WS-I tester i get an error message:
Assertion: BP2701
The wsdl:definitions namespace is not: http://schemas.xmlsoap.org/wsdl/
All the entrys inside teh WSDL are written from jdeveloper.
the output WSDL looks like:
<definitions targetNamespace="urn:CreditRating"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:CreditRating"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:types="http://CreditRating.xsd">
<types>
<schema targetNamespace="http://CreditRating.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<element name="ssn" type="string"/>
<element name="rating" type="int"/>
<element name="error" type="string"/>
</schema>
</types>
<message name="CreditRatingRequestMessage">
<part name="ssn" element="types:ssn"/>
</message>
<message name="CreditRatingResponseMessage">
<part name="rating" element="types:rating"/>
</message>
<message name="CreditRatingFaultMessage">
<part name="error" element="types:error"/>
</message>
<portType name="CreditRating">
<operation name="processCreditRating">
<input message="tns:CreditRatingRequestMessage"/>
<output message="tns:CreditRatingRequestMessage"/>
<fault message="tns:CreditRatingFaultMessage" name="negativCredit"/>
</operation>
</portType>
<binding name="CreditRatingSoapHttp" type="tns:CreditRating">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="processCreditRating">
<soap:operation soapAction="urn:CreditRating/processCreditRating"/>
<input>
<soap:body use="literal" parts="ssn"/>
</input>
<output>
<soap:body use="literal" parts="ssn"/>
</output>
<fault name="negativCredit">
<soap:fault use="literal" name="negativCredit"/>
</fault>
</operation>
</binding>
<service name="CreditRatingService">
<port name="CreditRatingServiceSoapHttpPort"
binding="tns:CreditRatingSoapHttp">
<soap:address location="tbd"/>
</port>
</service>
</definitions>
I can not see where the porblem is. Can someone help me please?
Tanks BsHi ,
there is not any problem in code or in function.
You just need to double click on Excel field where you are having that problem of ####.
Whenever display size of cell is less then the data size then it's showing as ###. so you just need to double click on it and make it as per data length...
-Maharshi -
SAX Parser Validation with Schemas (C, C++ and JAVA)
We are currently using the Oracle XML Parser for C to parse and validate XML data using the SAX parser interface with validation turned on. We currently define our XML with a DTD, but would like to switch to schemas. However, the Oracle XML Parser 9.2.0.3.0 (C) only validates against a DTD, not a schema when using the SAX interface. Are there plans to add schema validation as an option? If so, when would this be available? Also, the same limitation appears to be true for C++ and JAVA. When will any of these provide SAX parsing with schema validation?
Thanks!
JohnWill get back to you after checked with development team...
-
JAX-WS generated WSDL uses xsd:import and no option to inline schemas
Is it possible to configure JAX-WS 2.0/2.1 so that when generating WSDL at runtime it will inline the schema definitions instead of using the <xsd:import> method? Unfortunately, some clients (Adobe Flex, for example) do NOT know how to process schema imports. I realize that Adobe (and others) should fix the problem on their end and become fully spec compliant, but the cold reality is that they are not.
Any advice, suggestions, or solutions would be greatly appreciated.
Regards,
ToddYou should post this question either to the JAXB 2.0 and JAX-WS 2.0 forum (http://forums.java.net/jive/forum.jspa?forumID=46) or the JAX-WS dev mailing list ([email protected]) so that the team is aware of the issue.
That functionality currently does not exist. The only work around that I am aware of is to generate the WSDL before deployment and rearrange it as necessary. -
Generating the wsdl with inline schema for the bpel process
Hi
When a BPEL process is deployed, we can get the WSDL of the same by logging into the BPEL console, but the WSDL contains the reference to the schema using the namespace. Can we generate the wsdl with the inline schema.
Suggestions are highly appreciated.
ThanksHi,
If the wsdl is referring to a Schema file you won't be able to see the schema definition in the WSDL file itself,for that you have to refer to the deployed jar which contains the XML schema.The default path for the deployed jar is <Oracle_SOA_Installed_Home>/bpel/domains/<domain_name>/tmp/<bpelprocess.jar>
Otherwise if you have the source project you can always refer to it in JDev.
Rgrds. -
Xerces Validation Issues with Honour All schema Locations
Way back in 2009/2010 there was a bug - 284272 - that was never updated with Xerces information about validation. We have a similar issue in Luna and Mars with the WTP validation framework (with Xerxes at the center) and I'm wondering if it's due to Xerces 2.9 or something else.
I'm not a savvy XSD guy, but the issues detailed in 284272 still occur for us with certain schema combinations. We're encountering it specifically with the JBoss/SwitchYard project and the SCA schemas we extend for the SwitchYard runtime.
The following error is displayed in the Problems tab:
cvc-complex-type.2.4.a: Invalid content was found starting with element 'sca:interface.java'. One of '{"http://docs.oasis-open.org/ns/opencsa/sca/200912":documentation, "http://docs.oasis-open.org/ns/opencsa/sca/200912":interface, "http://docs.oasis-open.org/ns/opencsa/sca/200912":binding, "http://docs.oasis-open.org/ns/opencsa/sca/200912":callback, "http://docs.oasis-open.org/ns/opencsa/sca/200912":requires, "http://docs.oasis-open.org/ns/opencsa/sca/200912":policySetAttachment, "http://docs.oasis-open.org/ns/opencsa/sca/200912":extensions}' is expected. switchyard.xml src/main/resources/META-INF line 7 XML Problem
Can someone revisit 284272 and let me know if this is indeed a Xerxes issue under the covers with the example included in the bug? It's not our example, but has the same general problem.
I just don't want to open a duplicate of 284272 without knowing more about how the Honour All Schema Locations stuff works under the covers and if it is indeed caused by Xerces - indeed if it might be fixed by an update to Xerces further down the line (they're up to 2.11 and there was a 2.9.1 it looks like we might be able to more simply move to if it's fixed there).
Thanks all!
--FitzI think this is the odata4 that you need for 7.3
SCA
ODATACXFEXT11_0-10012140.SCA
SP11 for SAP ODATA4J+CXF-REST LIB 7.30
0
Info
10352
26.02.2014
This might be the only package you need; it might be in your best interest to avoid manually downloading files and rely upon Solution Manager's MOpz feature to query your IdM system and let it track down all the needed packages. -
Importing WSDL with external references issue
Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
Maybe you are looking for
-
Mac equivalent of blue screen of death?
So i recently updated osx to 10.5.4 i believe it is? Ever since then i randomly get a grayed over screen and a message that says i have to restart my computer. Before this, finder was crashing, but it hasn't happened in awhile. It seemed to happen wh
-
BAPI_GOODSMVT_CREATE Goods Receipt Reversal
Hello All, According to SAP docs I need to use goodsmvt_code-gm_code = '06' but with movement type 102 I get an error message "Goods movement not possible with movement type 102". Works fine if I use regular goods receipt code '01' and movement 102.
-
Way to close/reopen file and keep the same desktop position
When closing a Text Edit document, I would like to have it reopen in the exact same position on the desktop as when I closed it. Is there any way to make this happen? It seems to remember if the window was resized, but it always puts the document at
-
Installed 512mb RAM Memory and reads Empty!!!
Please help i just installed a 512mb Ram Memory chip into DIMM1 and it is reading under system profiler MEMORY as Empty and if you click DIAGNOSTICS under system profiler it says "Power On Self-Test: Last Run:2/2/07 7:52 AM Result: Failed Failure Typ
-
Scroll bar decided it didn't like me...
It appears that my scroll bar doesn't wan't to work anymore. All I've done is create a few buttons. If anyone is willing to take it a look at it? I'd be extremely greatful. Thanks, Nicko.