XML elements nesting problems

Hi,
Is it possible to create an XML report with 2 or more XML
elements in the same level? I was trying to do it with groups in
data model but I can't do it.
e.g.
<report>
<block1>
<element1>A</element1>
<element2>B</element2>
</block1>
<block2>
<element3>A</element3>
<element4>B</element4>
</block2>
</report>
thanks in advance,
Natxo Cabri
[email protected]

Similar Messages

XML element tag problem

Hi guys,
I am facing a problem in parseing a XML file when the element is in <element/> tag format. Iam using "javax.xml.parsers.SAXParser" to parse the XML. Basically XML contains many fields that are mandatary in my XSD. my requirement is that if there is a SAXParseException, I should get the name of the element for which the error is comming.
What I am doing is, I am storing the name of the element in startElement method, which I print it in the catch block of the error. This code is working fine for <element></element> type of tag. But when the element tag is <element/> this. it does not go in the startElement or endElement block. Hence I always get the name element which is previous to the error element.
How can I get the element name in both form of the element tag. As I have no control over the XML, which is posted on my servlet.

I'm not sure why you're having a problem - the SAXException tells you where in the input stream the error is, and SAX parsers may report a validation error at any time so long as it is before passing the invalid element to the content handler. So it's legal for the exception to occur immediately after the startDocument, and will not necessarily occur immediately after the callback for the preceding element.
Eg, if the DTD says you have <!ELEMENT foo (a,b,c,d)> and you have <foo><a/><x/><d/></foo>, then the parser may well report the error before the startElement() call for the foo element, as it is invalid. Such fail-fast parser validation means you can safely update a persistant resource on receipt of the events, rather than having to wait until the element is closed before you are sure it's valid.
This works fine for <element/> tag. But now there is a problem with <element></element> tag.Post the code you have, show how you are mapping from the line no. in the exception to the source data, and state which parser you are using.
Pete

Cannot transform Java to XML - nested XML elements are empty

Hi,
We're using WLI 9.2.1 and in one of our JPDs we're invoking a transformation control that is supposed to do Java -> XML transform. The XQuery for this gets written and works when tested independently within Workshop.
However, wehn we run the JPD, the transformation is not completely successful. What we find is that attributes values that go into top-level XML elements are populated from the Java object. The nested elements are NOT populated and show up as empty.
Q: Is this s limitation in WLI 9.2?
Googling turned up this reference:
XMLBeans APIs Not Supported for Local Element and Complex Type Variables Produced by XQuery
http://e-docs.bea.com/wli/docs85/relnotes/relnotesLimit.html#1375310
http://edocs.bea.com/wli/docs81/relnotes/relnotesLimit.html#1226313
Q: Is this the problem we are seeing?
Q: If yes, any ideas if this CR138983 fixed in WLI 9.2? (it is open in 8.1, 8.5).
Any pointers will be appreciated.
Thanks.

Note: This thread was originally posted in the Swing forum, but moved to this forum for closer topic alignment.

XML tag markers moved: Find and Replace causing problem in xml elements

Hi All,
I am doing find and replace using GREP. While using the expression like $1, $2 (Found Items) in the change to field it changes the placement of tag marker. If the found item is a part of two of more xml elements, I am getting a serious problem while replacing it. (ie. The xml tag markers are moved.)
See the screen shot below, then you may get better idea. And help me to overcome this issue.
This is just an example to show you what i'm trying to say, there are so many cases like this.
Original text/ Before doing find replace
After replacing
Green4ever

Hi Peter and John,
but it seems to me that the example is looking for any space that
follows a semi-colon and has two word characters following it, and
repalce that with an em space. I think you could do the same using look
behind and look ahead and not need to replace the found text.
Yes you are right about the look behind and look ahead. I'd like to show some more examples to show what the actual problem is,
Original/Before Replacing,
(Consider there is another case here, instead of em-space some times normal word space will also be there)
Using the Grep:
Find What---------> ^(\d+\.(?:\d+)?)~m
Change To------------->$1\t
After Replace:
Did I make any sense? Eventhough this will not make any changes in the layout, my requirement is to insert the tab out-side the tag marker not indise.
Green4ever

Problem changing XML element in Adapter Module

Hey!
I am developing an adapter module to transform a coded password back to clear text. I have access to the XML element where the password is and I get to transform it, but I have 2 problems as also stated in the code:
1) I cannot set the new value back to the node. I try with
firstNode.getFirstChild().setNodeValue(decodedPwd);
but this does not seem to work. How can I achieve this?
2) Between the first issue and the code
msg.setDocument(xmlpayload);
I am not sure how to get my new values for the node back in the XMLPayload. How can I achieve this?
Here is the code:
msg = (Message) inputModuleData.getPrincipalData();
          XMLPayload xmlpayload = msg.getDocument();
          factory = DocumentBuilderFactory.newInstance();
          DocumentBuilder builder = factory.newDocumentBuilder();
          Document document = builder.parse((InputStream)xmlpayload.getInputStream());
          password = (Element)document.getElementsByTagName("ns1:passord").item(0);
          firstNode = password.getFirstChild();
          pwd = firstNode.getNodeValue();
          if(pwd != null){
               decodedPwd = Decoder.decodeString(pwd);
// THIS FAILS!
          firstNode.getFirstChild().setNodeValue(decodedPwd);
//HOW TO SET NEW NODE VALUE TO XMLPAYLOAD HERE?
          msg.setDocument(xmlpayload);
          inputModuleData.setPrincipalData(msg);
               return inputModuleData;
Help is much appreciated!
Thanks!
regards Ole

Hey!
The problem was solved. The code snipped I found was:
               DOMSource DOMSource = new DOMSource(document);
               ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
               Result dest = new StreamResult(myBytes);
               TransformerFactory tf = TransformerFactory.newInstance();
               Transformer serializer = tf.newTransformer();
               serializer.transform(DOMSource, dest);
               byte[] docContent = myBytes.toByteArray();
               xmlpayload.setContent(docContent);
               msg.getDocument().setContent(xmlpayload.getContent());
Ole
Edited by: Ole Mugaas on Mar 27, 2008 8:43 PM

Multi-level nested tables for repeatable XML Elements

Hi there,
Suppose we have a XML Schema „ASchema“ like this (XMLDB schema annotations are left out for simplicity):
<xs:schema xmlns:xs=" .... " />
<xs:element name=“A“>
 <xs:complexType>
 <xs:sequence>
 <xs:element name=“B“ maxOccurs=“unbounded“/>
 <xs:complexType>
 <xs:sequence>
 <xs:element name = “C“ maxOccurs=“unbounded“/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
After registering this schema in Oracle, I can define a table like this:
CREATE TABLE ATable
id NUMBER,
doc XMLTYPE
XMLTYPE COLUMN doc
XMLSCHEMA “ASchema“ ELEMENT “A“
VARARRAY doc.“XMLDATA“.“B“ STORE AS TABLE “BTable“
((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)) ORGANIZATION INDEX)
This creates a nested table "BTable" within the table "ATable". So far so good, I can use this nested table to gain faster access on every possible subelement of Element B when I set an appropriate index.
I now want to create another nested table for element “C“ like this:
DROP TABLE ATable;
CREATE TABLE ATable
id NUMBER,
doc XMLTYPE
XMLTYPE COLUMN doc
XMLSCHEMA “ASchema“ ELEMENT “A“
VARARRAY doc.“XMLDATA“.“B“ STORE AS TABLE “BTable“
((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)) ORGANIZATION INDEX)
VARARRAY doc.“XMLDATA“.“B“.“C“ STORE AS TABLE “CTable“
((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)) ORGANIZATION INDEX)
But this statement fails with the error message something like „ ... no such attribute ... „
And here's my question: is it possible to create nested tables for repeatable XML Elements that are subelements of other repeatable XML Elements ? And if so, how can I do it ?
Thank you very much in advance
Jan

Found a (partial) solution myself:
If you add the attribute xdb:storeVarrayAsTable="true" to the root element of the XML schema, Oracle XMLDB generates nested tables for all repeatable XML Elements while registering the XML schema.
Unfortunately, the names of these nested tables are system-generated, hence it's a bit uncomfortable to set indices on them. You can find out the names of these nested tables as follows:
select table_name, parent_table_name, parent_table_column from user_nested_tables;
Further information on that subject is supplied in the following thread:
Re: default tables for elements with maxoccurs > 1
It would be nice if there was a way to name the generated nested tables via appropriate XMLDB schema annotations.
regards
Jan

Problem with XML element creation

hello,
i have a problem creating an XML element using XMLForest
and XMLConcat in Oracle 9.2.0.3 release.
This problem there wasn't when we had the Oracle 9.2.0.2
release.
If i make this statement:
SELECT XMLELEMENT( "message",
XMLATTRIBUTES( 1321324 AS IDSEQ,
'fff' AS CDMS,
'fff' AS TPMS,
SYSDATE AS TIME,
342134 AS REFID),
XMLCONCAT( XMLELEMENT("header",
XMLFOREST( 'ttt' AS TXID,
'rrr' AS RXID,
'QQQ' AS QUEUENAME,
XMLFOREST( 123456789 AS COD_COM,
111 AS ID_CAT,
'www' AS ID_ITM,
1123 AS PR_KEY,
'ST' AS STATUS) AS REFOBJ)),
xmltype('<body>gfgfg</body>') )).getstringval() FROM dual;
i got this XML document:
<message IDSEQ="1321324" CDMS="fff" TPMS="fff" TIME="28-MAR-03" REFID="342134">
<body>gfgfg</body>
</message>
D>rrr</RXID>
<QUEUENAME>QQQ</QUEUENAME>
<REFOBJ>
<COD_COM>123456789</COD_COM>
<ID_CAT>111</ID_CAT>
<ID_ITM>www</ID_ITM>
<PR_KEY>1123</PR_KEY>
<STATUS>ST</STATUS>
</REFOBJ>
</header>
instead of this:
<message IDSEQ="1321324" CDMS="fff" TPMS="fff" TIME="28-MAR-03" REFID="342134">
<header>
<TXID>ttt</TXID>
<RXID>rrr</RXID>
<QUEUENAME>QQQ</QUEUENAME>
<REFOBJ>
<COD_COM>123456789</COD_COM>
<ID_CAT>111</ID_CAT>
<ID_ITM>www</ID_ITM>
<PR_KEY>1123</PR_KEY>
<STATUS>ST</STATUS>
</REFOBJ>
</header>
<body>gfgfg</body>
</message>
any idea?
this happens only after we had installed the patch 9.2.0.3
thanks in advance
Mc

As Jim Stated the problem is related to using XMLCONCAT and a combination of SQL/XML non SQL/XML operators. In this example XMLCONCAT is not required. XMLElement allows multiple XMLType children to be included in the Element, as the attached SQL shows...
Christian please note that Oracle strongly recommend the use of the SQL/XML operators over ways of generating XML from SQL queries. All future development efforts will be focused on optimizing and improving this technology, rather that older, legacy approaches.
SQL> SELECT XMLELEMENT
2 ( "message",
3 XMLATTRIBUTES
4 (
5 1321324 AS IDSEQ,'fff' AS CDMS,'fff' AS TPMS,SYSDATE AS TIME,342134 AS REFID
6 ),
7 XMLELEMENT
8 (
9 "header",
10 XMLFOREST
11 (
12 'ttt' AS TXID,
13 'rrr' AS RXID,
14 'QQQ' AS QUEUENAME,
15 XMLFOREST
16 (
17 123456789 AS COD_COM,
18 111 AS ID_CAT,
19 'www' AS ID_ITM,
20 1123 AS PR_KEY,
21 'ST' AS STATUS
22 ) AS REFOBJ
23 )
24 ),
25 xmltype
26 (
27 '<body>gfgfg</body>'
28 )
29 ).getstringval()
30 FROM dual;
XMLELEMENT("MESSAGE",XMLATTRIBUTES(1321324ASIDSEQ,'FFF'ASCDMS,'FFF'ASTPMS,SYSDAT
<message IDSEQ="1321324" CDMS="fff" TPMS="fff" TIME="31-MAR-03" REFID="342134"><
header><TXID>ttt</TXID><RXID>rrr</RXID><QUEUENAME>QQQ</QUEUENAME><REFOBJ><COD_CO
M>123456789</COD_COM><ID_CAT>111</ID_CAT><ID_ITM>www</ID_ITM><PR_KEY>1123</PR_KE
Y><STATUS>ST</STATUS></REFOBJ></header><body>gfgfg</body>
</message>
SQL> select xmlelement("a", xmlelement("empno", empno), xmltype('1')) from emp;
XMLELEMENT("A",XMLELEMENT("EMPNO",EMPNO),XMLTYPE('1'))
<a><empno>7369</empno>1
</a>
<a><empno>7499</empno>1
</a>
<a><empno>7521</empno>1
</a>
<a><empno>7566</empno>1
</a>
XMLELEMENT("A",XMLELEMENT("EMPNO",EMPNO),XMLTYPE('1'))
<a><empno>7654</empno>1
</a>
<a><empno>7698</empno>1
</a>
<a><empno>7782</empno>1
</a>
<a><empno>7788</empno>1
XMLELEMENT("A",XMLELEMENT("EMPNO",EMPNO),XMLTYPE('1'))
</a>
<a><empno>7839</empno>1
</a>
<a><empno>7844</empno>1
</a>
<a><empno>7876</empno>1
</a>
XMLELEMENT("A",XMLELEMENT("EMPNO",EMPNO),XMLTYPE('1'))
<a><empno>7900</empno>1
</a>
<a><empno>7902</empno>1
</a>
<a><empno>7934</empno>1
</a>
14 rows selected.

How can we get the reference of XML element on frame as soon as frame is created in Document?

Hi,
When ever we copy any text/table cells from any frame, and paste it directly on page, A new Frame is created and the pasted text is placed inside that frame.
Now to capture this frame creation, We have two possible solutions:
1) Attach Observer on Document 'kDocBoss' on IID_IHIERARCHY_DOCUMENT and it will notify on frame creation in update function.
2) Notification event on new story creation.
Now, I need to perform some changes in the newly created table, for example:
a) Need to delete XML tags from newly created frame
b) Need to perform action on table cells if any in the created frame.
But the problem is, when the event comes, I can access basic properties of frame like it's name, type etc, but it does not give me the
XML element on frame or tables in frame until the event is com pleat.
I know it's quite a specif requirement, but I guess many of you might have faced these kind of challenges, while processing the event.
Does any one has any idea how I can get the reference of XML element on frame as soon as it is created?

Hi Kapoor,
please give also others a chance, and excuse that I get up late on vacation ;-)
Anyway, I'd keep the story creation responder to recognize the copy, then combine it with an observer on the backing xml story to catch the associated XML element which is created there. Something like below:
UIDRef xmlStoryRef = Utils<IXMLUtils>()->GetBackingStore(doc);
InterfacePtr<ISubject> subject ( xmlStoryRef,IID_ISUBJECT );
subject->AttachObserver(observer,IID_IIDXMLELEMENT,observer->GetAttachIID());

Hiding XML elements in the structure view – scripting influence to the structure view?

Hi
Is there a way to hide specific XML elements (really the elements and not the attributes) in the structure view?
I am asking this question to know if it is possible to influence the structure view by scripting.
Many elements are indeed used as a kind of help for constructions which have nothing to do with the actual contents especially in the case of tables.
You inflate the the structure view unnecessarily and the author will lose track of the real contents. It would be nice if there was a possibility to hide those help construction elements.
Thank you for any hints.
Regards
Apollo102

Hello Apollo,
There is a way to hide elements from the Structure View (one such method is offered by the free AXCM plug-in). What happens when you use AXCM (or other methods to hide elements) is that the elements get wrapped into hidden content. This might make the structure view less complex for your authors, but has a number of disadvantages and dangers.
1. The structure is normally invalidated, as the helper elements are usually required.
2. Accidentally deleting hidden content may make the invalidation permanent and render your documents useless.
It is NOT good practice to hide elements from authors in the structure view. Instead, you should either teach authors about the structure, or let them work in the Author View while adding sufficiently clear formatting to show them the underlying structure. In some cases, it might be better to create an authoring structure which is automatically transformed into the required full structure using an XSLT or other processing step. I have created a couple of such environments and they work fine. It just depends on the difference between the structure required for further processing and the structure that would be optimal for your authors (which in turn depends on the level at which your authors are experienced in working with structured content).
I hope this helps you solve your problem without having to tweak the structure view.
Kind regards
Jang

[CS3] [JS] add XML Element to Insertion Points

hi list,
i'll do some text parsing in indesign cs3 intended to add some xml elements to my document.
i just wonder why i can't markup an insertion point. is the following approach correct? The code works fine, only the return value (stored in the _xml variable) is not the new element but the parent element. The same code works without using the insertion point (marking up the text object [xmlElements.add(_dokument.xmlTags.item("index") , erg[0]))] ).
Any ideas or thoughts?
var _dokument = app.activeDocument;
main ();
// ** main ()
function main() {
//Set the find options.
app.findGrepPreferences = NothingEnum.nothing;
app.changeGrepPreferences= NothingEnum.nothing;
//find any string encloased by @
app.findGrepPreferences.findWhat = "@.*?@";
erg = _dokument.findGrep();
while (erg.length > 0) {
_xml = _dokument.xmlElements[0].xmlElements.item("text").xmlElements.add(_dokument.xmlTags.item( "index") , erg[0].insertionPoints[0]);
erg[0].contents = "";
erg = _dokument.findGrep();

hi dave,
gui testing is always a good idea :-) but in this case the behaviour is different:
your observation is correct (anyway at least a strange behaviour compared to any xml editing tool i know == how adobe intended to insert an empty element?), tagging in the gui a tagged insertion point tags the whole story.
in the script a new element is added but the return value is the parent element (the xmlElement of the whole story).
this causes a problem when i add an attribute (the intention of the above script is to add references) which is added to the parent element.
gregor

Remove xml element using JS[CS3]

Hi, I have an xml structure where i want to remove some paritcular element named "extlink".
I do have one script with me but it doesn't wipe out all specific xml element from structure.
var myDoc = app.activeDocument;
var foundtext = 0
Query_Remove (myDoc);
alert ("You have removed " + foundtext + " " +" Link !!")
exit (0);
function Query_Remove(elm)
try
for(var i=elm.xmlElements.length-1; i>=0; i--)
     if((elm.xmlElements[i].markupTag.name == "extlink") && (elm.xmlElements[i].xmlElements[0].markupTag.name == "http"))
    var Store_CitAttri = elm.xmlElements[i].xmlElements[0].xmlAttributes.item("c_style").value;
     if(Store_CitAttri == "URL")
      elm.xmlElements[i].remove();
     foundtext = foundtext + 1;
   Query_Remove(elm.xmlElements[i]);
catch (e){
Some time it skip the element from all figure captions and some time from body text and some time it works perfectly
Could any one figure it out why this script behaviour is not consistent as i am new to scripting and not getting any idea about this.
Thanks
Mac

Okay, after peering over your code and trying a few things out I see one immediate problem and one possible improvement.
The problem lies in this:
1. if condition is true, remove item
2. check recursively
The problem is .. if an item is removed, the following recursive check will always fail. However, the entire loop is wrapped into a try..catch, so InDesign will not alert you that it failed. Instead, it will continue with what's after the loop, exactly because the try..catch is around the entire loop!
Change the loop code to this
if((elm.xmlElements[i].markupTag.name == "http") && (elm.xmlElements[i].parent.markupTag.name == "extlink"))
    var Store_CitAttri = elm.xmlElements[i].xmlAttributes.item("c_style").value;
    if(Store_CitAttri == "URL")
      elm.xmlElements[i].remove();
       foundtext = foundtext + 1;
       continue;
Query_Remove(elm.xmlElements[i]);
so the recursive checking is skipped. You can also remove the entire try..catch block, as this may hide additional errors ...
The improvement is: as I started reading this thread from the top again, shouldn't you be removing the "extlink" items, rather than just the "http" ones inside?
If so, remove the parent of the found item (which is always the "extlink"):
      elm.xmlElements[i].parent.remove();
-- and, as this will break the loop (because you just removed the set of elements it was working in!), replace 'continue' with 'return'.
Hope this helps

Exception in XML Parser (format problem?)

Hi Experts,
I am working on IDOC -> AS2 Configuration and the AS2 Configuration has the below structure
<RecordSet>
 <Row1>
 <row1 - field1>
 <row1 - field2>
 <row1 - field3>
 </Row1>
 <Row2>
 <row2 - field1>
 <row2 - field2>
 <row2 - field3>
 </Row2>
 <Records>
 <Record1>
 <Record1-Field1>
 <Record1-Field1>
 <Record1-Field1>
 </Record1>
 <Record2>
 <Record2-Field1>
 <Record2-Field1>
 <Record2-Field1>
 </Record2>
 </Records>
</RecordSet>
We are getting the expected Structure when we AS2 Receiver has the xml format. But while doing module development with the strctxml2Plain, we are getting the below error in RWB CC Monitoring.
Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
Any ideas, why this error we are getting.....
Thanks in advance,
Regards,
Vasu

Hi Vasu,
Not in the Mapping of IR.
In BIC Mapping Designer you have to test with the standard Mappings by providing the sample file whether the Conversion is happening correctly or not.
You have to take the same input file that what ever you are having now.
So that it will say clearly what is the problem in converting the XMLto the required EDI Format...
Check whether you have any Date Format Values are comming from the input file.
Regards
Seshagiri

Howto use Converting File Content in Rec. Adapt. to suppress a xml-element

Hi,
we use PI/700, SP6.
I have following structure (example):
<MsgOut>
<Sender>Partner1</Sender>
<Receiver>Partner2</Receiver>
<FlatPayload>
 blabla blabla
</FlatPayload>
</Msgout>
Now I wanna use a XI-File-Adapter to write just a Flat-File with the content (of the element <FlatPayload>):
 blabla blabla
(in other words: I wanna suppress all other xml-elements beside of FlatPayload)
But I'm not able to configurate this with the function "Converting File Content"
I tried different possiblities:
e.g.
setting yyy.fieldFixedLengths = 0 and yyy.fixedLengthTooShortHandling = Cut
(yyy = Sender and Receiver)
or
just defining "MsgOut,FlatPayload" as RecordSet Structure (without Sender and Receiver)
Result: no success.
Now my question: is it possible to suppress some xml-elements?
Thanks for your help!
bye
Wolfgang

HI,
You can suppress the XML Nodes/Elements over here. Not Fields ..
For e.g if your outout xml is like this
<MsgOut>
 <Sender>Partner1</Sender>
 <Receiver>Partner2</Receiver>
<FlatPayload>
 <flatdata> blabla blabla</flatdatat>
</FlatPayload>
</Msgout>
In this case you can suppress the <FlatPayload> node/element here.. Using Cut Parameter in the Receiver File Content COnversion.
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
So in your case, you can restructure your data type as you required.. I have mentioned in vice-versa here
Hope this helps,
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

Remove XML element with JAXB

Hi all,
does anyone knows if it's possible to remove an xml element after that element has been set ? Using only jaxb if possible and not using other technology, for example DOM.
I explain:
umarshall car -->setOwner("me"); setSpeed("80"); -->marshall car
will result into:
<car>
<owner>me</owner>
<speed>80</speed>
</car>
I would like something that for example
unmarshall car -->remove(speed); ....-->marshall car
would result into:
<car>
<owner>me</owner>
</car>
could someone point out a way to do that ?
thanks in advance...

Okay, after peering over your code and trying a few things out I see one immediate problem and one possible improvement.
The problem lies in this:
1. if condition is true, remove item
2. check recursively
The problem is .. if an item is removed, the following recursive check will always fail. However, the entire loop is wrapped into a try..catch, so InDesign will not alert you that it failed. Instead, it will continue with what's after the loop, exactly because the try..catch is around the entire loop!
Change the loop code to this
if((elm.xmlElements[i].markupTag.name == "http") && (elm.xmlElements[i].parent.markupTag.name == "extlink"))
 var Store_CitAttri = elm.xmlElements[i].xmlAttributes.item("c_style").value;
 if(Store_CitAttri == "URL")
 elm.xmlElements[i].remove();
 foundtext = foundtext + 1;
 continue;
Query_Remove(elm.xmlElements[i]);
so the recursive checking is skipped. You can also remove the entire try..catch block, as this may hide additional errors ...
The improvement is: as I started reading this thread from the top again, shouldn't you be removing the "extlink" items, rather than just the "http" ones inside?
If so, remove the parent of the found item (which is always the "extlink"):
 elm.xmlElements[i].parent.remove();
-- and, as this will break the loop (because you just removed the set of elements it was working in!), replace 'continue' with 'return'.
Hope this helps

Imported XSLT cannot create attributes for generated XML element

I have two xslts. One imports the other.
The imported xslt creates XML elements with attributes and this XML is stored in a variable in the main stylesheet
If I perform the transformation with JRE prior to 1.6.0.18 then all works fine
If I use 1.6.0.18 or 1.6.0.19 then the attributes aren't added.
If I add attributes in the main xslt it works fine or if I output the element directly instead of first storing it in a variable then it also works fine.
Problem seems to be when you try to add attributes from an imported stylesheet and store the generated element in a variable.
Below two stylesheets to illustrate :
First MainStylesheet.xsl
<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:exsl="http://exslt.org/common"
extension-element-prefixes="exsl"
exclude-result-prefixes="xs">
<xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes" />
<xsl:import href="innerstylesheet.xsl"/>
<xsl:template match="/TestData">
<xsl:variable name="generatedElementXml">
<xsl:call-template name="generateElement">
<xsl:with-param name="s">testValue</xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:for-each select="exsl:node-set($generatedElementXml)">
*** GeneratedElementXML {<xsl:text>
</xsl:text><xsl:copy-of select="*"></xsl:copy-of>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>Next innerstylesheet.xsl
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:exsl="http://exslt.org/common"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
extension-element-prefixes="exsl" >
 <xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes"/>
 <xsl:template name="generateElement">
 <xsl:param name="s"/>
 <TestElement testAttribute="$s" />
 </xsl:template>
</xsl:stylesheet>The result output by jres before 1.6.0.18 is :
<?xml version="1.0" encoding="UTF-8"?>
 *** GeneratedElementXML {
 <TestElement xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" testAttribute="testValue"/>
 } The result output by jres since 1.6.0.18 is :
<?xml version="1.0" encoding="UTF-8"?>
 *** GeneratedElementXML {
 <TestElement xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 } Note : the 'testAttribute' attribute is missing

Have found the difference in the code
In both JRE1.6.0_17 & JRE1.6.0_18, the class 'com.sun.org.apache.xalan.internal.xsltc.dom.AdaptiveResultTreeImpl' has the following method
public void addUniqueAttribute(String qName, String value, int flags)
 throws SAXException
 addAttribute(qName, value);
 }In JRE1.6.0_17 the next method is
public void addAttribute(String name, String value)
 if (_openElementName != null) {
 _attributes.add(name, value);
 else {
 BasisLibrary.runTimeError(BasisLibrary.STRAY_ATTRIBUTE_ERR, name);
 }In JRE1.6.0_18 the next method is
public void addAttribute(String uri, String localName, String qname,
 String type, String value)
 if (_openElementName != null) {
 _attributes.addAttribute(uri, localName, qname, type, value);
 else {
 BasisLibrary.runTimeError(BasisLibrary.STRAY_ATTRIBUTE_ERR, qname);
 }Note - the addAttribute method has additional parameters in JRE1.6.0_18 but the call from addUniqueAttribute wasn't updated.
So in JRE1.6.0_18 addUniqueAttribute actually invokes the following method in the base package com.sun.org.apache.xml.internal.serializer.EmptySerializer
public void addAttribute(String name, String value)
 aMethodIsCalled();
void aMethodIsCalled()
 // throw new RuntimeException(err);
 return;
 }and as you can see this does nothing. Hence the fact that the attribute isn't added.

XML elements nesting problems

Similar Messages

Maybe you are looking for