WebService response object in XML - parsing attributes

Hi- new to Flex and I'm trying to parse out the attributes of the response object. I can get the entire object and see that its working, but I cant get just a single attribute. It pulls weather info for world cities. For example, I just want the location name and temperature.
Any advice on this? Thanks!
<?xml version="1.0"?>
<!-- fds\rpc\RPCResultFaultMXML.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
                xmlns:s="library://ns.adobe.com/flex/spark">
    <mx:Script>
        <![CDATA[
            import mx.rpc.soap.SOAPFault;        
            import mx.rpc.events.ResultEvent;
            import mx.rpc.events.FaultEvent;
            import mx.controls.Alert;
            import mx.utils.ObjectUtil;
            public function showErrorDialog(event:FaultEvent):void {
                // Handle operation fault.
                Alert.show(event.fault.faultString, "Error");
            public function defaultFault(event:FaultEvent):void {
                // Handle service fault.
                if (event.fault is SOAPFault) {
                    var fault:SOAPFault=event.fault as SOAPFault;
                    var faultElement:XML=fault.element;
                    // You could use E4X to traverse the raw fault element returned in the SOAP envelope.
                Alert.show(event.fault.faultString, "Error");              
            public function log(event:ResultEvent):void {
                // Handle result.
                trace(event.result);
                //trace(ObjectUtil.toString(event.result));
                //var len:int;
                //len = event.result.length;
                //trace(len);
                //trace(event.result);
                //trace(event.result.GetWeatherResponse.Location);
                //var myXML:XML = new XML(event.result);
                //trace(myXML.attribute("Location"));
        ]]>
    </mx:Script>
    <mx:WebService id="WeatherService" wsdl="http://www.webservicex.com/globalweather.asmx?wsdl"
                   fault="defaultFault(event)">
        <mx:operation name="GetWeather"
                      fault="showErrorDialog(event)"
                      result="log(event)"
                      resultFormat="xml">
            <mx:request>
                <CityName>{myCity.text}</CityName>
                <CountryName>{myCountry.text}</CountryName>
            </mx:request>
        </mx:operation>
    </mx:WebService>
    <mx:TextInput id="myCity" text="Madrid"/>
    <mx:TextInput id="myCountry" text="Spain"/>
    <!-- Call the web service operation with a Button click. -->
    <mx:Button width="60" label="Get Weather"
              click="WeatherService.GetWeather.send();"/>
    <!-- Display the Weather -->
    <mx:Label text="Weather:"/>
    <mx:TextArea text="{WeatherService.GetWeather.lastResult}" height="200"/>
</mx:Application>

The WSDL says GetWeatherResponse is a string, and it appears to be a string of XML, so set <mx:operation resultFormat="object"> as this will unwrap the SOAP response value and leave a string typed value intact. You can then create a new ActionScript 3.0 E4X-based XML instance from the unwrapped string:
    var myXML:XML = new XML(event.result.toString());
You can then travese the XML document using E4X syntax, a simple example is included below:
    trace(myXML..Location);
    trace(myXML..Temperature);

Similar Messages

  • XML Parsing attributes with encoded ampersand causes wrong order

    Hi all,
    I am writing in the forum first (because it could be that i am doing something wrong.... but i think it is a bug. Nonetheless, i thought i'd write my problem up here first.
    I am using Java 6, and this has been reproduced on both windows and linux.
    java version "1.6.0_03"
    Problem:
    read XML file into org.w3c.dom.Document.
    XML File has some attributes which contain ampersand. These are escaped as (i think) is prescribed by the rule of XML. For example:
    <?xml version="1.0" encoding="UTF-8"?>
         <lang>
              <text dna="8233" ro="chisturi de plex coroid (&gt;=1.5 mm)" it="Cisti del plesso corioideo(&gt;=1.5mm)" tr="Koro&#305;d pleksus kisti (&gt;=1.5 mm)" pt_br="Cisto do plexo cor&oacute;ide (&gt;=1,5 mm)" de="Choroidplexus Zyste (&gt;=1,5 mm)" el="&Kappa;&#973;&sigma;&tau;&epsilon;&iota;&sigmaf; &chi;&omicron;&rho;&omicron;&epsilon;&iota;&delta;&omicron;&#973;&sigmaf; &pi;&lambda;&#941;&gamma;&mu;&alpha;&tau;&omicron;&sigmaf; (&gt;= 1.5 mm)" zh_cn="&#33033;&#32476;&#33180;&#22218;&#32959;&#65288;&gt;= 1.5 mm&#65289;" pt="Quisto do plexo coroideu (&gt;=1,5 mm)" bg="&#1050;&#1080;&#1089;&#1090;&#1072; &#1085;&#1072; &#1093;&#1086;&#1088;&#1080;&#1086;&#1080;&#1076;&#1085;&#1080;&#1103; &#1087;&#1083;&#1077;&#1082;&#1089;&#1091;&#1089; (&gt;= 1.5 mm)" fr="Kystes du plexus choroide (&gt;= 1,5 mm)" en="Choroid plexus cysts (&gt;=1.5 mm)" ru="&#1082;&#1080;&#1089;&#1090;&#1099; &#1089;&#1086;&#1089;&#1091;&#1076;&#1080;&#1089;&#1090;&#1099;&#1093; &#1089;&#1087;&#1083;&#1077;&#1090;&#1077;&#1085;&#1080;&#1081; (&gt;=1.5 mm)" es="Quiste del plexo coroideo (&gt;=1.5 mm)" ja="&#33032;&#32097;&#33180;&#22178;&#32990;&#65288;&gt;=1.5mm&#65289;" nl="Plexus choroidus cyste (&gt;= 1,5 mm)" />
    </lang>As you might understand, we need to have the fixed text '>' for later processing. (not the greater than symbol '>' but the escaped version of it).
    Therefore, I escape the ampersand (encode?) and leave the rest of the text as is. And so my > becomes >
    All ok?
    Symptom:
    in fetching attributes, for example by the getAttribute("en") type call, the wrong attribute values are fetched.
    Not only that, if i only read to Document instance, and write back to file, the attributes are shown mixed up.
    eg:
    dna: 8233, ro=chisturi de plex coroid (>=1.5 mm), en=&#1082;&#1080;&#1089;&#1090;&#1099; &#1089;&#1086;&#1089;&#1091;&#1076;&#1080;&#1089;&#1090;&#1099;&#1093; &#1089;&#1087;&#1083;&#1077;&#1090;&#1077;&#1085;&#1080;&#1081; (>=1, de=Choroidplexus Zyste (>=1,5 mm)Here you can see that 'en' is shown holding what looks like greek, ... (what is ru as a country-code anyway?) where it should have obviously had the english text that originally was associated with the attribute 'en'
    This seems very strange and unexpected to me. I would have thought that in escaping (encoding) the ampersand, i have fulfilled all requirements of me, and that should be that.
    There is also no error that seems to occur.... we simply get the wrong order when fetching attributes.
    Am I doing something wrong? Or is this a bug that should be submitted?
    Kind Regards, and thanks to all responders/readers.
    Sean
    p.s. previously I had not been escaping the ampersand. This meant that I lost my ampersand in fetching attributes, AND the attribute order was ALSO WRONG!
    In fact, the wrong order was what led me to read about how to correctly encode ampersand at all. I had been hoping that correctly encoding would fix the order problem, but it didn't.
    Edited by: svaens on Mar 31, 2008 6:21 AM

    Hi kdgregory ,
    Firstly, sorry if there has been a misunderstanding on my part. If i did not reply to the question you raised, I appologise.
    In this 'reply' I hope not to risk further misunderstanding, and have simply given the most basic example which will cause the problem I am talking about, as well as short instructions on what XML to remove to make the problem disappear.
    Secondly, as this page seems to be displayed in ISO 8859-1, this is the reason the xml I have posted looks garbled. The xml is UTF-8. I have provided a link to the example xml file for the sample below
    [example xml file UTF-8|http://sean.freeshell.org/java/less2.xml]
    As for your most recent questions:
    Is it specified as an entity? To my knowledge (so far as my understanding of what an entity is) , yes, I am including entities in my xml. In my below example, the entities are the code for the greater than symbol. I am under the understanding that this is allowed in XML ??
    Is it an actual literal character (0xA0)? No, I am specifying 'greater than' entity (code?) in order to include the actual symbol in the end result. I am encoding it in form 'ampersand', 'g character', 't character', 'colon' in order for it to work, according to information I have read on various web pages. A quick google search will show you where I got such information from, example website: https://studio.tellme.com/general/xmlprimer.html
    Here is my sample program. It is longer than the one you kindly provided only because it prints out all attributes of the element it looks for. To use it, only change the name of the file it loads.
    I have given the xml code seperately so it can be easily copied and saved to file.
    Results you can expect from running this small test example?
    1. a mixed up list of attributes where attribute node name no longer matches its assigned attribute values (not for all attributes, but some).
    2. removing the attribute bg from the 'text' element will reduce most of these symptoms, but not all. Removing another attribute from the element will most likely make the end result look normal again.
    3. No exception is thrown by the presence of non xml characters.
    IMPORTANT!!! I have only just (unfortunately) noticed what this page does to my unicode characters... all the the international characters get turned into funny codes when previewed and viewed on this page.
    Whereas the only codes I am explicitly including in this XML is the greater than symbol. The rest were international characters.
    Perhaps that is the problem?
    Perhaps there is an international characters problem?
    I am quite sure that these characters are all UTF-8 because when I open up this xml file in firefox, It displays correctly, and in checking the character encoding, firefox reports UTF-8.
    In order to provide an un-garbled xml file, I will provide it at this link:
    link to xml file: [http://sean.freeshell.org/java/less2.xml]
    Again, sorry for any hassle and/or delay with my reply, or poor reply. I did not mean to waste anyones time.
    It will be appreciated however if an answer can be found for this problem. Chiefly,
    1. Is this a bug?
    2. Is the XML correct? (if not, then all those websites i've been reading are giving false information? )
    Kindest Regards,
    Sean
    import javax.xml.parsers.DocumentBuilderFactory;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.NamedNodeMap;
    import org.w3c.dom.Node;
    import org.w3c.dom.NodeList;
    import org.xml.sax.InputSource;
    public class Example
        public static void main(String[] argv)
              try
                   FileInputStream fis = new FileInputStream("/home/sean/Desktop/chris/less2.xml");
                 Document doc = DocumentBuilderFactory.newInstance()
                 .newDocumentBuilder()
                 .parse(new InputSource(fis));
                   Element root = doc.getDocumentElement();
                   NodeList textnodes = root.getElementsByTagName("text");
                   int len = textnodes.getLength();
                   int index = 0;
                   int attindex = 0;
                   int attrlen = 0;
                   NamedNodeMap attrs = null;
                   while (index<len)
                        Element te = (Element)textnodes.item(index);
                        attrs = te.getAttributes();
                        attrlen = attrs.getLength();
                        attindex = 0;
                        Node node = null;
                        while (attindex<attrlen)
                             node = attrs.item(attindex);          
                             System.out.println("attr: "+node.getNodeName()+ " is shown holding value: " + node.getNodeValue());
                             attindex++;                         
                        index++;
                        System.out.println("-------------");
                 fis.close();
              catch(Exception e)
                   System.out.println("we've had an exception, type "+ e);
    }  [example xml file|http://sean.freeshell.org/java/less2.xml]
    FOR THE XML, Please see link above, as it is UTF-8, and this page is not. Edited by: svaens on Apr 7, 2008 7:03 AM
    Edited by: svaens on Apr 7, 2008 7:23 AM
    Edited by: svaens on Apr 7, 2008 7:37 AM
    Edited by: svaens on Apr 7, 2008 7:41 AM

  • Memory Utilization during XML Parsing - Response time is high

    Slow response time while xml parsing is done.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes

    "Kris" <[email protected]> wrote in message news:40f2fcda$1@mktnews1...
    Sorry, I overlooked it.
    yes we do have 8 GB RAM. And as far as xml usage, we are parsing the xml to DOM
    (including validation) and then applying transformation. But its the parsing stuff
    which is eating the memory.1. Can you run JProbe to find out real CPU utilization/bottlenecks?
    2. Apache Xerses implementation that is used in weblogic has a design
    flaw that results in serialization of memory allocation by the transformer,
    that makes it impossible to use for intense multithreaded transformations.
    Consider using other transformers.
    Regards,
    Slava Imeshev
    >
    >
    "Slava Imeshev" <[email protected]> wrote:
    Please answer my questions.
    Regards,
    Slava Imeshev
    "Krisna" <[email protected]> wrote in message news:40f299ae$1@mktnews1...
    Thanks Slava for youe response. Coming back to response time, thisprocess is part
    of a big task. So i cant really tell what response time i can allocatejust for
    this piece alone. Might be, roughly it should be less than 0.4 seconds.what the
    major concenr is the memory utilization by these packages. So whatmakes it to
    use this kind of memory and whether its a known issue ?
    "Slava Imeshev" <[email protected]> wrote:
    "kris" <[email protected]> wrote in message news:40eaddce$1@mktnews1...
    Slow response time while xml parsing is done.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently thatgarbage collection
    is occurring multiple times per minute, impacting performance. In
    order
    to better
    understand the source of the memory usage issue, we used JProbe
    Memory
    Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determinewhich classes
    were using the most total or aggregate memory (the sum of the memoryrequired
    to instantiate not just a given object, but all the objects it uses.)The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap
    of
    121MB. In
    additional tests, the larger the heap, the greater these percentageswere.
    Large heap means longer garbage collections. Anyway, DOM is very heavy
    on memory and you can not escape it. What's is your usage patternfor
    XML
    processing? Do you use XSL?
    This results in slow response time.What do you consider as acceptable/inacceptable responce time?
    The following are the details of software and Hardware configurationsused:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 MegabytesDoes this mean you got 8GB RAM on 150Mhz box?
    Regards,
    Slava Imeshev

  • ERROR[WSDL Parser] Attribute 'name' not found at: wsdl:documentation

    Hello,
    I'm currently having a problem generating the Java source code from a WSDL, because the WSDL2Service ant class bundled with the WLS install (in the /server/lib/webservices.jar library) does not comply with the WSDL XSD.
    Check http://schemas.xmlsoap.org/wsdl/
    Especially if you add a <wsdl:documentation> in your <wsdl:portType> you end up with a WSDLParser error, while the file perfectly validates through Eclipse:
         <wsdl:portType name="ImportPortType">
              <wsdl:documentation>
                   Definitions of available operations through the webservice
              </wsdl:documentation>
              <wsdl:operation name="importData">
                   <wsdl:input message="tns:ImportInput" />
                   <wsdl:output message="tns:ImportOutput" />
              </wsdl:operation>
         </wsdl:portType> The error is:
    [wsdl2Service] Generating web service from wsdl C:\Java\Workspaces\MyWorkspace/WebServices/wsdl/Import.wsdl
    [wsdl2Service] weblogic.webservice.wsdl.WSDLParseException: ERROR[WSDL Parser] Attribute 'name' not found at:<wsdl:documentation>Definitions of available operations through the webservice
    [wsdl2Service]           </wsdl:documentation>
    [wsdl2Service]      at weblogic.webservice.wsdl.WSDLParser.getMustAttribute(WSDLParser.java:263)
    [wsdl2Service]      at weblogic.webservice.wsdl.WsdlPortType.parsePortType(WsdlPortType.java:29)
    [wsdl2Service]      at weblogic.webservice.wsdl.WsdlBinding.parseBinding(WsdlBinding.java:45)
    [wsdl2Service]      at weblogic.webservice.wsdl.WsdlPort.parsePort(WsdlPort.java:46)
    [wsdl2Service]      at weblogic.webservice.wsdl.WsdlService.parseService(WsdlService.java:37)
    [wsdl2Service]      at weblogic.webservice.wsdl.WsdlDefinitions.parseDefinition(WsdlDefinitions.java:38)
    [wsdl2Service]      at weblogic.webservice.wsdl.WSDLParser.visit(WSDLParser.java:71)
    [wsdl2Service]      at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:111)
    [wsdl2Service]      at weblogic.webservice.tools.build.internal.WSDL2JavaServiceImpl.runClassgen(WSDL2JavaServiceImpl.java:210)
    [wsdl2Service]      at weblogic.webservice.tools.build.internal.WSDL2JavaServiceImpl.run(WSDL2JavaServiceImpl.java:147)
    [wsdl2Service]      at weblogic.ant.taskdefs.webservices.wsdl2service.WSDL2Service.doWSDL2JavaService(WSDL2Service.java:211)
    [wsdl2Service]      at weblogic.ant.taskdefs.webservices.wsdl2service.WSDL2Service.execute(WSDL2Service.java:131)
    [wsdl2Service]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wsdl2Service]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wsdl2Service]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wsdl2Service]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wsdl2Service]      at java.lang.reflect.Method.invoke(Method.java:585)
    [wsdl2Service]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    [wsdl2Service]      at org.apache.tools.ant.Task.perform(Task.java:348)
    [wsdl2Service]      at org.apache.tools.ant.Target.execute(Target.java:357)
    [wsdl2Service]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    [wsdl2Service]      at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
    [wsdl2Service]      at org.eclipse.ant.internal.ui.antsupport.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    [wsdl2Service]      at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
    [wsdl2Service]      at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
    [wsdl2Service]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wsdl2Service]      at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
    [wsdl2Service]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wsdl2Service]      at java.lang.reflect.Method.invoke(Method.java:585)
    [wsdl2Service]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    [wsdl2Service]      at org.apache.tools.ant.Task.perform(Task.java:348)
    [wsdl2Service]      at org.apache.tools.ant.Target.execute(Target.java:357)
    [wsdl2Service]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    [wsdl2Service]      at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
    [wsdl2Service]      at org.eclipse.ant.internal.ui.antsupport.EclipseSingleCheckExecutor.executeTargets(EclipseSingleCheckExecutor.java:30)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    [wsdl2Service]      at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
    [wsdl2Service]      at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
    [wsdl2Service]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wsdl2Service]      at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
    [wsdl2Service]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wsdl2Service]      at java.lang.reflect.Method.invoke(Method.java:585)
    [wsdl2Service]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    [wsdl2Service]      at org.apache.tools.ant.Task.perform(Task.java:348)
    [wsdl2Service]      at org.apache.tools.ant.Target.execute(Target.java:357)
    [wsdl2Service]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    [wsdl2Service]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wsdl2Service]      at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
    [wsdl2Service]      at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    [wsdl2Service]      at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
    [wsdl2Service]      at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
    BUILD FAILED
    C:\Java\Workspaces\MyWorkspace\EAR\ant\build.xml:22: The following error occurred while executing this line:
    C:\Java\Workspaces\MyWorkspace\EAR\ant\build.xml:26: The following error occurred while executing this line:
    C:\Java\Workspaces\MyWorkspace\EAR\ant\build_config.xml:65: weblogic.webservice.tools.build.WSBuildException: weblogic.webservice.wsdl.WSDLParseException: ERROR[WSDL Parser] Attribute 'name' not found at:<wsdl:documentation>Definitions of available operations through the webservice
              </wsdl:documentation> Digging through the WSDLPortType class (package weblogic.webservice.wsdl ) decompiled code, I clearly saw this kind of parsing does not respect the WSDL XSD:
    public class WsdlPortType {
        public WsdlPortType() {
            operations = new ArrayList();
        void parsePortType(WSDLParser wsdlparser, XMLNode xmlnode, Port port) throws WSDLParseException {
            Iterator iterator = xmlnode.getChildren();
            do {
                if(!iterator.hasNext())
                    break;
                XMLNode xmlnode1 = (XMLNode)iterator.next(); // THE NEXT XML NODE IS NOT COMPULSORILY THE <wsdl:operation> ONE!!!
                String s = wsdlparser.getMustAttribute("name", xmlnode1);
                if(wsdlparser.canHandleMethod(xmlnode1)) {
                    weblogic.webservice.Operation operation = port.addOperation(s);
                    WsdlOperation wsdloperation = new WsdlOperation();
                    wsdloperation.parseOperation(wsdlparser, operation, xmlnode1);
                    operations.add(wsdloperation);
            } while(true);
        private ArrayList operations;
    } X-(
    Edited by maxxyme at 03/13/2008 10:34 AM

    I created a new project and tried to repeat the steps to import. Still getting the same error.
    This is my Message type definition if that helps
    <message name="Composite_Weather_ServiceRequestMessage">
              <part name="payload" type="tns1:NDFDgenRequest"/>
         </message>
         <message name="Composite_Weather_ServiceResponseMessage">
              <part name="payload" type="tns1:NDFDgenResponse"/>
         </message>

  • Memory Utilization during XML Parsing

    We have a slow response time during XML Parsing.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes
    Please let me know if there is any work around or patches available.

    We have a slow response time during XML Parsing.
    Description of the problem:
    During XML parsing, memory is used and discarded so frequently that garbage collection
    is occurring multiple times per minute, impacting performance. In order to better
    understand the source of the memory usage issue, we used JProbe Memory Debugger.
    JProbe Memory Debugger was run in Aggregate mode in order to determine which classes
    were using the most total or aggregate memory (the sum of the memory required
    to instantiate not just a given object, but all the objects it uses.) The result
    was that weblogic.apache. xerces.impl.xs.dom.DocumentImpl and weblogic.apache.xerces.jaxp
    comprise 23.8% and 15.4%, respectively, of total memory on a heap of 121MB. In
    additional tests, the larger the heap, the greater these percentages were.
    This results in slow response time.
    The following are the details of software and Hardware configurations used:
    Server: weblogic 8.1
    OS: Solaris 8
    System Configuration: Sun Microsystems sun4u Sun Fire 6800
    System clock frequency: 150 MHz
    Memory size: 8192 Megabytes
    Please let me know if there is any work around or patches available.

  • XML Parser returning XML content

    This probably seems like overkill..
    Im building a JSP that reads in XML and parses it. I then need to filter for specific values in the XML, and return a chunk of the XML to the output stream.
    So far I've got..
          //set-up in and content-type
            FileInputStream file = new FileInputStream (getServletContext().getRealPath("/games_arcade/xml/game_marketing_content.xml"));
            //response.setContentType("text/xml");
            //parse the request
            Document doc = null ;
            try {
                   DocumentBuilderFactory docBuilderFact = DocumentBuilderFactory.newInstance();
                   DocumentBuilder docBuilder = docBuilderFact.newDocumentBuilder();
                   doc = docBuilder.parse(file);
                   out.println("Go on ya good thing!!!");
            } catch (ParserConfigurationException pcEx) {
                throw new ServletException("jaxp not configured!", pcEx);
            //get needed data from the xml
            NodeList games = doc.getElementsByTagName("game");
              out.println(output.toString());
              Now Im lost. All the requisites are there, imports etc, Im just stuck with filtering the NodeList.
    Or am I completely wrong with this approach?
    Any help greatly appreciated.
    thanks!
    Stephen

    Hi,
    thanks for the replyand suggestions. Have a bit of an issue with this method, this method (due to technical limitations) is completely JSP, using a standard iPlanet 6.1 classpath. I cant deploy WAR's (and cant use taglibs). Xpath/XSL would be ideal, but how do I write the output as XML?
    So are you suggesting
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
      <xsl:output method="html"/>
        <xsl:template match="/">
            <xsl:for-each select="games/game">
              <xsl:if test="@id = $GAMEID">
                   ... output the xml node using value-of's etc...
              </xsl:if>
            </xsl:for-each>
          </xsl:template>
        </xsl:stylesheet>Cheers Dr Clap!
    Stephen

  • Receive XML document as Webservice Response

    Hi
    I have implemented webservices using axis.This works fine.
    But I need an receive the response as an XML document.because for multiple entries of same tag name, i can parse through the document and do what ever i want.
    Also how can i attach an external xsd for a wsdl.
    I am stuck up at these two places,Your help would be appriciated
    Thanks in advance

    Web service is platform independent hence most programming languages should return basic datatypes. In your case easiest thing would be to read that XSD file and convert entire file as String and return it as String. A document object will always throw an error.
    Google to find out datatypes supported.
    Hi Everyone,
    Please let me know if this can be a quick resolution to his problem.

  • Webservice response (XML response) with tag not mandatory

    Hello all,
    I have a problem with a webservice response.
    I implemented a wsdl who created some method to call webservices (Methox X, Y ,Z).
    I call the method 'X' with a table of string who have3 values in input, and I have in a  XML Answer of the webservice call that :
    <tag1> Value 1.1
    <tag2> Value 1.2
    <tag3> Value 1.3
    <message>OK
    <tag3> Value 2.3
    <message>KO
    <tag1> Value 3.1
    <tag2> Value 3.2
    <tag3> Value 3.3
    <message>OK
    Tags 1, 2 and 3 are not mandatory in wsdl (Min occurs = 0).
    In output of the method 'X' (created by wsdl implemantation) a ABAP structure with that :
    ValueTag1 | ValueTag2 | ValueTag3 | message
    Value 1.1 | Value 1.2 | Value 1.3 | OK
    Value 3.1 | Value 3.2 | Value 2.3 | KO
    No value. | No value. | Value 3.3 | OK
    I expect to have logically:
    ValueTag1 | ValueTag2 | ValueTag3 | message
    Value 1.1 | Value 1.2 | Value 1.3 | OK
    No value. | No value. | Value 2.3 | KO
    Value 3.1 | Value 3.2 | Value 3.3 | OK
    SAP put into the line 2of the structure, data of 3rd response because it dont found tag in the 2nd response.
    If i do my call, value by value and i concatenate anwsers, i have no problem.
    I dont understand the error and i cant find SAP note on the subject.
    Someone know ths problem ?
    Thanks.

    Hello,
    I have a wsdl file who describe webmethod and his parameters.
    I implemented this wsdl into a client proxy.
    SAP create automatically some CLASS, METHOD, STRUTURE.
    I call one of this method to ask the webservice.
    A XML flow sent and the webservice respond to me with a other XML flow.
    The XML flow response his automatically transforme by SAP, and i receive it into a structure in output of my method.
    Example :
    CREATE OBJECT XXX
      EXPORTING
        logical_port_name = `ZZZZ`.
    CATCH cx_ai_system_fault INTO fault.
      RAISE EXCEPTION fault.
    IF XXX IS BOUND.
      TRY.
        XXX->METHODYYY(
                EXPORTING
                   input =  ii_input
                IMPORTING
                   output = oo_output ).
       CATCH cx_ai_system_fault INTO fault1.
         RAISE EXCEPTION lr_fault1 .
       CATCH Error_ws INTO fault2.
         RAISE EXCEPTION lr_fault2.
       CATCH cx_ai_application_fault INTO fault3.
         RAISE EXCEPTION lr_fault3.
       CLEANUP.
      ENDTRY.
    ENDIF.
    METHODYYY was created by SAP with wsdl file.
    ii_input and oo_output and typed like structure in wsdl file.
    I can see XML flow and his content in SOAMANAGER transaction when i activate full trace.

  • Oracle XML DOM parser - attribute values are not printing on the screen ??

    Hi Everyone,
    I am just trying to use oracle DOM parser to paerse one of my xml file, java file can be compiled and run agianst a xml file, But I cannot see any attribute values printing on the screen..
    Appreciate if anyone can help, where I have gone wrong please?
    Below is the java file:
    // menna puthe DOMSample eka - duwanawa 19/12/2005
    import java.io.*;
    import java.net.*;
    import org.w3c.dom.*;
    import org.w3c.dom.Node;
    import oracle.xml.parser.v2.*;
    public class DOMSample {  //public class eka ***
    static public void main(String[] argv){  // main method eka ###
    try {
    if (argv.length != 1){
    // Must pass in the name of the XML file...
    System.err.println("Usage: java DOMSample filename");
    System.exit(1);
    // Get an instance of the parser
    DOMParser parser = new DOMParser();
    // Generate a URL from the filename.
    URL url = createURL(argv[0]);
    // Set various parser options: validation on,
    // warnings shown, error stream set to stderr.
    parser.setErrorStream(System.err);
    parser.showWarnings(true);
    // Parse the document.
    parser.parse(url);
    // Obtain the document.
    Document doc = parser.getDocument();
    // Print document elements
    System.out.print("The elements are: ");
    printElements(doc);
    // Print document element attributes
    System.out.println("The attributes of each element are: ");
    printElementAttributes(doc);
    catch (Exception e){
    System.out.println(e.toString());
    } // main method eka ###
    static void printElements(Document doc) {
    NodeList nl = doc.getElementsByTagName("*");
    Node n;
    for (int i=0; i<nl.getLength(); i++){
    n = nl.item(i);
    System.out.print(n.getNodeName() + " ");
    System.out.println();
    static void printElementAttributes(Document doc){
    NodeList nl = doc.getElementsByTagName("*");
    Element e;
    Node n;
    NamedNodeMap nnm;
    String attrname;
    String attrval;
    int i, len;
    len = nl.getLength();
    for (int j=0; j < len; j++){
    e = (Element)nl.item(j);
    System.out.println(e.getTagName() + ":");
    nnm = e.getAttributes();
    if (nnm != null){
    for (i=0; i<nnm.getLength(); i++){
    n = nnm.item(i);
    attrname = n.getNodeName();
    attrval = n.getNodeValue();
    System.out.print(" " + attrname + " = " + attrval);
    System.out.println();
    static URL createURL(String filename) {  // podi 3 Start
    URL url = null;
    try {
    url = new URL(filename);
    } catch (MalformedURLException ex) { /// BBBBBB
    try {
    File f = new File(filename);
    url = f.toURL();
    } catch (MalformedURLException e) {
    System.out.println("Cannot create URL for: " + filename);
    System.exit(0);
    } // BBBBBB
    return url;
    } // podi 3 End
    } //public class eka ***
    // End of program
    output comes as below:
    Isbn:
    Title:
    Price:
    Author:
    Message was edited by:
    chandanal

    Hi Chandanal,
    I edited your code slightly and I was able to get the correct output.
    I changed the following line:
    for (int j=0; j >< len; j++)to:
    for (int j=0; j < len; j++)I have included the complete source below:
    // menna puthe DOMSample eka - duwanawa 19/12/2005
    import java.io.*;
    import java.net.*;
    import org.w3c.dom.*;
    import org.w3c.dom.Node;
    import oracle.xml.parser.v2.*;
    public class DOMSample {
        //public class eka ***
        public static void main(String[] argv) {
            // main method eka ###
            try {
                if (argv.length != 1) {
                    // Must pass in the name of the XML file...
                    System.err.println("Usage: java DOMSample filename");
                    System.exit(1);
                // Get an instance of the parser
                DOMParser parser = new DOMParser();
                // Generate a URL from the filename.
                URL url = createURL(argv[0]);
                // Set various parser options: validation on,
                // warnings shown, error stream set to stderr.
                parser.setErrorStream(System.err);
                parser.showWarnings(true);
                // Parse the document.
                parser.parse(url);
                // Obtain the document.
                Document doc = parser.getDocument();
                // Print document elements
                System.out.print("The elements are: ");
                printElements(doc);
                // Print document element attributes
                System.out.println("The attributes of each element are: ");
                printElementAttributes(doc);
            } catch (Exception e) {
                System.out.println(e.toString());
        // main method eka ###
        static void printElements(Document doc) {
            NodeList nl = doc.getElementsByTagName("*");
            Node n;
            for (int i = 0; i < nl.getLength(); i++) {
                n = nl.item(i);
                System.out.print(n.getNodeName() + " ");
            System.out.println();
        static void printElementAttributes(Document doc) {
            NodeList nl = doc.getElementsByTagName("*");
            Element e;
            Node n;
            NamedNodeMap nnm;
            String attrname;
            String attrval;
            int i, len;
            len = nl.getLength();
            for (int j = 0; j < len; j++) {
                e = (Element)nl.item(j);
                System.out.println(e.getTagName() + ":");
                nnm = e.getAttributes();
                if (nnm != null) {
                    for (i = 0; i < nnm.getLength(); i++) {
                        n = nnm.item(i);
                        attrname = n.getNodeName();
                        attrval = n.getNodeValue();
                        System.out.print(" " + attrname + " = " + attrval);
                System.out.println();
        static URL createURL(String filename) {
            // podi 3 Start
            URL url = null;
            try {
                url = new URL(filename);
            } catch (MalformedURLException ex) {
                /// BBBBBB
                try {
                    File f = new File(filename);
                    url = f.toURL();
                } catch (MalformedURLException e) {
                    System.out.println("Cannot create URL for: " + filename);
                    System.exit(0);
            // BBBBBB
            return url;
        // podi 3 End
    } //public class eka ***-Blaise

  • Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute

    This is a Bursting problem under EBS 5.6.3. In production we have 5.6.2 and since our development system to 5.6.3 has been upgraded, the following error occurs on every single Burst being done using the Concurrent Manager only:
    Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
         at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1502)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1408)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1350)
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1180)
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:201)
         at oracle.apps.xdo.batch.BurstingProcessorEngine.burstingConfigParser(BurstingProcessorEngine.java:1340)
         at oracle.apps.xdo.batch.BurstingProcessorEngine.process(BurstingProcessorEngine.java:1297)
         at oracle.apps.xdo.batch.DocumentProcessor.process(DocumentProcessor.java:213)
         at xxwel.ebs.xmlp.XXWELBurster.processDocuments(XXWELBurster.java:143)
    I can run the same file through 5.6.3 ($JAVA_TOP) libraries mounted on my JDev with no problems. Also the same XML file runs fine on Production under 5.6.2 - no problems. I have also checked the XML file using a syntax checker. I know this is not a syntax issue even though it looks like it.
    Could someone point me in the right direction - explain what this means. Getting desperate as 5.6.3 will be going into production soon and all Bursting will fail with this error. I can't get the simplest XML File to Burst - NOTE this is only occurring on the EBS system (even running without the CM ie. a standalone java main it fails). I think this has something to do with the XML parser version and the EBS environment.
    Please help...

    Hi Tim, good thinking - wouldn't have thought to check this file. Anyway can confirm that the problem is happening with multiple burst control files so I haven't checked the files themselves as the problem seems systemic. anyway here is an example.
    <?xml version="1.0" encoding="UTF-8"?>
    <xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
    <xapi:request select="/XXWEL_BIP_UNI_INVOICES/LIST_G_CUSTOMER_NUMBER/G_CUSTOMER_NUMBER">
    <xapi:delivery>
    <xapi:email server="mailwa01" port="25"
    from="${ADMIN_EMAIL}" reply-to ="${ADMIN_EMAIL}">
    <xapi:message id="111" to="${ADMIN_EMAIL}" attachment="true" subject="Unigas Inv
    oice No: ${TRX_NUMBER}">
    </xapi:message>
    </xapi:email>
    </xapi:delivery>
    <xapi:document output-type="pdf" delivery="111">
    <xapi:template type="rtf" location="/u02/prod/prodappl/wel/11.5.0/interface/bip/templates/uni_invoice_template.rtf">
    </xapi:template>
    </xapi:document>
    </xapi:request>
    </xapi:requestset>
    I will start stripping the control files to make sure they are not the problem in the meantime.

  • Oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'RO

    I'm using the oracle.xml.parser.v2. The files (xml, xsl) are:
    <?xml version="1.0" ?>
    <?xml-stylesheet type="text/xsl" href="king.xsl" ?>
    <ROWSET>
    <ROW>
    <EMPNO>7839</EMPNO>
    <ENAME>KING</ENAME>
    </ROW>
    </ROWSET>
    <?xml version="1.0"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output method="xml" indent="yes"/>
    <xsl:template match="/">
    <INVITATION>
    <TO>
    <xsl:value-of select="ROWSET/ROW/ENAME"/>
    <xsl:text> &; FAMILY </xsl:text>
    </TO>
    </INVITATION>
    </xsl:template>
    </xsl:stylesheet>
    The error is: oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'ROWSET'.
    The files are well formed (tested with XML Spy 3.5). Can you see what's the problem? or is it a bug with the parser?
    help,
    Alberto
    null

    I encountered the same problem. When I change the order of the XML and XSL files, i am the same problem.
    Perhaps it's the environment AIX 4.3.3, JDK IBM 1.2.2 with JIT disable (because when JIT is enable some other problems become)??
    How can i resolve this bug ?
    Thanks.
    null

  • Using XML parser objects

    This question was posted in response to the following article: http://help.adobe.com/en_US/Director/11.5/UsingScripting/WScf09ce35f85d76b4-31c73ea211d558 551a5-7ffb.html

    where is the samples XML parser & JScript ?

  • XML parsing inside some webservices

    Hi,
    I made some webservice where I tryed to use some XML parser made myself. The XML parser works fine in other implementation, but doesn't in this particular case.
    It looks like the Oracle OC4J handles some XML and parses itself with worng result. After parsing procedure I obtian final result by calling:
    document.getDocumentElement().toString();
    In other situation I get there XML String after parsing routine, but the same inside webservice on OC4J gives result as below:
    oracle.xml.parser.v2.XMLElement@93
    What's a reason of two different results?
    Thanks for some help
    Krzysztof

    Hi Krzysztof,
    If you are looking to convert a DOM to a String I would recommend using one of the following approaches instead of using the "toString()" method.
    XDK
    import java.io.FileReader;
    import java.io.StringWriter;
    import oracle.xml.parser.v2.DOMParser;
    import oracle.xml.parser.v2.XMLDocument;
    import oracle.xml.parser.v2.XMLElement;
    import org.w3c.dom.Node;
    public class Test {
        public static void main(String[] args) throws Exception {
            FileReader reader = new FileReader("xpath.xml");
            DOMParser parser = new DOMParser();
            parser.parse(reader);
            XMLDocument xmlDocument = parser.getDocument();
            XMLElement xmlElement = (XMLElement)xmlDocument.getDocumentElement();
            StringWriter stringWriter = new StringWriter();
            xmlElement.print(stringWriter);
            String string = stringWriter.toString();
            System.out.println(string);
    JAXP
    import java.io.File;
    import java.io.StringWriter;
    import javax.xml.transform.Transformer;
    import javax.xml.transform.TransformerException;
    import javax.xml.transform.TransformerFactory;
    import javax.xml.transform.stream.StreamSource;
    import javax.xml.transform.stream.StreamResult;
    public class Test {
        public static void main(String[] args) {
            try {
                File file = new File("sample.xml");
                StreamSource source = new StreamSource(file);
                StringWriter stringWriter = new StringWriter();
                StreamResult result = new StreamResult(stringWriter);
                TransformerFactory transformerFactory = TransformerFactory.newInstance();
                Transformer transformer = transformerFactory.newTransformer();
                transformer.transform(source, result);
                String string = stringWriter.toString();
                System.out.println(string);
            } catch (TransformerException e) {
                // Handle the exception
                e.printStackTrace();
    }-Blaise

  • XML Parser Exception on Punch Out Setup Request

    I am on the supplier side of the procurement process. Recently I was tasked with bringing on a new buying group, but we have encountered a strange issue. The buyer set up my company in their ERP system, however they are getting an error when trying to punch out to my website...which is listed below.
    Error Code: 400 Invalid XML Format In Login Response Document Unable to parse the Login Response XML.
    XMLParserException
    oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'meta'.
    at oracle.xml.parser.v2.XMLError.flushErrors1
    After some investigation, I am confident the problem resides in the buyers BrowserFormPost URL. The problem seems to be that instead of using "&amp;" for ampersand between the URL variables, it is passing in the & symbol (& is a protected character in XML), which is causing the Oracle XML parser to throw this exception. As a result, the set up request is never getting to me.
    The buyer has opened a couple of tickets now with Oracle support, but both times the ticket has been closed and the buyer has been instructed to contact the supplier (me). I don't know enough about the buyer side Oracle system to instruct them on how to fix this issue. Any help would be greatly appreciated.

    Hi Rakesh,
    You need to have an S-User ID to access SAP Notes. For your convenience, I am pasting the content of SAP Note 954035.
    Process, block and CO could not be created in GP
    Symptom
    After upgrade of SAP-EU component to version 7.0 SP8 in Guided Procedures process, block and callable object could not be created. On design time screen   appears error message:
    com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
    During attempt to start process through the Runtime screen you will get an error message:
    Cannot load callable object container:
    Failed to get Related Model Object for the object
    com.sap.caf.eu.gp.ui.actions.decpage.
    CDecisionPageInterfaceViewdecisionPageUsage1,relation View
    In SP9, the following message could be found:
    Failed to get Related Model Object for the object com.sap.caf.eu.gp.ui.co.exec.decision.COExecDecision
    Proceed as stated for SP8.
    Other terms
    This is WebDynpro problem caused by an inconsistency of versions.
    Solution
          1. Redeploy the SCA SAP-EU (if redeployment does not help undeploy and deploy again) components:
              o caf/eu/gp/ui/dt/comp/cons,
              o caf/eu/gp/ui/dt/comp and
              o caf/eu/gp/ui/actions  from software component SAP-EU
    or
          2. Apply the SP8 patch 1 if you upgrade to SP8. Both components mentioned below will be updated:
              o caf/eu/gp/ui/dt/comp/cons
              o caf/eu/gp/ui/dt/comp
    See if it solves your problem.
    Bye
    Ankur

  • Synchonous webservice call is missing xml schema information

    Hello,
    We migrated an interface to a new PI server. All repository objects were exported and imported. The interfaces is working fine on old PI environment but on new environment we get an error:
    From an Integration Process we do a call to a synchronous webservice via a soap receiver communication channel.
    In the old envrionment we get response back with right message content and:
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    In the new environment we get response back with right message content but without:
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    The first message mapping needs this XMLSchema information and throws an error:
    RuntimeException
    during appliction Java mapping
    com/sap/xi/tf/_______
    Thrown:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: The prefix
    "xsi" for attribute "xsi:type" associated with an element
    type "ns0:responseOut" is not bound.
    I expect this error is thrown because this XMLSchema information is missing in webservice response:
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    Does anybody know why this information could be missing?
    I also used SOAP UI from the new PI server to call same synchronous webservice and then I do get this XML Schema information back.
    Many thanks for your help!

    Hi ,
    Go through below links for sol.
    PI 7.11: Prefix for attribute is bound
    &amp;lt;element xsi:type=&quot;T3&quot; attribute=&quot;USD&quot;&amp;gt;1.... | SCN
    Regards
    Venkat

Maybe you are looking for

  • Contingencia: numeraçao parada no monitor!

    Boa tarde gente! Estou testando o scenario da contingencia depois de implantar SP34 no SAP 4.7 e preparando tudo para a NFE V2.0. Activé a contingencia para um local de negocio e crié uma nota. Mas a nota no monitor fica sem numero e sem ser identifi

  • Business area in FI changing without using substitutions

    Hi all,   Is it possible to change the business area when we post a clearing document?   For example, we need to pay the line item that have business area 3000. Then we use transaction F110 to create a payment then a clearing docuement will be create

  • My applications are not responding

    It started with Word, now Pages and iTunes are doing the same thing. I can open the apps but as soon as I start working in them I get the spinning wheel and have to force quit, quite maddening. Help.

  • PR: Procurement w/o material from vendor with plant assignment not defined

    Hi, Getting the error message:  06806 - Procurement w/o material from vendor with plant assignment not defined while creating the PR with account assingment (P- project) & without material no. instead entering the short text in the PR. this issue (Er

  • Hide cursor in DVD Player

    How do you hide the mouse cursor while in fullscreen mode in DVD Player?