Syndication mapping when changing XML schema
I have used a ARTMAS04 XML schema and done mapping in the syndicator and saved the map. Then we are doing changes i SAP R/3 and need to add some extentions in the IDOC and therefor also the XML schema. I then add my new schema with the extentions into the the syndicator, and try to open the mapping. Then the mapping is done using the old schema. This means that if I do a change in an XML schema, I need to to map everything from scratch. Does anyone have a solution to this problem?
Regards John-Kjell
Hi John,
The maps saves not only the mappings but also the destination properties for that particular scenario.
Hence as soon as you change the destination properties i.e your XML schema, and try to open your old map which is using different XML schema your changes will be lost and you will end up with using old XML schema only.
As far as i know, to handle this situation you have to do all the mappings again.
Hope this helps.
Regards,
Pooja
Similar Messages
-
Update of XML syndication map when XSD is changed
All,
So we recently upgraded to MDM 7.1 SP 06 and found a new feature which we were waiting for quiet some time. Thought i'll share with the community as well.
Update of XML syndication map when XSD is changed in Console
In earlier SP's of MDM, if we had to update an XML syndication map, we had to upload the new XSD in Console, go to syndicator and basically re-create the whole map. there was no way for syndicator to preserve the old mapping.
Well with this new feature, the old mapping is preserved, we only need to re-map the new fields.
The process is as below:
1. Upload the new XSD in Console.
2. Go to syndicator and open the syndication map which you want to update(File->Open).
3. Click File -> Update XML Schema. (this is the new option)
4. It will give a pop-up, select the new schema you have uploaded in console and hit OK.
5. You will get a prompt saying that syndication map is being changed, hit OK.
6. Now you will see the new XSD in syndicator, the older fields are still mapped, you only need to map the new fields.
It a nice feature which will definitely save lot of time. Thanks SAP
Regards
AamirIf this post answered your question or helped, please mark it as such.
This works.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
<![CDATA[
import mx.events.DataGridEvent;
import mx.collections.ArrayCollection;
[Bindable] private var ac:ArrayCollection = new ArrayCollection([
{bgColor: "0xFF0000", num: 100, name: "Test1"},
{bgColor: "0xFF0000", num: 200, name: "Test2"},
{bgColor: "0xFF0000", num: 300, name: "Test3"},
private function changeBK(evt:DataGridEvent):void{
var row:uint = evt.rowIndex;
var data:Object = ac.getItemAt(row);
data.bgColor = "0x00FF00";
]]>
</mx:Script>
<mx:DataGrid id="dg" dataProvider="{ac}" itemEditEnd="changeBK(event);"
editable="true">
<mx:columns>
<mx:DataGridColumn dataField="num">
<mx:itemRenderer>
<mx:Component>
<mx:TextArea backgroundColor="{data.bgColor}" text="{data.num}"/>
</mx:Component>
</mx:itemRenderer>
</mx:DataGridColumn>
<mx:DataGridColumn dataField="name"/>
</mx:columns>
</mx:DataGrid>
</mx:Application> -
Redo the syndication map if the Repository schema changes?
Hi ,
We have changed the repository structure after creating the syndication map which is based on the repository schema.Now when I load the syndication map with the updated schema ,i am not seeing the newly added fields on the destination items,so we loaded the destination properties with new schema again but the map of all the fields are no more available which leaves us to redo the map again.Is there anyway that the destination is updated with new fields without redoing the map again.
ThanksHi Aravind,
unfortunately there is no way to solve this issue but rebuilding the map. The reason is the way syndciation maps are stored in MDM 5.5. This is subject to change (and improve a lot!) in MDM 7.1. But in 5.5 you'll have to rebuild the syndication map completely if you change the repository schema, respectively the XSD file you use as a basis for XML distribution.
Best regards
Michael -
Mapping DTO to XML Schema for Worship Web Service
I have a number of DTOs that my application uses. This application
needs to consume a number of document style web services created in
workshop. When I generate the proxies for this web service, it creates
Java beans for the XML schema types defined in the web service.
Is there a way to get the workshop stubs to map my DTOs to XML schema?
If not, what is the best way to do this mapping? Thanks.
MikeI have a number of DTOs that my application uses. This application
needs to consume a number of document style web services created in
workshop. When I generate the proxies for this web service, it creates
Java beans for the XML schema types defined in the web service.
Is there a way to get the workshop stubs to map my DTOs to XML schema?
If not, what is the best way to do this mapping? Thanks.
Mike -
Mapping DTO to XML Schema for Workshop Web Service
I have a number of DTOs that my application uses. This application
needs to consume a number of document style web services created in
workshop. When I generate the proxies for this web service, it creates
Java beans for the XML schema types defined in the web service.
Is there a way to get the workshop stubs to map my DTOs to XML schema?
If not, what is the best way to do this mapping? Thanks.
MikeI have a number of DTOs that my application uses. This application
needs to consume a number of document style web services created in
workshop. When I generate the proxies for this web service, it creates
Java beans for the XML schema types defined in the web service.
Is there a way to get the workshop stubs to map my DTOs to XML schema?
If not, what is the best way to do this mapping? Thanks.
Mike -
How to change XML Schema in MDM Console?
Hi Experts,
My scenario: SRM send products to MDM Catalog using PI.
I need to change the XML Schema (XSD) for processing some new fields that don't exist in Catalog. So I created a copy of the XSD file in my station and made the necessary changes.
In XML Schema (MDM Console), I changed the FileName for getting the XSD I created.
But when I tested SRM Shopping Cart again, this couldn't access the products in Catalog anymore.
1) After my chage the FileName shows the name with "c:\Documents and Settings\...". Does it work?? Is this the cause of the error?
2) Do you know why my change affect the Shopping Cart access to the products in the Catalog?
3) Now I don't know how to undo my change in FileName. I can't do it because in the FileName MDM Console it doesn't allow to write it. It allows only to choose a file in some place, my station for example.
Could anyone help me?
Thanks!
RoseHi Kanstantsin,
I was analysing what you explain, but it was not exactly this problema. But what you wrote, help me to understand better the MDM and lets me know more about schemas .
Thank you very much for your help.
Hi Vinary,
It was exactly this. I had edited the name. I changed it and now it is working.
Thank you very much for your help!
Rose -
Error when registering XML Schema
When I try to register a schema with XDB I keep getting an ORA-31000 error. It says that the schema it references is not a valid XDB schema, but when I try to register that one it says the first one isn't valid.
Testing with 11g I get
I assume you have registered 'http://www.w3.org/2005/08/addressing/ws-addr.xsd'
SQL> set echo on
SQL> spool testcase.log
SQL> --
SQL> connect sys/ as sysdba
Enter password:
Connected.
SQL> set define on
SQL> set timing on
SQL> --
SQL> define USERNAME = IXSEMF01
SQL> --
SQL> def PASSWORD = IXSEMF01
SQL> --
SQL> def USER_TABLESPACE = USERS
SQL> --
SQL> def TEMP_TABLESPACE = TEMP
SQL> --
SQL> drop user &USERNAME cascade
2 /
old 1: drop user &USERNAME cascade
new 1: drop user IXSEMF01 cascade
drop user IXSEMF01 cascade
ERROR at line 1:
ORA-01918: user 'IXSEMF01' does not exist
Elapsed: 00:00:00.03
SQL> grant connect, resource to &USERNAME identified by &PASSWORD
2 /
old 1: grant connect, resource to &USERNAME identified by &PASSWORD
new 1: grant connect, resource to IXSEMF01 identified by IXSEMF01
Grant succeeded.
Elapsed: 00:00:00.01
SQL> grant create any directory, drop any directory to &USERNAME
2 /
old 1: grant create any directory, drop any directory to &USERNAME
new 1: grant create any directory, drop any directory to IXSEMF01
Grant succeeded.
Elapsed: 00:00:00.00
SQL> grant alter session, create view to &USERNAME
2 /
old 1: grant alter session, create view to &USERNAME
new 1: grant alter session, create view to IXSEMF01
Grant succeeded.
Elapsed: 00:00:00.00
SQL> alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
2 /
old 1: alter user &USERNAME default tablespace &USER_TABLESPACE temporary tablespace &TEMP_TABLESPACE
new 1: alter user IXSEMF01 default tablespace USERS temporary tablespace TEMP
User altered.
Elapsed: 00:00:00.00
SQL> connect &USERNAME/&PASSWORD
Connected.
SQL> --
SQL> alter session set events ='19027 trace name context forever, level 0x800'
2 /
Session altered.
Elapsed: 00:00:00.00
SQL> var schemaURL varchar2(700)
SQL> var schemaURL1 varchar2(700)
SQL> var schemaURL2 varchar2(700)
SQL> var xmlschema CLOB
SQL> --
SQL> begin
2 :schemaURL := 'http://www.w3.org/2005/08/addressing/ws-addr.xsd';
3 :xmlSchema :=
4 '<?xml version="1.0" encoding="utf-8"?>
5 <!--
6 <!DOCTYPE xs:schema PUBLIC "-//W3C//DTD XMLSCHEMA 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd">
7 W3C XML Schema defined in the Web Services Addressing 1.0 specification
8 http://www.w3.org/TR/ws-addr-core
9
10 Copyright c 2005 World Wide Web Consortium,
11
12 (Massachusetts Institute of Technology, European Research Consortium for
13 Informatics and Mathematics, Keio University). All Rights Reserved. This
14 work is distributed under the W3Cr Software License [1] in the hope that
15 it will be useful, but WITHOUT ANY WARRANTY; without even the implied
16 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
17
18 [1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
19
20 $Id: ws-addr.xsd,v 1.3 2005/08/09 13:17:35 hugo Exp $
21 -->
22 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.w3.org/2005/08/addressing" targetNamespace="http://www.w3.
org/2005/08/addressing" blockDefault="#all" elementFormDefault="qualified" finalDefault="" attributeFormDefault="unqualified">
23
24 <!-- Constructs from the WS-Addressing Core -->
25
26 <xs:element name="EndpointReference" type="tns:EndpointReferenceType"/>
27 <xs:complexType name="EndpointReferenceType" mixed="false">
28 <xs:sequence>
29 <xs:element name="Address" type="tns:AttributedURIType"/>
30 <xs:element name="ReferenceParameters" type="tns:ReferenceParametersType" minOccurs="0"/>
31 <xs:element ref="tns:Metadata" minOccurs="0"/>
32 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
33 </xs:sequence>
34 <xs:anyAttribute namespace="##other" processContents="lax"/>
35 </xs:complexType>
36
37 <xs:complexType name="ReferenceParametersType" mixed="false">
38 <xs:sequence>
39 <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
40 </xs:sequence>
41 <xs:anyAttribute namespace="##other" processContents="lax"/>
42 </xs:complexType>
43
44 <xs:element name="Metadata" type="tns:MetadataType"/>
45 <xs:complexType name="MetadataType" mixed="false">
46 <xs:sequence>
47 <xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
48 </xs:sequence>
49 <xs:anyAttribute namespace="##other" processContents="lax"/>
50 </xs:complexType>
51
52 <xs:element name="MessageID" type="tns:AttributedURIType"/>
53 <xs:element name="RelatesTo" type="tns:RelatesToType"/>
54 <xs:complexType name="RelatesToType" mixed="false">
55 <xs:simpleContent>
56 <xs:extension base="xs:anyURI">
57 <xs:attribute name="RelationshipType" type="tns:RelationshipTypeOpenEnum" use="optional" default="http://www
.w3.org/2005/08/addressing/reply"/>
58 <xs:anyAttribute namespace="##other" processContents="lax"/>
59 </xs:extension>
60 </xs:simpleContent>
61 </xs:complexType>
62
63 <xs:simpleType name="RelationshipTypeOpenEnum">
64 <xs:union memberTypes="tns:RelationshipType xs:anyURI"/>
65 </xs:simpleType>
66
67 <xs:simpleType name="RelationshipType">
68 <xs:restriction base="xs:anyURI">
69 <xs:enumeration value="http://www.w3.org/2005/08/addressing/reply"/>
70 </xs:restriction>
71 </xs:simpleType>
72
73 <xs:element name="ReplyTo" type="tns:EndpointReferenceType"/>
74 <xs:element name="From" type="tns:EndpointReferenceType"/>
75 <xs:element name="FaultTo" type="tns:EndpointReferenceType"/>
76 <xs:element name="To" type="tns:AttributedURIType"/>
77 <xs:element name="Action" type="tns:AttributedURIType"/>
78
79 <xs:complexType name="AttributedURIType" mixed="false">
80 <xs:simpleContent>
81 <xs:extension base="xs:anyURI">
82 <xs:anyAttribute namespace="##other" processContents="lax"/>
83 </xs:extension>
84 </xs:simpleContent>
85 </xs:complexType>
86
87 <!-- Constructs from the WS-Addressing SOAP binding -->
88
89 <xs:attribute name="IsReferenceParameter" type="xs:boolean"/>
90
91 <xs:simpleType name="FaultCodesOpenEnumType">
92 <xs:union memberTypes="tns:FaultCodesType xs:QName"/>
93 </xs:simpleType>
94
95 <xs:simpleType name="FaultCodesType">
96 <xs:restriction base="xs:QName">
97 <xs:enumeration value="tns:InvalidAddressingHeader"/>
98 <xs:enumeration value="tns:InvalidAddress"/>
99 <xs:enumeration value="tns:InvalidEPR"/>
100 <xs:enumeration value="tns:InvalidCardinality"/>
101 <xs:enumeration value="tns:MissingAddressInEPR"/>
102 <xs:enumeration value="tns:DuplicateMessageID"/>
103 <xs:enumeration value="tns:ActionMismatch"/>
104 <xs:enumeration value="tns:MessageAddressingHeaderRequired"/>
105 <xs:enumeration value="tns:DestinationUnreachable"/>
106 <xs:enumeration value="tns:ActionNotSupported"/>
107 <xs:enumeration value="tns:EndpointUnavailable"/>
108 </xs:restriction>
109 </xs:simpleType>
110
111 <xs:element name="RetryAfter" type="tns:AttributedUnsignedLongType"/>
112 <xs:complexType name="AttributedUnsignedLongType" mixed="false">
113 <xs:simpleContent>
114 <xs:extension base="xs:unsignedLong">
115 <xs:anyAttribute namespace="##other" processContents="lax"/>
116 </xs:extension>
117 </xs:simpleContent>
118 </xs:complexType>
119
120 <xs:element name="ProblemHeaderQName" type="tns:AttributedQNameType"/>
121 <xs:complexType name="AttributedQNameType" mixed="false">
122 <xs:simpleContent>
123 <xs:extension base="xs:QName">
124 <xs:anyAttribute namespace="##other" processContents="lax"/>
125 </xs:extension>
126 </xs:simpleContent>
127 </xs:complexType>
128
129 <xs:element name="ProblemHeader" type="tns:AttributedAnyType"/>
130 <xs:complexType name="AttributedAnyType" mixed="false">
131 <xs:sequence>
132 <xs:any namespace="##any" processContents="lax" minOccurs="1" maxOccurs="1"/>
133 </xs:sequence>
134 <xs:anyAttribute namespace="##other" processContents="lax"/>
135 </xs:complexType>
136
137 <xs:element name="ProblemIRI" type="tns:AttributedURIType"/>
138
139 <xs:element name="ProblemAction" type="tns:ProblemActionType"/>
140 <xs:complexType name="ProblemActionType" mixed="false">
141 <xs:sequence>
142 <xs:element ref="tns:Action" minOccurs="0"/>
143 <xs:element name="SoapAction" minOccurs="0" type="xs:anyURI"/>
144 </xs:sequence>
145 <xs:anyAttribute namespace="##other" processContents="lax"/>
146 </xs:complexType>
147
148 </xs:schema>';
149 end;
150 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.00
SQL> declare
2 xmlschema xmltype := xmltype(:xmlschema);
3 begin
4 dbms_xmlschema.registerSchema
5 (
6 schemaURL => :schemaURL
7 ,schemaDoc => xmlschema
8 ,local => TRUE
9 ,genBean => false
10 ,genTypes => TRUE
11 ,genTables => TRUE
12 );
13 end;
14 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:03.07
SQL>
SQL> begin
2 :schemaURL1 := 'muws1-2.xsd';
3 :xmlSchema :=
4 '<?xml version="1.0" encoding="utf-8"?>
5 <!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Dirk Grissett (Oracle Corp.) --> <xs:schema xmlns:muws1="http://docs.
oasis-open.org/wsdm/muws1-2.xsd" xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://docs.oasis-open.org/wsdm/muws1-2.xsd" elementFormDefault="qualified" att
ributeFormDefault="unqualified">
6 <xs:import namespace="http://docs.oasis-open.org/wsdm/muws2-2.xsd" schemaLocation="muws2-2.xsd"/>
7 <xs:import namespace="http://www.w3.org/2005/08/addressing" schemaLocation="http://www.w3.org/2005/08/addressing/ws-addr.xsd"/>
8 <xs:element name="ResourceId" type="xs:anyURI"/>
9 <xs:element name="ManageabilityCapability" type="xs:anyURI"/>
10 <xs:complexType name="CorrelatablePropertiesType">
11 <xs:sequence>
12 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
13 </xs:sequence>
14 <xs:attribute name="Dialect" type="xs:anyURI"/>
15 <xs:attribute name="NegativeAssertionPossible" type="xs:boolean"/>
16 <xs:anyAttribute namespace="##other"/>
17 </xs:complexType>
18 <xs:element name="CorrelatableProperties" type="muws1:CorrelatablePropertiesType"/>
19 <xs:complexType name="ComponentAddressType">
20 <xs:sequence>
21 <xs:element name="ManagementURL" type="xs:string"/>
22 <xs:any namespace="##any" processContents="lax"/>
23 </xs:sequence>
24 </xs:complexType>
25 <xs:complexType name="ComponentType">
26 <xs:sequence>
27 <xs:element name="ResourceId" type="xs:anyURI" minOccurs="0"/>
28 <xs:element name="ComponentAddress" type="muws1:ComponentAddressType" minOccurs="0"/>
29 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
30 </xs:sequence>
31 <xs:anyAttribute namespace="##other"/>
32 </xs:complexType>
33 <xs:complexType name="ManagementEventType">
34 <xs:sequence>
35 <xs:element name="EventId" type="xs:anyURI"/>
36 <xs:element name="SourceComponent" type="muws1:ComponentType"/>
37 <xs:element name="ReporterComponent" type="muws1:ComponentType" minOccurs="0"/>
38 <xs:element ref="muws2:Situation"/>
39 <xs:element name="ExtendedData" type="muws1:ExtendedDataType" minOccurs="0" maxOccurs="unbounded"/>
40 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
41 </xs:sequence>
42 <xs:attribute name="ReportTime" type="xs:dateTime" use="optional"/>
43 <xs:anyAttribute namespace="##other"/>
44 </xs:complexType>
45 <xs:element name="ManagementEvent" type="muws1:ManagementEventType"/>
46 <xs:element name="ManageabilityEndpointReference" type="wsa:EndpointReferenceType"/>
47 <xs:complexType name="ExtendedDataElementType">
48 <xs:sequence>
49 <xs:choice>
50 <xs:element name="values" minOccurs="0">
51 <xs:simpleType>
52 <xs:restriction base="xs:string">
53 <xs:maxLength value="1024"/>
54 </xs:restriction>
55 </xs:simpleType>
56 </xs:element>
57 <xs:element name="hexValue" type="xs:hexBinary" minOccurs="0"/>
58 <xs:element name="intValues" type="xs:int" minOccurs="0"/>
59 <xs:element name="longValues" type="xs:long" minOccurs="0"/>
60 <xs:element name="shortValues" type="xs:short" minOccurs="0"/>
61 <xs:element name="dateTimeValues" type="xs:dateTime" minOccurs="0"/>
62 <xs:element name="byteValues" type="xs:byte" minOccurs="0"/>
63 <xs:element name="booleanValues" type="xs:boolean" minOccurs="0"/>
64 <xs:element name="floatValues" type="xs:float" minOccurs="0"/>
65 <xs:element name="doubleValues" type="xs:double" minOccurs="0"/>
66 <xs:element name="largeStringValue" type="xs:string" minOccurs="0"/>
67 </xs:choice>
68 </xs:sequence>
69 <xs:attribute name="name" use="required">
70 <xs:simpleType>
71 <xs:restriction base="xs:Name">
72 <xs:maxLength value="64"/>
73 </xs:restriction>
74 </xs:simpleType>
75 </xs:attribute>
76 <xs:attribute name="type" use="required">
77 <xs:simpleType>
78 <xs:restriction base="xs:string">
79 <xs:enumeration value="noValue"/>
80 <xs:enumeration value="byte"/>
81 <xs:enumeration value="short"/>
82 <xs:enumeration value="int"/>
83 <xs:enumeration value="long"/>
84 <xs:enumeration value="float"/>
85 <xs:enumeration value="double"/>
86 <xs:enumeration value="string"/>
87 <xs:enumeration value="dateTime"/>
88 <xs:enumeration value="boolean"/>
89 <xs:enumeration value="byteArray"/>
90 <xs:enumeration value="shortArray"/>
91 <xs:enumeration value="intArray"/>
92 <xs:enumeration value="longArray"/>
93 <xs:enumeration value="floatArray"/>
94 <xs:enumeration value="doubleArray"/>
95 <xs:enumeration value="stringArray"/>
96 <xs:enumeration value="dateTimeArray"/>
97 <xs:enumeration value="booleanArray"/>
98 <xs:enumeration value="hexBinary"/>
99 <xs:enumeration value="largeStringValue"/>
100 </xs:restriction>
101 </xs:simpleType>
102 </xs:attribute>
103 </xs:complexType>
104 <xs:complexType name="ExtendedDataType">
105 <xs:sequence>
106 <xs:element name="ExtendedDataElement" type="muws1:ExtendedDataElementType" minOccurs="0" maxOccurs="unbounded"/>
107 </xs:sequence>
108 <xs:attribute name="profile" type="xs:ID"/>
109 </xs:complexType>
110 <!--
111 SCHEMA COPY Material Copy and paste element references below into the schema of a resource prope
rties document.
112 These references are provide to insure that the correct minOccurs/maxOccurs attributes are specified in a resource property document sc
hema.
113
114 NOTE: You must import the MUWS Part 1 schema namespace (MUWS1).
115
116 ** Identity Properties **
117 <xs:element ref="muws1:ResourceId"/>
118
119
120 ** ManageabilityCharacteristics Properties **
121 <xs:element ref="muws1:ManageabilityCapability"
122 minOccurs="0" maxOccurs="unbounded"/>
123
124 ** Correlatable Properties **
125 <xs:element ref="muws1:CorrelatableProperties"
126 minOccurs="0" maxOccurs="unbounded"/>
127
128 -->
129 </xs:schema>';
130 end;
131 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.00
SQL> declare
2 xmlschema xmltype := xmltype(:xmlschema);
3 begin
4 dbms_xmlschema.registerSchema
5 (
6 schemaURL => :schemaURL1
7 ,schemaDoc => xmlschema
8 ,local => TRUE
9 ,genBean => false
10 ,genTypes => TRUE
11 ,genTables => TRUE
12 ,force => TRUE
13 );
14 end;
15 /
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.35
SQL> begin
2 :schemaURL2 := 'muws2-2.xsd';
3 :xmlSchema :=
4 '<?xml version="1.0" encoding="utf-8"?>
5 <!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Dirk Grissett (Oracle Corp.) -->
6 <xs:schema xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd" xmlns:muws1="http://docs.oasis-open.org/wsdm/muws1-2.xsd" xmlns:ws
a="http://www.w3.org/2005/08/addressing" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://docs.oasis-open.org/wsdm/muws2-
2.xsd" elementFormDefault="qualified" attributeFormDefault="unqualified">
7 <xs:import namespace="http://docs.oasis-open.org/wsdm/muws1-2.xsd" schemaLocation="muws1-2.xsd"/>
8 <xs:import namespace="http://www.w3.org/2005/08/addressing" schemaLocation="http://www.w3.org/2005/08/addressing/ws-addr.xsd"/>
9 <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/>
10 <xs:complexType name="LangString">
11 <xs:simpleContent>
12 <xs:extension base="xs:string">
13 <xs:attribute ref="xml:lang" use="required"/>
14 <xs:anyAttribute namespace="##other"/>
15 </xs:extension>
16 </xs:simpleContent>
17 </xs:complexType>
18 <!-- Begin properties for the Description capability -->
19 <xs:element name="Caption" type="muws2:LangString"/>
20 <xs:element name="Description" type="muws2:LangString"/>
21 <xs:element name="Version" type="xs:string"/>
22 <!-- End properties for the Description capability -->
23 <xs:complexType name="CategoryType">
24 <xs:sequence>
25 <xs:any namespace="##any" processContents="lax" minOccurs="0"/>
26 </xs:sequence>
27 </xs:complexType>
28 <xs:complexType name="StateType">
29 <xs:complexContent>
30 <xs:extension base="muws2:CategoryType"/>
31 </xs:complexContent>
32 </xs:complexType>
33 <xs:element name="State" type="muws2:StateType"/>
34 <xs:element name="EnteredState" type="muws2:StateType"/>
35 <xs:element name="PreviousState" type="muws2:StateType"/>
36 <xs:complexType name="StateTransitionType">
37 <xs:sequence>
38 <xs:element ref="muws2:EnteredState"/>
39 <xs:element ref="muws2:PreviousState" minOccurs="0"/>
40 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
41 </xs:sequence>
42 <xs:attribute name="TransitionIdentifier" type="xs:anyURI" use="optional"/>
43 <xs:attribute name="Time" type="xs:dateTime" use="required"/>
44 <xs:anyAttribute namespace="##other"/>
45 </xs:complexType>
46 <xs:element name="StateTransition" type="muws2:StateTransitionType"/>
47 <!-- Begin properties for the OperationalStatus capability -->
48 <xs:element name="OperationalStatus">
49 <xs:simpleType>
50 <xs:restriction base="xs:string">
51 <xs:enumeration value="Available"/>
52 <xs:enumeration value="PartiallyAvailable"/>
53 <xs:enumeration value="Unavailable"/>
54 <xs:enumeration value="Unknown"/>
55 </xs:restriction>
56 </xs:simpleType>
57 </xs:element>
58 <!-- End properties for the OperationalStatus capability -->
59 <xs:attributeGroup name="MetricAttributes">
60 <xs:attribute name="ResetAt" type="xs:dateTime"/>
61 <xs:attribute name="LastUpdated" type="xs:dateTime"/>
62 <xs:attribute name="Duration" type="xs:duration"/>
63 </xs:attributeGroup>
64 <!-- Begin properties for the Metrics capability -->
65 <xs:element name="CurrentTime" type="xs:dateTime"/>
66 <!-- End properties for the Metrics capability -->
67 <xs:complexType name="RelationshipTypeType">
68 <xs:complexContent>
69 <xs:extension base="muws2:CategoryType"/>
70 </xs:complexContent>
71 </xs:complexType>
72 <xs:element name="Self">
73 <xs:complexType/>
74 </xs:element>
75 <xs:complexType name="RelationshipParticipantType">
76 <xs:sequence>
77 <xs:element ref="muws2:Self" minOccurs="0"/>
78 <xs:element ref="muws1:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/>
79 <xs:element ref="wsa:EndpointReference" minOccurs="0" maxOccurs="unbounded"/>
80 <xs:element ref="muws1:ResourceId" minOccurs="0"/>
81 <xs:element name="Role" type="xs:anyURI"/>
82 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
83 </xs:sequence>
84 <xs:anyAttribute namespace="##other"/>
85 </xs:complexType>
86 <!-- Begin properties for the RelationshipResource capability -->
87 <xs:element name="Name" type="xs:string"/>
88 <xs:element name="Type" type="muws2:RelationshipTypeType"/>
89 <xs:element name="Participant" type="muws2:RelationshipParticipantType"/>
90 <!-- End properties for the RelationshipResource capability -->
91 <xs:complexType name="RelationshipType">
92 <xs:sequence>
93 <xs:element ref="muws2:Name" minOccurs="0"/>
94 <xs:element ref="muws2:Type"/>
95 <xs:element ref="muws2:Participant" minOccurs="2" maxOccurs="unbounded"/>
96 <xs:element name="AccessEndpointReference" type="wsa:EndpointReferenceType" minOccurs="0"/>
97 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
98 </xs:sequence>
99 <xs:anyAttribute namespace="##other"/>
100 </xs:complexType>
101 <!-- Begin properties for the Relationship capability -->
102 <xs:element name="Relationship" type="muws2:RelationshipType"/>
103 <!-- End properties for the Relationship capability -->
104 <xs:element name="RelationshipCreatedNotification">
105 <xs:complexType>
106 <xs:sequence>
107 <xs:element ref="muws2:Relationship"/>
108 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
109 </xs:sequence>
110 <xs:anyAttribute namespace="##other"/>
111 </xs:complexType>
112 </xs:element>
113 <xs:element name="RelationshipDeletedNotification">
114 <xs:complexType>
115 <xs:sequence>
116 <xs:element ref="muws2:Relationship"/>
117 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
118 </xs:sequence>
119 <xs:anyAttribute namespace="##other"/>
120 </xs:complexType>
121 </xs:element>
122 <xs:element name="QueryRelationshipsByType">
123 <xs:complexType>
124 <xs:sequence>
125 <xs:element name="RequestedType" type="xs:QName"/>
126 </xs:sequence>
127 </xs:complexType>
128 </xs:element>
129 <xs:element name="QueryRelationshipsByTypeResponse">
130 <xs:complexType>
131 <xs:sequence>
132 <xs:element ref="muws2:Relationship" minOccurs="0" maxOccurs="unbounded"/>
133 </xs:sequence>
134 </xs:complexType>
135 </xs:element>
136 <xs:element name="CreationNotification">
137 <xs:complexType>
138 <xs:sequence>
139 <xs:element ref="muws1:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/>
140 </xs:sequence>
141 <xs:anyAttribute namespace="##other"/>
142 </xs:complexType>
143 </xs:element>
144 <xs:element name="DestructionNotification">
145 <xs:complexType>
146 <xs:sequence>
147 <xs:element ref="muws1:ResourceId" minOccurs="0"/>
148 </xs:sequence>
149 <xs:anyAttribute namespace="##other"/>
150 </xs:complexType>
151 </xs:element>
152 <xs:complexType name="SituationCategoryType">
153 <xs:complexContent>
154 <xs:extension base="muws2:CategoryType">
155 <xs:sequence>
156 <xs:element name="SituationName" minOccurs="0"/>
157 </xs:sequence>
158 </xs:extension>
159 </xs:complexContent>
160 </xs:complexType>
161 <xs:element name="fred" type="xs:string"/>
162 <xs:complexType name="SubstitutableMsgType">
163 <xs:sequence>
164 <xs:element name="Value" type="xs:anySimpleType" minOccurs="0" maxOccurs="unbounded"/>
165 </xs:sequence>
166 <xs:attribute name="MsgId" type="xs:string" use="required"/>
167 <xs:attribute name="MsgIdType" type="xs:anyURI" use="required"/>
168 </xs:complexType>
169 <xs:complexType name="SituationType">
170 <xs:sequence>
171 <xs:element name="SituationCategory" type="muws2:SituationCategoryType"/>
172 <xs:element name="SuccessDisposition" minOccurs="0">
173 <xs:simpleType>
174 <xs:restriction base="xs:string">
175 <xs:enumeration value="Successful"/>
176 <xs:enumeration value="Unsuccessful"/>
177 </xs:restriction>
178 </xs:simpleType>
179 </xs:element>
180 <xs:element name="SituationTime" type="xs:dateTime"/>
181 <xs:element name="Priority" type="xs:short" minOccurs="0"/>
182 <xs:element name="Severity" type="xs:short" minOccurs="0"/>
183 <xs:element name="Message" type="muws2:LangString" minOccurs="0"/>
184 <xs:element name="SubstitutableMsg" type="muws2:SubstitutableMsgType" minOccurs="0"/>
185 </xs:sequence>
186 </xs:complexType>
187 <xs:element name="Situation" type="muws2:SituationType"/>
188 <xs:complexType name="EventCorrelationPropertiesType">
189 <xs:sequence>
190 <xs:element name="repeatCount" minOccurs="0">
191 <xs:simpleType>
192 <xs:restriction base="xs:short">
193 <xs:minInclusive value="0"/>
194 </xs:restriction>
195 </xs:simpleType>
196 </xs:element>
197 <xs:element name="elapsedTime" minOccurs="0">
198 <xs:simpleType>
199 <xs:restriction base="xs:long">
200 <xs:minInclusive value="0"/>
201 </xs:restriction>
202 </xs:simpleType>
203 </xs:element>
204 </xs:sequence>
205 <xs:attribute name="sequenceNumber" type="xs:unsignedLong"/>
206 </xs:complexType>
207 <xs:element name="EventCorrelationProperties" type="muws2:EventCorrelationPropertiesType"/>
208 <xs:complexType name="MsgCatalogInformationType">
209 <xs:sequence>
210 <xs:element name="msgCatalog" type="xs:anyURI"/>
211 <xs:element name="msgCatalogType" type="xs:anyURI" minOccurs="0"/>
212 </xs:sequence>
213 </xs:complexType>
214 <xs:element name="MsgCatalogInformation" type="muws2:MsgCatalogInformationType"/>
215 <!-- ##### Metadata description elements ##### -->
216 <xs:element name="Capability" type="xs:anyURI"/>
217 <xs:complexType name="DialectableExpressionType" mixed="true">
218 <xs:sequence>
219 <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
220 </xs:sequence>
221 <xs:attribute name="Dialect" type="xs:anyURI" use="required"/>
222 <xs:anyAttribute namespace="##other"/>
223 </xs:complexType>
224 <xs:element name="ValidWhile" type="muws2:DialectableExpressionType"/>
225 <xs:element name="Units" type="xs:string"/>
226 <xs:element name="ChangeType">
227 <xs:simpleType>
228 <xs:restriction base="xs:string">
229 <xs:enumeration value="Counter"/>
230 <xs:enumeration value="Gauge"/>
231 <xs:enumeration value="Unknown"/>
232 </xs:restriction>
233 </xs:simpleType>
234 </xs:element>
235 <xs:element name="TimeScope">
236 <xs:simpleType>
237 <xs:restriction base="xs:string">
238 <xs:enumeration value="Interval"/>
239 <xs:enumeration value="PointInTime"/>
240 <xs:enumeration value="SinceReset"/>
241 </xs:restriction>
242 </xs:simpleType>
243 </xs:element>
244 <xs:element name="GatheringTime">
245 <xs:simpleType>
246 <xs:restriction base="xs:string">
247 <xs:enumeration value="OnChange"/>
248 <xs:enumeration value="Periodic"/>
249 <xs:enumeration value="OnDemand"/>
250 <xs:enumeration value="Unknown"/>
251 </xs:restriction>
252 </xs:simpleType>
253 </xs:element>
254 <xs:element name="CalculationInterval" type="xs:duration"/>
255 <xs:element name="MetricGroup" type="xs:anyURI"/>
256 <xs:element name="PostCondition" type="muws2:DialectableExpressionType"/>
257 <!-- ========= StartSituation ============ -->
258 <xs:element name="StartSituation">
259 <xs:complexType>
260 <xs:complexContent>
261 <xs:restriction base="muws2:SituationCategoryType"/>
262 </xs:complexContent>
263 </xs:complexType>
264 </xs:element>
265 <xs:element name="StartInitiated">
266 <xs:complexType>
267 <xs:complexContent>
268 <xs:restriction base="muws2:SituationCategoryType">
269 <xs:sequence>
270 <xs:element ref="muws2:StartSituation"/>
271 </xs:sequence>
272 </xs:restriction>
273 </xs:complexContent>
274 </xs:complexType>
275 </xs:element>
276 <xs:element name="RestartInitiated">
277 <xs:complexType>
278 <xs:complexContent>
279 <xs:restriction base="muws2:SituationCategoryType">
280 <xs:sequence>
281 <xs:element ref="muws2:StartSituation"/>
282 </xs:sequence>
283 </xs:restriction>
284 </xs:complexContent>
285 </xs:complexType>
286 </xs:element>
287 <xs:element name="StartCompleted">
288 <xs:complexType>
289 <xs:complexContent>
290 <xs:restriction base="muws2:SituationCategoryType">
291 <xs:sequence>
292 <xs:element ref="muws2:StartSituation"/>
293 </xs:sequence>
294 </xs:restriction>
295 </xs:complexContent>
296 </xs:complexType>
297 </xs:element>
298 <!-- ========= StopSituation ============ -->
299 <xs:element name="StopSituation">
300 <xs:complexType>
301 <xs:complexContent>
302 <xs:restriction base="muws2:SituationCategoryType"/>
303 </xs:complexContent>
304 </xs:complexType>
305 </xs:element>
306 <xs:element name="StopInitiated">
307 <xs:complexType>
308 <xs:complexContent>
309 <xs:restriction base="muws2:SituationCategoryType">
310 <xs:sequence>
311 <xs:element ref="muws2:StopSituation"/>
312 </xs:sequence>
313 </xs:restriction>
314 </xs:complexContent>
315 </xs:complexType>
316 </xs:element>
317 <xs:element name="AbortInitiated">
318 <xs:complexType>
319 <xs:complexContent>
320 <xs:restriction base="muws2:SituationCategoryType">
321 <xs:sequence>
322 <xs:element ref="muws2:StopSituation"/>
323 </xs:sequence>
324 </xs:restriction>
325 </xs:complexContent>
326 </xs:complexType>
327 </xs:element>
328 <xs:element name="PauseInitiated">
329 <xs:complexType>
330 <xs:complexContent>
331 <xs:restriction base="muws2:SituationCategoryType">
332 <xs:sequence>
333 <xs:element ref="muws2:StopSituation"/>
334 </xs:sequence>
335 </xs:restriction>
336 </xs:complexContent>
337 </xs:complexType>
338 </xs:element>
339 <xs:element name="StopCompleted">
340 <xs:complexType>
341 <xs:complexContent>
342 <xs:restriction base="muws2:SituationCategoryType">
343 <xs:sequence>
344 <xs:element ref="muws2:StopSituation"/>
345 </xs:sequence>
346 </xs:restriction>
347 </xs:complexContent>
348 </xs:complexType>
349 </xs:element>
350 <!-- ========= RequestSituation ============ -->
351 <xs:element name="RequestSituation">
352 <xs:complexType>
353 <xs:complexContent>
354 <xs:restriction base="muws2:SituationCategoryType"/>
355 </xs:complexContent>
356 </xs:complexType>
357 </xs:element>
358 <xs:element name="RequestInitiated">
359 <xs:complexType>
360 <xs:complexContent>
361 <xs:restriction base="muws2:SituationCategoryType">
362 <xs:sequence>
363 <xs:element ref="muws2:RequestSituation"/>
364 </xs:sequence>
365 </xs:restriction>
366 </xs:complexContent>
367 </xs:complexType>
368 </xs:element>
369 <xs:element name="RequestCompleted">
370 <xs:complexType>
371 <xs:complexContent>
372 <xs:restriction base="muws2:SituationCategoryType">
373 <xs:sequence>
374 <xs:element ref="muws2:RequestSituation"/>
375 </xs:sequence>
376 </xs:restriction>
377 </xs:complexContent>
378 </xs:complexType>
379 </xs:element>
380 <!-- ========= DestroySituation ============ -->
381 <xs:element name="DestroySituation">
382 <xs:complexType>
383 <xs:complexContent>
384 <xs:restriction base="muws2:SituationCategoryType"/>
385 </xs:complexContent>
386 </xs:complexType>
387 </xs:element>
388 <xs:element name="DestroyInitiated">
389 <xs:complexType>
390 <xs:complexContent>
391 <xs:restriction base="muws2:SituationCategoryType">
392 <xs:sequence>
393 <xs:element ref="muws2:DestroySituation"/>
394 </xs:sequence>
395 </xs:restriction>
396 </xs:complexContent>
397 </xs:complexType>
398 </xs:element>
399 <xs:element name="DestroyCompleted">
400 <xs:complexType>
401 <xs:complexContent>
402 <xs:restriction base="muws2:SituationCategoryType">
403 <xs:sequence>
404 <xs:element ref="muws2:DestroySituation"/>
405 </xs:sequence>
406 </xs:restriction>
407 </xs:complexContent>
408 </xs:complexType>
409 </xs:element>
410 <!-- ========= CreateSituation ============ -->
411 <xs:element name="CreateSituation">
412 <xs:complexType>
413 <xs:complexContent>
414 <xs:restriction base="muws2:SituationCategoryType"/>
415 </xs:complexContent>
416 </xs:complexType>
417 </xs:element>
418 <xs:element name="CreateInitiated">
419 <xs:complexType>
420 <xs:complexContent>
421 <xs:restriction base="muws2:SituationCategoryType">
422 <xs:sequence>
423 <xs:element ref="muws2:CreateSituation"/>
424 </xs:sequence>
425 </xs:restriction>
426 </xs:complexContent>
427 </xs:complexType>
428 </xs:element>
429 <xs:element name="CreateCompleted">
430 <xs:complexType>
431 <xs:complexContent>
432 <xs:restriction base="muws2:SituationCategoryType">
433 <xs:sequence>
434 <xs:element ref="muws2:CreateSituation"/>
435 </xs:sequence>
436 </xs:restriction>
437 </xs:complexContent>
438 </xs:complexType>
439 </xs:element>
440 <!-- ========= ConnectSituation ============ -->
441 <xs:element name="ConnectSituation">
442 <xs:complexType>
443 <xs:complexContent>
444 <xs:restriction base="muws2:SituationCategoryType"/>
445 </xs:complexContent>
446 </xs:complexType>
447 </xs:element>
448 <xs:element name="ConnectInitiated">
449 <xs:complexType>
450 <xs:complexContent>
451 <xs:restriction base="muws2:SituationCategoryType">
452 <xs:sequence>
453 <xs:element ref="muws2:ConnectSituation"/>
454 </xs:sequence>
455 </xs:restriction>
456 </xs:complexContent>
457 </xs:complexType>
458 </xs:element>
459 <xs:element name="ReconnectInitiated">
460 <xs:complexType>
461 <xs:complexContent>
462 <xs:restriction base="muws2:SituationCategoryType">
463 <xs:sequence>
464 <xs:element ref="muws2:ConnectSituation"/>
465 </xs:sequence>
466 </xs:restriction>
467 </xs:complexContent>
468 </xs:complexType>
469 </xs:element>
470 <xs:element name="ConnectCompleted">
471 <xs:complexType>
472 <xs:complexContent>
473 <xs:restriction base="muws2:SituationCategoryType">
474 <xs:sequence>
475 <xs:element ref="muws2:ConnectSituation"/>
476 </xs:sequence>
477 </xs:restriction>
478 </xs:complexContent>
479 </xs:complexType>
480 </xs:element>
481 <!-- ========= ReportSituation ============ -->
482 <xs:element name="ReportSituation">
483 <xs:complexType>
484 <xs:complexContent>
485 <xs:restriction base="muws2:SituationCategoryType"/>
486 </xs:complexContent>
487 </xs:complexType>
488 </xs:element>
489 <xs:element name="PerformanceReport">
490 <xs:complexType>
491 <xs:complexContent>
492 <xs:restriction base="muws2:SituationCategoryType">
493 <xs:sequence>
494 <xs:element ref="muws2:ReportSituation"/>
495 </xs:sequence>
496 </xs:restriction>
497 </xs:complexContent>
498 </xs:complexType>
499 </xs:element>
500 <xs:element name="SecurityReport">
501 <xs:complexType>
502 <xs:complexContent>
503 <xs:restriction base="muws2:SituationCategoryType">
504 <xs:sequence>
505 <xs:element ref="muws2:ReportSituation"/>
506 </xs:sequence>
507 </xs:restriction>
508 </xs:complexContent>
509 </xs:complexType>
510 </xs:element>
511 <xs:element name="HeartbeatReport">
512 <xs:complexType>
513 <xs:complexContent>
514 <xs:restriction base="muws2:SituationCategoryType">
515 <xs:sequence>
516 <xs:element ref="muws2:ReportSituation"/>
517 </xs:sequence>
518 </xs:restriction>
519 </xs:complexContent>
520 </xs:complexType>
521 </xs:element>
522 <xs:element name="StatusReport">
523 <xs:complexType>
524 <xs:complexContent>
525 <xs:restriction base="muws2:SituationCategoryType">
526 <xs:sequence>
527 <xs:element ref="muws2:ReportSituation"/>
528 </xs:sequence>
529 </xs:restriction>
530 </xs:complexContent>
531 </xs:complexType>
532 </xs:element>
533 <xs:element name="TraceReport">
534 <xs:complexType>
535 <xs:complexContent>
536 <xs:restriction base="muws2:SituationCategoryType"&g -
Can't create defaultTable when registering XML Schema
Hi,
when registering an XML Schema with a xdb:defaultTable Attribute the default table is not created. The user owns role XDBADMIN!
What goes wrong with my example??
<code>
<?xml version='1.0'?>
<xsd:schema xmlns:xdb="http://xmlns.oracle.com/xdb"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="Invoice" xdb:defaultTable="INVOICE_SIMPLE">
<xsd:complexType >
<xsd:sequence>
<xsd:element name="CustomerRef" type="xsd:integer" />
<xsd:element name="Supplier" type="xsd:string" />
<xsd:element name="TotalAmount" type="xsd:decimal" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
begin
dbms_xmlschema.registerSchema('invoice_simple.xsd', getDocument('invoice_simple.xsd'),
FALSE, TRUE, FALSE, FALSE);
end;
</code>
Any hint is wellcome!
Thanx.this works fine for me:
declare
doc varchar2(2000) := '<xsd:schema xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="_new"
xmlns="_new">
<xsd:element name="Invoice" xdb:defaultTable="INVOICE_SIMPLE">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CustomerRef" type="xsd:integer"/>
<xsd:element name="Supplier" type="xsd:string"/>
<xsd:element name="TotalAmount" type="xsd:decimal"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>';
begin
dbms_xmlschema.registerSchema('invoice_simple.xsd', doc);
end; -
[KDE 4.6] No preview when changing color scheme
In systemsettings > appearence > color schemes when change scheme in preview area dysplayed the same scheme, which current set. I test this bug in two machines. On one of them with new kde-profile.
I noticed it too; that is, each preview shows the last active color scheme when I change it. I've been using 4.6 since RC1, and wanted to wait and see if others had the problem after upgrading to the final release. A bug report was file a couple weeks ago; you can view it here.
Last edited by ANOKNUSA (2011-01-28 16:04:06) -
ORA-00600 error when registering XML Schema
Dear Mark!
1. Database version: 9.2.0.3.0
2. Operating system: Windows XP Prof
3. XML Schema: (it's too big to be posted_
4. Instance document: no
5. SQL statement used to register the schema
DBMS_XMLSCHEMA.registerSchema(schemaURL => aSchemaURL, schemaDoc => fBFile_Loc);
6. SQL statement that exposes the problem: above
Attempt to register XML Schema caused the following error:
ORA-00600: internal error code, arguments: [qmtsGetAttrElemName1], [], [], [], [], [], [], []
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 131
ORA-06512: at "DVLP.PRIME_BRIDGE", line 91
ORA-06512: at line 6
What does it mean?
Thank you in advance
Artem RodinIf you cannot post the schema please open a itar with oralce support so that the schema can be uploaded.
-
Mapping problem with XML scheme
Hi All,
I have a scenario which I am trying to send a XML file through SFTP (Advanco) to a Z RFC.
I created the message mapping, but I am dealing with a issue that I would like to see if it already happened with someone else and which is the best way to solve it.
In the message mapping - test tab - source view we can find this xml tag regarding the messagetype (see that my MT is called ROOT)
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ROOT xmlns:ns0="http://www.post.ch/schemas/dfu/2006/20/Report6">
the problem is, when I am testing the interface the original file comes like this below
<?xml version="1.0" encoding="UTF-8"?>
<ROOT xmlns="http://www.post.ch/schemas/dfu/2006/20/Report6">
without ns0:
And if I test in message mapping without ns0: I have the problem.
Shouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
Does someone have any suggestion regarding my issue above ?
Thank you
Regards
Diego
Edited by: Diego Crespo on Feb 10, 2011 10:01 AMShouldnt it be equivalent ? I mean, as far as I know the ns0: shouldnt be a problem
when you have a namespace in the message then you need to associate it with some prefix....since ns0 (or any other prefix) is not present you are getting the error....having the namespace but not ns0 is the problem.
XMLAnonymizer bean may help you to add the namespace prefix... -
Specify field mapping when changing table location
I want to change the tables in a report to refer to database tables with a different schema, and specify the mapping of fields in code.
I already have code that changes table locations successfully when the schema does not differ, using the RAS API. As far as I can tell, the RAS API doesn't have a way of handling schema differences. Is that true?
OTOH, the higher-level CR API does appear to have a mechanism to do field mapping, using the FieldMapping event in the ReportDocument class. I've been trying to use this API for the job, but I don't seem to be able to change the location of a table in the report.
Here's an example scenario:
The report was created using an ODBC data source Source1 that contains a table Table1
I have an ODBC data source Source2 that contains Table1 as well as a table Table2 that is identical to Table1 except that the field names are all slightly different
I want to change the report so that it uses Table2 in Source2
I've managed to get the report switched to Source2 with code like this:
report.DataSourceConnections[0].SetConnection("Source2", "", id, pwd);
Here's the code I'm using to try to change the report table to refer to Table2:
Table table = report.Database.Tables[0]; // only one table in the report
TableLogOnInfo logOnInfo = table.LogOnInfo;
logOnInfo.TableName = "Table2";
table.ApplyLogOnInfo(logOnInfo);
report.VerifyDatabase();
I've also tried the simpler
table.Location = "Table2";
Neither approach changes the table location. I know this because when I preview the report I see data. Since the field names are all different, changing the location should have removed all the fields from the report. (Also, the event handler I have hooked up to the FieldMapping event is not called. Yes, I did enable the event in the ReportDocument.)
So:
How do you change the location of a table using the high-level API?
If you change the location using the RAS API, is the FieldMapping event fired? (Haven't tried this, but somehow I doubt it.)
Is there a way to do field mapping with the RAS API?
Thanks!
- rick cameronHi Rick
This is not considered a bug. It is a limitation that has been discusses extensively in many of our internal meetings. The implementation job proved to be much too massive and with highly limited ROI. E.g.; the number of requests for the feature is just not there...
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter -
Issue in OWB mapping - when changing source and target database
Hi,
I need help for resolution of the issue I am facing when moving mapping from development environment to QA.
Here is situation,
We develop ETL using one source, one staging and one target database.
In development we use one control_center for Source to staging and another control center staging to target.
All works fine in development.
Now I have created new runtime repository and imported all OWB projects (with full dependencies, exact replica of development). Now I need to change source and staging and target as different database.
I have created new database location connections and defined/attached DB connectors with stage and target location.
Now issues are
1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
Not sure how to proceed from here.
I have recreated new repository and re-imported all project/mappings and defined all connection but still same issue.
Thanks in advance,
Vipin1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
The above error were resolved when re-synchronized the table (for few I have to reimport the table) and mapping.
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
The above error still pending. My target mapping are not able to deployed/compiled.
For the above I have defined one Staging location to one target target location and target location have connector to staging (not sure if I have to define connector name same as staging location, as I have created DB connector with different name but reference database is same as staging location).
Mapping are assoicated with desired data locatoin and meta data.
control center is also have that data location.
Mapping are configured for the desired location. -
How do i change xml schema in java
i want to change a oracle.xml.parser.schema.xmlschema object in java (adding or changing elements, types, etc). is there some hidden way i didn't think of besides changing the xmldocument object behind the schema and rebuilding the schema? i find that rather uncomfortable.
i'd appreciate any answers, even negative ones :)
thanksRefer to
http://java.sun.com/webservices/docs/1.1/tutorial/doc/JAXPDOM9.html -
Refresh mapping when changes were done to the database
I created a mapping with three tables to java objects. I added one extra column to the table. How do I refresh/synchronize/map my objects again? I'm using JDeveloper 10.1.3
In the offline database schema you can either re-import or refresh the table definitions. This will make the new column available for mapping purposes.
Doug
Maybe you are looking for
-
How to move Projects and Events with iPhoto video included in iMovie '11?
I work with a group of educators using iPads for video. One method for getting their clips into iMovie '11 is via iPhoto and then using the iPhoto Video link in iMovie to get the footage on a timeline (trying to import directly into iMovie '11, using
-
Dear Experts, I am quiet confused about this clearing process in SAP. For example a cash discount in SAP is posted with the following entry 01 Cust a/c 15000 40 Cash disc a/c 3000 50 Sales or revenue a/c 18000. The above open item in the customer acc
-
Unable to retrive the service details
Good day. After i've restarted the UCCX mashine,in the control center i have the "Unable to retrive the service details" and "java.lang.Null.pointer.exception" concerning to the recording and statistics service. But the service itself working properl
-
ICHAT: It says my Built-in iSight is in use my another program (help)
Alright. So at first my iSight worked in nothing. so i reinstalled quicktime. Now it works in photobooth and iMovie But it still says its in use by another program in ichat This is my first mac, its very upsetting I looked in the system profiler and
-
How to refer the class package "com.sapportals.connector" for MDM API?
Hi, Iam trying to execute one example mdm api program in dynpro/ejb. I could not refer the class package com.sapportals.connector. What SCA or build path package needed for dev time and runtime and where do i get that. Please help me. Thanks Hari