Declaring namespaces ONLY on root element during serialization

I'm using JAXP 1.3 and I'd like to be able to serialize a document so that the namespace declarations are only specified once on the root element and not repeated throughout the document.
I'm working on a journal publication system and the request came from our users (i.e., editors) who say the repeated declarations are distracting when editing the XML. They are using an XML editor (Arbortext), but when they have the view set to display tags all the namespace declarations really clutters up the screen. In particular, we use the MathML namespace:
<m:math overflow="scroll" xmlns:m="http://www.w3.org/1998/Math/MathML">
Can this be done?
Thanks,
Jeff Bailey

It's just declared on on the root element on the input file.
I just tried what you suggested and it worked great. The mathml namespace is only declared on the root element in my output file now.
Odd that there's a difference between the two methods. For posterity, here's the code I used to serialize the XML:
TransformerFactory transformerFactory = TransformerFactory
.newInstance();
Transformer transformer = transformerFactory.newTransformer();
transformer.setOutputProperty(OutputKeys.METHOD, "xml");
transformer.setOutputProperty(OutputKeys.ENCODING, "US-ASCII");
transformer.setOutputProperty(OutputKeys.DOCTYPE_PUBLIC,
doc.getDoctype().getPublicId());
transformer.setOutputProperty(OutputKeys.DOCTYPE_SYSTEM,
doc.getDoctype().getSystemId());
OutputStream outputStream = new FileOutputStream(new File(
"C:\\temp\\foo.xml"));
transformer.transform(new DOMSource(doc),
new StreamResult(outputStream));
Thanks very much for your help.
Jeff

Similar Messages

  • Namespace prefix in Root element missing during variable assignment in SOA Suite 11g

    I need qualified element Namespaces in one of the target variables. All elements being referred to would have the namespace prefixed. This is working for all child elements, but not the for root element. How can i get the root element prefixed with the namespace?
    We are using SOA Suite 11g and the Jdeveloper version we are using is 11.1.1.6.0
    when i use transform operation to populate the target variable the variable gets populated something like this :
    <inputVariable>
    <part  name="payload">
    <Message>
    <msg:Header>
    <head:field1>xxxxxx</head:field1>
    <head:field2>2013-07-09T08:00:55</head:field1>
    </msg:Header>
    </Message>
    But the actual output we need is
    <inputVariable>
    <part  name="payload">
    <msg:Message>
    <msg:Header>
    <head:field1>xxxxxx</head:field1>
    <head:field2>2013-07-09T08:00:55</head:field1>
    </msg:Header>
    </msg:Message>
    We tried the fix suggested in one of the SOA threads but its not working for us and looks like that will work only for SOA SUITE 10g.
    Please provide us any help/suggestions if anyone know the solution.
    Thank you in advance for the help.

    Any one can help us please.......

  • Namespace prefix in Root element missing during variable assignment

    In bpel 10.1.3.4, I need qualified element Namespaces in one of the target variables. I have an xsd that has elementFormDefault = "qualified" set, therefore all elements being referred to would have the namespace prefixed. This is working for all child elements, but not the root element. How can i get the root element prefixed with the namespace?
    If i use transform or copy/append operation to populate in the target variable the variable gets populated something like this :
    <Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
    <pidx:InvoiceProperties>
    <pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
    </pidx:InvoiceProperties>
    </Invoice>
    Whereas i need :
    <*pidx:*Invoice xmlns:pidx="http://www.api.org/pidXML/v1.0" pidx:transactionPurposeIndicator="Original" pidx:version="1.0" xmlns="http://www.api.org/pidXML/v1.0">
    <pidx:InvoiceProperties>
    <pidx:InvoiceNumber>test123</pidx:InvoiceNumber>
    </pidx:InvoiceProperties>
    </*pidx:*Invoice>
    Is there some way to accomplish this?
    Regards,
    Sandeep

    Hi Sandeep,
    We have exactly the same issue, but, when we implemented the solution, we are getting the following error, when we tried to compile the code, we are using 11.1.1.4.0 version of SOA 11g, appreciate if there is any way you can help us on this:
    Jul 12, 2011 2:40:28 PM com.collaxa.cube.CubeLogger info
    INFO: validating "BPELProcess1.bpel" ...
    oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
         at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
         at oracle.integration.platform.blocks.WLSPlatformConfigurationProvider.<clinit>(WLSPlatformConfigurationProvider.java:44)
         at oracle.integration.platform.blocks.FabricConfigManager.<clinit>(FabricConfigManager.java:154)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXpathFunctions(FabricXPathFunctionResolver.java:282)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.loadXPathConfigFile(FabricXPathFunctionResolver.java:156)
         at oracle.integration.platform.blocks.xpath.FabricXPathFunctionResolver.init(FabricXPathFunctionResolver.java:49)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.loadFabricXpathFunctions(BPELXPathFunctionNameResolver.java:57)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<init>(BPELXPathFunctionNameResolver.java:48)
         at com.collaxa.cube.xml.xpath.BPELXPathFunctionNameResolver.<clinit>(BPELXPathFunctionNameResolver.java:44)
         at com.collaxa.cube.lang.compiler.bpel.XPathExprValidatorVisitor.<init>(XPathExprValidatorVisitor.java:122)
         at com.collaxa.cube.lang.compiler.bpel.AssignValidator.<init>(AssignValidator.java:89)
         at com.collaxa.cube.lang.compiler.bpel.BpelParser.<init>(BpelParser.java:452)
         at com.collaxa.cube.lang.compiler.bpel.BPELValidator.validate(BPELValidator.java:60)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.validate(BPEL1Processor.java:329)
         at com.collaxa.cube.lang.compiler.BPEL1Processor.process(BPEL1Processor.java:153)
         at com.collaxa.cube.lang.compiler.CubeParserHelper.compile(CubeParserHelper.java:47)
         at oracle.fabric.bpel.bpelc.BPELComponentValidator.validate(BPELComponentValidator.java:40)
         at oracle.soa.scac.ValidateComposite.validateComponentTypeServicesReferences(ValidateComposite.java:1117)
         at oracle.soa.scac.ValidateComposite.doValidation(ValidateComposite.java:500)
         at oracle.soa.scac.ValidateComposite.run(ValidateComposite.java:150)
         at oracle.soa.scac.ValidateComposite.main(ValidateComposite.java:135)
    Jul 12, 2011 2:40:29 PM CubeProcessGenerator compile
    WARNING: classpath is: C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.sca.modeler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.mediator_11.1.1\mediator_client.jar;C:\oracle\Middleware\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\oracle\Middleware\jdeveloper\jdev\extensions;;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\classes;C:\JDeveloper\mywork\InvoiceTransferApp\InvoiceTransferProj\SCA-INF\gen-classes;C:\oracle\Middleware\oracle_common\modules\commonj.sdo_2.1.0.jar;C:\oracle\Middleware\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;C:\oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel1-1-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-common.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpel_coherence_config.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\bpm-analytics.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-thirdparty.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\wsif-binding.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel-validator.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\monitor-rt-xbean.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\oracle.soa.bpmn.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.bpel_11.1.1\orabpel1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\user-patch.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.thirdparty.jar;C:\oracle\Middleware\jdeveloper\uddi\lib\oracle.soa.uddi.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\bpm-infra.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\testfwk-xbeans.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-ext.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-scheduler.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\xmlunit-1.1.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-infra-tools.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\soa-xpath-exts.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-client.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-was.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime-ext-wls.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\oracle\Middleware\jdeveloper\soa\modules\oracle.soa.ext_11.1.1\classes
    Regards,
    Sireesh

  • OrgChart Hierarchy only shows root element

    Hi experts
    In OrgChart module, when position hierachy is accessed, only shows the
    root element, not hierachy structure of postion elements.
    When click this element, no data was showed in details pannel.
    Any idea?

    Hi Savier,
    Do you maintain S A 002 S relationships in SAP? If not then you will not get the Position Hierarchy because the Positions do not have a relationship between themselves. In Staged you have to derive the relationships and in Live you will either have to maintain the relationships or use an FM to derive the relationships and add it to an Evaluation Path. Otherwise you will have to disable the feature.
    Good luck!
    Luke

  • Namespace Prefix in the Root Element of the variable

    Hi Gurus,
    We need to call a webservice which requires a namespace prefix at the root elemnt of the xml payload. But as we know that the default behaviour of BPEL removes the prefix so the invoke activity is failing and so we are stuck.
    I found this thread Namespace prefix in Root element missing during variable assignment but i feel the solution specified in this link works only in SOA 10g environment Please let us know what needs to be done?
    Appreciate a prompt response.
    NOTE: SOA Suite Version- 11.1.1.4
    Regards
    Ayush

    Hi All,
    we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

  • Several namespaces in root element

    Hi,
    I'm using JDOM and I would like to create an XML document that starts like this:
    <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0"
    xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0"
    xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"
    xmlns:ccts="urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0"
    xmlns:cur="urn:oasis:names:specification:ubl:schema:xsd:CurrencyCode-1.0"
    xmlns:sdt="urn:oasis:names:specification:ubl:schema:xsd:SpecializedDatatypes-1.0"
    xmlns:udt="urn:oasis:names:specification:ubl:schema:xsd:UnspecializedDatatypes-1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd">
    </Invoice>
    Is there a way to add several namespaces to the root element?? I have tried hard, but nothing works...
    Thank you very much for your help,
    Susana

    OK, it's like dvohra09 said. I had an old copy of jdom.jar and the method addNamespaceDeclaration() didn't exist.
    So, here you have the code to generate the beginning of my file, if ever it's useful to someone as I found it a little bit complicated to find out:
    For this:
    <?xml version="1.0" encoding="UTF-8"?>
    <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0"
    xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
    xsi:schemaLocation="urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd">
         <ID>serie1_04/00011</ID>
         <cbc:CopyIndicator>false</cbc:CopyIndicator>
    </Invoice>
    The code is:
    Element rootElement = new Element("Invoice", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0");
    rootElement.addNamespaceDeclaration(Namespace.getNamespace("cbc", "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"));("schemaLocation", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0 UBL-Invoice-1.0.xsd", Namespace.getNamespace("xsi", "http://www.w3.org/2000/10/XMLSchema-instance" ));
    rootElement.setAttribute(schemaLoc);
    Document invoiceDocument = new Document(rootElement);
    // ID          
    rootElement.addContent(new Element("ID", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-1.0").setText(invoice.getId_serie_desc() + "_" + invoice.getNum_factura()));
    // cbc:CopyIndicator     
    rootElement.addContent(new Element("CopyIndicator", "cbc",
    "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0").setText(copyIndicator));
    Thank you for your answers.
    Susana

  • Multiple Root elements in the XSD Schema

    Hi Dear MDM gurus,
    I have manually created an XSD Schema and I can import it in the Syndicator without any problem.
    I have 3 different Root elements in the schema that I want to use and map to the corresponding table of this type.
    In my Syndicator screen in the Rood dropdown box I can see all three of the Root elements that I have in the schema.
    If I select the first Root element - everything goes fine and I can do my mapping, save the map, etc.
    The problem is that if I select the second or third root element to do the mapping for them, the syndicator does not show the structure in the Item Mapping after that.
    I tried moving the Second root element of the schema and make it first and it works with it, but then the other two are not appearing and I have the same issue.
    Does MDM support only one Root element in the Schema? If that's the case, why does it show all three of them in the dropdown?
    Here is an example:
    1. If I have them in this order in my XSD
              <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
              <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
              <xs:element name="SupplierLocationNumber" type="Suppliers"/>
    I can only see the structure when I select the "ManufacturerGroupNumber".
    2. If I have them in the Schema in this order
              <xs:element name="SupplierLocationNumber" type="Suppliers"/>
              <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
              <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
    I can only see the structure when I select the first one again "SupplierLocationNumber" and I can only do the mapping for it.
    Any help would be appreciated.
    Thanks in advance,
    Boris

    Hello Satish,
    Thank you for your quick response.
    I read some of the architectural approaches and XML specifications and depending on your design, you may have only one Root element or in rare cases Several Root elements. In my case, I was advised by our PI experts to use Multiple Root elements and this gives me the following:
    Advantages:
    u2022 The reusability of the schema definition is available for all types and all elements defined in the global namespace.
    Disadvantages:
    u2022 Since there are many global elements, there are many valid XML documents.
    I initially had the schema as you suggested, but they didn't like it in PI and advised me to change it with having multiple roots.
    What I'm trying to figure out is if there is a bug in MDM that does not allow to use the rest of the root elements, so I can open an OSS message.
    Thanks,
    Boris

  • Failure to save the element during dehydration

    Hi all,
    Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
    Oracle Enterprise Manager 11g Fusion Middleware Control [Version 11.1.1.2.0]
    i am facing this below problem when trying to read a list. actually it a parent will get list from 2-3 process and before sending this list to another process i am looping through to set the input values for the last process. at that time i am getting this below error. kindly help me to fix this problem. thanks in advance.
    <bpelFault><faultType> <message>0</message></faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>
    Cannot save xml element. failure to save the element {http://xmlns.oracle.com/Process_Contracts_Build_XML}Header during dehydration
    This element was not a root element and the scope had reference to this element. The scope should have references only to root element.
    Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
    </summary></part><part name="detail"><detail>javax.xml.ws.soap.SOAPFaultException: Cannot save xml element.
    failure to save the element {http://xmlns.oracle.com/Process_Contracts_Build_XML}Header during dehydration
    This element was not a root element and the scope had reference to this element.
    The scope should have references only to root element. Contact Oracle Support Services.
    Provide the error message and the exception trace in the log files (with logging level set to debug mode).
    </detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>
    Best Regards,
    Kalyan
    Edited by: ydkalyan on May 23, 2012 4:25 AM
    Edited by: ydkalyan on May 23, 2012 4:26 AM
    Edited by: ydkalyan on May 23, 2012 4:29 AM
    Edited by: ydkalyan on May 23, 2012 4:30 AM
    Edited by: ydkalyan on May 23, 2012 4:31 AM

    does your process have doXslTransform with multiple source documents? if yes then that patch should work. if not, please log an sr and please provide your current test case that can be used to reproduce the problem.

  • Add dynamic namespace declaration into xml root element

    Hello all,
    i've have two scenarios (mail to mail and file to file) with the same issue : no namespace in my XML file and i have to create one 'dynamically' from XML values.
    Example :
    <root>
    <name>test</name>
    <email>test</email>
    <schema>schemaID</schema>
    </root>
    Now I want to add infos into the root element for namespace declaration and so on, without expansion of the xsd. I've must use the value from the field schemaID.
    Example:
    <root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns: namespace="http://test.de/schemaID">
    <name>test</name>
    <email>test</email>
    </root>
    I've already done it before through XSLT but it wasn't dynamic !! I don't know how to do it in XSL and i am not a java expert.
    Someone got an idea ?
    Thanks,
    Jean-Philippe.

    Hi,
      If you want to add name space at mapping level two options
    1)Using XSLT Mapping ,its very easy,google it to get sample XSLT code ,it will solve your problem.
    2)Using java mapping,in java mapping use regular expression code ,using regex(Regulkar expresion)we can add any content in message at any level.
    Regards,
    Raj

  • How to remove namespace from root-element

    Hi Gurus,
    I want one xml output from xslt transformation with no namespace. I managed to remove namespace from child elements by leveraging elementFormDefault ='unqualified' property of xsd. But not able remove namespace from root-element.
    Output that I want is :
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <inp1:Email_Mod_Root>
       <Email_Mod_Root_Element>
          <Email_Record1>
             <PERSON_NUMBER>123456</PERSON_NUMBER>
             <COUNTRY/>
              <EMAIL_TYPE>WORK</EMAIL_TYPE>
             <EMAIL>EMAIL3</EMAIL>
             <PRIMARY_FLAG>Y</PRIMARY_FLAG>
          </Email_Record1>
    </Email_Mod_Root_Element>
    </Email_Mod_Root>
    Output that I am getting:
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <inp1:Email_Mod_Root xmlns:inp1="http://www.example.org">
       <Email_Mod_Root_Element>
          <Email_Record1>
             <PERSON_NUMBER>123456</PERSON_NUMBER>
             <COUNTRY/>
             <EMAIL_TYPE>WORK</EMAIL_TYPE>
             <EMAIL>EMAIL3</EMAIL>
             <PRIMARY_FLAG>Y</PRIMARY_FLAG>
          </Email_Record1>
    </Email_Mod_Root_Element>
    </Email_Mod_Root>
    Anyone, pls suggest.
    Thanks in advance,
    SG_SOA

    First of all :
    <inp1:Email_Mod_Root>
       <Email_Mod_Root_Element>
          <Email_Record1>
             <PERSON_NUMBER>123456</PERSON_NUMBER>
             <COUNTRY/>
              <EMAIL_TYPE>WORK</EMAIL_TYPE>
             <EMAIL>EMAIL3</EMAIL>
             <PRIMARY_FLAG>Y</PRIMARY_FLAG>
          </Email_Record1>
    </Email_Mod_Root_Element>
    </Email_Mod_Root>
    isn't valid xml (you start with inp1: prefix and you end the tag with no prefix, but let's assume you don't want any prefix/namespace at all)
    if i use :
    [code]
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:inp1="http://www.example.org" exclude-result-prefixes="inp1">
      <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
    <xsl:template match="*">
        <xsl:element name="{local-name(.)}">
          <xsl:apply-templates select="@* | node()"/>
        </xsl:element>
      </xsl:template>
      <xsl:template match="@*">
        <xsl:attribute name="{local-name(.)}">
          <xsl:value-of select="."/>
        </xsl:attribute>
      </xsl:template>
    </xsl:stylesheet>
    [/code]
    i get this
    [code]
    <Email_Root_Element>
      <Email_Record>
      <EMPLID>EMPLID46</EMPLID>
      <EMAIL>EMAIL48</EMAIL>
      <E_ADDR_TYPE>E_ADDR_TYPE49</E_ADDR_TYPE>
      <COUNTRY>US</COUNTRY>
      </Email_Record>
      <Email_Record>
      <EMPLID>EMPLID47</EMPLID>
      <EMAIL>EMAIL49</EMAIL>
      <E_ADDR_TYPE>E_ADDR_TYPE50</E_ADDR_TYPE>
      <COUNTRY>US</COUNTRY>
      </Email_Record>
      <Email_Record>
      <EMPLID>EMPLID48</EMPLID>
      <EMAIL>EMAIL49</EMAIL>
      <E_ADDR_TYPE>E_ADDR_TYPE51</E_ADDR_TYPE>
      <COUNTRY>US</COUNTRY>
      </Email_Record>
    </Email_Root_Element>
    [/code]

  • Adding namespace prefix to the XMLa root element

    I am facing a problem in our application. I am assigning an XML content to a XSD variable. While assignment operation is performed the prefix of the XML root element alone is getting replaced with default namespace, though the source XML has the prefix. Please let me know if any patch or workaround is available to address this issue.
    Thanks!

    Hi All,
    we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

  • Document type declaration for root element type "web-app" must end with ' '

    I am attempting to deploy an application (.war file) using the Sun Access Manager Agent installed, (Reference http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view -near the bottom) and I get this error:
    Error loading deployment descriptors for ajacs Line 3 Column 19 -- The document type declaration for root element type "web-app" must end with '>'.
    Here is the relavent code:
    <!DOCTYPE web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <web-app>
    <filter>
    <filter-name>Agent</filter-name>
    <filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class>
    </filter>
    <filter-mapping>
    <filter-name>Agent</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>ERROR</dispatcher>
    </filter-mapping>
    <display-name>AJACS</display-name>
    <welcome-file-list>
    <welcome-file>frameSet.jsp</welcome-file>
    </welcome-file-list>
    etc...
    Now, when I remove the parts that http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view said to add, it deploys just like it used to deploy- just fine with no errors. However, I add that code and it breaks.
    Note: The code was a straight copy/paste, so if there is any error in the code, it is because it's written incorrectly on the Sun doc website.
    Any help would be MUCH appreciated. Thanks!

    Well, if that was pasted on one line, it would be:
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
    So it's supposed to be that way. I just tried it with the extra quotes, and no dice...

  • Xmlns in root element

    When converting exchange rates xml from http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml
    I'm getting problem with xmlns in root element.
    CALL TRANSFORMATION triggers CX_XSLT_ABAP_CALL_ERROR, but only if there is xmlns attribute in first line in input xml:
    <gesmes:Envelope xmlns:gesmes="http://www.gesmes.org/xml/2002-08-01" xmlns="http://www.ecb.int/vocabulary/2002-08-01/eurofxref">
    Without this xmlns=.....  (or when modifying e.g. abcxmlns= ) works following xslt fine:
    <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
      <xsl:strip-space elements="*"/>
      <xsl:template match="/">
        <xsl:copy>
          <xsl:apply-templates/>
        </xsl:copy>
      </xsl:template>
      <xsl:template match="Cube/Cube">
        <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
          <asx:values>
            <ROOT2>
              <xsl:value-of select="@time"/>
            </ROOT2>
            <ROOT1>
              <xsl:apply-templates select="Cube"/>
            </ROOT1>
          </asx:values>
        </asx:abap>
      </xsl:template>
      <xsl:template match="Cube/Cube/Cube">
        <loop>
          <AMOUNT>
            <xsl:value-of select="1"/>
          </AMOUNT>
          <CCYCODE>
            <xsl:value-of select="@currency"/>
          </CCYCODE>
          <VALUE>
            <xsl:value-of select="@rate"/>
          </VALUE>
        </loop>
      </xsl:template>
    </xsl:transform>
    I'd appreciate if someone migh advise me how to alternate the xslt or tell me what the xmlns in input does.
    Cheers
    Edited by: Viktor Kunc on Sep 29, 2008 3:25 PM

    If a namespace is specified on root level, it propagates down to all children, see:
    http://www.w3.org/TR/REC-xml-names/scoping
    The namespace is part of a name. So, if you have an element <Cube> as child of the root element <root xmlns="http://www.gesmes.org/xml/2002-08-01">, then
    <xsl:apply-templates select="Cube"/>
    won't be applied, since the qualified name of the element is not Cube but {http://www.gesmes.org/xml/2002-08-01}Cube
    If you want the XSLT to work with and without namespace equally well, you have to work with local names in XPath expressions:
    <xsl:apply-templates select="local-name() = 'Cube'"/>
    The same holds for all XPath functions working with element names.
    Usually, however, the namespace is part of the contract with the client and is
    either obligatory to be used
    or obligatory to be omitted.
    But not both.
    Regards,
    Rüdiger

  • Name Space deplaration in root element in soap message

    My soap client is having problems interpreting the response received from my Java service. When implemented using Endpoint.publish it works, whoever once packaged up inside an WAR file it break my client. After some investigation I found that the response message differs slightly. It seems that the namespace is declared on the root element using JAX-WS 2.0, and within the content body using JAX-WS 2.1. As I am not able to change the soap framework on my client, I am wondering if there is an option I could get either JAX-WS or JAX-B to produce the response message in the working format.
    This is the fault generated by Endpoint.publish (Java5 with JAX-WS 2.0):
    HTTP/1.1 500 Internal Server Error
    Content-length: 507
    Content-type: text/xml; charset=utf-8
    <?xml version="1.0" ?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns1="http://addressbookserver.j2anywhere.com/">
    <soapenv:Body>
    <soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <faultcode>soapenv:Server</faultcode>
    <faultstring>Unable to verify license</faultstring>
    <detail><ns1:LicenseException>
    Unable to verify license
    </ns1:LicenseException></detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>This is the fault received from Tomcat (Java5 with JAX-WS 2.1):
    HTTP/1.1 500 Internal Server Error
    Server: Apache-Coyote/1.1
    Content-Type: text/xml;charset=utf-8
    Date: Thu, 19 Jun 2008 22:26:17 GMT
    Connection: close
    <?xml version="1.0" ?>
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <S:Fault xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
    <faultcode>S:Server</faultcode>
    <faultstring>Unable to verify license</faultstring>
    <detail>
    <ns2:LicenseException xmlns:ns2="http://addressbookserver.j2anywhere.com/">
    Unable to verify license
    </ns2:LicenseException>
    </detail>
    </S:Fault>
    </S:Body>
    </S:Envelope>Thanks in advance

    Those two documents look functionally the same to me. It shouldn't matter whether the namespaces are declared at a higher level than necessary. If you have a client that treats those two documents differently then I would say it's not working correctly.

  • Error parsing envelope: (1, 1) Start of root element expected.

    Hello BI Publisher:
    The issue has been resolved. I found the cause the problem. The following line in my WSDL was preventing BI Publisher from reading the WSDL, which will return the "Error parsing envelope" message:
    <xsd:attribute name="dateTimeTagFormat" fixed="xsd" use="required"/>
    Once I removed the above line, BI Publisher was able to read the WSDL without any issues, and run the report.
    Benjamin
    Hello BI Publisher:
    I am trying to define a new dataset of type "Web Service", with a Complex Type configuration using WS-Security 2004. I get the following error when I try to "View" it:
    **"javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected."**
    This happens even if my Application Server (where the service is located) is not running, so I suspect that the error happens before the Publisher server tries to send the SOAP envevelop to the service server.
    Publisher Version: Release 10.1.3.4
    Complex Type: True
    Username: User1
    Password: ******
    Time Out: 60
    WSDL URL: http://localhost:4100/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF?WSDL
    Web Service: ZZ_BIP_XAI_ZFService
    Method: ZZ_BIP_XAI_ZF
    ResponseData XPath: <blank>
    Here is the Publisher server log in debug mode:
    [072909_110222553][][STATEMENT] Setting data definition:New DataSet 1 type:oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11
    [072909_110222569][][STATEMENT] Skip migration for cookie (ORA_XDO) is not found
    [072909_110228644][][STATEMENT] Skip migration for cookie (ORA_XDO) is not found
    [072909_110228690][][STATEMENT] WebServiceBoundValue11::getValue m_xpath =
    [072909_110228690][][STATEMENT] WSS Parameter = 2004
    09/07/29 11:02:28 WebServiceCall::callComplexClient SOAP Message = null
    [072909_110228706][][STATEMENT] SOAP Response XPATH =
    [072909_110228706][][STATEMENT] http://localhost.us.oracle.com:4100/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF?WSDL
    [072909_110228706][][STATEMENT] ZZ_BIP_XAI_ZF
    [072909_110228706][][STATEMENT] null
    09/07/29 11:02:28 WebServiceCall::callComplexClient WS-Security Enabled - uid [SPLBPG], pwd [splbpg00], spec-2004 [true]
    09/07/29 11:02:28 javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    09/07/29 11:02:28 at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    09/07/29 11:02:28 at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    09/07/29 11:02:28 at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    09/07/29 11:02:28 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    09/07/29 11:02:28 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    09/07/29 11:02:28 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    09/07/29 11:02:28 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    09/07/29 11:02:28 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    09/07/29 11:02:28 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    09/07/29 11:02:28 at java.lang.Thread.run(Thread.java:595)
    09/07/29 11:02:28 Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    09/07/29 11:02:28 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    09/07/29 11:02:28 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    09/07/29 11:02:28 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    09/07/29 11:02:28 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    09/07/29 11:02:28 ... 30 more
    [072909_110228862][][EXCEPTION] oracle.apps.xdo.webservice.wsclient.WSClientException: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1406)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    ... 27 more
    Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    ... 30 more
    [072909_110228878][][EXCEPTION] oracle.apps.xdo.webservice.wsclient.WSClientException: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1406)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    ... 27 moreCaused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    ... 30 more
    Here is my WSDL:
    <?xml version="1.0"?>
    <!-- root element wsdl:definitions defines set of related services -->
    <wsdl:definitions name="ZZ_BIP_XAI_ZF"
    targetNamespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"
    xmlns:xai="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"
    xmlns:xaixsd="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF.xsd"
    xmlns:schemans1="http://oracle.com/ZZ_BIP_XAI_ZF.xsd"
    xmlns:schemans2="http://oracle.com/ZZ_BIP_XAI_ZF.xsd"
    xmlns:ouaf="urn:oracle:ouaf"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <!-- wsdl:types encapsulates schema definitions of communication types;
    here using xsd -->
    <wsdl:types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:oracle:ouaf" elementFormDefault="qualified">
    <xsd:element name="Fault">
    <xsd:complexType>
    <xsd:all>
    <xsd:element name="ResponseStatus" type="xsd:string"/>
    <xsd:element name="ResponseCode" type="xsd:int"/>
    <xsd:element name="ResponseText" type="xsd:string"/>
    <xsd:element name="ResponseData" minOccurs="0">
    <xsd:complexType>
    <xsd:attribute name="parm1" type="xsd:string"/>
    <xsd:attribute name="parm2" type="xsd:string"/>
    <xsd:attribute name="parm3" type="xsd:string"/>
    <xsd:attribute name="parm4" type="xsd:string"/>
    <xsd:attribute name="parm5" type="xsd:string"/>
    <xsd:attribute name="text" type="xsd:string"/>
    <xsd:attribute name="category" type="xsd:string"/>
    <xsd:attribute name="numParm" type="xsd:int"/>
    </xsd:complexType>
    </xsd:element>
    </xsd:all>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:oracle:ouaf" elementFormDefault="qualified">
    <xsd:simpleType name="money">
    <xsd:restriction base="xsd:decimal"/>
    </xsd:simpleType>
    </xsd:schema>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ouaf="urn:oracle:ouaf" targetNamespace="http://oracle.com/ZZ_BIP_XAI_ZF.xsd" elementFormDefault="qualified">
    <xsd:import namespace="urn:oracle:ouaf"/>
    <xsd:element name="ZZ_BIP_XAI_ZF">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="startDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="endDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="crew" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="crewId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="crewName" type="xsd:string"/>
    <xsd:element name="task" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="crewId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="taskId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="taskName" type="xsd:string"/>
    <xsd:element name="status" type="xsd:string"/>
    <xsd:element name="startDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="endDttm" type="xsd:dateTime" minOccurs="0"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="dateTimeTagFormat" fixed="xsd" use="required"/>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </wsdl:types>
    <!-- wsdl:message elements describe potential transactions -->
    <!-- request ZZ_BIP_XAI_ZFRequest is of type ZZ_BIP_XAI_ZF -->
    <wsdl:message name="ZZ_BIP_XAI_ZFRequest">
    <wsdl:part name="body" element="schemans1:ZZ_BIP_XAI_ZF"/>
    </wsdl:message>
    <!-- response ZZ_BIP_XAI_ZFResponse is of type ZZ_BIP_XAI_ZFResponse -->
    <wsdl:message name="ZZ_BIP_XAI_ZFResponse">
    <wsdl:part name="body" element="schemans2:ZZ_BIP_XAI_ZF"/>
    </wsdl:message>
    <!-- fault ZZ_BIP_XAI_ZFFault is of type ZZ_BIP_XAI_ZFFault -->
    <wsdl:message name="ZZ_BIP_XAI_ZFFault">
    <wsdl:part name="fault" element="ouaf:Fault"/>
    </wsdl:message>
    <!-- wsdl:portType describes messages in an operation -->
    <wsdl:portType name="ZZ_BIP_XAI_ZFPortType">
    <!-- the value of wsdl:operation eludes me -->
    <wsdl:operation name="ZZ_BIP_XAI_ZF">
    <wsdl:input message="xai:ZZ_BIP_XAI_ZFRequest"/>
    <wsdl:output message="xai:ZZ_BIP_XAI_ZFResponse"/>
    <wsdl:fault name="fault" message="xai:ZZ_BIP_XAI_ZFFault"/>
    </wsdl:operation>
    </wsdl:portType>
    <!-- wsdl:binding states a serialization protocol for this service -->
    <wsdl:binding name="ZZ_BIP_XAI_ZFSoapBinding"
    type="xai:ZZ_BIP_XAI_ZFPortType">
    <!-- leverage off soap:binding document style @@@(no wsdl:foo pointing at
    the soap binding) -->
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <!-- semi-opaque container of network transport details classed by
    soap:binding above @@@ -->
    <wsdl:operation name="ZZ_BIP_XAI_ZF">
    <!-- again bind to SOAP? @@@ -->
    <soap:operation soapAction="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    <!-- furthur specify that the messages in the wsdl:operation
    "ZZ_BIP_XAI_ZF" use SOAP? @@@ -->
    <wsdl:input>
    <soap:body use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:output>
    <wsdl:fault name="fault">
    <soap:fault name="fault" use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <!-- wsdl:service names a new service "ZZ_BIP_XAI_ZFService" -->
    <wsdl:service name="ZZ_BIP_XAI_ZFService">
    <wsdl:documentation>ZZ_BIP_XAI_ZF version 3: Test XAI WS for BIP</wsdl:documentation>
    <!-- connect it to the binding "ZZ_BIP_XAI_ZFSoapBinding" above -->
    <wsdl:port name="ZZ_BIP_XAI_ZFPort"
    binding="xai:ZZ_BIP_XAI_ZFSoapBinding">
    <!-- give the binding an network address -->
    <soap:address location="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Edited by: bperezg on Aug 12, 2009 2:49 PM
    Edited by: bperezg on Aug 12, 2009 2:56 PM

    Hello BI Publisher:
    The issue has been resolved. I found the cause the problem. The following line in my WSDL was preventing BI Publisher from reading the WSDL, which will return the "Error parsing envelope" message:
    <xsd:attribute name="dateTimeTagFormat" fixed="xsd" use="required"/>
    Once I removed the above line, BI Publisher was able to read the WSDL without any issues, and run the report.
    Benjamin
    Hello BI Publisher:
    I am trying to define a new dataset of type "Web Service", with a Complex Type configuration using WS-Security 2004. I get the following error when I try to "View" it:
    **"javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected."**
    This happens even if my Application Server (where the service is located) is not running, so I suspect that the error happens before the Publisher server tries to send the SOAP envevelop to the service server.
    Publisher Version: Release 10.1.3.4
    Complex Type: True
    Username: User1
    Password: ******
    Time Out: 60
    WSDL URL: http://localhost:4100/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF?WSDL
    Web Service: ZZ_BIP_XAI_ZFService
    Method: ZZ_BIP_XAI_ZF
    ResponseData XPath: <blank>
    Here is the Publisher server log in debug mode:
    [072909_110222553][][STATEMENT] Setting data definition:New DataSet 1 type:oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11
    [072909_110222569][][STATEMENT] Skip migration for cookie (ORA_XDO) is not found
    [072909_110228644][][STATEMENT] Skip migration for cookie (ORA_XDO) is not found
    [072909_110228690][][STATEMENT] WebServiceBoundValue11::getValue m_xpath =
    [072909_110228690][][STATEMENT] WSS Parameter = 2004
    09/07/29 11:02:28 WebServiceCall::callComplexClient SOAP Message = null
    [072909_110228706][][STATEMENT] SOAP Response XPATH =
    [072909_110228706][][STATEMENT] http://localhost.us.oracle.com:4100/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF?WSDL
    [072909_110228706][][STATEMENT] ZZ_BIP_XAI_ZF
    [072909_110228706][][STATEMENT] null
    09/07/29 11:02:28 WebServiceCall::callComplexClient WS-Security Enabled - uid [SPLBPG], pwd [splbpg00], spec-2004 [true]
    09/07/29 11:02:28 javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    09/07/29 11:02:28 at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    09/07/29 11:02:28 at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    09/07/29 11:02:28 at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    09/07/29 11:02:28 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    09/07/29 11:02:28 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    09/07/29 11:02:28 at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    09/07/29 11:02:28 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    09/07/29 11:02:28 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    09/07/29 11:02:28 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    09/07/29 11:02:28 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    09/07/29 11:02:28 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    09/07/29 11:02:28 at java.lang.Thread.run(Thread.java:595)
    09/07/29 11:02:28 Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    09/07/29 11:02:28 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    09/07/29 11:02:28 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    09/07/29 11:02:28 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    09/07/29 11:02:28 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    09/07/29 11:02:28 at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    09/07/29 11:02:28 ... 30 more
    [072909_110228862][][EXCEPTION] oracle.apps.xdo.webservice.wsclient.WSClientException: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1406)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    ... 27 more
    Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    ... 30 more
    [072909_110228878][][EXCEPTION] oracle.apps.xdo.webservice.wsclient.WSClientException: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1406)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.callComplexClient(WebServiceCall.java:179)
    at oracle.apps.xdo.servlet.data.server.WebServiceCall.doFetch(WebServiceCall.java:63)
    at oracle.apps.xdo.servlet.data.server.AbstractDataCall.execute(AbstractDataCall.java:63)
    at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:147)
    at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:412)
    at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
    at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
    at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
    at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
    at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
    at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
    at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
    at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
    at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.soap.SOAPException: Error parsing envelope: (1, 1) Start of root element expected.
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:103)
    at oracle.j2ee.ws.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:76)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1429)
    at oracle.apps.xdo.webservice.wsclient.WSClient.insertSecurityHeaders(WSClient.java:1399)
    ... 27 moreCaused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:206)
    at oracle.j2ee.ws.saaj.soap.soap11.SOAPImplementation11.createEnvelope(SOAPImplementation11.java:77)
    ... 30 more
    Here is my WSDL:
    <?xml version="1.0"?>
    <!-- root element wsdl:definitions defines set of related services -->
    <wsdl:definitions name="ZZ_BIP_XAI_ZF"
    targetNamespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"
    xmlns:xai="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"
    xmlns:xaixsd="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF.xsd"
    xmlns:schemans1="http://oracle.com/ZZ_BIP_XAI_ZF.xsd"
    xmlns:schemans2="http://oracle.com/ZZ_BIP_XAI_ZF.xsd"
    xmlns:ouaf="urn:oracle:ouaf"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <!-- wsdl:types encapsulates schema definitions of communication types;
    here using xsd -->
    <wsdl:types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:oracle:ouaf" elementFormDefault="qualified">
    <xsd:element name="Fault">
    <xsd:complexType>
    <xsd:all>
    <xsd:element name="ResponseStatus" type="xsd:string"/>
    <xsd:element name="ResponseCode" type="xsd:int"/>
    <xsd:element name="ResponseText" type="xsd:string"/>
    <xsd:element name="ResponseData" minOccurs="0">
    <xsd:complexType>
    <xsd:attribute name="parm1" type="xsd:string"/>
    <xsd:attribute name="parm2" type="xsd:string"/>
    <xsd:attribute name="parm3" type="xsd:string"/>
    <xsd:attribute name="parm4" type="xsd:string"/>
    <xsd:attribute name="parm5" type="xsd:string"/>
    <xsd:attribute name="text" type="xsd:string"/>
    <xsd:attribute name="category" type="xsd:string"/>
    <xsd:attribute name="numParm" type="xsd:int"/>
    </xsd:complexType>
    </xsd:element>
    </xsd:all>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:oracle:ouaf" elementFormDefault="qualified">
    <xsd:simpleType name="money">
    <xsd:restriction base="xsd:decimal"/>
    </xsd:simpleType>
    </xsd:schema>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ouaf="urn:oracle:ouaf" targetNamespace="http://oracle.com/ZZ_BIP_XAI_ZF.xsd" elementFormDefault="qualified">
    <xsd:import namespace="urn:oracle:ouaf"/>
    <xsd:element name="ZZ_BIP_XAI_ZF">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="startDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="endDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="crew" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="crewId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="crewName" type="xsd:string"/>
    <xsd:element name="task" minOccurs="0" maxOccurs="unbounded">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="crewId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="taskId" type="xsd:string" minOccurs="0"/>
    <xsd:element name="taskName" type="xsd:string"/>
    <xsd:element name="status" type="xsd:string"/>
    <xsd:element name="startDttm" type="xsd:dateTime" minOccurs="0"/>
    <xsd:element name="endDttm" type="xsd:dateTime" minOccurs="0"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="dateTimeTagFormat" fixed="xsd" use="required"/>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </wsdl:types>
    <!-- wsdl:message elements describe potential transactions -->
    <!-- request ZZ_BIP_XAI_ZFRequest is of type ZZ_BIP_XAI_ZF -->
    <wsdl:message name="ZZ_BIP_XAI_ZFRequest">
    <wsdl:part name="body" element="schemans1:ZZ_BIP_XAI_ZF"/>
    </wsdl:message>
    <!-- response ZZ_BIP_XAI_ZFResponse is of type ZZ_BIP_XAI_ZFResponse -->
    <wsdl:message name="ZZ_BIP_XAI_ZFResponse">
    <wsdl:part name="body" element="schemans2:ZZ_BIP_XAI_ZF"/>
    </wsdl:message>
    <!-- fault ZZ_BIP_XAI_ZFFault is of type ZZ_BIP_XAI_ZFFault -->
    <wsdl:message name="ZZ_BIP_XAI_ZFFault">
    <wsdl:part name="fault" element="ouaf:Fault"/>
    </wsdl:message>
    <!-- wsdl:portType describes messages in an operation -->
    <wsdl:portType name="ZZ_BIP_XAI_ZFPortType">
    <!-- the value of wsdl:operation eludes me -->
    <wsdl:operation name="ZZ_BIP_XAI_ZF">
    <wsdl:input message="xai:ZZ_BIP_XAI_ZFRequest"/>
    <wsdl:output message="xai:ZZ_BIP_XAI_ZFResponse"/>
    <wsdl:fault name="fault" message="xai:ZZ_BIP_XAI_ZFFault"/>
    </wsdl:operation>
    </wsdl:portType>
    <!-- wsdl:binding states a serialization protocol for this service -->
    <wsdl:binding name="ZZ_BIP_XAI_ZFSoapBinding"
    type="xai:ZZ_BIP_XAI_ZFPortType">
    <!-- leverage off soap:binding document style @@@(no wsdl:foo pointing at
    the soap binding) -->
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <!-- semi-opaque container of network transport details classed by
    soap:binding above @@@ -->
    <wsdl:operation name="ZZ_BIP_XAI_ZF">
    <!-- again bind to SOAP? @@@ -->
    <soap:operation soapAction="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    <!-- furthur specify that the messages in the wsdl:operation
    "ZZ_BIP_XAI_ZF" use SOAP? @@@ -->
    <wsdl:input>
    <soap:body use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:output>
    <wsdl:fault name="fault">
    <soap:fault name="fault" use="literal"
              namespace="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <!-- wsdl:service names a new service "ZZ_BIP_XAI_ZFService" -->
    <wsdl:service name="ZZ_BIP_XAI_ZFService">
    <wsdl:documentation>ZZ_BIP_XAI_ZF version 3: Test XAI WS for BIP</wsdl:documentation>
    <!-- connect it to the binding "ZZ_BIP_XAI_ZFSoapBinding" above -->
    <wsdl:port name="ZZ_BIP_XAI_ZFPort"
    binding="xai:ZZ_BIP_XAI_ZFSoapBinding">
    <!-- give the binding an network address -->
    <soap:address location="http://sf-fwwin-03.us.oracle.com:4400/spl/XAIApp/xaiserver/ZZ_BIP_XAI_ZF"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Edited by: bperezg on Aug 12, 2009 2:49 PM
    Edited by: bperezg on Aug 12, 2009 2:56 PM

Maybe you are looking for