Secondary XML source via document() function

Has anyone used the XSLT document function in an XSL-FO template where the file is an URL. We are trying to do this to get extra information for the PO output in an EBS installation without horrible customisations
eg
<xsl:text>Person : <xsl:value-of select="document('http://dbsdev11.uk.baa.com:8031/OA_HTML/test.xml')/xxpo:PO_DATA/xxpo:PERSON_ID"/></xsl:text>
where test.xml is:
<?xml version="1.0" encoding="UTF-8" ?>
<xxpo:PO_DATA xmlns:xxpo="http://uk.baa.com/oracle/apps/po/info">
<xxpo:PERSON_ID>120</xxpo:PERSON_ID>
<xxpo:SERVER_PORT>8031</xxpo:SERVER_PORT>
</xxpo:PO_DATA>
and the URL http://dbsdev11.uk.baa.com:8031/OA_HTML/test.xml resolves quite happily when pasted into a browser.
But nothing comes back when previewing the template in EBS. PDF is produced but Person value is not populated.
Is the document function supported??
Rgds
James M

Hi Jame
Document() is supported but what you are trying to do with it is not, i.e.
document('http://dbsdev11.uk.baa.com:8031/OA_HTML/test.xml')/xxpo:PO_DATA/xxpo:PERSON_ID"/
will not work. You need to load the doc to a variable and then reference the PERSON_ID element.
Something like:
Variable Declaration
==================
<xsl:variable name="news" select="document('http://rss.news.yahoo.com/rss/topstories')"/>
Value
========================
<?$news/rss/channel/title?>
regards
Tim

Similar Messages

Error during XML inbound via Function Module 'EDI_DATA_INCOMING'

Hi Team,
I am facing below error while trying to upload a inbound XML file via Function Module 'EDI_DATA_INCOMING'.
The control record must begin with <EDI_DC40 segment="1"> instead of
Message no. EA719
Diagnosis
The tag '<EDI_DC40 segment="1">' must be at the start of a control record in XML format, otherwise string '' would be found.
System Response
The file cannot be processed.
Procedure
Correct file DEV_H\SGIDOCI\MSUTEST\00082_ATT..
Please suggest a proper solution for the same. If it is because of wrong structure of XML file then please send me correct XML format for file upload.
Regards,
Amit Sharma

Hello,
It's the error is SAP code.
Look notes 1616333 and 1535033. Those should fix the error.
BR, Janne

Use DOM as an argument of XSLT document() function

I have in memory several DOM documents. I have not stored in file system the XML files that are represented by these DOMs. I want to process with a stylesheet
all of these DOMs (as DOMSource's) using document() function from the stylesheet. How can I refer to the secondary DOMs from document function if I haven't the files?
F.e.
<xsl:value-of select="document('file.xml')/.../..."/> file.xml only exists loaded in memory as DOM.
Can anybody help me?? Thanks

Thank you DrClap but I'm not sure about the use of URIResolver:
if my xslt:
<xsl:value-of select="document('file1.xml')\...\..."/>
<xsl:value-of select="document('file2.xml')\...\..."/>
I must define my own class that implements URIResolver and write my own resolve method, isn't it?
class Resuelve implements URIResolver{
     private Document doc1;
     private Document doc2;
     public Resuelve(Document doc1, Document doc2){
          this.doc1 = doc1;
          this.doc2 = doc2;
     public Source resolve(String href, String base){
          if(base.equalsIgnoreCase("file1.xml")){
               Source s1 = new DOMSource(doc1);
               return s1;
          else if(base.equalsIgnoreCase("file2.xml")){
               Source s2 = new DOMSource(doc2);
               return s2;
          else{
               return null;
I suppose that XSLT processor use automatically resolve method. I don't understand the href parameter...
Is this class correct? if not, can you show me an example please?
Thank you very much

Error when attaching a remote XML source

Hello,
When I try and attach a remote XML source to my XSL file,
Dreamweaver CS3
tells me "Unable to locate or parse the XML source".
The XML file in question is located at
http://weather.yahooapis.com/forecastrss?p=UKXX0085
- which is a fully
functioning URL to an XML page - I can load it okay, and I
can view the XML
source.
Why does Dreamweaver report that it cannot access it? If I
open the source
of that URL and save it as a .xml file and attach it to my
XSL locally, it
works just fine - so it works locally but not remotely. The
source is likely
to change frequently, so attaching a local XML file is not an
option.
If I ignore the Dreamweaver error message and use that source
anyway, the
browser just responds with "An error occured while loading
XML document
http://weather.yahooapis.com/forecastrss?p=UKXX0055".
Error message was: A
connection with the server could not be established ".
The only thing I can think of is, the URL to the XML source
doesn't end in
".xml" - but then again, hardly any XML sources on the web do
so I can't be
the first person who wants to try and incorporate one in
their site like
this!
Any help appreciated!
Cheers,
D.

> I'm told that, in the ASP that uses the XSL fragment, I
can define the
> proxy server manually so that the request can still be
made. Try as I
> might I cannot find any code for ASP.net or ASP VBScript
that allows me to
> manually specify the proxy to be used (or, indeed, to
force the code to
> use the browsers default proxy). Any ideas?
Okay, now using this in a new file called web.config
<configuration>
<system.net>
<defaultProxy>
<proxy
usesystemdefault = "false"
proxyaddress="
http://myproxy.blah.blah:80"
bypassonlocal="false"
/>
</defaultProxy>
</system.net>
</configuration>
All is well - except, that restricts the app to people who
are using this
proxy - any idea how to fix that code to make it default to
the users
browser settings? (Which I thought was the default in .Net
but maybe not??).
D.

Un Expected end of XML Source...

Hi,
I am using Java Script in Html, while executing this program I am getting the Error "Un-Expected end of XML Source }\n" but i have closed all the brakets properly.
Please help me why this error riseing while executing the program.
<html>
<head>
<script>
function selectValue()
var selected_value=document.getElementById("mySelect");
document.getElementById("expression").value = mySelect.options[mySelect.selectedIndex].text;
document.getElementById("expression").value=m
function generator()
var theExpression = document.forms[0].expression.value;
var token=theExpression.split(' ');
var name=token[0].toUpperCase();
if(name="MULTIGEN")
   multiGen(theExpression);
function multiGen(theExpression)
var tokenArray=theExpression.split(' ');
var quantity=parseInt(tokenArray[1]);
var output='';
for(var j =2;j < tokenArray.length; j++)
   output=output+tokenArray[j];
for(var i = 1;i <= quantity; i++)
     document.forms[0].theResults.value=output;<br>
</script>
</head>
<body>
<form name="theForm" id="theForm">
<table>
<tr>
<td>
Enter generator expression: <input type="text" name="expression" id="expression" maxlength="60" size="60">
<input type="button" name="generate" value="generate" onclick="javascript:generator()">
</td>
</tr>
<tr>
<td>
Results:
<input type="button" name="Select" value="Select" onclick="javascript:selectValue()">
</td>
</tr>
<tr>
<td>
<textarea name="theResults" rows="20" cols="60"/></textarea>
<select name="mySelect" size="20" id="mySelect">
<option>MultiGen Quantity String</option>
<option>MultiGen 900 Testers love TestersDesk.com</option>
<option>MultiGen 900 Testing</option>
<option>SyntaxStringGen Syntax Quantity</option>
<option>SimpleStringGen UCase 10 100</option>
<option>SimpleStringGen LCase 10 100</option>
<option>SimpleStringGen Num 10 100</option>
<option>SimpleStringGen AlphaNum 10 100</option>
<option>SyntaxStringGen AAA999ULN 800</option>
<option>SyntaxStringGen 999--LN 800</option>
<option>SyntaxStringGen AAA999ULN 800</option>
<option>SyntaxStringGen AXXX999ULN 800</option>
<option>SimpleStringGen Format Length Quantity</option>
<option>NumGen Type Minimum Maximum Quantity</option>
<option>NumGen Integers 30 3000 25</option>
<option>NumGen Real 30 3000 25</option>
<option>QTGen Length [symbol] [CharFirst/NumFirst]</option>
<option>QTGen 500</option>
<option>QTGen 500 # NumFirst</option>
<option>QTGen 500 X</option>
</select>
</td>
</tr>
</table>
</form>
</body>
</html>Thanks
Buntty
Edited by: Buntty on Dec 4, 2008 2:30 PM

This is not a Javascript forum. You've been told before not to post javascript questions. I'm locking.

Using document() function in xsl - first iteration is OK; second iteration is Empty.

I am processing an input xml file (say input.xml) via (report.xsl) to generate
a report.
report.xsl in turn loads another *xml file (schema.xml) through document() function
so as to process the input.xml. <schema.xml> contains some look-up information
dictating how <input.xml> need to be processed.
Here is how I am referencing the "schema.xml" in the "report.xsl".
<xsl:variable name="schemaFile" select="document('schema.xml')"/>
<xsl:variable name="schemaRoot" select="$schemaFile/Schema"/>
<xsl:variable name="schemaList" select="$schemaRoot/SchemaFactors"/>
When I run the report first time (my appserver is weblogic 7.0), everything is
working fine. I see the results I wanted.
However, when I run the report for the second time during the same session, I
am getting "schemaList" as empty.
The values of "schemaFIle" and "schemaRoot" appear to be correctly loaded in both
the cases. The problem is with "schemaList" variable which is coming out empty
during the second iteration.
can any of you please throw some pointers on why this is happening and how to
resolve this?

Hello,
Sounds like a bug. If you have a small test case, could you provide
that to our outstanding support group (http://support.bea.com or
[email protected]), it would certainly help tracking this down.
Thanks,
Bruce
venkata wrote:
>
I am processing an input xml file (say input.xml) via (report.xsl) to generate
a report.
report.xsl in turn loads another *xml file (schema.xml) through document() function
so as to process the input.xml. <schema.xml> contains some look-up information
dictating how <input.xml> need to be processed.
Here is how I am referencing the "schema.xml" in the "report.xsl".
<xsl:variable name="schemaFile" select="document('schema.xml')"/>
<xsl:variable name="schemaRoot" select="$schemaFile/Schema"/>
<xsl:variable name="schemaList" select="$schemaRoot/SchemaFactors"/>
When I run the report first time (my appserver is weblogic 7.0), everything is
working fine. I see the results I wanted.
However, when I run the report for the second time during the same session, I
am getting "schemaList" as empty.
The values of "schemaFIle" and "schemaRoot" appear to be correctly loaded in both
the cases. The problem is with "schemaList" variable which is coming out empty
during the second iteration.
can any of you please throw some pointers on why this is happening and how to
resolve this?

Looking for example - abap xslt - that uses xslt document() function

Hello,
I'm looking for an example that shows the use of abap xslt with the xslt document() function. Using the xslt document() function seems like a straightforward way to use xslt to create a result xml document by processing the content of two or more
source documents. For example, if source document A.xml and aux.xml are available in memory as xstringand using stylesheet ztransformwhat would be the argument for the document() function to associate aux.xml. Thanks for any insight.
Regards,
jb10809

Hi,
Sorry, perhaps I should have been clearer! The function that I picked just to test what you need to do just happened to return a string that contains SPAN tags with style attributes. The actual function code is:
create or replace FUNCTION out_string_fn
   RETURN VARCHAR2
IS
   CURSOR emp_cur
   IS
      SELECT ename
        FROM emp;
   v_string   VARCHAR2 (4000);
BEGIN
   v_string := ' ';
   FOR c IN emp_cur
   LOOP
      v_string :=
            v_string
         || '<SPAN style="font-weight:bold;color:green">'
         || c.ename
         || '</SPAN>'
         || ', </br></br>';
   END LOOP;
   RETURN v_string;
END;And this returned a naff list in green (see [http://apex.oracle.com/pls/otn/f?p=55041:57] and click the Test button) - but it does show that you can style the validation error messages
Andy

Document() function problem in Cocoon

Hi,
I have a problem using document() function in xslt. Transformation is done via Cocoon. I know that document() function is problematic in Cocoon, but I think still it is possible to use document() in Cocoon or?
Here is the simple code:I am getting Java NullPointerException.
<xsl:variable name="myfile"
select="document('file:///c:/Temp/temp.xml')" />
<xsl:value-of select="$myfile/document/doc/@id" />
If document() function is not possible in Cocoon, can anyone suggest me another way?
thanks

Are you sure that you can access a local file?

Xml source

Hi All
I am importing multiple xml files via ftp task in control flow and in the data flow section I am placing xml source. I am using variable as xml source. The source file in variable is *.XML
What need some help in completing this package.
1. Getting error message path is invalid
2. How to setup XSD destination.

You need to use the For each loop container to identify the individual XML files. This gives a summary of the process.
http://stackoverflow.com/questions/6956409/ssis-reading-multiple-xml-files-from-folder
The xml files need to have compatible structures.
These explain the process of working with the XML Source.
http://blogs.msdn.com/b/mattm/archive/2007/12/11/using-xml-source.aspx
http://www.mssqltips.com/sqlservertip/3141/importing-xml-documents-using-sql-server-integration-services/
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

Resolving url after document() function has been called by the xslt

I am having problems resolving a URI when document() function in my xslt is called. The xml document that is being called has a reference to a dtd that is in another location of the webserver. When document() is called it downloads the xml document then tries to download the referenced dtd from the same location. I get an error kinda like this.
file:///C:/dev.xsl; Line 15; Column 62; Can not load requested doc: File "http://dev.server.com/templatedata/lhj/story/data/dcr4.5.dtd" not found.
The DTD is in a different location on the server and that is why it can not find it. I have tried resolving the URL but have been unsucessfull. See my java solution that does not work. How can I fix this? Any assistance will be greatly appreciated
Java solution
try {
TransformerFactory tFactory = TransformerFactory.newInstance();
tFactory.setURIResolver(new XMLURIResolver());
Transformer transformer = tFactory.newTransformer(new StreamSource(xslFile));
File f = new File(xmlFile);
FileReader fr = new FileReader(f);
InputSource inputSource = new InputSource(fr);
transformer.transform(new SAXSource(inputSource),
new StreamResult(new FileOutputStream(outPutPath)));
Vince.

here is the resolver. The if in never excuted.
public class XMLURIResolver implements URIResolver{
public static final String DTD_HREF = "dcr4.5.dtd";
public Source resolve(String s, String s1) throws TransformerException{
System.out.println("s = "+ s);
System.out.println("s1 = " + s1);
InputStreamReader isr = null;
try{
if (s.indexOf(DTD_HREF) != -1){
System.out.println("Fetching DTD....");
URL url = new URL("http://mydomain/xml/validation/dcr4.5.dtd");
isr= new InputStreamReader(url.openStream());
return new SAXSource(new InputSource(isr));
}catch(MalformedURLException mue){
System.out.println(mue);
}catch(IOException ioe){
System.out.println(ioe);
return null;
}

Using document function in xsl template - not working in BI Publisher

Hi,
I have a requirement where I need to display the data in one xml file based on the contents of a second xml. I am using Oracle BI Publisher 10.1.3.4.1 and template used for report generation is xsl-fo.
1) ReportData.xml - contains the data xml
2) ReportFilter.xml - contains the display information.
I need to display the tags in the ReportData.xml based on the presence , absence of different tags in ReportFiler.xml
I guess one of the option is to declare 2 datasource as use concatenated datasources. However , I am trying to use the "Document" function that is available in xsl transformation to reference the display xml.
I have tried the different options for using the document function
*1) <xsl:variable name="filterCheck" select="document('ReportFilter.xml')"/>*
Errors out saying : XML-22021: (Error) Error parsing external document: 'Access not allowed : file:/
C:/OracleBI/oc4j_bi/bin/ReportFilter.xml '.
*2) <xsl:variable name="filterCheck" select="document('file:///C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out saying ; Caused by: oracle.xdo.parser.v2.XPathException: Access not allowed : file:/C:/Or
acleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml
*3) <xsl:variable name="filterCheck" select="document('C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out saying : Caused by: java.net.MalformedURLException: unknown protocol: c
at oracle.xdo.parser.v2.XSLStylesheet.flushErrors(XSLStylesheet.java:153
*4)<xsl:variable name="filterCheck" select="document('file:/C:/OracleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml')" />*
Errors out syaying : Caused by: oracle.xdo.parser.v2.XPathException: Access not allowed : file:/C:/Or
acleBI/xmlp/XMLP/DemoFiles/ReportFilter.xml
I have placed the document I need to access in all the 3 locations mentioned above
ie in my
*1) C folder*
*2) C:/OracleBI/oc4j_bi/bin*
*3) C:/OracleBI/xmlp/XMLP/DemoFiles*
Is there any special permissions that I need to grant to enable access to these files?
Please let me know if anyone has successfully made the document function to reference other xml documents in BI Publisher.
Regards
Sujith
Edited by: user10979469 on Dec 8, 2009 11:48 AM

Tim,
Thanks a lot for the reply. Set the option to enable external document access and it works perfectly.
Just for other who are looking at this post.
Go to the Report in BI Publisher
Click on Configure link on the top right
Go to the Section FO Processing
Disable external references - Server value is "True" . Set it to "False".
Apply changes.
Restarted the oc4j, just to be on safer side (not sure if this is required)
The document function will open documents from any location on your machine.
Thanks again Tim
Regards
Sujith

Error in xml to html transform function in 11g(Help needed urgent)

We are migrating from 9g to 11g.Code given below is working fine with 9g but giving following error while converting xml to html.
Error:Exception occurred in XML_TO_HTML :ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00609: Function call with invalid number of arguments in 'position (//USER)'.
Code :<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="/">
<HTML>
<BODY>

<xsl:for-each select="AMAP_REMMIT_EMP/HEADERS/HEADER">
<TABLE border="0" cellpadding="0" cellspacing="0" style="padding:1px" width="100%" height="95" bgcolor="#EAEAEA"><font size="6" face="Arial">amdocs </font>
<TR >
<TD width="50%" align="left" ><b/><font size="2" face="Verdana" /> <xsl:value-of select="VENDOR_NAME"/></TD>
<TD width="50%" align="left"><b/><font size="2" face="Verdana" />Date: <xsl:value-of select="RUN_DATE"/>
</TD>
</TR>
<TR >
<TD width="50%" align="left" ><b/><font size="2" face="Verdana" /> <xsl:value-of select="ADDRESS"/></TD>
<TD width="50%" align="left"><b/><font size="2" face="Verdana" /> <xsl:value-of select="TAX_ID"/>
</TD>
</TR>
<TR >
<TD width="50%" align="left" ><b/><font size="2" face="Verdana" /> <xsl:value-of select="CITY"/> <xsl:value-of select="ZIP"/></TD>
<TD width="50%" align="left"><b/><font size="2" face="Verdana" />Vendor Number: <xsl:value-of select="OSEK_MURSHE"/>
</TD>
</TR>
<TR >
<TD width="50%" align="left" ><b/><font size="2" face="Verdana" /> </TD>
<TD width="50%" align="left"><b/><font size="2" face="Verdana" />Fax Number: <xsl:value-of select="FAX"/>
</TD>
</TR>
</TABLE>
</xsl:for-each>


<p dir="ltr" align="center">
<span style="font-family: Arial; text-decoration: underline; font-weight: 700">
Subject: Remittance Advice</span></p>
<table border="1" cellspacing="1" width="100%" bgcolor="#C0C0C0">
<tr>
<th width="20%"><font face="Arial"><b>Invoice Date</b></font></th>
<th width="20%"><font face="Arial"><b>Invoice Number</b></font></th>
<th width="40%"><font face="Arial"><b>Description</b></font></th>
<th width="20%"><font face="Arial"><b><xsl:value-of select="AMAP_REMMIT_EMP/HEADERS/HEADER/CURRENCY"/> Amount</b></font></th>
</tr>
<xsl:for-each select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE">
<tr>
<td width="20%" >
<xsl:attribute name="bgcolor">
<xsl:if test="position() mod 2 = 0">#DDDDDD</xsl:if>
<xsl:if test="position() mod 2 = 1">#FFFFCC</xsl:if>
</xsl:attribute>
<xsl:value-of select="INVOICE_DATE"/></td>
<td width="20%" >
<xsl:attribute name="bgcolor">
<xsl:if test="position() mod 2 = 0">#DDDDDD</xsl:if>
<xsl:if test="position() mod 2 = 1">#FFFFCC</xsl:if>
</xsl:attribute>
<xsl:value-of select="INVOICE_NUM"/></td>
<td width="40%" >
<xsl:attribute name="bgcolor">
<xsl:if test="position() mod 2 = 0">#DDDDDD</xsl:if>
<xsl:if test="position() mod 2 = 1">#FFFFCC</xsl:if>
</xsl:attribute>
<xsl:value-of select="DESCRIPTION"/></td>
<td width="20%" >
<xsl:attribute name="bgcolor">
<xsl:if test="position() mod 2 = 0">#DDDDDD</xsl:if>
<xsl:if test="position() mod 2 = 1">#FFFFCC</xsl:if>
</xsl:attribute>
<xsl:value-of select="AMOUNT"/></td>
</tr>
</xsl:for-each>
<tr>
<td width="80%" bgcolor="#FFFFFF" colspan="3" align="right">
<b>Total Payment:</b></td>
<td width="20%" bgcolor="#FFFFFF"><xsl:value-of select="//TOTAL"/></td>
</tr>
</table>
<p dir="ltr" align="left"><span style="font-family: Arial"><font size="2">In accordance with your instructions, this amount will be transferred to your <xsl:if test="AMAP_REMMIT_EMP/MERGE_LINE/SITES/SITE/INCLUDE_BANK_DETAILES='Y'">
account number <xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/ACCOUNT"/> in bank
<xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/BANK"/> , branch <xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/BRANCH"/>
on the date of <xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/CHECK_DATE"/>.
</xsl:if>
<xsl:if test="AMAP_REMMIT_EMP/MERGE_LINE/SITES/SITE/INCLUDE_BANK_DETAILES!='Y'">
account on the date of <xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/CHECK_DATE"/>.
</xsl:if>
<xsl:if test="AMAP_REMMIT_EMP/MERGE_LINE/CREDITNOTES/CREDITNOTE/CREDITNOTE>'0'">
<p>The payment will be credited in two days from the payment date in your account.</p>
</xsl:if>
<p>In case this date is not a valid value date in the bank system, the money will be transferred in the next valid value date.</p>
<xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/NOTES/NOTE/DESCRIPTION"/>
</font></span></p>
<TABLE border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" width="100%" height="50">
<TR >
<TD width="60%" ></TD>
<TD width="40%" align="left"><b/><font size="2" face="Verdana" />Yours sincerely,</TD>
</TR>
<TR >
<TD width="60%" ></TD>
<TD width="40%" align="left"><b/><font size="2" face="Verdana" /> <xsl:value-of select="AMAP_REMMIT_EMP/MERGE_LINE/LINES/LINE/COMPANY_NAME"/></TD>
</TR>


</TABLE>
<table cellpadding="0" cellspacing="0" style="border-collapse: collapse; border-left-width: 1; border-right-width: 1; border-top-style: solid; border-top-width: 1; border-bottom-width: 1; padding: 0" bordercolor="#111111" width="100%">
<tr>
<td width="34%">Alert No:<xsl:value-of select="AMAP_REMMIT_EMP/HEADERS/HEADER/ALERT_ID"/></td>
<td width="33%">Environment: <xsl:value-of select="AMAP_REMMIT_EMP/HEADERS/HEADER/DB_NAME"/></td>
<td width="33%">Date:<xsl:value-of select="AMAP_REMMIT_EMP/HEADERS/HEADER/MAIL_DATE"/></td>
</tr>
</table>

</BODY>
</HTML>
</xsl:template>
</xsl:stylesheet>
Thanks in advance.

#1. We need to see the code that is being used to invoke the stylesheet.
#2. We need to see the document that is being transformed...
It's most likely a bug in 9g which has been fixed in 11g...

Problem in Coverting XML String into Document

Hi,
I am getting some problem while parsing a String XML in to Document object.
CODE :
public static Document converDocument(String xml){
DocumentBuilderFactory factory=DocumentBuilderFactory.newInstance();
DocumentBuilder builder = null;
try {
builder = factory.newDocumentBuilder();
} catch (ParserConfigurationException e) {
e.printStackTrace();
Document document = null;
try {
document = builder.parse(new InputSource(new StringReader(xml)));
System.out.println("Document is after parsing ====>>>"+document);
} catch (SAXException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
} catch (IOException e1) {
e1.printStackTrace();
return document;
The xml which I am passing is :
<?xml version="1.0" encoding="UTF-8"?>
<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>abc</body>
</note>
It is giving the document as null;
Can anybody please help?
Regards,
sheeetal.

>
Vikas Sridharan wrote:
>
>       CALL TRANSFORMATION ('ID')
>       SOURCE XML = lv_output_str "<============ ERRONEOUS = HERE
>       RESULT ref = <fst_dyn_table> .
>
Remove the "=" sign, this code will work :
      CALL TRANSFORMATION ('ID')
      SOURCE XML lv_output_str
      RESULT ref = <fst_dyn_table> .

How to use xsl document() function with LiveCycle XSLT processor

Hello,
I would like to use LiveCycle XSLT processor to merge xml documents by using the xsl document() function.
However, I have not, yet, found clear reference information on the specifics of how to accomplish in LC. For instance if you have
a transformation that does merging using a standalone xml editor (such as Oxygen), than what is required to accomplish the same
using the LiveCycle XSLT service. How do you specify the URI of the XML document that is specified as an input in the xsl document() function. Your insight is appreciated. Regards

Hello Steve,
I checked the reference that you cited (XSLT Transformation). The reference omits discussing how to use xlst document() function within a stylesheet. I think that probably means that feature of xslt technology is not directly available through LiveCycle. When I find a workaround, I'll post an update...for the user community that might encounter the same issue. Thank you for your response and insight. Regards, jb1809

Use of document function in XSL

We have an existing XSL document which uses a separate XML document for mapping of enumerated values. So in the XSL document, we have a line in our XSL as follows:
<xsl:variable name="enum-doc" select="document('enumerations.xml')"/>
Followed by a load of:
<xsl:key name="a-name" match="//enum[@name ='a-name']/enumeration" use="@value"/> etc.
We would like to use the existing XSL in BPEL. Is this possible? We have been able to deploy the mapping XML file with our BPEL process, but the XML mapping file is not beinig picked up by our XSL, so in our output we have a lot of missing enumerated values.
Any suggestions?
Thanks,
ma7asw

We managed to resolve the problem (We were using the wrong namespace in the XML mapping file).
So to confirm, it is possible to use the document function in an XSL transform within a BPEL process.
ma7asw

Secondary XML source via document() function

Similar Messages

Maybe you are looking for