Weblogic.xml.schema.binding.DeserializationException

Hi all.
I am using WLS 8 and in my web application I have implemented a web service client. The client uses an API that I created with the clientgen executable providing a valid WSDL. That WSDL defines custom data types that are used during the communication to the web service server. Whenever I use one of those custom data types in my web service request everything works fine. But when I call a web service that responds with one of those custom data types I am getting the following exception:
Error occured while calling webservice! Error : web service invoke failed; nested exception is:
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure.
The weird thing is that weblogic somehow tries to refer to that custom data type with an IP address (e.g. 123.123.123.123) but in the WSDL all the URLs are defined with names (e.g. my.web-service.de) .
Has anyone experienced a similar problem and/or can help me with this issue?

Similar Messages

Webserviceclient.jar does not have weblogic/xml/schema/binding/SequenceCodecBase

Hello,
I am building JSP client for webservice. The client is deployed on tomcat 4.x.
This time fortunatelly clientgen swallowed WSDL and I got client code generated.
I added webserviceclient.jar to WEB-INF/lib. However I am getting java.lang.NoClassDefFoundError:
weblogic/xml/schema/binding/SequenceCodecBase Exception.
Indeed webserviceclient.jar has no weblogic/xml/schema/binding/SequenceCodecBase
class defined. Do I have bad webserviceclient.jar or am I doing something wrong?
Also I've found weblogic/xml/schema/binding/SequenceCodecBase in weblogic.jar
so I added it to my application. Now I am getting
java.lang.ClassCastException: com.sun.xml.messaging.soap.dom4j.BodyImpl
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:218)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:268)
at weblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation.java:328)
at weblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation.java:304)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:141)
at client.WeatherServicesSoap.GetWeather(WeatherServicesSoap.java:69)
at client.WeatherServicesSoap.GetWeather(WeatherServicesSoap.java:89)
What am I doing wrong?
Thanks,
Aleksey

It looks like you have the JAXM suns RI registered. We do not
work with other JAXM impls. To set your MessageFactory to
use WLS jaxm impl do the following:
System.setProperty( "javax.xml.soap.MessageFactory",
"weblogic.webservice.core.soap.MessageFactoryImpl" );
before you invoke the web service method.
regards,
-manoj
"Aleksey" <[email protected]> wrote in message
news:3c9a43f7$[email protected]..
>
Hello,
I am building JSP client for webservice. The client is deployed on tomcat4.x.
This time fortunatelly clientgen swallowed WSDL and I got client codegenerated.
I added webserviceclient.jar to WEB-INF/lib. However I am gettingjava.lang.NoClassDefFoundError:
weblogic/xml/schema/binding/SequenceCodecBase Exception.
Indeed webserviceclient.jar has noweblogic/xml/schema/binding/SequenceCodecBase
class defined. Do I have bad webserviceclient.jar or am I doing somethingwrong?
>
Also I've found weblogic/xml/schema/binding/SequenceCodecBase inweblogic.jar
so I added it to my application. Now I am getting
java.lang.ClassCastException: com.sun.xml.messaging.soap.dom4j.BodyImpl
atweblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:218)
atweblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:268)
atweblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation
.java:328)
atweblogic.webservice.core.DefaultOperation.invokeMultiOutput(DefaultOperation
.java:304)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:141)
atclient.WeatherServicesSoap.GetWeather(WeatherServicesSoap.java:69)
atclient.WeatherServicesSoap.GetWeather(WeatherServicesSoap.java:89)
>
What am I doing wrong?
Thanks,
Aleksey

ClassNotFoundException at weblogic.xml.schema.binding.util.ClassUtil!!

Hi,
We are getting below exception everytime we are starting the weblogic 10 server. This is coming in clustered as well as non-clustered environment. Full stack trace is as below:-
<03-Oct-2009 12:24:19 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
Any pointers will be helpful.....
Thanks & Regards,
Sanjeev

How are you starting your weblogic server? From the console or command prompt? Try both ways and see still the error occurs. Both uses different script to start the server. See that makes any difference.

XML Schema binding - dynamic form

I am new to Designer and XML. I have been given a basic interactive form and have persevered for a couple of (often frustrating) weeks to extend its functionality to link to an xml schema and provide for dynamic record creation. Unfortunately I am still having problems when adding new instances of subforms. I have a main form for reporting issues. Underneath it there are major components on a subform (can be multiple major components for each issue) and under major components are sub-components (can be multiple sub-components for each major component) on a child subform of major. I can add and delete instances of the subforms for both levels of records. I have created an xml schema based on the form since it already existed, and so the form fields have not inherited properties from the schema. However, I have bound the fields in the form to the xml fields through a data connection. The schema basically looks as follows (bot not literally the same as you will see from the tags): <element complextype issue> <element issueId string/> ... ... <element complextype majorcomponent unbounded> <element majcomponentname string/> ... <element complextype subcomponent unbounded> <element subcomponent string/> <element quantity string/> ... ... </element> </element> </element> My problem is as follows: When I add an instance of a sub-component or major component subform, the first new instance appears to work correctly. However, every subsequent one inherits the values of the previous record and when it is changed, it changes the values of existing fields of the same name but of a different node. When I change each element in the xml schema to "unbounded", the forms appear to work properly but the values are then not nested correctly in the outputted xml data file (many records will appear under one sub-component, for example, when a new sub-component should be added for each). I suspected my problem might be that the "unbounded" property in the schema of the major component and sub-component elements are not linked to the Designer form because the major component and sub-component subforms are not bound to the xml schema. The reason they are not bound is because if I bind the subform, the first element, major/sub component name as applicable, loses its binding. I am sorry if this doesn't make any sense but I am hoping that someone might recognise the problem I am talking about as it is really creating much bother. Thanks.

Thanks Justin for the reply. Unfortunately I can't explain exactly what was happening because I didn't keep sufficient notes and now the form is behaving differently. You are right in that when I bind the subform to the xml schema element, child fields do change their bindings from a full to a relative path. I had seen this before on all except the first field on a subform, which had losts any binding reference at all.
I finally gave up on the schema and bound the forms to sample xml data. This fixed my problem. Now (several days later), I have revisited the problem and deleted my data connection to the xml file to connect to the schema once again. I am quite sure I have not changed the schema at all, nor the form, but for some reason it now appears to work correctly.
I will continue to work with it, once again but thanks very much for your interest.

Dynamic tables with XML schema binding

Hello,
I'm currently fighting a strange issue dealing with a complex dynamic form. This form contains multiple dynamic tables to which the user may add new lines or delete lines that are no longer needed. This is being implemented using the instanceManager and works just fine.
However, if I try to bind XML based data to this table, it looks like if rows added by the instance manager are always bound to the same record (they all contain identical values). The XML schema is correct, the issue also happens with sample XML data files.
This seems to have something to do with the programatically added lines, but I have run out of ideas ... Can anyone provide some pointers?
Thanks a million,
Steffen.

Thanks for the reply, Paul.
I have the question about the schema,
say i have a table like this:
Item | Cost
A | 10.3
B | 21.1
Total| 31.4
and my schema is:
so when I bind the table row should it be $.ItemTable[*].Item ?

XML schema binding

Hi,
when I bind a form to a XML schema, what ever changes to the XML schema like the max length, will it be reflected in the form? Seem like it is not. I have to delete the existing data connection and created a new data connection, and rebind the XML to the form items. What if there is many changes to the XML, all the items will have to be rebinded? Oh...:(

@ Edgar_van_Waardenburg:
"You actually create a new form-field, which automatically inherits its type and properties from the related data type AT THAT MOMENT"
As quoted above from your reply, do you mean that what type of control is generated for a xml element is defined as type in the schema?
When i make a dataconnection using a schema file(.xsd), all my elements are shown as TextField. While I need some radio buttons and checkboxes etc...
Can i know how to specify the type in schema so that different types of controls can be generated? Below is my schemal defination.
<?
xml version="1.0" encoding="utf-8"?><
xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"><
xs:element name="form1"><
xs:complexType><
xs:sequence><
xs:element maxOccurs="unbounded" name="sub"><
xs:complexType><
xs:sequence><
xs:element minOccurs="0" name="GroupTitle" type="xs:string" /><
xs:element ref="QuestionInfo" minOccurs="0" maxOccurs="unbounded" /><
xs:element ref="sub" minOccurs="0" maxOccurs="unbounded" /></
xs:sequence></
xs:complexType></
xs:element></
xs:sequence></
xs:complexType></
xs:element><
xs:element name="sub"><
xs:complexType><
xs:sequence><
xs:element minOccurs="0" name="GroupTitle" type="xs:string" /><
xs:element ref="QuestionInfo" minOccurs="0" maxOccurs="unbounded" /><
xs:element ref="sub" minOccurs="0" maxOccurs="unbounded" /></
xs:sequence></
xs:complexType></
xs:element><
xs:element name="QuestionInfo"><
xs:complexType><
xs:sequence><
xs:element minOccurs="0" name="SubTYPE" type="xs:string" /><
xs:element minOccurs="0" name="Question" type="xs:string" /><
xs:element minOccurs="0" maxOccurs="unbounded" name="item"><
xs:complexType><
xs:attribute name="token" type="xs:string" use="required" /><
xs:attribute name="uiname" type="xs:string" use="required" /></
xs:complexType></
xs:element></
xs:sequence></
xs:complexType></
xs:element></
xs:schema>
Thanx

Autotype from XML schema problems

Hello,
I am trying to autotype the following Xml schema:
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3
My build.xml contains:
<target name="autotype" >
 <autotype
 schemaFile="REL-5-MM7-1-3.xsd"
 targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"
 packageName="com.foo"
 keepGenerated = "True"
 destDir="output" />
</target>
1.
I run using ant but it fails..
SubmitRspTypeCodec.java:15: cannot resolve symbol
[autotype] symbol : class GenericResponseTypeCodec
[autotype] location: package soap
[autotype] extends javax.xml.soap.GenericResponseTypeCodec
weblogic.webservice.tools.build.WSBuildException: Failed to do type mapping -
with nested exception:
[weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
- with nested exception:
[java.io.IOException: Compiler failed executable.exec]]
The interesting point is when i deleted following 3 lines from schema (line 413
to 415 in REL-5-MM7-1-3.xsd),
<xs:sequence>
 <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
no compile error is thrown.
2.
But the weird thing is that some of classes are not generated, for example SubmitReqType,
ReplaceReqType. This is because they reference RelativeOrAbsoluteDateType (line
367). And RelativeOrAbsoluteDateType contains the following union definition:
<xs:union memberTypes="xs:dateTime xs:duration"/>
i think that this union definition might cause problem but neither an error nor
a warning message is submitted from ant. It says successful but missing classes.
I am struggling with these 2 problems for days, any help would be appreciated.
Thanks,
aLi

Hi Ali,
I suspect that the reason you are having this problem is covered in the following
link:
http://e-docs.bea.com/wls/docs81/webserv/overview.html#1074641
I guess my question is, what else do you have in the build.xml that uses (or attempts
to use) the autotype Ant task? Are you trying to build a client (i.e. a JAX-RPC
static stub) for a web service? Is this for a WebLogic Web Service you want to
build? Or are you just trying to see if autotype can process the .xsd file, in
question? If so, the above link states why it currently won't work.
One alternative option, is to use a Workshop Schema project (or XMLBeans) to process
the .xsd file. I just did that, and it worked fine :-)
Regards,
Mike Wooten
"Ali Pakkan" <[email protected]> wrote:
>
Hello,
I am trying to autotype the following Xml schema:
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3
My build.xml contains:
<target name="autotype" >
 <autotype
 schemaFile="REL-5-MM7-1-3.xsd"
 targetNamespace="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"
 packageName="com.foo"
 keepGenerated = "True"
 destDir="output" />
</target>
1.
I run using ant but it fails..
SubmitRspTypeCodec.java:15: cannot resolve symbol
[autotype] symbol : class GenericResponseTypeCodec
[autotype] location: package soap
[autotype] extends javax.xml.soap.GenericResponseTypeCodec
weblogic.webservice.tools.build.WSBuildException: Failed to do type mapping
with nested exception:
[weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
- with nested exception:
[java.io.IOException: Compiler failed executable.exec]]
The interesting point is when i deleted following 3 lines from schema
(line 413
to 415 in REL-5-MM7-1-3.xsd),
<xs:sequence>
 <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
no compile error is thrown.
2.
But the weird thing is that some of classes are not generated, for example
SubmitReqType,
ReplaceReqType. This is because they reference RelativeOrAbsoluteDateType
(line
367). And RelativeOrAbsoluteDateType contains the following union definition:
<xs:union memberTypes="xs:dateTime xs:duration"/>
i think that this union definition might cause problem but neither an
error nor
a warning message is submitted from ant. It says successful but missing
classes.
I am struggling with these 2 problems for days, any help would be appreciated.
Thanks,
aLi

Failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema

I have generated my Web Service Client Control Class based on WSDL file provided by Web Service Provider using JAX-RPC in "Oracle Workshop for WebLogic version 10.3".
I am using Web Service Client Control class in WebLogic Portal portlet backing class to invoke Web Service. But while invoking Web Service, I am getting following error:
Caused by: java.rmi.RemoteException: Failed to invoke; nested exception is:
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://xyz.com/abc/UpdateSR']:updateSRRequest}
Here is the code of my Portlet Backing class where I am using Service Control to invoke Web Service:
URL webServiceUrl = new URL(webServiceLocation);
ServiceFactory serviceFactory = ServiceFactory.newInstance();
QName qName = new QName(nameSpaceURI, serviceName);
Service siebelService = serviceFactory.createService(webServiceUrl, qName);
updateSRServiceControl siebelServiceProxy = (updateSRServiceControl)siebelService.getPort(qName, updateSRServiceControl.class);
UpdateSRResponse updateSRResponse = siebelServiceProxy.updateSR(updateSRRequest);
Please let me know if more information required.
I appreciate for help.
Thanks in advance.
Regards
Neeraj

I have generated my Web Service Client Control Class based on WSDL file provided by Web Service Provider using JAX-RPC in "Oracle Workshop for WebLogic version 10.3".
I am using Web Service Client Control class in WebLogic Portal portlet backing class to invoke Web Service. But while invoking Web Service, I am getting following error:
Caused by: java.rmi.RemoteException: Failed to invoke; nested exception is:
javax.xml.soap.SOAPException: failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://xyz.com/abc/UpdateSR']:updateSRRequest}
Here is the code of my Portlet Backing class where I am using Service Control to invoke Web Service:
URL webServiceUrl = new URL(webServiceLocation);
ServiceFactory serviceFactory = ServiceFactory.newInstance();
QName qName = new QName(nameSpaceURI, serviceName);
Service siebelService = serviceFactory.createService(webServiceUrl, qName);
updateSRServiceControl siebelServiceProxy = (updateSRServiceControl)siebelService.getPort(qName, updateSRServiceControl.class);
UpdateSRResponse updateSRResponse = siebelServiceProxy.updateSR(updateSRRequest);
Please let me know if more information required.
I appreciate for help.
Thanks in advance.
Regards
Neeraj

How to bind data from script created variable to embed element of XML schema (xsd) in "Data View"

Hi, i have got another problem with livecycle designer scripting.
I have got script line which is defining of string variable:
var aaa = "this is my string";
and i have got embed XML schema like this (it`s only short part of whole file):
... xs:element name="bbb" type="xs:string"/ ...
After saving data to XML i would like to get "this is my string" as a value of my "bbb" XML element.
To save this data i`m using submit button which is connect with submit.php file on my server.
How to connect script created variable and embed XML schema element which is present on my "Data View" tab.
Please help me a bit becouse i don`t know even where to search answer of it...
Of course i know possibilities to create fake unvisible text field object and bind it with 'bbb' and than put "this.rawValue = aaa" to connect those two variables but i think that is not a good idea to solve it in that way. It`s too primitive

i solve it, i should write this:
xfa.datasets.data.bbb.value = aaa;

How to create our own XML Schema (.xsd) in Weblogic WorkShop

Hi,
I am new to Weblogic Workshop.I want to create one xml schema with custom elements.
when I am creating a file xml schema(.xsd).The file contains default namespace and no child elements in it.I don't know how to add elements to that file.
please tell me how to add parent elements and child elements and also our own xml namingspace.

Hi Sivaram,
Unfortunately, the 8.1 IDE did not have special tooling for schema generation.
You will need to create it by hand or using an external tool
If you are using an external tool to create the file within the schema project, you might want to disable the schema project auto build, which will be triggered every time a file save takes place
cheers
Raj

BINDING the xml schema schema

Hello all,
Did anyone tried to take the schema of "xml schema" and generate jaxb code for it?
does anyone knows where can i find such schema?
thanx

It's fairly easy and thoroughly explained in The Java Web Services Tutorial (available from http://java.sun.com)
see chapter "using JAXB"

XML Schema to generate table data from a repeating subform data

Hi All, I would like to have a check box that when checked, will hide a quotation form, and make a purchase order form visible, carrying over some of the field data from the quotation form into a new table on the Purchase order form. I've attached this form at https://workspaces.acrobat.com/?d=pqpsXx5VPi*LkMeVKrX57w if you would like to take a look. When the checkbox is unchecked, it will hid the PO form, and make the quite form visible.
The idea behind this is that my client will create his quote and send t to his customer. Once the customer accepts the quote, he can just click a button to generate his purchase order that he will send to his supplier.
It seems that because I've got buttons to add rows on the quote form that the problem is more complex. I would be able to do this myself if the table had a fixed number of rows and I was able to use global fields and naming each cell something different, but beacuse it's a single repeating subform, I can't seem to make it work at all.
I understand that because its a repeating subform that I need to create an XML schema to accomplish this, but also can't figure out for the life of me how to actually create the schema. I've been reading tons of tutorials, but no clue how to apply it to my specific need. I have only been able only find info on how to bind the data source once it's been created.
I would be forever grateful if anyone could help me out.
Thank you!

I've edited your form and put it here.
Here's what I've done:
Inserted script into your checkbox renamed Accpted that hides/shows the Purchase Order/ Sales Quotation
I've included a scripting object with a function I wrote to transfer data from like named fields/subforms from one section to another
Inserted a few common fields into your Purchase Order table
What you need to do is complete the development of your Purchase Order table. Make sure the common fields between the quote and purchase tables have the same names in order to transfer the data.
No schema necessary.
Kyle

Forms pulling Multiple Records from an XML Schema and XML data files - Adobe LiveCycle Designer

I built a form in Adobe LiveCycle with an xml schema and data file. The problem is with how the form renders the xml data file.
I have a statement element that consists of about 6 fields (statementID, statementName, statementAddress, statementCountry, statementZip, statementDate, etc) of data in the schema that allows for multiple iterations - so one xml data file can contain multiple statements. These fields allow for null values.
But here's the problem: When any of the statements - say statement 2 of 6 - has a null value in one of the fields, if the xml data file doesn't have a placeholder
(example of placeholder: <statementName type="String"/> )in the xml for that field, my form pulls the field value from the NEXT statement.
This corrupts all the rest of the statement records, as this field is shifted up for all the rest.
I know that in the past I haven't needed a placeholder when a field was null. But I'm wondering if when the data allows for multiple records the xml data file needs to generate the placeholder. And where is the problem? In the Schema? The xml data file? My form? And the 64-thousand-dollar question: How to fix it?

If your <statement> element is the one that repeats, it should be bound to a subform with the binding string of something like $.statement[*]. Then in that subform should be your fields and they should have bindings of $.statementID, $.statementName, $.statementAddress, etc.
Kyle

Error while adding XML Schemas with cyclic references

I have to use the 3rd party bunch of XML Schema files, but two of them reference each other, i.e. there are cyclic references. ESB displays a conflict in this case.
Is there any way to resolve the problem without changing source xsd-files?
My configuration is WebLogic Platform 9.2.1 + AquaLogic Service Bus 2.6

Our scenario is that the corporate data model (in UML) is transformed into XSD and delivered as several separate XSD files. Our modellers argue that cyclic references make sense in this context and are not forbidden by the standard.
We restructured the transformation so that only a single XSD file is delivered (~550K) but this is unwieldy, inflexible and ALSB is sloooooooooow when manipulating a schema of this size inside the console.

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 
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 
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 
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  <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 
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 
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 
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 
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 
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 
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 
65 <xs:element name="CurrentTime" type="xs:dateTime"/>
66 
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 
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 
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 
102 <xs:element name="Relationship" type="muws2:RelationshipType"/>
103 
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 
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 
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 
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 
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 
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 
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 
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 
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

Weblogic.xml.schema.binding.DeserializationException

Similar Messages

Maybe you are looking for