No Swap root element options..
Hi,
I am trying to use Adobe Flash Island.. but when i right click on root element container i dont get option as Swap root element..
I also tried creating new element with Flash Island option...
I also cant find library stored in the MIME repository under SAP/PUBLIC/BC/UR/nw7/FlashIslands..
What configuatin are required to be done for using flash island in WebDynpro ABAP...
Regards,
Jigar OZa
To be able to work with Flex Island you need to install NW EHP1 for standalone Netweaver instances or EHP 4 for ERP 6.0 ( Still under ramp up - Target Release date AFAIK - 21st May 2009 ).
Regards
Rohit Chowdhary
Similar Messages
-
ECC 6.04 : missing 'swap root element' option
Hi Experts,
I've developped a WDA application with a Flex component using Adobe Flash Islands on our HR system (ECC 6.04 - NW 7.01). Everything works just fine on this system but now I'd like to copy this application to another system. The new system is also an ECC 6.04 - NW 7.01 system but I can't find the required 'swap root element' option to use Adobe Flash Islands. The Flash Islands libraries are in the MIME repository.
Do we have to activate something to use the new WDA functionalities?
Regards,
PierreHi,
My view was empty but the logon language wasn't english. Thanks!
Regards,
Pierre -
Flah Islands: missing SWAP ROOT ELEMENT
Hi All,
I have tired to recreate the tuotrial (pls see http://blip.tv/file/1417778) .
When I have rightclicked in the views ROOTELEMENTSCONTAINER in order to create a
SWAP ROOT ELEMENT i was suprised since this option did not exist in my system.
What can be the resason for it ? Maybe the system release ?
SAP_BASIS 700
Component version SAP ECC 6.0
Regards
ertasHi Mr. Jung
I am having a severe problem with my calculator
I have created a search help (freely programmed).
I have used this search help in another component. This search help is used at an input
field. It has the data type i (integer). But if I calculate with zeros and decimals I dont see
the complete result. I know this is because of the data type. But i also tried it with f .
It was not possible. in the search help i am using type numeric
Which data type can I choose.
method ONACTIONBUTTONPRESS .
DATA lo_nd_calculator TYPE REF TO if_wd_context_node.
DATA lo_el_calculator TYPE REF TO if_wd_context_element.
data lr_value type ref to data.
data l_string type c LENGTH 60.
data: val type string.
data l_binding_string type string.
lo_nd_calculator = wd_context->get_child_node( name = wd_this->wdctx_calculator ).
lo_el_calculator = lo_nd_calculator->get_element( ).
lr_value = lo_el_calculator->get_attribute_ref( WD_COMP_CONTROLLER->value_help_listener->f4_attribute_info-name ).
FIELD-SYMBOLS <wa_numeric> type numeric.
ASSIGN lr_value->* to <wa_numeric>.
val = wdevent->GET_string( 'ID' ).
CASE val.
WHEN 'BTN_1'.
IF WD_COMP_CONTROLLER->COMP EQ 'X'.
CLEAR: WD_COMP_CONTROLLER->erg, WD_COMP_CONTROLLER->merker, <wa_numeric>, l_string, WD_COMP_CONTROLLER->COMP.
ENDIF.
move <wa_numeric> to l_string.
CONCATENATE l_string `1` into l_string. CONDENSE l_string NO-GAPS.
<wa_numeric> = l_string.
endmethod. -
Org.xml.sax.SAXParseException: Document root element is missing.
Hi,
I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
I get this follwoing error
org.xml.sax.SAXParseException: Document root element is missing.
at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
at com.sun.xml.parser.Parser.parse(Parser.java:284)
at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
<May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
com.iplanet.portalserver.session.SessionException
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
Any help/pointers will be appreciated.
AshishJust for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
In this case, the XML file was created using a Microsft DOM (save).
My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
try {
// Open file for reading.
f = new File(path);
FileInputStream fis = new FileInputStream(f);
PushbackInputStream pis = new PushbackInputStream(fis);
byte[] buf = new byte[3];
pis.read(buf, 0, 3);
if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
pis.unread(buf, 0, 3);
builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
doc = builder.parse(pis);
catch (Exception x) {
x.printStackTrace();
} -
"Root element is missing." - While using Sharepoint List Source in SSIS.
Hi Team,
We are trying to import data from sharepoint list using sharepointlist source in SSIS. But the following error pops-up.
[SP_SRC_SharePointList [67]] Error: System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XElement.Parse(String text, LoadOptions options)
at System.Xml.Linq.XElement.Parse(String text)
at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
We are unable to debug / move any further. Request your help.
Thank you.
Best Regards,
GayathriIt appears that the XML you trying to load does indeed not have the root element.
E.g.
<?xml version="1.0" encoding="UTF-8"?>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>has nonemust be<?xml version="1.0" encoding="UTF-8"?>
<Root><iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii></Root>
Arthur My Blog -
hi All,
I am currently working with MDM Syndicator.
My problem is about Root element
when i am opening in the syndicator file-->destination properties
it will open dialog box with the following options, (i.e. type,Remote system,port,xml schema,xml file name,Root.
when i am selecting type as xml schema , romote system(i.e which i have declared in console for that repository). but when i click on OK button.
it is asking for the Root element required.
can any one help me about:
1)what is root element?
2)where we can declare root element and where we can use it in syndicator?
3)what actually Root element holds in it?
can any please provide answers to this questions
thanks in Advance
Bharat.chinthapatlaHi Michael,
Thanks for your reply for the pervious question Michael.
But.................?
My Problem is..........
Under Admin in console i have selected XML Schema table and i have created one record with Name as "xml schema file one" and in the filename field i have clicked on the browse button and selected one .xsd file in the repository.
(i have tried with .xml schema file also but not....)
I have opened the syndicator on that particular repository and in the source item i am able to see the table and fields of that particular repository and i have clicked on the file option and i have choosen "Destination properties" it has opened dialog box with different input fields, there i have selected type as "xml schema" and Remote system " MDM "(default). when i selected type as xml schema automatically xml schema input field is enabled and it as shown all the xml schema files or record which i have created in the XML schema table under Admin of the console.
But Root element is not enabled, what i have to do?
In the previous question you have said like this " <b>you have to add an XML Schema to your repository using the <u>corresponding branch</u> in the Console Admin menu</b>.
what is the corresponding branch in the console Admin menu, can you please explain me in details...
if there is any other procedure to come out of this problem, can you please explain me in details ?
Thanks in advance
bharat.chinthapatla -
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 advanceThose 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.
-
Textframe Associated with Root element
Hi,
I want to add a Processing Instructions before the first character of any TextFrame. (This is pure xml workflow)
InterfacePtr<IIDXMLElement> root_elt (Utils<IXMLUtils>()->QueryRootElement(doc));
From this 'root_elt' how can i find the Associated TextFrame?. I have planned to go iteratively using TextFrame threads.
Thanks in advance.
Saravanan.KThe root element of an InDesign document can't be associated with a text box. It represents the entire document, any story you tag will be a child of this element. Take a look at IXMLHandler. The other option you have it to post process the XML document after the InDesign export finishes, i.e re-parsing / re-writting it.
-
How to use SAX Parseto paser xml without root element
Hello,
I have big a xml file(500M) with without root element. How can I use SAXParse to parse it.A well-formed XML file has a single root element. Your parser can't deal with any other kind. So find the person who produced that file and explain politely that it's no good. (Hitting them with a big stick would be optional.)
You could write a non-XML program that reads it in and creates a new version, wrapped in a single root element, if your supplier can't fix their problem. -
Connect by query, need root element for each row
Hi,
I am working on a hierarchical query, using connect by prior. Each node in the tree has two properties, an type and a sequence.
The table that contains the hierarchy has 4 fields:
element_type_from
element_sequence_from
element_type_to
element_sequence_to
Each child has one parent, a parent can have multiple childeren. For a leaf, the fields element_type_to and element_sequence_to are null.
To generate a tree you can run:
select element_type_to
, element_sequence_to
from element_hierarchy
start with element_type_from = [root_element_type]
and element_sequence_from = [root_element_sequence]
connect by prior element_type_to = element_type_from
and prior element_sequence_to = element_sequence_fromThat works fine... however... not only do I want the child elements, I would like to return the root element sequence for each child (in our table the root element type is always the same). There are multiple root elements and I want to create a list containing all trees and each node in the tree must have its root as well.
There is the option of using sys_connect_by_path. This returns the root, but also the entire path to the current child. Also it returns a varchar2, that needs to be substr-ed and to_number-ed to get to the sequence... not nice.
warning, extremely ugly (but functional) code:
select element_type_to
, element_sequence_to
, to_number(substr(sys_connect_by_path(element_sequence_from ,','),2,instr(sys_connect_by_path(element_sequence_from ,',') ||',',',',2)-2)) root_sequence
from element_hierarchy
start with element_type_from = [root_element_type]
and element_sequence_from = ( select [root_element_sequence] from all_root_elements )
connect by prior element_type_to = element_type_from
and prior element_sequence_to = element_sequence_fromThere has to be a simple solution that I am missing here! Can you help?
Edit: Oops, database version is 10.2.0.4.0Hi,
What you posted was actually the best way to do it in Oracle 9.
Since you're using Oracle 10, you can use CONNECT_BY_ROOT, as William said:
select element_type_to
, element_sequence_to
, connect_by_root element_sequence_from AS root_sequence -- Changed
from element_hierarchy
start with element_type_from = [root_element_type]
and element_sequence_from = ( select [root_element_sequence] from all_root_elements )
connect by prior element_type_to = element_type_from
and prior element_sequence_to = element_sequence_from
I hope this answers your question.
If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, and the results you want from that data.
Explain how you get those results from that data. -
I am having some trouble unmarshalling an xml document using JAXB 1.0. I am getting the error unexpected root element. Can someone please tell me what causes this? The root element of the document I'm trying to unmarshall matches the schema root element. I have exhausted all resources, and have hit a wall. Please help. I can post the source code, schema and xml document at your request.
Thank you.Thank you for you reply. Here is all the info below:
schema file:
<?xml version="1.0"?>
<!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Henry C. Octapod (Obermeyer's Insurance) -->
<xs:schema targetNamespace="schemas/v1.01/TIMA_REQUEST.xsd" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:TIMA_XML="schemas/v1.01/TIMA_REQUEST.xsd" elementFormDefault="qualified" id="TIMA_REQUEST">
<xs:element name="TIMAREQUEST">
<xs:annotation>
<xs:documentation>The Root element for all TIMA requests and responses. Contains the TIMA_XML_VERSION attribute, which, must be set to teh release version of the Schema in use (Currently "1.1")</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="REQUEST_INFO">
<xs:annotation>
<xs:documentation>This element contains all the basic information about the request itself, such as the subscriber, any inventory items requested and their type, etc.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SUBSCRIBER" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>The unique TIMA Subscriber ID of the subscriber making this request.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="INVENTORY_ITEM" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>One(1) or more elements containing the TIMA Inventory Item IDs and TIMA Inventory Type Codes representing one or more Inventory items to be processed for this request. This element may also contain subscriber supplied "SUPPLIER" elements for use in filtering the rates returned.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SUPPLIER" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>0 or more supplier tags. The SUPPLIER element is use to normalize between the TIMA ID and the Supplier's UNIQUE ID and is optional for the Subscriber. If the subscriber chooses to, they may include the SUPPLIER elements as part of their request. The TIMA system will then use the EXCLUDED attribute to control which suppliers to request. inventory from.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="INVENTORY_ID" type="xs:string" form="unqualified">
<xs:annotation>
<xs:documentation>The Unique ID of this Inventory Item, in the Supplier's System (See "SUPPLIER_ID" below). </xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="EXCLUDED" type="xs:boolean" use="optional" form="unqualified">
<xs:annotation>
<xs:documentation>True/False. Whether or not to exclude this supplier, for this property.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="SUPPLIER_ID" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>The Unique TIMA Member ID of the supplier to whom this inventory ID belongs.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="CODE" type="xs:string" form="unqualified">
<xs:annotation>
<xs:documentation>The Unique TIMA ID of the inventory Item</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="INVENTORY_TYPE" type="xs:integer">
<xs:annotation>
<xs:documentation>Integer value specifing what type of inventory which is being requested. For example, if a subscriber seeks hotel rooms then they would use "2" .</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="REQUEST_TYPE" type="xs:string">
<xs:annotation>
<xs:documentation>A String containing the type of transaction to be processed. See Appendix "Transaction Types")</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="REQUEST_DATA">
<xs:annotation>
<xs:documentation>Contains all sub-elements which define this request's data.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="CANCEL_INFO" minOccurs="0">
<xs:annotation>
<xs:documentation>The element used in all transaction cancellation requests. This element is dependent on information previously aqueired from a succesful ORDER_ITEM transaction.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="TIMA_TRANSACTION_ID" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>TIMA TransactionID as returned in the TRANSACTION_DATA element by a successful ORDER_ITEM transaction. </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CONFIRMATION_CODE" type="xs:positiveInteger">
<xs:annotation>
<xs:documentation>Confirmation code as returned in the TRANSACTION_DATA element by a successful ORDER_ITEM transaction. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ORDER_INFO" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>The Root element for all transactions requesting rates or booking. This element always contains the Custom element for the inventory type.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="HOTEL_INFO" minOccurs="0">
<xs:annotation>
<xs:documentation>Custome Element for inventory type two (2). The Hotel Info Element. Used when requesting information about hotel rates and availability.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="RATE_CODE" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>(optional) Supplier-Specific code for this room and rate. As returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="INDATE" type="xs:date" minOccurs="0">
<xs:annotation>
<xs:documentation>The checkin date requested for this transaction.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OUTDATE" type="xs:date" minOccurs="0">
<xs:annotation>
<xs:documentation>The checkout date requested for this transaction.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ROOMS" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of rooms requested in this transaction.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ADULTS" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of adults requested in this transaction.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CHILDREN" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>Number of children included in this stay.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NATIVE_CURRENCY" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The native currency code of the supplier or inventory locations (such as a Hotel in France). </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SMOKING" type="xs:boolean" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>True/False. Does the guest want a smoking room(s)</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="GUEST" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>One(1) to ADULTS guest elements. The first GUEST element will usually be the same as the PAYMENT_DATA (FIRST_NAME, LAST_NAME)</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="GUEST_REQUESTS" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Any specific requests the guest would like to make. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="FIRST_NAME" type="xs:string" use="required"/>
<xs:attribute name="LAST_NAME" type="xs:string" use="required"/>
<xs:attribute name="INITIAL" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="PAYMENT_DATA" minOccurs="0">
<xs:annotation>
<xs:documentation>Element Containing all the credit card information neccesary to complete the transaction. USED ONLY FOR THE ORDER_ITEM REQUEST.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="FIRST_NAME" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>First name of the payee as listed on the credit card.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="LAST_NAME" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Last name of the payee as listed on the credit card.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_ADDRESS" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Striing containg payee's Address. May be multiple lines (sepreated by CR/LF).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_CITY" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Striing containg payee's address-city name.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_STATE" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Striing containg payee's two(2) leter state code or Province name (US or international).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_COUNTRY" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Striing containg payee's country code.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_ZIP" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Striing containg payee's zip or postal code (US or international).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BILL_PHONE" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Contact Phone for the payee (credit card holder). </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CREDIT_CARD_TYPE" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The two (2) letter Credit Card Code (see appendix) specifying the type of card used for payment.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CREDIT_NUMBER" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The Credit Card Number on the payee's credit card.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CREDIT_EXPIRE_MONTH" type="xs:gMonth" minOccurs="0">
<xs:annotation>
<xs:documentation>The expiration month on the payee's credit card.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CREDIT_EXPIRE_YEAR" type="xs:gYear" minOccurs="0">
<xs:annotation>
<xs:documentation>The expiration year on the payee's credit card.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="TRANSACTION_DATA">
<xs:annotation>
<xs:documentation>Information used to inform the TIMA system about the transaction being requested, or in the case of a successful response message, the amounts actually charged.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="DATETIMESTAMP" type="xs:dateTime" minOccurs="0">
<xs:annotation>
<xs:documentation>Datetime stamp indicating the subscriber's time the transaction was submitted.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NATIVE_CURRENCY" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The native currency code of the supplier or inventory locations (such as a Hotel in France). </xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="PAYMENT_CURRENCY" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>The currency code in which the payment should be made. For versions 1.1 and below, this value is always "USD".</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="WHOLESALE_RATE" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>The rate/cost at which the supplier has aquired the inventory as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="RESALE_RATE" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>The Displayable retail rate or cost for the transaction as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="GROSS_SALE" type="xs:double" minOccurs="0">
<xs:annotation>
<xs:documentation>This is the retail rate including any supplier taxes and/or fees as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FEES" type="xs:double" minOccurs="0" msdata:Caption="Any Fees for this request, as returned by the supplier's reply to the REQUEST_RATE_COST_DETAILS transaction.">
<xs:annotation>
<xs:documentation>Total supplier fees for the ORDER_ITEM transaction as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TAXES" type="xs:double" minOccurs="0" msdata:Caption="Any Taxes for this request, as returned by the supplier's reply to the REQUEST_RATE_COST_DETAILS transaction.">
<xs:annotation>
<xs:documentation>Total supplier taxes for the ORDER_ITEM transaction as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="CANCELLATION_POLICY" type="xs:string" minOccurs="0" msdata:Caption="String containing the Cancellation Policy as defined by the Supplier Reply to REQUEST_RATE_COST_DETAILS">
<xs:annotation>
<xs:documentation>String containing the cancellation policy as returned from the supplier in the REQUEST_RATE_DETAILS response.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SUBSCRIBER_CHARGE" type="xs:double" minOccurs="0" msdata:Caption="Any additional fees the subscriber would like to add to the ORDER_ITEM Transaction">
<xs:annotation>
<xs:documentation>USD Monentary value of any additional charges the subscriber would like to add to an ORDER_ITEM request.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="TIMA_XML_VERSION" type="xs:string" use="required" form="unqualified">
<xs:annotation>
<xs:documentation>TIMA XML Schema Version.. Curently: "1.1"</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:schema>
xml input file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TIMAREQUEST TIMA_XML_VERSION="1.1" xmlns:ns1="schemas/v1.01/TIMA_REQUEST.xsd">
<REQUEST_INFO REQUEST_TYPE="2">
<SUBSCRIBER>7</SUBSCRIBER>
<INVENTORY_ITEM INVENTORY_TYPE="2" CODE="123"/>
</REQUEST_INFO>
<REQUEST_DATA>
<ORDER_INFO>
<HOTEL_INFO>
<INDATE>2003-03-11</INDATE>
<OUTDATE>2003-03-11</OUTDATE>
<ROOMS>3</ROOMS>
<ADULTS>2</ADULTS>
<CHILDREN>1</CHILDREN>
</HOTEL_INFO>
<TRANSACTION_DATA/>
</ORDER_INFO>
</REQUEST_DATA>
</TIMAREQUEST>
test program:
package test;
* Test.java
* Version information
* Mar 11, 2003 5:36:46 PM
* Copyright notice
* @author cboyd
* @version
public class Test extends TestCase {
* Constructor for Test.
* @param arg0
public Test(String arg0) {
super(arg0);
public void testUnmarshall() {
try {
JAXBContext context = JAXBContext.newInstance("test");
Unmarshaller unmarshaller = context.createUnmarshaller();
unmarshaller.unmarshal(new java.io.FileInputStream("TIMAREQUEST.xml"));
} catch (JAXBException e) {
fail("failed to unmarshall: " + e.getMessage());
} catch (Throwable e) {
fail("failed to unmarshall: " + e.getMessage());
Thank you. -
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 -
I have just downloaded a trial version of Photoshop Elements onto my Mac Book Pro (10.9.4). The installation to my hard drive went fine so I attempted to use Elements on an existing Photoshop file. I did not see the Elements option in my filter menu and am uncertain as to how to "add" the Elemnts to my existing filter choices. Please advise.
I'm sorry but it's very hard to understand what you mean. What filter menu? In which program? Do you mean you're trying to use PSE as an external editor with some other asset management program? Which one?
-
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
Maybe you are looking for
-
Frustrations Trying to Install CF 9 on Windows 7/IIS 7
I am trying to install CF 9 (as a Developer Install) on Windows 7 Pro/32-bit and am going crazy. My box is running IIS7 and the CF install goes OK (I have it set to configure for all IIS sites). When I try to launch Administrator at the end of the in
-
Photoshop elements won't switch to the editor workspace from the organizer.
I can't edit more than one photograph per session when using Photoshop Elements 10. When I first open up the organizer, I can select a photograph for editing and send it to the editing workspace. However, when I try to edit a second photograph in the
-
Can't remember security answers
I have just upgraded to a new iPad and iTunes won't allow me to purchase an app without answering security questions. I have never provided any info and have no idea on the answers. How can I access my ITunes Store or provide answers to new security
-
Is it possible to run a form offline (in the background)..?
Is it possible to run a form offline (in the background) by passing all the required parameters? I know this sounds crazy...but like to know if a form can be run in silent mode. This will help us in reusing the form for online and background processi
-
Adding third party video card to P700 - no power connectors? New Power Supply Question...
Hello, I have a new P700 30A90012US with a 650W PSU and that didn't come with a video card. I am planning to use it as a DAW and for occasional gaming via a dual boot. I wanted to put in a third party video card like a nVidea 970 but there aren't ANY