Removing the dummy root element
Looks like I created a topic that cannot
be replied to! The topic maintainers will
have to delete it.
After looking at the XMLSample code I realized my mistake... oops!
A quick edit turned off the <root>
containment. Not sure why it's there in
the sample in the first place.
For anyone else who tries this, here's the
change to remove the dummy root element:
The new code in XMLSample.java is:
out.appendChild(result);
instead of:
// create a dummy document element for the
// output document
Element root = out.createElement("root");
out.appendChild(root);
// append the transformed tree to the dummy
// document element
root.appendChild(result);
null
Hi,
Please try deleting the xml files corresponding to the dimensions from the backend and try opening the dimension member sheet.
For deleting the XML file follow the workaround in my reply of the below thread,
Re: Master data issue in CV
Hope this helps,
Regards,
G.Vijaya Kumar
Similar Messages
-
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_SOAFirst 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. -
How do I remove the Adobe Premiere Elements Trail Version Sign from my video?
I'm making a video using the Adobe Premiere Elements, but they have a trail version logo across the screen so I cannot fully make a video without that showing. Is there any possible way that I can remove it? Thanks!
uggrrl
You cannot remove the Adobe watermark from an export of the Premiere Elements tryout, be it an export to file saved to the computer hard drive or a burn to disc.
But, you can remove the Adobe watermark from the Premiere Elements project file (known as the project.prel) after you purchase the program.
All you do is open the project file from the tryout in the purchase Premiere Elements and then....
a. In the opened project, go to Timeline Menu/and click on Delete Rendered Files
or
b. do nothing (some of us have found that the Adobe watermark automatically disappears from the tryout project file when that tryout project file in opened in the purchased Premiere Elements.
See which one works for you. The classical version of the how to is "a" above.
Looking forward to your results.
Thanks.
ATR -
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,
BorisHello 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 -
What to do when root element is a list?
Hi,
I've been looking at the PurchaseOrder examples and found them really useful and excellent for making a
start at XML DB. However, Ive run into a stumbling block when trying to use my own data
(but i've used the purchase order example below to make illustrating easier).
The problem is rather than have purchase orders in individual XML files,
i have a single file of a few hundred thousand purchase orders inside a parent tag of <PurchaseOrderList>
I can edit the XSD to add the following:
<xs:element name="PurchaseOrderList" xdb:defaultTable="PURCHORDERLIST" xdb:SQLType="PO_LIST_TYPE">
<xs:complexType>
<xs:sequence>
<xs:element name="PurchaseOrder" type="PurchaseOrderType" minOccurs="0" maxOccurs="unbounded" xdb:SQLCollType="PUR_ORDERS"/>
</xs:sequence>
</xs:complexType>
</xs:element>
And remove the line:
<xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
And sure enough, i can now load my <PurchaseOrderList> containing all the Purchase orders.
However, I dont really care about the PurchaseOrderList table, its only there because i dont want to have
to break up the list file into the individual entries. But when i load the data like this, as PurchaseOrder is
no longer the root table, I cant work out how to do simple things like select 1 Purchase order document or add
the unique ID constraint etc. (For instance if you load 100 entries in a list and do a select count from the
PURCHORDERLIST table, you get "1", which is correct, but not what Im after).
So, the essence of my question is if I have to load the data where the parent element is there to hold a list
of the "real" documents, how do i design my xsd and subsequent queries to make querying/indexing/retrieving the
data as easy as possible? Ideally I'd like the PurchaseOrder table back & for it to work in an identical way to that in the examples.....
Sorry if I've missed something very basic, but any help would be very gratefully appreciated...
LeeContinues [http://forums.sun.com/thread.jspa?threadID=5424890]
-
"root element is missing" - UTF-8
I have 2 identical files, except they are stored in ISO-8859-1 and UTF-8.
"Test ansii.xml":
<?xml version="1.0" encoding="ISO-8859-1"?><e></e>
"Test utf8.xml":
<?xml version="1.0" encoding="UTF-8"?><e></e>
When I look at them in Internet Explorer they show correctly. But when I parse them with SAX in java I get an error when I parse the file stored in UTF-8.
import java.io.*;
import javax.xml.parsers.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
public static void testXML(){
try{
File ansiiFile=new File("Test ansii.xml");
File utf8File=new File("Test utf8.xml");
SAXParserFactory factory = SAXParserFactory.newInstance();
SAXParser saxParser = factory.newSAXParser();
//try ISO-8859-1
InputSource in = new InputSource(new InputStreamReader(new FileInputStream(ansiiFile),"ISO-8859-1"));
saxParser.parse(in,new DefaultHandler());
//try UTF-8
in = new InputSource(new InputStreamReader(new FileInputStream(utf8File),"UTF-8"));
saxParser.parse(in,new DefaultHandler());
}catch(Exception e){
e.printStackTrace();
}The first file parses well, but when I parse the file encoded in UTF-8 I get this error:
org.xml.sax.SAXParseException: The Document root element is missing.
at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3170)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:501)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at test.Test.testXML(Test.java:44)
at test.Test.main(Test.java:25)
GilSigh, I found the answer.
http://www.i18ngurus.com/encyclopedia/byte_order_mark.html
byte order mark
Also known as BOM.
Name given to the Unicode character U+FEFF when used at the beginning of a Unicode byte stream. This invisible character generally know as ZERO WIDTH NO-BREAK SPACE (ZWNBSP) serves to identify unambiguously the Unicode transformation form used (and especially the byte order) for the stream. Indeed U+FFFE is a noncharacter so there is no risk of misinterpretation.
The following represents the byte signature of the character U+FEFF with the various Unicode Transformation Forms:
Bytes Encoding
00 00 FE FF UTF-32, big-endian
FF FE 00 00 UTF-32, little-endian
FE FF UTF-16, big-endian
FF FE UTF-16, little-endian
EF BB BF UTF-8
Historically the ZWNBSP was also used to indicate non-breaking but this use is now deprecated and replaced by the character U+2060 for that purpose.
http://p2p.wrox.com/archive/xslt/2002-11/79.asp
I suspect you edited the stylesheet using a text editor that inserts the
BOM at the start of the file. For example, I think Windows Notepad does
this.
Some XML parsers accept a BOM at the start of a UTF-8 file, others
don't. For example, the Crimson parser that comes with JDK 1.4 doesn't.
You basically need to find a text editor and an XML parser that agree
with each other about whether or not to use a byte order mark.
Alternatively, use a different encoding for the stylesheet, e.g.
iso-8859-1.
The code above found these strange bytes while expecting '<', and crashed of course.
Gil -
Root element required error in syndication
Hi,
We have added few new fields into the main table. Now accordingly we need to update the Oubound map to include these new fields. I have created a new XSD file having these new fields. But when I try to use this in syndicator to update, it throws me an error back saying "Root element required". I checked in SDN but couldnt find enough clues.
Any pointers will be highly appreciated.
Regards,
Ponraj MHello,
There are few possible root causes to this error appearing in MDM Syndicator:
1. This error indicates that the XSD is not valid as there is no declaration of the root element.
If you try to validate this XSD in XMLspy you will receive a similar error.
2. The XSD declares the root element but it does not appear in the XML.
If you validate the XML against the XSD in XMLspy you will receive a similar error.
3. An illegal character in the XSD root element declaration makes it impossible for Syndicator to detect it.
Please check these possible causes.
Best regards,
Hedda Cohen. -
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.......
-
Hi all,
JDeveloper 11.1.1.6.0
We're in the process of implementing a credit card processing page that will be performing a cross domain form action via jQuery or some other means. One of our primary requirements is to guarantee that form data on this page is not submitted to our server but we would like ADF to render the page to maintain a consistent look and feel for the site.
Would dropping the af:form element be an effective means of guaranteeing form data is not sent to our WLS server (via post, ajax, server side validation)? Any pitfalls?
Thanks!Hi,
removing the af:form element will not generate the HTML form element and this not submit anything to the server. So yes, this would work.
Frank -
How to customize (or remove) the documentviewer toolbar in code (no xml)?
Hi all,
I have a tab control that gets a new tab (with a documentviewer and a button) at runtime as the user selects items from a listbox. There is no xml for the new tabs ( but there is for the tabControl). The new tabs are generated at run time. After some
time I was able to put a couple of rows and have the button in the top row and the documentviewer on the bottom row. Now I'm thinking I want to get rid of the documentviewer toolbar but all examples I can find use xml. I also read that I need to change
the default template for the documentviewer... but again most stuff involves xml. So ... I'm thinking maybe I should modify the toolbar instead to include the button. But I'm not sure which way would be easier.
Comments welcome.
Thanks
private void myListbox_SelectionChanged(object sender, SelectionChangedEventArgs e)
if (myListbox.Items.Count > 0)
TabItem newTab = new TabItem();
newTab.Header = myListbox.SelectedValue.ToString();
Button closeButton = new Button();
closeButton.Content = "Close Report";
closeButton.Width = 105;
closeButton.Height = 25;
closeButton.Margin = new Thickness(50, 0, 50, 0);
closeButton.HorizontalAlignment = System.Windows.HorizontalAlignment.Right;
closeButton.VerticalAlignment = System.Windows.VerticalAlignment.Center;
closeButton.AddHandler(Button.ClickEvent, new RoutedEventHandler(closeButton_Click));
DocumentViewer mydoc = new DocumentViewer();
// Need to remove or modify documentViewer toolbar Grid myGrid = new Grid();
RowDefinition topRow = new RowDefinition();
RowDefinition bottomRow = new RowDefinition();
topRow.Height = new GridLength(5, GridUnitType.Star);
bottomRow.Height = new GridLength(95, GridUnitType.Star);
myGrid.RowDefinitions.Insert(myGrid.RowDefinitions.Count, topRow);
myGrid.RowDefinitions.Insert(myGrid.RowDefinitions.Count, bottomRow);
Grid.SetRow(closeButton, 0);
myGrid.Children.Add(closeButton);
Grid.SetRow(mydoc, 1);
myGrid.Children.Add(mydoc);
newTab.Content = myGrid;
mainTabcontrol.Items.Insert(mainTabcontrol.Items.Count, newTab);
private void closeButton_Click(object sender, RoutedEventArgs e)
TabItem tabToClose = new TabItem();
tabToClose = mainTabcontrol.SelectedItem as TabItem;
mainTabcontrol.Items.Remove(tabToClose);You could add a "dummy" DocumentViewer to your XAML, switch to design mode in Visual Studio 2012 or later, right-click on it and choose Edit Template->Edit a copy to copy the default template into your XAML and then modify it as per your requirements.
You can then remove the "dummy" control, but keep the generated style and assign the Style property of your DocumentViewer to this custom style at runtime:
DocumentViewer mydoc = new DocumentViewer();
mydoc.Style = this.Resources["DocumentViewerStyle1"] as Style;
//or mydoc.Style = Application.Current.Resources["DocumentViewerStyle1"] as Style;
Hiding/removing the Toolbar can be accomplished by setting the Visibility property of the first ContentControl in the default ControlTemplate to Collapsed:
<Window.Resources>
<Style x:Key="DocumentViewerStyle1" BasedOn="{x:Null}" TargetType="{x:Type DocumentViewer}">
<Setter Property="Foreground" Value="{DynamicResource {x:Static SystemColors.WindowTextBrushKey}}"/>
<Setter Property="Background" Value="{DynamicResource {x:Static SystemColors.ControlBrushKey}}"/>
<Setter Property="FocusVisualStyle" Value="{x:Null}"/>
<Setter Property="ContextMenu" Value="{DynamicResource {ComponentResourceKey ResourceId=PUIDocumentViewerContextMenu, TypeInTargetAssembly={x:Type Documents:PresentationUIStyleResources}}}"/>
<Setter Property="Template">
<Setter.Value>
<ControlTemplate TargetType="{x:Type DocumentViewer}">
<Border BorderBrush="{TemplateBinding BorderBrush}" BorderThickness="{TemplateBinding BorderThickness}" Focusable="False">
<Grid Background="{TemplateBinding Background}" KeyboardNavigation.TabNavigation="Local">
<Grid.ColumnDefinitions>
<ColumnDefinition Width="*"/>
</Grid.ColumnDefinitions>
<Grid.RowDefinitions>
<RowDefinition Height="Auto"/>
<RowDefinition Height="*"/>
<RowDefinition Height="Auto"/>
</Grid.RowDefinitions>
<ContentControl Visibility="Collapsed" Grid.Column="0" Focusable="{TemplateBinding Focusable}" Grid.Row="0" Style="{DynamicResource {ComponentResourceKey ResourceId=PUIDocumentViewerToolBarStyleKey, TypeInTargetAssembly={x:Type Documents:PresentationUIStyleResources}}}" TabIndex="0"/>
<ScrollViewer x:Name="PART_ContentHost" CanContentScroll="true" Grid.Column="0" Focusable="{TemplateBinding Focusable}" HorizontalScrollBarVisibility="Auto" IsTabStop="true" Grid.Row="1" TabIndex="1"/>
<DockPanel Grid.Row="1">
<FrameworkElement DockPanel.Dock="Right" Width="{DynamicResource {x:Static SystemParameters.VerticalScrollBarWidthKey}}"/>
<Rectangle Height="10" Visibility="Visible" VerticalAlignment="top">
<Rectangle.Fill>
<LinearGradientBrush EndPoint="0,1" StartPoint="0,0">
<LinearGradientBrush.GradientStops>
<GradientStopCollection>
<GradientStop Color="#66000000" Offset="0"/>
<GradientStop Color="Transparent" Offset="1"/>
</GradientStopCollection>
</LinearGradientBrush.GradientStops>
</LinearGradientBrush>
</Rectangle.Fill>
</Rectangle>
</DockPanel>
<ContentControl x:Name="PART_FindToolBarHost" Grid.Column="0" Focusable="{TemplateBinding Focusable}" Grid.Row="2" TabIndex="2"/>
</Grid>
</Border>
</ControlTemplate>
</Setter.Value>
</Setter>
</Style>
</Window.Resources>
If you just want to hide the Toolbar, you could do this programmatically by findind the ContentControl in the visual tree using a helper method like this:
private void myListbox_SelectionChanged(object sender, SelectionChangedEventArgs e)
DocumentViewer mydoc = new DocumentViewer();
mydoc.Loaded += (ss, ee) =>
ContentControl cc = FindVisualChildren<ContentControl>(mydoc).FirstOrDefault();
cc.Visibility = System.Windows.Visibility.Collapsed;
private static IEnumerable<T> FindVisualChildren<T>(DependencyObject depObj) where T : DependencyObject
if (depObj != null)
for (int i = 0; i < VisualTreeHelper.GetChildrenCount(depObj); i++)
DependencyObject child = VisualTreeHelper.GetChild(depObj, i);
if (child != null && child is T)
yield return (T)child;
foreach (T childOfChild in FindVisualChildren<T>(child))
yield return childOfChild;
If you want to do some more advanced customization, then use the XAML approach and edit the template accordingly.
Hope that helps.
Please remember to close your threads by marking helpful posts as answer and then start a new thread if you have a new question. Please don't post several questions in the same thread. -
Read XML response with multiple root elements
Hi ,
I am trying to achieve the below scenario but unable to do so.Please help urgently.
I am getting a response from a service which has multiple root elements.these root elements can change at runtime..I need to read the different root elements and extract data from its sub elements.
Regards...
Hoping for an anwser..i assume on runtime the service just returns 1 rootnode, but this rootnode can change
you could use a switch after the invoke
if $response/myroot1
assign $response/myroot to myroot1_var
if $response/myroot2
assign $response/myroot to myroot2_var
etc
so you check what's in the root node before you assign to you temp variable
or if you have logic which is specific based on this root nod you can just implement all these branches in the switch and execute logic in there based on the selected rootnode
several implementations are possible -
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. -
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. -
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
Maybe you are looking for
-
Can't add music to iTunes 11.0.2
Hey guys, I am using iTunes 11.0.2 on Windows 7 and I just recently purchased a new nano. When I went to go add some more music onto it tonight to my suprise nothing I selected would upload my iTunes library at all. I have tried restarting my compute
-
Why does ps ask for a serial number when I've joined creative cloud
I just joined creative cloud and downloaded PS. Why is it asking me for a serial number or use it as a trial? Shouldnt it recognize I've paid? Imac 27" Mavericks OS Rob
-
I recently turned my handwriting into a font that I want to use on my artist website. The font works just fine in photoshop but it is the ONLY font that isn't coming up in Muse. All of my other downloaded fonts are there, just not the one I want. How
-
Garageband - using apogee Jam and acoustic guitar sound
Hi I am trying to record an acoustic guitar on garageband (using my actual acoustic guitar), however the sound of the low strings sounds really muffled and low quality. i am using the built-in mic on my Mac to do this, not any external equipment. Is
-
How is it legal to sell itunes match
It has not worked for months and still apple sell it - Dick Turpin had nothing on Apple!!!!