Using # in element name
Hi,
How can i use special character like # in the element name.I have a element which has name like 'abc#'.I am getting the following error in xml spy if i try to use it.
Value 'abc#' is not allowed for attribute 'name'.
Hint: A valid value would be 'NCName'.
Error location: schema / element / complexType / sequence / element / @name
How can i handle this.
Thanks
Back to basics...
http://www.w3.org/TR/REC-xml/#NT-NameStartChar
gives allowed characters for an Attribute name.
Similar Messages
-
Dynamically Using XML Element name as column names
I have a requirement where I need to show data for 31 days or days of the month based on the data in the xml result.
Based on the month you are running the report, some may have 28 elements and some may have 31 elements in the data for days.
How do I dynamically show 28 columns or 31 columns etc - the trick here is I have to use the name of the XML element and not the value for column names.
My requirement is like this.
Deal --------01 -------- 02 -------- 03 -------- 04 05 .upto ... 31days
Deal 1 : 22218 : 32218 : 11918
Deal 2 : Qty1 : Qty2 : Qty3
I need to be able to use the XML Element names , Day01, Day02 etc as the column names in the report.
How can I use the XML Element name - in this case I need to remove the "Day" and use just the number part for the column name.
I can't have xml element names as numbers, thats why "Day" string is prefixed.
<Row state="">
<DEAL>Deal 1</DEAL>
<PORTFOLIO>AM ST Prod PDP</PORTFOLIO>
<CPTY>DTEGO</CPTY>
<FACILITY>MICHCON</FACILITY>
<POINT>100013 : Chestonia 17-Rec</POINT>
<TYPE>Purchase</TYPE>
<Day01>22218</Day01>
<Day02>32218</Day02>
<Day03>11918</Day03>
<Day04>11918</Day04>
<Day05>11918</Day05>
<Day06>11918</Day06>
<Day07>11918</Day07>
<Day08>11918</Day08>
<Day09>11918</Day09>
<Day10>11918</Day10>
<Day11>11918</Day11>
<Day12>23238</Day12>
<Day13>11918</Day13>
<Day14>11918</Day14>
<Day15>11918</Day15>
<Day16>32328</Day16>
<Day17>11918</Day17>
<Day18>11918</Day18>
<Day19>11918</Day19>
<Day20>11918</Day20>
<Day21>11918</Day21>
<Day22>11918</Day22>
<Day23>11918</Day23>
<Day24>11918</Day24>
<Day25>11918</Day25>
<Day26>11918</Day26>
<Day27>13511</Day27>
<Day28>13550</Day28>
<Day29>13550</Day29>
<Day30>13550</Day30>
</Row>I have a requirement where I need to show data for 31 days or days of the month based on the data in the xml result.
Based on the month you are running the report, some may have 28 elements and some may have 31 elements in the data for days.
How do I dynamically show 28 columns or 31 columns etc - the trick here is I have to use the name of the XML element and not the value for column names.
My requirement is like this.
Deal --------01 -------- 02 -------- 03 -------- 04 05 .upto ... 31days
Deal 1 : 22218 : 32218 : 11918
Deal 2 : Qty1 : Qty2 : Qty3
I need to be able to use the XML Element names , Day01, Day02 etc as the column names in the report.
How can I use the XML Element name - in this case I need to remove the "Day" and use just the number part for the column name.
I can't have xml element names as numbers, thats why "Day" string is prefixed.
<Row state="">
<DEAL>Deal 1</DEAL>
<PORTFOLIO>AM ST Prod PDP</PORTFOLIO>
<CPTY>DTEGO</CPTY>
<FACILITY>MICHCON</FACILITY>
<POINT>100013 : Chestonia 17-Rec</POINT>
<TYPE>Purchase</TYPE>
<Day01>22218</Day01>
<Day02>32218</Day02>
<Day03>11918</Day03>
<Day04>11918</Day04>
<Day05>11918</Day05>
<Day06>11918</Day06>
<Day07>11918</Day07>
<Day08>11918</Day08>
<Day09>11918</Day09>
<Day10>11918</Day10>
<Day11>11918</Day11>
<Day12>23238</Day12>
<Day13>11918</Day13>
<Day14>11918</Day14>
<Day15>11918</Day15>
<Day16>32328</Day16>
<Day17>11918</Day17>
<Day18>11918</Day18>
<Day19>11918</Day19>
<Day20>11918</Day20>
<Day21>11918</Day21>
<Day22>11918</Day22>
<Day23>11918</Day23>
<Day24>11918</Day24>
<Day25>11918</Day25>
<Day26>11918</Day26>
<Day27>13511</Day27>
<Day28>13550</Day28>
<Day29>13550</Day29>
<Day30>13550</Day30>
</Row> -
Dynamic Columns, using the element name as the column header name
BI Publisher Experts,
I'm a relative newbie in the RTF layout world and i'm trying to acheive a layout which dynamically nominates the column headers as the element name.
For example using the XML below:
<?xml version="1.0" encoding="UTF-8" ?>
- <ROWSET>
- <DATA>
- <THREECOLUMNDATA>
<FIRST_NAME>First Name</FIRST_NAME>
<LAST_NAME>Last Name</LAST_NAME>
<EMAIL>[email protected]</EMAIL>
</THREECOLUMNDATA>
</DATA>
</ROWSET>
Excuse formatting, looked ok in preview!
I'd like to acheive the following output:
| FIRST_NAME | LAST_NAME | EMAIL |
|-----------------------|---------------------- |--------------------------------------------------------|
| First Name | Last Name | [email protected] |
I've managed to get the row data columns working using:
<?for-each@cell:current()/*?><?.?><?parent::*/text()?> <?end for-each?>
And i've been working on the header for a while now, using
<?for-each@column:current()/THREECOLUMNDATA[1]/*?><?name(.)?><?end for-each?>
But no luck with the header. I only ever get a blank header.
I've also reviewed the following syntax:
<?split-column-header:THREECOLUMNDATA?> <?/FIRST_NAME?>
But of course, this pulls specific element data out as the header, not quite what I need.
Question is: Is there specific functionality to pull the element name out as the header, or do I somehow specifically need to include the header name as a data value in the XML?
Advice appreciated!If you could get your XML to look like this instead of what you have, you will be able to use split-column-header and split-column-data
<?xml version="1.0" encoding="UTF-8" ?>
<ROWSET>
<DATA>
<THREECOLUMNDATA>
<COL_DTLS>
<COL_LABEL>FIRST_NAME</COL_LABEL>
<COL_VALUE>First Name</COL_VALUE>
</COL_DTLS>
<COL_DTLS>
<COL_LABEL>LAST_NAME</COL_LABEL>
<COL_VALUE>Last Name</COL_VALUE>
</COL_DTLS>
<COL_DTLS>
<COL_LABEL>EMAIL</COL_LABEL>
<COL_VALUE>[email protected]</COL_VALUE>
</COL_DTLS>
</THREECOLUMNDATA>
</DATA>
</ROWSET>
Now if you <?split-column-header:COL_DTLS?><?COL_LABEL?> and <?split-column-data:COL_DTLS?><?COL_VALUE?> you'll get the required output... -
Element name too long when using ROWTYPE
I've come across an issue with xml element names longer than 30 characters. Seems it has something to do with ROWTYPE. Creation of this function is successful:
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL.dummy%TYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
However, specifying the variable as ROWTYPE gives ORA-00972 error (unless I shorten the element name...):
<pre>
CREATE OR REPLACE FUNCTION test_fnc
RETURN XMLTYPE
AS
var_return XMLTYPE;
l_dummy DUAL%ROWTYPE;
BEGIN
SELECT dummy INTO l_dummy FROM DUAL;
SELECT XMLCONCAT(XMLELEMENT (
"TEST",
XMLFOREST (
l_dummy.dummy "THIS_IS_OVER_30_CHARACTERS_LONG"
data_set
INTO var_return
FROM DUAL;
RETURN var_return;
END test_fnc;
</pre>
Has anyone come across this before, or have any ideas for a solution? I could specify all my variables as TYPE but as there are many within the tables it would be easier to use ROWTYPE.
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
Thanks.it works if you add "AS" after l_dummy.dummy
SQL> CREATE OR REPLACE FUNCTION test_fnc
2 RETURN XMLTYPE
3 AS
4 var_return XMLTYPE;
5 l_dummy DUAL%ROWTYPE;
6 BEGIN
7 SELECT dummy INTO l_dummy FROM DUAL;
8
9 SELECT XMLCONCAT(XMLELEMENT (
10 "TEST",
11 XMLFOREST (
12 l_dummy.dummy AS "THIS_IS_OVER_30_CHARACTERS_LONG"
13 )
14 ))
15 data_set
16 INTO var_return
17 FROM DUAL;
18 RETURN var_return;
19 END test_fnc;
20 /
Function created.Ants -
Autotyping not preserving XML element names for use in Web service
I am trying to generate a web service from an existing WSDL (ServiceOrderingContract.wsdl,
attached). The WSDL contains as a message part with an element dsl_FirmOrderProvideRequest.
Autotyping produces a corresponding class DSLFirmOrderProvideRequest. I use the
output of autotyping to implement a web service corresponding to this WSDL. I
then deploy this web service. The WSDL of the DEPLOYED webservice now has a message
part with an element DSLFirmOrderProvideRequest, per the autotype, but in mismatch
with the source WSDL. Of course, the clientgen from the source WSDL wont work
against the latter deployed WSDL.
Something is changing dsl_ to DSL in the autotyping process. Is this a bug? Or
am I doing something wrong? Is there any option in autotype task to preserve element
names?
Thanks a lot.Hello,
Take a look at the docs on roundtripping generated data types [1]
Regards,
Bruce
[1]
http://edocs.bea.com/wls/docs81/webserv/assemble.html#1074725
Suteertha wrote:
>
This is in basic WLS 8.1 SP2. -
How to use '*' character in element names ?
Hi,
I have to use '*' character in element names. But, it throws DOMException. is there a workaround to use such illegal characters ?
thanks in advance...No, there is no work around as such. The '*' character is not a legal character in a tag name (it means zero or more in DTD content specifications).
http://www.w3.org/TR/2004/REC-xml-20040204/#NT-Name
What does the star mean? Replace it with something more meaningful. The closest thing to a work around is using "-star-", but then you have to replace dash with "-dash-" and it all gets a bit silly, and won't really add meaning to the tagname.
Pete -
Automatically using a file name as a caption in Adobe Photoshop Elements 8
Hello!
I am trying to import a group of photos that have file names which describe the photo. Is there a way for PSE to automatically caption imported images using the file name as a caption?Buy PSE9 or wait another month or two and buy PSE10 when it comes out.
-
When I am using Premiere Elements 13 I get a message that pops up "There is no disk in the drive" I click on it and it keeps coming back "very annoying", but about three months ago it happened to me and I was told to change the file name from OldFilm.AEX to OldFilm.AEXold. Well now the file is back in Folder OldFilm.AEX. Here is a screen shot the files are highlighted.What should I do now to correct this once and for all, or can I? Thank you for your time.
TomWolves
I would do another rename to disable or just delete all the OldFilm.AEX and OldFilm.AEXOLD in that NewBlue Folder.
If you do, please let me know if that OldFilm.AEX regenerates itself the next time you open Premiere Elements 13.
Here is the strange story...at least from my Premiere Elements 13 Windows perspective...never had the No Disc error issue
Here are some details to sort through trying to figure out why you have 2 OldFilm.AEX file in the NewBlue Folder.
1. The original OldFilm.AEX file of Premiere Elements 13 has the date of 9/4/2014 (just before the version was released on 9/24/2014).
After the 13.1 update is done (whenever date), that OldFilm.AEX file has the date of 1/31/2015. I first saw notification of the 13.1 Update
release early in February 2015.
2. Now in Premiere Elements 13.1, if I take my OldFilm.AEX (date 1/31/2015) and disable it by renaming it to OldFilm.AEXOLD, close out of there, and reopen
the program, the OldFilm.AEX is not seen to regenerate. The OldFilm.AEXOLD remains there as its lone self.
3. So, I am thinking that your OldFilm.AEXOLD in the screenshoot is "original equipment" that you disabled to get rid of No disc error.
Why the OldFilm.AEX is there also is not clear, but the dating on it suggests that it came along with the 13.1 Update.
Bottom line: let us try the deletion or disabling one more time and see what happens.
Looking forward to further reports on your findings, as your time permits.
Thanks.
ATR -
Cannot use duplicate table name error in AMDP
Hi Experts,
I'm developing an application which has the following architecture
SAP UI5->Gateway->ABAP Managed DB procedures(AMDP)->HANA SP(Stored Procedure)
We are having a very peculiar problem where the gateway service works inconsistently for the same input data.
i.e If I execute the same service n number of times, I get the results successfully for say n-3 times but the other 3 times I get a "RFC Error :Error while executing Database procedure"
There is no change in the input data or DB table data during all the executions.
Running the stored procedure stand alone in HANA studio works all the time.
We tried executing the AMDP from SE24 and the same behavior occurred.
When trouble shooting we found that the exception occurs inside the AMDP when the call db procedure statement is executed.
Could you please advise what could be the possible reason for this any tuning parameter/unavailability of db connections?
Or could you please suggest some other troubleshooting mechanism by which we can zero in on the cause?
When I go in the debug mode I can see the exact error as
cannot use duplicate table name: [288] SAPXXX.ZCL_PLAN_MAINTENANCE=>GET_COMP_TYPE#stub#20140905055908: line 15 col 3 (at pos 492): cannot use duplicate table name exception:
where ZCL_PLAN_MAINTENANCE=>GET_COMP_TYPE is the AMDP class and method. SAPXXXis the schema.I reported this to Adobe customer support on 11/29, and here is their response:
Wednesday, December 5, 2007 12:51:27 PM PST
Hello John,
Thank you for contacting Adobe® Web Support for assistance with Adobe
Photoshop Elements® 6.0.
I understand that images are deleted if you accidentally try to move
them to a folder that already includes a file of the same name.
Thank you for bringing this to our attention. I was able to replicate
this behavior as well. The best method to report errors of this nature
is using the following form on our website:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I will report this to the product team through my channels. You may want to submit this issue through the web form as it goes directly to the product development team.
I hope this information helps to resolve your issue. If you require
further assistance with this issue, please update your web case with
complete details, including what steps you have applied and any error
messages you are receiving.
You may also call Technical Support at (800) 642-3623. We are available from 6:00 am to 5:00 pm Monday - Friday, Pacific Time.
Kind regards,
Alan C.
Adobe Web Support -
XML element names required in lower case
Hi,
I am on release 4.6C
I create an XML file from internal table using FM SDIXML_DATA_TO_DOM and SDIXML_DOM_TO_XML.
The internal table is defined such that the fieldnames of internal table are same as element names in XML file.
The XML file gets created properly, but the element names appear in upper case.
The requirement is to have it in lower case.
Does anybody have any idea about how to control the case here?Hi Sudhir
you can convert field names manually using translate command to convert it to lower case.
hope this helps. -
Simple Transformation with very long XML element names
I am trying to write a program to deserialize XML documents using the Simple Transformation technique. There are many optional elements in the XML document, so I need to have conditional statements statements to avoid trying to process elements that are not in the document. The XML document, however, has several Element Names that are greater than 30 characters in length. The Simple Transformation technique seems to require ABAP data dictionary structures that mirror the schema of the XML document. But one cannot create structure component names that are greater than 30 characters in length. We don't have any control over the XML schema as the XML documents come from the US government. The ST fragment below shows the statement that I want to write, but since the ABAP Structure PlasticCardInformationGroup cannot have a component AuthorizationResponseInformation, the ST syntax checker yields an "Illegal Reference ADDITIONALPLASTICCARDINFORMATION" error message.
Does anyone know a way to avoid this error?
<tt:d-cond check="exist(TRS_TradingPartner_Agreement.TRS_FinancialTransaction.PlasticCardInformationGroup.AdditionalPlasticCardInformation)">
<ns2:AdditionalPlasticCardInformation>
<tt:attribute name="CardNetworkType" value-ref="TRS_TRADINGPARTNER_AGREEMENT.TRS_FINANCIALTRANSACTION.PLASTICCARDINFORMATIONGROUP.ADDITIONALPLASTICCARDINFORMATI.CARDNETWORKTYPE"/>
<tt:attribute name="DraftLocatorNumber" value-ref="TRS_TRADINGPARTNER_AGREEMENT.TRS_FINANCIALTRANSACTION.PLASTICCARDINFORMATIONGROUP.ADDITIONALPLASTICCARDINFORMATI.DRAFTLOCATORNUMBER"/>
</ns2:AdditionalPlasticCardInformation>could anyone help me?
-
Specifying Case-Insensitive Element Names in XML Schema
Hope someone knows this!
Is it possible to define an an XML Schema Definition so that Element names in the target XML File can be case insensitive.
At the moment my Parser throws an error if the element names in the XML file do not have the exact same case as the definition in the XML schema.
E.g
In Schema i have:
<xsd:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" maxOccurs="unbounded" minOccurs="0"/>
but in xml file i have
<HostInventoryLine field=""/>
or
<hostinventoryline field=""/>
Does anyone know anyway to get around this, so that the parser accepts the HostInventoryLine element in the xml as an instance of the HOSTINVENTORYLINE element defined in the schema.
Thanks in Advance
JJ
Message was edited by:
[email protected]You could use substitution groups to handle this. You would need an entry in the schema for each valid capitalization. This won't scale well if you want to be completely case insensitive, but if you only support lower case, upper case, and camel case it should do the trick.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="HostInventoryLineType">
<xs:sequence>
<xs:element name="an-element" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:element name="HostInventoryLine" type="HostInventoryLineType"/>
<xs:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
<xs:element name="hostinventoryline" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
</xs:schema>-Blaise -
Using photoshop elements 13 for creating a brochure -drew the rectanle shape for the first column but when i go to the move tool it doesnt allow me to highlite this shape why?
The faulting module is photoshop. Report below.
Source
Adobe Photoshop CC 2014
Summary
Stopped working
Date
2/2/2015 4:54 PM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 15.2.2.310
Application Timestamp: 5480338c
Fault Module Name: Photoshop.exe
Fault Module Version: 15.2.2.310
Fault Module Timestamp: 5480338c
Exception Code: c000001d
Exception Offset: 00000000049de322
OS Version: 6.3.9600.2.0.0.768.101
Locale ID: 1033
Additional Information 1: 8db4
Additional Information 2: 8db473619c10c0c8b85ce99afe676ed8
Additional Information 3: f06d
Additional Information 4: f06da704bdd5338df2a8d09bde2244bb
Extra information about the problem
Bucket ID: 1fe6d1d4e5765bd348843b981b8ec4d2 (85990875000) -
Using text elements in so10 standard texts
How to use text elements in so10 standard texts.
HI,
In DDIC we have two structures :
1. THEAD - Text Header
2. TLINE - Text Lines
SO10 is the tcode..for standard text...
We have a FM to read the text ... read_text...
and save_text is for create text..
this text is are used in SAP scripts...
the standard text is identified by three parameters :
1. Text Name
2. Text ID ( ST for standard text )
3. Language
hope helpfull
Raghunath.S -
XSLT Transformation error: Non-canonical structure of element name
Good day experts,
I have recently started using xslt, and came upon the following demo in the sdn.
http://wiki.sdn.sap.com/wiki/display/ABAP/XMLXSLTwith+ABAP
I have retrieved the example xml files from airplus.com, as per the instructions, and implemented the code.
When I test the xslt transformation in se80, it transforms correctly.
However, when I run the program, I get the following error.
CX_XSLT_FORMAT_ERROR
Transformation error: Non-canonical structure of element name XML_OUTPUT
Is there an error in the example that I am not aware of?
Thanks in advance,
Johan KriekFound the solution.
You rename the tag <XML_OUTPUT> to anything else like <TEST>. And Hurray!!! it works.
It looks like SAP is using this name internally somewhere so we are getting error when we are using same name.
Anyways the problem is solved.
Regards,
Jai
Maybe you are looking for
-
HP 8500 All In One COLOR print issues
My all in one will not print in color, I have just replaced all of the cartridges and even ran a TEST page and all other available diagnostic functions with no success. I also checked the print options to be sure COLOR was selected and everything inc
-
My macbook says runtime corruption detected on macintosh hd, fsck will be forced on next mount.
Help
-
Command line startup options to Graphical Debugger
Hi, With Workshop 5.0 as well as Forte Developer 6, it was possible to pass a program name at the command line with the -D option. This, in conjunction with an appropriate .dbxrc file, allowed me to invoke Workshop (and Forte Developer 6) from my own
-
Out of the box workflow failed on start when started programatically
I have an approval workflow (out of the box) associated with a list and need to start it for some items programmatically when some conditions are met. My application runs under an account which is a farm admin. I do have another user dedicated to st
-
Hyperlink column with link parameters as region column values
On my APEX page i have region which has sql query as source and it displays as HTML table the query result to the user. I want to display addinonal column with a hyperlink inside, and that hyperlink would have CGI/URL-parameters which contains the ot