WSDL incorrect - in XSD elements always must be the root element?
Hi!
First of all, sorry about my english, but I'm not accustomed to write in this language ;-)
We're trying to publish a Webservice with JAXWS and with a classes generated via JAXB parsing a group of XSD files, always in a maven project with java 5.
More explained the steps we are trying to follow:
1) parse the XSD files with JAXB and generate a JAR file to be included like a dependency in the webapp
2) use the classes packaged in the JAR in other maven project and define and deploy a webapp with the webservice using JAXWS defining a SEI that uses and returns a Type included in the JAR generated in the previous step. Here it is the interface that implements the SEI:
@WebMethod
public TESTELEMENT test(
@WebParam(name = "test")
TESTELEMENT element);The problem seems to be that if the elements in the original XSD files aren't root elements the WSDL generated is incorrect.
Here there are the XSD files we are using and the WSDL error result (XMLSpy dixit, "ns1:Example" must refer to an existing element).
Anyone knows what happens?
Thank you in advance and sorry about this large message!
+--- start of TEST.XSD --+
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="TEST_TYPE.xsd"/>
<!--
if we define the Example Element like this, everything works ok! why? because Example is defined global?
<xs:element name="Example" type="ExampleType"/>
-->
<xs:element name="TEST_ELEMENT">
<xs:annotation>
<xs:documentation>Blablabla</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="Example" type="TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>+-- end --+
+--- start of TEST_TYPE.xsd --+
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="TestType">
<xs:annotation>
<xs:documentation>Example type</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>+-- end --+
+-- start WSDL error --+
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="TestBO" targetNamespace="http://our.package.test/" xmlns:ns1="http://our.package.test/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Example" type="tns:TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TestType">
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://our.package.test" xmlns:ns1="http://example.work/test" xmlns:tns="http://our.package.test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
<xs:sequence>
<xs:element minOccurs="0" name="test">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/> *<!-- here is the error - XMLSpy dixit that ns1:Example must refer to an existing element -->*
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="test">
<wsdl:part element="ns1:test" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="testResponse">
<wsdl:part element="ns1:testResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="TestBO">
<wsdl:operation name="test">
<wsdl:input message="ns1:test" name="test">
</wsdl:input>
<wsdl:output message="ns1:testResponse" name="testResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>+-- end --+
Hi again.
About my last post, say that the WSDL generated, in fact, was generated with CXF, sorry.
Using JAXWS (wsgen to be more explicit) the WSDL results still are not ok, as you can see, the error is in the last ns1:Example reference in ServeiTestBO_schema1.xsd, that XMLSpy says that doesn't exists :-( :
+--- ServeiTestBOImplService.wsdl [ServeiTestBOImpl - SEI] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.5-b03-. -->
<definitions targetNamespace="http://impl.our.package.test/" name="ServeiTestBOImplService" xmlns:tns="http://impl.our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://our.package.test/" location="ServeiTestBO.wsdl"/>
<binding name="ServeiTestBOImplPortBinding" type="ns1:ServeiTestBO" xmlns:ns1="http://our.package.test/">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="test">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="ServeiTestBOImplService">
<port name="ServeiTestBOImplPort" binding="tns:ServeiTestBOImplPortBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>+--- ServeiTestBO.wsdl [SEI interface] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.5-b03-. -->
<definitions targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<xsd:schema>
<xsd:import namespace="http://our.package.test/" schemaLocation="ServeiTestBO_schema1.xsd"/>
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
</xsd:schema>
</types>
<message name="test">
<part name="parameters" element="tns:test"/>
</message>
<message name="testResponse">
<part name="parameters" element="tns:testResponse"/>
</message>
<portType name="ServeiTestBO">
<operation name="test">
<input message="tns:test"/>
<output message="tns:testResponse"/>
</operation>
</portType>
</definitions>+--- ServeiTestBO_schema1.xsd *[with error in the last "ns1:Example"]* ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema version="1.0" targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:ns1="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
<xs:sequence>
<xs:element name="test" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
<xs:sequence>
<xs:element name="return" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
--- ServeiTestBO_schema2.xsd ---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
<xs:complexType>
<xs:sequence>
<xs:element name="Example" type="tns:TestType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TestType">
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
<xs:element name="Sex" type="tns:SexType"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="SexType">
<xs:restriction base="xs:string">
<xs:enumeration value="M"/>
<xs:enumeration value="W"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>Thanks in advance again.
Similar Messages
-
The markup in the document following the root element must be well-formed.
I have my XML root element that looks like this:
<DataResponseOfListOfSite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www
.w3.org/2001/XMLSchema" xmlns="http://xxxxxx/webservices/sites/">
and I get the error "The markup in the document following the root element must be well-formed."
If I use this it works fine:
<DataResponseOfListOfSite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www
.w3.org/2001/XMLSchema" xmlns:xsi="http://xxxxxx/webservices/sites/">
Does anyone know why I have to have the xmlns:xsi="" instead of just xmlns=""
If I paste this XML into any validator, it says that its good, so I dont know why Flex is complaining about it.In the first one you have two namespaces both with the same prefix.
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" and xmlns:xsi="http://xxxxxx/webservices/sites/"
Thanks,
Gaurav Jain
Flex SDK Team
http://www.gauravj.com/blog -
TLD Error:The markup in the document preceding the root element must...
Hello, I am new to using the Tag Libraries, i am getting the following error which seems to be in my treeTag.tld file, I am pasting the error message and the treeTag.tld at the bottom of this message. Any help is much appreciated.
Apache Tomcat/4.0.1 - HTTP Status 500 - Internal Server Error
type Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: XML parsing error on file /TreeTag/treeTag.tld: (line 5, col 1): The markup in the document preceding the root element must be well-formed.
at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:218)
at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:283)
at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:219)
at ***************************************************
Here is my treeTag.tld file
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
- <taglib>
<tlibversion>1.1</tlibversion>
<jspversion>1.1</jspversion>
<shortname>Tree taglib</shortname>
<uri>http://www.servletsuite.com/servlets/treetag</uri>
<info>Tree tags</info>
- <tag>
<name>createTree</name>
<tagclass>com.cj.tree.createTree</tagclass>
<bodycontent>JSP</bodycontent>
<info>Creates HTML-based tree view</info>
</tag>
- <tag>
<name>addNode</name>
<tagclass>com.cj.tree.addNode</tagclass>
<bodycontent>JSP</bodycontent>
<info>adds node</info>
- <attribute>
<name>code</name>
<required>true</required>
<rtexprvalue>true</rtexprvalue>
</attribute>
</tag>
</taglib>
Regards,
Navin Pathuru.You might make sure - if you havent already - that you are using the must up to date jsp version
-
The markup in the document preceding the root element must be well-formed
Hi,
Each time I add some library, something serious happens to my NetBeans5.5 and Tomcat 5.5.17. This time I added jsf-facelets.jar and now nothing is being deployed. I m getting following exception
javax.servlet.ServletException: Error Parsing /Dept.jsp: Error Traced[line: 1] The markup in the document preceding the root element must be well-formed.
javax.faces.webapp.FacesServlet.service(FacesServlet.java:202)
Is there any special procedure to follow to add libraries?
Plz help.Facelets is XHTML. XHTML is XML-HTML. XML require strict well-formness of the tags. I.e. every tag should be correctly nested and closed.
I would say, read the Facelets Developer Documentation: http://www.google.com/search?q=facelets+developer+documentation -
Real time transaction response - unable to locate the root element
Hi There
Has anyone integrated webMethods with Data Services 3.2 for real time transactions?
We are trying to create a real time dataflow, initiated by webMethods. We are sending the request to the Access Server which runs our
real time dataflow and does process the request. However, our return response is null. No data in the response back to webMethods. We have
tested this in soapUI, and our transaction does work. We get the correct response back.
So my question is has any experienced this issue with webMethods? Any suggestions or ideas?
Here is the error
===========================================
Path name:
PortType: Real-time_Services
Operation: Realtime_address_cleanse
WSDL code: S-9043
[ISS.0092.9043] Schema Error: 1
pathName: null
errorCode: CONV-004
errorMessage: [ISC.0082.9104] DataOut - unable to locate the root element
identifier: null
===========================================
ps- xmlspy does not work as well
Please let me know
Thanks
KurtThe problem was the generated test SOAP message from Netbeans. When built, the interface had more levels than described below. I've also had similar issues caused by bad namespaces - either not defined properly or not picking up the default namespace.
-
E4X: What happens to the root element?
I'm working with XML using the E4X notation. I'm used to the "old school" XML APIs that use DOM and I'm a bit confused.
For example, let's consider the following XML
<mx:XML id="myXML" >
<top>
<sub1 id="uno">
<sub2>hello</sub2>
<sub3>world</sub3>
</sub1>
<sub1 id="duo">
<sub2>ok</sub2>
<sub3>ko</sub3>
</sub1>
</top>
</mx:XML>
In my code I use the following traces. This is done with the De MonsterDebugger, but all others should work the same way. I have casted the traces to String only to make it easier to ask this question (no need post images)
MonsterDebugger.trace(this, "myXML:" + myXML);
MonsterDebugger.trace(this, "myXML.sub1: " + myXML.sub1);
MonsterDebugger.trace(this, "myXML.sub1.sub2: " + myXML.sub1.sub2);
What I get as output is
(String) = myXML:<top>
<sub1 id="uno">
<sub2>hello</sub2>
<sub3>world</sub3>
</sub1>
<sub1 id="duo">
<sub2>ok</sub2>
<sub3>ko</sub3>
</sub1>
</top>
(String) = myXML.sub1: <sub1 id="uno">
<sub2>hello</sub2>
<sub3>world</sub3>
</sub1>
<sub1 id="duo">
<sub2>ok</sub2>
<sub3>ko</sub3>
</sub1>
(String) = myXML.sub1.sub2: <sub2>hello</sub2>
<sub2>ok</sub2>
All is fine above and this was a bit long abstract for my question. The question is what happens to the root element, in this case <top>? I was trying to access the data with the following notation
myXML.top.sub1; // etc
I spent quite a lot of time trying to get it to work, until I discovered that the root element is not used. Can anyone explain this?
Or, I guess the simple explanation is that the root node is ignored and the sub nodes are created as properties of the object. The question also could be stated as: Why isn't this documented in the Flex API Reference?
Thanks.
P.S. I found this article on common E4X pitfalls which also has other interesting topics when working with E4X.its gone
downgrading would kill the phone.. -
How can i change the ROOT ELEMENT name in my ADOBE Form
Hello All,
I need to change "data" the Root Element default name to another name.
Is this possible? How do i do this?
Thank you all in advance,
EranHello Chintan and Otto,
thank you for your replies...
Chintan: There is Adobe livecycle designer CE and its a stand alone application :[ designer CE2|http://www.adobe.com/products/livecycle/]
Otto: I know i can send the xml back and change it in my abap program but i'm talking about stand alone form in a computer with no sap on it.
The user will fill it and submit it ...
Thank you all in advance,
Eran -
Xerces Sockets and The root element is required
Hi,
I have a problem with Xerces 1.4.3 saying "The root element is required in a well-formed document.". The story is as follows:
When I read the XML from a file, it works OK.
But when I send the file over a socket stream, and try to parse it in the client side, it gives this silly message.
I am sure that there is no space before <?xml ... ?> and also the xml file is well formed.
I guess someone can say Xerces 2 solves this problem but I am using JBuilder 7 and I could not install the new xerces over old one. If someone knows how to do this please let me know. (Copying the jars into jbuilder7/lib does not seems to work as the file names are different and it wont overwrite the old xerces parser)
Any solution?
Thanks,saving and parsing is working fine. hehe :)
seems that the parser is somewhat going crazy.
btw. I had written a class extending InputStream, so that it reads more than one file from a socket stream. But I have used it in this save and parse test and it worked so I dont think I have problems with that.
In one forum here, I saw someone saying that changing the version solved his problems about this silly thing. I think I wil try this.
Tankut -
Rename the root element in a XMLTYPE field
Hello, I have to rename the root element of an XMLTYPE like :
Change :
<Address>
<Name>Dupont</Name>
<Street>Av de la gare</Street>
</Address>
To :
<CustomerAddress>
<Name>Dupont</Name>
<Street>Av de la gare</Street>
</CustomerAddress>
One solution will be to use the EXTRACT (a.xml, '/*/*') AS "CustomerAddress"
I am just afraid about performance !!!
Anyone has an advice
Best RegardsPl go through this doc/Title
XML Schema Evolution
This chapter describes how you can update your XML schema after you have registered it with Oracle XML DB. XML schema evolution is the process of updating your registered XML schema and let me know if this helps. -
Start of the root element expected.
Hello Gurus,
I moved all my project contents from one root directory to another, after seting up everything. It gives compile time error on adf-faces-config.xml and adf-faces-skins.xml.
The error:
XML-20108 - Start of the root element expected.
I have no idea what could have originated this error and how to fix it. Can any one help me?
Thank you.
RuchirI built the new project structure from scratch. i.e. created new application, then added a web project, then added all css file from old locations, then, created new xml documents and renamed it to adf-config-faces.xml and adf-faces-skins.xml and manually copied from these config xml documents from old location to newer one.
And then at last, copied the .jspx page and when compiling that, control moves to adf-config-faces.xml file and gives the error.
Thanks,
Ruchir -
The root element is required in a well-formed document.
While trying to parse the following xml file using jaxp.jar and xerces.jar I am getting the following exception
org.xml.sax.SAXParseException: The root element is required in a well-formed document.
at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1196)
at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:570)
at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:790)
at org.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:418)
at org.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:694)
at org.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1026)
at org.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
at org.apache.xerces.readers.AbstractCharReader.changeReaders(AbstractCharReader.java:150)
at org.apache.xerces.readers.AbstractCharReader.lookingAtChar(AbstractCharReader.java:217)
at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:686)
at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
at XMLConverter.parse(XMLConverter.java:65)
at XMLConverter.parse(XMLConverter.java:116)
at XMLConverter.main(XMLConverter.java:282)
xml file
<?xml version="1.0"?>
<CustomerOrder>
<Customer>
<FirstName> Bob </FirstName>
<LastName> Hustead </LastName>
<CustId> abc.123 </CustId>
</Customer>
<OrderItems>
<OrderItem>
<Quantity> 1 </Quantity>
<ProductCode> 48.GH605A </ProductCode>
<Description> Pet Rock </Description>
<Price> 19.99 </Price>
</OrderItem>
<OrderItem>
<Quantity> 12 </Quantity>
<ProductCode> 47.9906Z </ProductCode>
<Description> Bazooka Bubble Gum </Description>
<Price> 0.33 </Price>
</OrderItem>
<OrderItem>
<Quantity> 2 </Quantity>
<ProductCode> 47.7879H </ProductCode>
<Description> Flourescent Orange Squirt Gun </Description>
<Price> 2.50 </Price>
</OrderItem>
</OrderItems>
</CustomerOrder>
Can anybody please help me.
Thanks in advanceHi There,
I too am experiencing the same problem. I originally began with the problem described in
http://forum.java.sun.com/thread.jsp?forum=34&thread=138862
I removed the jaxp.jar and parser.jar from Tomcat's Lib folder and added the xerces.jar. This moved me on to the problem described in this thread.
Here is my XML file:
<?xml version="1.0"?>
<training_seminar>
<student>
<id>0001</id>
<name>Joe Jones</name>
<email>[email protected]</email>
<passport level="4 course">yes</passport>
</student>
<student>
<id>0031</id>
<name>Patrick Thompson</name>
<email>[email protected]</email>
<passport>no</passport>
</student>
</training_seminar>
And here is my XSL:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:template match="training_seminar">
<HTML><BODY>
<TABLE BORDER="1">
<TR>
<TH>Student ID</TH>
<TH>Name</TH>
<TH>E-Mail</TH>
<TH>Passport</TH>
</TR>
<xsl:for-each select="student">
<TR>
<TD> <xsl:value-of select="id"/></TD>
<TD> <xsl:value-of select="name"/> </TD>
<TD> <xsl:value-of select="email"/> </TD>
<TD> <xsl:value-of select="passport"/> </TD>
</TR>
</xsl:for-each>
</TABLE>
</BODY></HTML>
</xsl:template>
</xsl:stylesheet>
And I guess while I am at it, my classpath:
CLASSPATH=e:\java\jdk1.3.1\jre\lib\rt.jar;e:\jakarta-tomcat-3.2.3\lib\servlet.jar;E:\Dev Tools\xalan-j_2_1_0\bin\xerces.jar;E:\Dev Tools\xalan-j_2_1_0\bin\xalan
.jar;E:\Dev Tools\xalan-j_2_1_0\bin\xsltc.jar;E:\Dev Tools\xalan-j_2_1_0\bin\xml
.jar;.
Any ideas is truly appreciated.
Thanks,
Gregg -
XSD from PI in Syndicator - no root element selectable
Hello
I have created a message type in PI and exported the XSD. However when I want to use that XSD in the syndicator no root element is available. Why is that?
I have searched the forums and found that MDM won't show a root element if the XSD is not sane. What part of the XSD is not sane? I have validated it in Liquid XML and it works in the import manager.
Has anyone had the same problem?
BR
/AlexanderHi,
I also faced same problem. We removed namespace from XSD manually. When u create file from PI it contains namespace.
It worked then !!!!
if still not solved tell me in detail i will give eg ..
Regards
Himanshu
reward if helpful -
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
AyushHi All,
we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version. -
I have 8 picture controls inside an array and I would like to set the caption text of these controls.
I have used the property node of the array and used the array elements property caption text to set the text.
The problem is however that I set the same text to all the picture controls inside the array.
My question is how to set caption text of specific elements (Picture control) that I have so far only been able to access using the array elements caption text property.Some more help
1 You could use the caption of the array and place it in front of the selected picture and update that using property nodes.
2 Like Norbett said if you use a cluster of pictures then their caption can be updated individually.
Here is a an example that demonstrates the above
David
Attachments:
Modify the Captions Of Pictures.vi 83 KB -
I'm running Acrobat 9.4 if that makes any difference. This question was spurred by another discussion on inserting an item into a list. Basically loadXML is erasing the attributes on the reference node. For example, if domNode is a node in the data DOM and newXML is a replica of domNode's XML with some child elements changed and newXML_str is the string representation of newXML, then the statement domNode.loadXML(newXML_str,true,true) eliminates the attributes in domNode. A commenter in the above link states that it happens because the attribute is not stored in the data DOM as an attribute but rather as a child node with prefix '@' but if that were the case it would seem that saveXML should show it as a child element and not as an attribute. However, saveXML (as shown below) correctly shows the attribute as an attribute.
What I would like to happen is to have the child attribute node(s) preserved and the child element nodes replaced. It seems to me that if the second argument is true (ignore root element in xmlArg) then the root element in the data DOM (including attributes) should be unchanged but that is not what happens.
Here is some sample XML:
<docroot>
<contact uid="29033737">
<firstName>George</firstName>
<lastName>Sinkenschneider</lastName>
</contact>
</docroot>
Here's some JavaScript:
var domNode = xfa.resolveNode("xfa.data.docroot.contact.(uid.value=='29033737')");
var domNodeXML_str = domNode.saveXML();
console.println(" contact data node saveXML (domNode) = ".concat(domNodeXML_str));
console.println(" domNode.uid.value=".concat(domNode.uid.value));
var newXML_str = domNodeXML_str.replace("George", "Johnny");
console.println(" newXML_str = ".concat(newXML_str));
domNode.loadXML(newXML_str, true, true);
console.println(" DOM node after executing loadXML(newXML_str, true, true) = ".concat(domNode.saveXML()));
xfa.form.remerge();
Here's the console output from the script (including all the ugly line-feeds):
contact data node saveXML (domNode) = <?xml version="1.0" encoding="UTF-8"?>
<contact uid="29033737"
><firstName
>George</firstName
><lastName
>Sinkenschneider</lastName
></contact
>
domNode.uid.value=29033737
newXML_str = <?xml version="1.0" encoding="UTF-8"?>
<contact uid="29033737"
><firstName
>Johnny</firstName
><lastName
>Sinkenschneider</lastName
></contact
>
DOM node after executing loadXML(newXML_str, true, true) = <?xml version="1.0" encoding="UTF-8"?>
<contact
><firstName
>Johnny</firstName
><lastName
>Sinkenschneider</lastName
></contact
>
Note that the uid attribute is missing from the final DOM node.Looks like you may have found a bug .....If I append the new xml I see that the uid attribute is maintained (oit is not touching the root attribute). If I replace it then it seems that the attribute is ignored when the node is re-written. We will need to open a bug with support ...do you want to do that?
Paul
Maybe you are looking for
-
Rotation does not work correct after last update iOS 8
EVerything on the screen rotates with the Ipad except the icons of all my one hundred apps. After opening any app its content rotates, but after closing the icon of the app still has the wrong position. is this a bug And how I can fix it?
-
Obligatory Fields in Moule Pool
Hi all, My requirement is such that... I have created 2 radiobuttons in the selection screen When I select the 1st button, a particular field in the same screen should become obligatory and when I select the 2nd button another field should become obl
-
Are there any apps which helps resolving this? Say as for example it can turn my wiriting to some ascii text and then it becomes highly reusable. Advanced features can be that it understands drawings and convert them into separate jpegs which can be
-
Importing classes with embedded java
I have the following line of code: Element input = (Element)getVariableData("sourceString"); I'm trying to get the value the the variable 'sourceString' from the bpel process. When I try and compile I get the error: class bpel.testmq.Element not foun
-
How to implement H323 based VCS behind PIX 6.3
There are some articles talking about issue with H323 traffic passing through firewall.I have a client will deploy Polycom endpoint behind PIX 6.3,my question are 1. Should I do no-NAT or regular Static (inside,outside)? I saw some threads talking H3