Extract xsi:type of an element from xquery

Hi,
i need to extract the xsi:type of an element in xml.
<record A="3983" B="3983" xsi:type="listAcct:InventoryItem">
I know that for attribute we can use @ how do we extract xsi:type?
Please let me know.
Thanks

Hi,
I know that for attribute we can use @
What's the problem then?
The situation is no different, except you also have to declare the namespace prefix (if not already done) :
declare namespace xsi = "http://www.w3.org/2001/XMLSchema-instance";
let $e := <record A="3983" B="3983" xsi:type="listAcct:InventoryItem">
return $e/@xsi:type

Similar Messages

Did not find needed xsi:type attribute on element anyType

The followings exception is thrown when using the access a web service using the
proxy jar.
The return xml contains
<debts xm:bind="debts is return.safaccount.debts">
<anyType xm:multiple="debt in return.safaccount.debts">{debt}</anyType>
</debts>
debts is a vector contains Serializable Object class.
How do you resolve this?
<Nov 14, 2002 2:36:27 PM ICT> <Error> <HTTP> <101019> <[ServletContext(id=553030
0,name=EAIService,context-path=/EAIService)] Servlet failed with IOException
java.rmi.RemoteException: web service invoke failed; nested exception is:
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.sch
ema.binding.DeserializationException: did not find needed xsi:type attribute on
element <anyType>
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.bind
ing.DeserializationException: did not find needed xsi:type attribute on element
<anyType>
at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:35
9)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:465)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav

Hi Daniel,
This is really an "constructing and XMLMap issue" with WebLogic Workshop, so I
would post it on that newsweb group:
weblogic.developer.interest.workshop
BTW: Serialization/Deserialization required instanciable classes with no-arg constructors.
You should attach the WSDL for this web service, so that folks can see what Workshop
generated for the schema element(s). This (the schema elements) is probably where
the problem starts :-) Also, state if that is the default xmlmap generated by
Workshop, or a custom one.
Regards,
Mike Wooten
"daniel" <[email protected]> wrote:
>
The followings exception is thrown when using the access a web service
using the
proxy jar.
The return xml contains
<debts xm:bind="debts is return.safaccount.debts">
<anyType xm:multiple="debt in return.safaccount.debts">{debt}</anyType>
</debts>
debts is a vector contains Serializable Object class.
How do you resolve this?
<Nov 14, 2002 2:36:27 PM ICT> <Error> <HTTP> <101019> <[ServletContext(id=553030
0,name=EAIService,context-path=/EAIService)] Servlet failed with IOException
java.rmi.RemoteException: web service invoke failed; nested exception
is:
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.sch
ema.binding.DeserializationException: did not find needed xsi:type attribute
on
element <anyType>
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.bind
ing.DeserializationException: did not find needed xsi:type attribute
on element
<anyType>
at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:35
9)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:465)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav

How to extract a set of XML elements from an XML element

My XML, stored in a variable called v_XML_input, is as follows:
<Root>
<PackageName>MY_PKG</PackageName>
<ProcedureName>SAVE_ADJ_VALUES</ProcedureName>
    <Parameters>
      <Parameter>
          <Name>p_xml_string</Name>
          <Value><DocumentElement>
                   <tblAdjustments>
                     <EmpID>41439</EmpID>
                     <UserNTID>APPUSER</UserNTID>
                     <Comment>TEST RECORD</Comment>
                     <Amount>2000</Amount>
                     <RecordType>R</RecordType>
                   </tblAdjustments>
                  </DocumentElement>
          </Value>
      </Parameter>
    </Parameters>
</Root>I want to extract only whatever is between <Value> and </Value>. In this case just this:
                <DocumentElement>
                   <tblAdjustments>
                     <EmpID>41439</EmpID>
                     <UserNTID>APPUSER</UserNTID>
                     <Comment>TEST RECORD</Comment>
                     <Amount>2000</Amount>
                     <RecordType>R</RecordType>
                   </tblAdjustments>
                  </DocumentElement>The actual values between the <Value> and </Value> may not always be these same elements; they may be strings, numerical values, or other XML values.
I've tried the following in a LOOP, and it works for other strings and numerical values, but I get a ORA-30625: method dispatch on NULL SELF argument is disallowed when trying to extract an XML value as a string.
v_sql_str := v_XML_input .extract('//Parameters/Parameter[position() = '||i||']/Value/text()') .getstringVal()||'''';Any help is appreciated...TIA!

Not sure what you are actually trying to accomplish.
What's wrong with
SQL> SELECT xmlserialize(content XMLTYPE
          ('<Root>
<PackageName>MY_PKG</PackageName>
<ProcedureName>SAVE_ADJ_VALUES</ProcedureName>
    <Parameters>
      <Parameter>
          <Name>p_xml_string</Name>
          <Value><DocumentElement>
                   <tblAdjustments>
                     <EmpID>41439</EmpID>
                     <UserNTID>APPUSER</UserNTID>
                     <Comment>TEST RECORD</Comment>
                     <Amount>2000</Amount>
                     <RecordType>R</RecordType>
                   </tblAdjustments>
                  </DocumentElement>
          </Value>
      </Parameter>
    </Parameters>
</Root>'
          ).extract('//Value/*') indent)xml
FROM DUAL
XML
<DocumentElement>
<tblAdjustments>
    <EmpID>41439</EmpID>
    <UserNTID>APPUSER</UserNTID>
    <Comment>TEST RECORD</Comment>
    <Amount>2000</Amount>
    <RecordType>R</RecordType>
</tblAdjustments>
</DocumentElement> ?
Note: xmlserialize is not necessary and is there just for pretty printing the result.

element xsi:type="T3" attribute="USD" 1.99 /element mapping error ......

Dear All,
I have following source structure from WSDL file which cannot be change.
I have map it with target structure by one to one mapping. But getting following error.
Please guide me do I need to use some node function/technique to map this element with target?
because direct mapping is giving error.
Structure         Occurance     Type
-<Node>             1..1                T1
--<element>        1..1                T2
---<attribute>      1..1                T3
<element xsi:type="T3" attribute="USD">1.99</element>    it is mapped one to one graphical mapping with   <element></element>
But in mapping test I am getting error:
The prefix "xsi" for attribute "xsi:type" associated with an element type "<element>" is not bound.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: The prefix "xsi" for attribute "xsi:type" associated with an element type "<element>" is not bound.
at com.sap.aii.mappingtool.tf7.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:253)
at com.sap.aii.mappingtool.tf7.rt.xparser.XParser.run(XParser.java:79)
Caused by: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:type" associated with an element type "<element>" is not bound.
Regards

Hi Raj,
Thanks for reply..
I am not trying to map attribute to target element.
I am trying to map element (having value like 1.99) to the target element.
This element having type as well as attribute.
But in testing getting error"The prefix "xsi" for attribute "xsi:type" associated with an element type "element" is not bound."
But when I am removing type declaration from WSDL then there is no error: example following
<element attribute="USD">1.99</element> <<-mapped with>> <target element>
error is coming when source structure is like:
<element xsi:type="T3" attribute="USD">1.99</element> <<-mapped with>> <target element>
i.e. source structure is having both type & attribute.
Regards

How do I extract elements from a file?

Let's say I have a larger file with several layers and various elements on the layers - like a web page layout.
On 1 layer the is top logo.
I am trying to extract just that 1 part and save for web as small jpg or png and put that one pic in my web design app.
Q: How do I easily exctract / export / save for web (small version) just that one part?

If you do a lot of saving graphic elements from web page mock-ups, it's worth reading up on using slices.
Also have a look at layer comps. Combining the two enables you to save all the graphic elements of the web page (including various roll-over states) from one master file.

Is it possible to get the element data type of a Queue from itself?

Hi everyone,
i have a Q that has a cluster as element data type.
now when i want to enqueue
i'll use bundle-by-name
and for that i'd have to have my data-type present
(long cable from whereever (possibly from where i obtained the Q).
my question is,
whether there is a method/property-node/something that allows me to
wire the Queue Refnum into it and receive the element-data-type,
so i can then input into the top of bundle-by-name?
(i really dont want to have that cable all over the place)
the reason i ask here is that
the help for the outgoing Queue Refnum from the Obtain Queue method,
shows the element-data-type and so i hope there might be a solution.
thx for your time
and cheers
j
Solved!
Go to Solution.

If I understand your question correctly, the answer is "Yes, it's very easy ..."
The answer is "Preview Queue". Here I create a Queue of some mysterious type (it's a cluster having a Thing and a Center, but you don't know that yet). I take the Queue reference from whereever I can find it and pass it into Preview Queue Element. I take the output and use it to define my cluster in Bundle by Name.
Two caveats. This copies the first element of the Queue into the cluster, so you probably need to be sure to define all of the elements of your cluster. But what if the Queue is empty (as mine is, above, as I just Obtained it) -- well, that's why 0 is wired into the TimeOut input, since I do not want to wait "forever" (-1) for the empty Queue to have an element! Turns out that even in this case, you still get the correct Cluster elements!
Neat, huh?
Bob Schor

Reduce Sales Order element from MRP using MIGO (Movement Types)

Hi Folks,
I was wondering if its possible to remove the Sales Order element from MRP through a movement type using transaction MIGO.
Basically we don't want to use a delivery document to do this.
Thanks in advance for your help.
Regards,
Gilberto Li

to remove the Sales Order element from MRP through a movement type
Sorry I am not sure whether I understood your requirement correctly. You need to reduce the inventory by doing MIGO instead throgh PGI which means, the movement type will also differ. Better if you can brief about your requirement, a suitable suggestion can be given.
Incidentally, this is not the right forum to post. You can post in the following forum
[Forum: ERP - Sales and Distribution (SD) General |SAP ERP Sales and Distribution (SAP SD);
thanks
G. Lakshmipathi

Sending xsi types using Axis from web service client

Hello,
I am using axis to consume a web service, the soap message generated contain xsi types which cause the validation of the message to fail. Example:
xsi:type="xsd:string"I have tried to remove these types using call.setProperty(Call.SEND_TYPE_ATTR,Boolean.FALSE); but this does not seem to work.
OPERATION_STYLE=document
Can someone please help
Thanks

Haven't worked on this, but have you tried by putting the axis libraries inside the plugin lib folder when you are building up the plugin? Also you need to check asix2 compatibility with weblogic version with R2.
-Bikash

XPath Question related to xsi:type

I have the response of a service callout that I need to process. The service callout response uses xsi:type to specify the type of the object being returned. I need to use the value of the xsi:type attribute to collect the xml elements.
Here is the xpath that I am trying to use:
$addAssetInfoResponse/ast:addAssetInfoResponse/ast:result/ast:asset\[local-name-from-QName(attribute::xsi:type)='Customer'\]
(ast: is mapped to http://www.fatspaniel.com/ws/asset/)
When I test this XPath with the following XML fragement as value of addAssetInfoResponse variable:
<env:Body xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:addAssetInfoResponse xmlns:ns2="http://www.fatspaniel.com/ws/asset/" >
<ns2:result>
<ns2:status>SUCCESS</ns2:status>
<ns2:asset xsi:type="ns4:Customer" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns4="http://www.fatspaniel.com/ws/sysobj/" >
<entityId>106934</entityId>
<type>Customer</type>
<name>AAI Customer - 200909081651</name>
</ns2:asset>
</ns2:result>
</ns2:addAssetInfoResponse>
</env:Body>
I get the following error:
Error executing the transformation: {err}XP0021: "ns4:Customer": can not cast to {http://www.w3.org/2001/XMLSchema}QName: error: Invalid QName value: Can't resolve prefix 'ns4'
Have I made a mistake in the xpath ? Is there a better way for extracting assets elements of certain type ?
Thank you.
Rahul Phadnis
Edited by: RahulPhadnis on Sep 15, 2009 10:57 AM

John Spencer wrote:
Unless I missed something in the 11g new features, the maximum line length in DBMS_OUTPUT.Put_Line is still 255 characters.
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> set serveroutput on
SQL> exec dbms_output.put_line(lpad('X',512,'X'));
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
PL/SQL procedure successfully completed.
SQL> SY.

XMLBeans and xsi:type overrides

The issue is one of the split of responsibility for the XML meta-data and the XML info-set. The XMLBeans classes are allowed to choose XML namespace prefixes at will (following the usual rules about uniqueness) and drop unused namespace prefixes. However the XMLBeans are not allowed to change the values of any elements or attributes which would alter the info-set.
The XML schema type attribute is held in the XML info-set as an attribute and therefore cannot be changed by the XMLBeans, however it also contains details of the namespace prefix.
For example the following piece of XML shows the usage of a xsi:type qualifier :
<v11:createOrderByValueRequest
xmlns:v1="http://videonetworks.com/ServiceActivation/v1-0"
xmlns:v11="http://ossj.org/xml/ServiceActivation/v1-1">
<v11:orderValue xsi:type="v1:VNLCreateOrderValue"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<v11:description>IPTV Consumer Order for WO999</v11:description>
</v11:orderValue>
</v11:createOrderByValueRequest>
If we extract the order value from the createOrderByValueRequest object as the only use of the namespace v1 is within the info-set, under the xsi:type attribute the newly created xml-fragment may look like the following :
<xml-fragment xsi:type="v1:VNLCreateOrderValue"
xmlns="http://ossj.org/xml/ServiceActivation/v1-1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
<description>IPTV Consumer Order for WO999</description> </orderValue>
This no longer validates as the v1 namespace prefix is not defined. As a workaround we have created a method which checks for xsi:type attributes and inserts the namespaces required based on a set of types and namespaces we are using. The output would then look like :
<xml-fragment xsi:type="v1:VNLCreateOrderValue"
xmlns="http://ossj.org/xml/ServiceActivation/v1-1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:v1="http://videonetworks.com/ServiceActivation/v1-0">
<description>IPTV Consumer Order for WO999</description> </orderValue>

Of course this is a namespace issue. But how can i solve it?
In jdeveloper a see all the variables and just use the graphical assign.
This writes
<to variable="inputVariable" part="payload" query="/payload/client:Reference/client:my_nte"/>
If i change from client: to anything else the workflow does not compile anymore...

XSLT Mapper doesn't support xsi:type

I'm starting to think that XSLT Mapper supports only the basic features of XML Schema ...
It (XSLT Mapper in JDeveloper) does not seem to support mapping to generate this kind of element (cannot do it in Design view, when added to the Source view, cannot go back to Design view):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>
If we leave this in Source view and run the xsl, the resulting XML has a validation error, the last element (FromAChildEntity is not known). The XML is valid in XML Spy.
This problem combines with not being able to map two source elements to one target element, makes XSLT Mapper not able to deal with XML Schema inheritance at all.... ?

I just want to reformat the XML from the original message (didn't realize I had to escape some of the characters). This is the XML that cannot be validated by JDeveloper):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>

Problem to validate XML document if the type of root element is abstract

I have the following XML document:
<?xml version="1.0" encoding="UTF-8"?>
<ct013/>
It corresponds to the following XSD Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:element name="ct013" type="foo"/>
     <xs:complexType abstract="true" name="foo"/>
     <xs:complexType name="fixedType">
          <xs:complexContent>
               <xs:restriction base="foo"/>
          </xs:complexContent>
     </xs:complexType>
</xs:schema>
Please take attention to the fact that the type of root element of that BDD is abstract.
XML Schema provides a mechanism to force substitution for a particular element or type. When an element or type is declared to be "abstract", it cannot be used in an instance document. When an element is declared to be abstract, a member of that element's substitution group must appear in the instance document. When an element's corresponding type definition is declared as abstract, all instances of that element must use xsi:type to indicate a derived type that is not abstract.
Declaring an element as abstract requires the use of a substitution group. Declaring a type as abstract simply requires the use of a type derived from it (and identified by the xsi:type attribute) in the instance document.
For more information of using abstract types please see chapter 4.7 Abstract Elements and Types of XML Schema Part 0: Primer Second (http://www.w3.org/TR/xmlschema-0/#abstract).
In this case there is Oracle bug when I try to validate this XML document using Oracle XDK:
String validate(String xml, String schema)
throws XSDException, XMLParseException, SAXException, IOException
System.setPropert("oracle.xml.parser.debugmode", "true");
XSDValidator xsdValidator = new XSDValidator();
XMLError xmlError = new XMLError();
xmlError.setErrorHandler(new DocErrorHandler());
XMLDocument xmlDocument = parseXMLDocument(xml);
XMLDocument schemaXMLDocument = parseXMLDocument(schema);
XMLSchema xmlSchema = (XMLSchema) new XSDBuilder().build(schemaXMLDocument, null);
xsdValidator.setError(xmlError);
xsdValidator.setSchema(xmlSchema);
xsdValidator.validate(xmlDocument);
return getValidationError(xsdValidator);
I get the following error:
Can't find resource for bundle oracle.xml.mesg.XMLResourceBundle, key XSD-2046.
I tried to validate this XML document using two other libraries - XSD Schema Validator (http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx) and xsdvalid-29 (http://www.w3.org/XML/Schema#XSDValid). Both libraries pointed me on the error that the type of root element is abstract and it cannot be used for doing validation.
I think that Oracle should return me explaining message but not to throw exception.
Am I right? Is there really Oracle bug or I miss something?
Any help, hits, advices would be gratfully apriciated.

Define Element1 as follows:
<xs:element name="Element1">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:string"/>
</xs:complexContent>
</xs:complexType>
</xs:element>
Does the XML document get validated if the element is specified as
<Element1></Element1>

JAXB 1.6 and xsi:type attribute

Does JAXB version 1.6 suppurt xsi:type attribute? I have mapped schema to Java classes and when I marshall it to xml, xsi:type attribute is missing.

I found one workaround for the problem,
"<from variable="StopSeq"/>"
As of now , StopSeq was a variable created by me in BPEL file.
I was using this variable to do some calculations.
As a workaround of the problem, I created a schema with "StopSeqType" as a simple int type element.
Then inside the BPEL, I marked the the existing variable "StopSeq" as a type of "StopSeqType" of my new schema.
After this change I found the expected result.
Now my doubt is , Is it the case for all variables created in BPEL ?
If yes , how we can prevent this ?

DSP Web Service Data Source runtime error "Invalid xsi:type qname"

I have created a DSP data service that uses a web service as a data source.
The web service wraps an Oracle PL/SQL package and works when tested independantly of the DSP data service.
When I test the DSP data service using the weblogic workshop test view I get the error below:
weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
(The full stack trace and the WSDL imported into DSP are at the bottom of this posting)
I am new to DSP but I have created data services from the DSP tutorials succesfully before.
This is the first data service I have tried to create which is not from a DSP tutorial.
I dont really understand the error message.
It appears to me that type EmpRecUser is being prefixed by the wrong name space. In the WSDL the namespace is 'tns:' in the error message the namespace is: 'ns0'.
<element name="getEmpResponseElement">
<complexType>
<sequence>
<element name="result" type="tns:EmpRecUser" nillable="true"/>
</sequence>
</complexType>
</element>
I created the web service in Oracle J Developer from the tutorial URL below.
http://www.oracle.com/technology/obe/obe1013jdev/10131/wsfromplsqlpackage/devwsfrom%20plsql.htm#p
weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:169)
     at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
     at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
     at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
     at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
Caused by: weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ValidationException: null
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ExceptionCollection.add(XMLValidatorForXMLBeans.java:340)
     at org.apache.xmlbeans.impl.validator.Validator.emitError(Validator.java:175)
     at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:207)
     at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:193)
     at org.apache.xmlbeans.impl.validator.Validator.beginEvent(Validator.java:458)
     at org.apache.xmlbeans.impl.validator.Validator.nextEvent(Validator.java:246)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processBeginElementToken(XMLValidatorForXMLBeans.java:1205)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processToken(XMLValidatorForXMLBeans.java:1322)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processTokensOnHold(XMLValidatorForXMLBeans.java:1349)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.gotBeginElementToken(XMLValidatorForXMLBeans.java:772)
     at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:100)
     at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
     at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
     at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
     at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
     at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
     at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
     at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
     at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
     at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
     at com.bea.ld.server.QueryInvocation.getResult(QueryInvocation.java:461)
<definitions
name="EmpWebService"
targetNamespace="http://hr/EmpWebService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://hr/EmpWebService.wsdl"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns0="http://hr/EmpWebService.wsdl/types/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hr/EmpWebService.wsdl/types/"
elementFormDefault="qualified" xmlns:tns="http://hr/EmpWebService.wsdl/types/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<element name="getEmpElement">
<complexType>
<sequence>
<element name="empNo" type="decimal" nillable="true"/>
</sequence>
</complexType>
</element>
<element name="getEmpResponseElement">
<complexType>
<sequence>
<element name="result" type="tns:EmpRecUser" nillable="true"/>
</sequence>
</complexType>
</element>
<complexType name="EmpRecUser">
<complexContent>
<extension base="tns:EmpRecBase">
<sequence>
<element name="departmentId" type="decimal" nillable="true"/>
<element name="managerId" type="decimal" nillable="true"/>
<element name="hireDate" type="dateTime" nillable="true"/>
<element name="jobId" type="string" nillable="true"/>
<element name="employeeId" type="decimal" nillable="true"/>
<element name="commissionPct" type="decimal" nillable="true"/>
<element name="salary" type="decimal" nillable="true"/>
<element name="lastName" type="string" nillable="true"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="EmpRecBase">
<sequence/>
</complexType>
</schema>
</types>
<message name="EmpWebService_getEmp">
<part name="parameters" element="tns0:getEmpElement"/>
</message>
<message name="EmpWebService_getEmpResponse">
<part name="parameters" element="tns0:getEmpResponseElement"/>
</message>
<portType name="EmpWebService">
<operation name="getEmp">
<input message="tns:EmpWebService_getEmp"/>
<output message="tns:EmpWebService_getEmpResponse"/>
</operation>
</portType>
<binding name="EmpWebServiceSoapHttp" type="tns:EmpWebService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getEmp">
<soap:operation soapAction="http://hr/EmpWebService.wsdl/getEmp"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="EmpWebService">
<port name="EmpWebServiceSoapHttpPort" binding="tns:EmpWebServiceSoapHttp">
<soap:address location="http://localhost:8888/PL_SQL_WS-GetEmployee-context-root/EmpWebServiceSoapHttpPort"/>
</port>
</service>
</definitions>

DSP validates the results from webservices. Whatever you tested the webservice with outside of DSP, probably does not.
Can you capture the output of the webservice and attach it as well? You can capture the webservice response by running the wls server with the command-line property -Dweblogic.webservice.verbose=true
Can you also open a case with customer support for this? I will not likely have much time to look at it.
- Mike
btw - the namespace prefixes are just place-holders that are defined with xmlns:prefix="some-uri". It is the namespace uri's that must be equivalent. If, in one case you have the definition xmlns:tns="myUri" and in another case xmlns:ns0="myUri" - then tns:EmpRecUser is equivalent to ns0:EmpRecUser.
Perhaps in the webservice result there is no definition, or an incorrect definition for the namespace prefix ns0 - that would explain the complaint about the QName ns0:EmpRecUser. According to the wsdl, there should be a definition for ns0 as :
xmlns:ns0="http://hr/EmpWebService.wsdl"
in the webservice response.

"xsi:type" attribute coming automatically in XML by using Assign activity

Hi,
I am using below copy operation in assign activity
*<copy>*
*<from variable="StopSeq"/>*
*<to variable="InvokeGlog_IV" part="Transmission"*
*query="/ns2:Transmission/ns2:TransmissionBody/ns2:GLogXMLElement/ns2:ActualShipment/ns2:Shipment /ns2:ShipmentStop[bpws:getVariableData('SCounter')]/ns2:StopSequence"/>*
*</copy>*
which is copying from one local variable(StopSeq of int type ) to another variable(StopSequence of string type).
It was working fine in SOA 11.1.1.3 and I was getting result as below
Expected Result *<StopSequence>1</StopSequence>*
But recently we have migrated from 11.1.1.3 to 11.1.1.5 and we started to get below output for the same assign activity.
Current Result *<StopSequence xsi:type="ns:int">1</StopSequence>*
Please suggest.
Thanks

I found one workaround for the problem,
"<from variable="StopSeq"/>"
As of now , StopSeq was a variable created by me in BPEL file.
I was using this variable to do some calculations.
As a workaround of the problem, I created a schema with "StopSeqType" as a simple int type element.
Then inside the BPEL, I marked the the existing variable "StopSeq" as a type of "StopSeqType" of my new schema.
After this change I found the expected result.
Now my doubt is , Is it the case for all variables created in BPEL ?
If yes , how we can prevent this ?

Extract xsi:type of an element from xquery

Similar Messages

Maybe you are looking for