Universal xsl(:fo) stylesheet

Hi out there!
Just a short one: Trying to generate a *.pdf file, using xsl:fo and FOP technology, i need ONE common xsl:fo stylesheet, fitting to different xml files of different structures and containing different elements and tags. That why i would call it "universal". Don`t need a nice one - just looking for suggestions. Piece of code anybody?
Thanks for paying attention!
Best regards, Jens

take a glance to these two url they are very usefull
http://www.onjava.com/pub/a/onjava/2002/10/16/fop.html
http://xml.apache.org/fop/

Similar Messages

XSL-FO Stylesheets (Oracle XSLT processor via command line)

How does one go about editing BIP XSL-FO stylesheets converted from the MSWord plug in by using external tools?
The converted files have many, many calls to Oracle functions that are unrecognized by the editing tools.
We are using Stylus Studio and are getting errors on functions calls such as:
<xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,' ',$_XDOCURMASKS,' ',$_XDONFSEPARATORS))"/>
This is but one example of course. There are many calls in each template and they are quite varied.
Is there a way to "register" these with the tools so that they can call them (via tnsnames?). Even to having them ignored would be preferable to having the previewer completely fail.
Scott

Hi Scott.
there's a JavaAPI which you can use. So it's not really a command line interface, but perhaps it can fullfill you requirements.
Regards
Rainer

Modifying the XSL-FO stylesheet.

I currently have created my own custom .rtf and I am exporting it to xsl-fo stylesheet.
We have some flex fields in tables that are the same column name, example attribute1 in the Line Table and Shipment Line Table. When attribute1 from the line table is null it pulls the data that is in the Shipment line attribute1 column.
I have properly ended my groups with <?end for-each?> so I would think it would not be pulling the information from another group.
I was looking through Oracle's Standard PO xsl-fo stylesheet and noticed that it places a path in front of the form field name.
Example:
<xsl:value-of select="$ROOT_OBJ/CURRENCY_CODE" /> or some have BOILER_PLATE_MESSAGES_OBJ
When I look at the exported style sheet from the custom created rtf it displays: <xsl:value-of select=".//ATTRIBUTE1" xdofo:field-name="ATTRIBUTE1" />
I'm not sure if I have to establish the path in the stylesheet or if I can write something in the .rtf saying... if null then null. Can someone please explain what is going on? I'm thinking I have to put the path before the attribute but I'm not sure how this is supposed to work.
Thanks,
Jessica
Edited by: Jessica on Mar 24, 2009 3:06 PM

Jessica
See this thread:
Logo on a Standard Purchase Order Stylesheet
It's long but contains lots of good info on the EBS PO.
1. You no longer need to create an XSL-FO version of your template, you can use the rtf direct, see the patch mentioned in the above thread.
2. I suspect your XML does not contain the attribute1 element when it is null and the .//attribute1 will cause the process to look through your XML structure until it comes to the first occurrence, hence it gets the one from the level (or levels) below.
3. The thread, above, explains how you can setup debugging to allow you to get the XML for your PO, which makes it a lot easier to debug issues such as this.
4. <?if:ATTRIBUTE1?> will determine if the attribute exists so if you wrap this around the attribute1 element you should only get it if it exists. Like you say you might still have to define the path to attribute1 more fully and point 3 above will help you to determine the full path more easily.
Hope this helps.
Regards,
Dave

Dynamic Logo file names in PO XSL-FO stylesheet

We have different company logo files for different operating units. Hence , we require to use a dynamic logo file name in XSL-FO template.
When I use the below for a single file it works.
<fo:inline>
<fo:external-graphic content-width="50pt" content-height="50pt" src="url({'${OA_MEDIA}/Logo_medium_COMCEL.jpg'})" />
</fo:inline>
However, I would need to make the filename dynamic.
When a tried usng an xsl variable tos tore fielname, it didnt work.
Any pointers as to how we can achieve that would be helpful

Thanks for your quick reply Dave, I appreciate your time.
But I couldn't test the new template as I was neither able to create a new PO nor was able to run the PO Output for communication Report. When I tried to create a PO the Purchase Order form did not open saying I am not setup as an employee, even the PO Output for communication did not give any LOV for the PO's.
I tried to define employee name in the employee's login
information (System administrator/Security/User/Define) for my user, but some how my name doesn't appear in LOV. Any help is appreciated.
Thanks,
Sharmila

Add terms and conditions on last page of PO using XSL-FO stylesheet

Hi
I need to add terms and conditions on last page of PO pdf. I have changed the values for profile options PO;Terms and Conditions Filename and PO: In file path to the file name and filepath of my terms and conditions txt file. Do I have to make any changes to the stylesheet for it to be printed on the last page? if so, what are the changes to be made?
This is really urgent and I would appreciate any help.
Thanks,
Sharmila

Hi,
In main window &next-page& eq 0. condition does not work .
even &page& eq &formpages& may not work out not sure.So what you need to do is.
In the print program
just describe your internal table say lines v_lines
and in the loop put one count varaible say v_count
then in the script put condition as below.
if v_count eq v_lines.
/:NEW-PAGE pagename ( say last)
endif.
Reward points if useful.
Regards,
Nageswar

Unit Price Format in XSL-FO Code for Standard Purchase Order Printing

Hi All,
As I am new to XSL-FO, so i am not aware of doing XML,XSL-FO changes. I have an issue with the xsl-fo for standard po layout. My report layout gives ##,## instead of ##.## as my Unit Price. i.e. in the report for POs, it is showing unit price in the format as #,## eg: 0,32 or u can say like 1,70 instead it should show #.## something like 0.32 and 1.70 as my unit price. The piece of code related to unit price formatting in report as follows:
<xsl:choose>
<xsl:when test="(UNIT_PRICE,1,1 > 1) and (substring-before(UNIT_PRICE,',') > 0)">
<fo:table-cell xsl:use-decimal-format="euro2"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
<xsl:value-of select="format-number(substring-before(UNIT_PRICE,','),'#.###','euro2')"/>,<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) > 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) =''"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 1"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 2"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 3"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),3,1)) = 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,','),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,','),2,1)) = ''"><xsl:value-of select="((substring(substring-after(UNIT_PRICE,','),1,1))-(substring(substring-after(UNIT_PRICE,','),1,1)))"/></xsl:if>
          </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
<xsl:when test="(substring(UNIT_PRICE,1,1)=',')">
     <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
     <xsl:value-of select="UNIT_PRICE"/>
     </fo:block>
     </fo:table-cell>
</xsl:when>
<xsl:when test="(UNIT_PRICE,1,1 > 1) and (substring-after(UNIT_PRICE,'.') > 0)">
<fo:table-cell xsl:use-decimal-format="euro2"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
     <xsl:value-of select="format-number(substring-before(UNIT_PRICE,'.'),'#.###','euro2')"/>,<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) > 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) =''"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 1"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 2"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 3"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),3,1)) = 4"><xsl:value-of select="(substring(substring-after(UNIT_PRICE,'.'),1,5))"/></xsl:if>
<xsl:if test="(substring(substring-after(UNIT_PRICE,'.'),2,1)) = ''"><xsl:value-of select="((substring(substring-after(UNIT_PRICE,'.'),1,1))-(substring(substring-after(UNIT_PRICE,'.'),1,1)))"/></xsl:if>
     </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
<xsl:when test="(UNIT_PRICE,1,1 > 1 ) and (substring-after(UNIT_PRICE,',') ='') ">
<fo:table-cell xsl:use-decimal-format="euro"> <fo:table-cell xsl:use-attribute-sets="table.cell5"> <fo:block xsl:use-attribute-sets="form_data1">
<xsl:value-of select="format-number(UNIT_PRICE,'#,###.00','euro')"/>
          </fo:block>
     </fo:table-cell>
</fo:table-cell>
</xsl:when>
</xsl:choose>
PS: My decimal formats for euro and euro2 are:
<xsl:decimal-format name="euro" decimal-separator="," grouping-separator="."/>
<xsl:decimal-format name="euro2" grouping-separator="." NaN="0"/>
Any help or reply regarding this issue will be highly appreciated.
Regards,
Sumir

Hi Michele:
I can check out for you how to print page number in XSL-FO (There is an O'Reilly) book, but I think I help you better by recommending a different strategy - Don't write XSL-FO stylesheets. While Purchasing does not support RTF templates you can still write RTF templates and convert them to FO using the XML Publisher Template Builder for Word.
Download the matching Template Builder for Word (5.0) or XML Publisher Desktop 5.5 (includes the Template Builder) patch and then Create your template as an RTF template.
You can then EXPORT the template as XSL-FO stylesheet and upload as to Purchasing AS LONG AS THE VERSION OF THE DESKTOP and E-Businees Suite XML Publisher MATCH.
If you still want to write XSL stylesheet, you can just use the Template Builder to generate you the code and paste the code (e.g. for page numbers) into your stylesheet.
By the way - Purchasing will support RTF templates in future versions...
Hope that helps,
Klaus

XSL-FO for Standard Purchase Order, doesn't print page number

Hi,
I worked on XSL-FO code to custom the PDF output for Standard PO. Everything works great: I added company logo (in a different position of the standard commented code  ), i created new attribute sets to highlight some elements on the print, I added a footer with company details and document type and number (instead of placing this in the header, the costumer didn't like it where it was..)
OK. BUT: the page number at the bottom on the right isn't printed anymore. For example: if the PO page is n.1 of 2 pages, it comes only '12' and not Page 1 of 2. So i tought not to use the original template (tihs one)


<xsl:template name="pageNumber">
     <xsl:variable name="po_page">
     <xsl:value-of select="$BOILER_PLATE_MESSAGES_OBJ[MESSAGE='PO_FO_PAGE'][1]/TEXT"/>
     </xsl:variable>
     
     <xsl:variable name="string_before_page_num">
     
     <xsl:value-of select="substring-before($po_page,'Pag.;PAGE_NUM')"/>
     </xsl:variable>
     
     <xsl:variable name="string_after_page_num">
     
     <xsl:value-of select="substring-after($po_page,'/ ;PAGE_NUM')"/>
     </xsl:variable> ......
but inseriting a select just where I want the page num to be displayed (see code)
<fo:block xsl:use-attribute-sets="test_style" >
<xsl:value-of select="$BOILER_PLATE_MESSAGES_OBJ[MESSAGE='PO_FO_PAGE'][1]/TEXT"/>
                                                  </fo:block>
but this gave me as result 'Page &PAGE_NUM of &END_PAGE'.
Where did I do wrong?? It's like the PO_FO_PAGE message is not dinamically insered in the PDF. Hope I've been clear enough and somene can help me. Thaks in advance, Michele

Hi Michele:
I can check out for you how to print page number in XSL-FO (There is an O'Reilly) book, but I think I help you better by recommending a different strategy - Don't write XSL-FO stylesheets. While Purchasing does not support RTF templates you can still write RTF templates and convert them to FO using the XML Publisher Template Builder for Word.
Download the matching Template Builder for Word (5.0) or XML Publisher Desktop 5.5 (includes the Template Builder) patch and then Create your template as an RTF template.
You can then EXPORT the template as XSL-FO stylesheet and upload as to Purchasing AS LONG AS THE VERSION OF THE DESKTOP and E-Businees Suite XML Publisher MATCH.
If you still want to write XSL stylesheet, you can just use the Template Builder to generate you the code and paste the code (e.g. for page numbers) into your stylesheet.
By the way - Purchasing will support RTF templates in future versions...
Hope that helps,
Klaus

Imported DocBook stylesheet location for XSQL Page

Hi all,
I've got the following XSQL page which queries a DocBook document stored in XMLDB as a schema-based CLOB.
<?xml version = '1.0' encoding = 'UTF-8'?>

<page xmlns:xsql="urn:oracle-xsql" connection="jdbc/DBConnection1DS">
<xsql:query max-rows="1" null-indicator="yes" tag-case="lower">
SELECT extractValue(x.DOCBOOKS_DOC, '/book/part/title', 'xmlns="http://docbook.org/ns/docbook"') "BOOK_TITLE",
extract(x.DOCBOOKS_DOC, '/book/part/chapter/sect1/sect2', 'xmlns="http://docbook.org/ns/docbook"').getStringVal() "BOOK_CONTENT"
FROM DOCBOOKS_STORE x</xsql:query>
</page>
Which outputs the following:

     <page>
     <rowset>
     <row num="1">
<book_title>
This is a test string
</book_title>
     <book_content>
<sect2 xmlns="http://docbook.org/ns/docbook"><title>
This is sect2/title test text.
</title><para>
This is sect2/para test text.
</para></sect2>
</book_content>
</row>
</rowset>
</page>
The query runs fine (thanks to help from the XML DB forum). I'm now trying to use the docbook.xsl HTML stylesheet but I'm not sure of the following:
1) Where do imported stylesheets need to be stored for the XLST processor to find them and can we change the default location (DocBooks has loads of associated stylesheet includes)? I've tried several locations and corresponding hrefs but nothing seems to work.
2) Since the output contains a mixture of both DocBook and non-DocBook tags, I'm guessing/hoping that the XLST processor can parse the string extract and all what I would need to do is use is the <xsl:import/> and <xsl:apply-import/>. Is this correct?
Many thanks in advance.
George.

Just closing the loop on this one...
1) After more trial and error, I found that the XLST stylesheet need to be in the same location as the *.xsql page. To check, I wrote a simple XLST to output HTML rather than confuse the issue with applying the docbook imported stylesheets. This worked as expected with the resulting HTML output, bar the fact that I now have a security issue with my stylesheet sitting in the /PUBLIC_HTML folder. For the moment this is OK since the application is for internal prototyping purposes.
2) If I want the XLST processor to parse the underlying XML tags, then the data needs to be returned as XMLType and not a VARCHAR2 string which my <xsl:query extract().getStringVal())> does.
Unfortunately I now have an enviromental problem retrieving XMLType data through my XSQL query. I believe this has something to do with my JDBC driver and/or missing libraries.
Cheers

RTFProcessor produces invalid XSL-FO in WebLogic

I've been writing an application that uses the RTProcessor class to process an rtf file into XML, which I can then parse to information about the report layout.
While developing on tomcat this worked fine. However for production we will be deploying on WebLogic. WebLogic seems to be using a different XML parser that is stricter than tomcats so when using the application the XML parser throws an error when parsing the XSL-FO.
The problem is that XSL-FO is not valid XML as it contains an invalid character on the line:
<xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,'',$_XDOCURMASKS,'',$_XDONFSEPARATORS))"/>
So my first question is: Is there a way to stop this element from being generated in the XSL-FO? This seems to have been looked at in this thread but without much of a conclusion:
BI Publisher produces invalid XSL:FO stylesheet
My second question: I don't understand how Tomcat can parse the XML and WebLogic can't. I'm deploying the same code so I'd assumed it would be using the same parser. As a work around around is it possible to configure WebLogic to use the same parser as tomcat? The relevant code I'm using is posted below:
ByteArrayOutputStream templateOutputStream = new ByteArrayOutputStream();
               RTFProcessor rtfProcessor = new RTFProcessor(
                         new FileInputStream(template.getTemplateFile())
               rtfProcessor.setOutput(templateOutputStream);
               rtfProcessor.process();
               logger.debug(this.className + " - " + methodName +
                         ":#2 XSL-FO : " + templateOutputStream.toString());
               DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
               DocumentBuilder db = dbf.newDocumentBuilder();
               // parse using builder to get DOM representation of the XML file
               Document dom = db.parse(new ByteArrayInputStream(templateOutputStream.toByteArray()));
Thanks in advance.

Hi,
Thanks for your reply, After debugging the application carefully in Tomcat and Weblogic it became apparent that weblogic was using it's preferred XML parsers when parsing my XML.
In Tomcat has a different order or precedence for its class loader so it was parsing my XML with the oracle.xml package, Weblogic was instead using its own weblogic.xml parser. So I had to set up a weblogic-application.xml file to control this.
If you're right that the XML is valid, then this looks like there is a bug in the weblogic parser. I'm not at work at the moment but if you want more details I can get you them next week.
Thanks.

Help:displaying Arabic characters using XSL

How do I display static Arabic characters using XSL in a HTML page, from within a JSP?
I need to display a HTML page wherein static Arabic characters have to be shown. I use the following XSL document with static Arabic characters inside:
<?xml version = '1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html"/>
<xsl:template match="/">
<HTML>
<HEAD/>
<xsl:apply-templates/>
</HTML>
</xsl:template>

<xsl:template match="booklist">
<BODY BGCOLOR="#CCFFFF">
<H1>^GFcI cSGZOI
</H1>
<P> This will illustrate the transformation of XML file containing list of books to a HTML table form
</P>
<xsl:apply-templates/>
</BODY>
</xsl:template>
<xsl:template match="booklist/book">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="booklist/book/title">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="booklist/book/author">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="booklist/book/publisher"/>
<xsl:template match="booklist/book/price"> Price: $
<xsl:apply-templates/>
</xsl:template>
</xsl:stylesheet>
When I try to read the XSL document using an IO stream, like this,
InputStream is = getClass().getResourceAsStream("myXSLDocument.xsl");
XSLStylesheet stylesheet = new XSLStylesheet(inputStream, null);
from within a JSP, I get a null pointer exception as shown below:
java.lang.NullPointerException:
at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:175)
at mip.portlets._cardvalidaterportlet._cardentry._jspService(_cardentry.java:143)
at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java)
at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java)
at oracle.jsp.JspServlet.doDispatch(JspServlet.java)
at oracle.jsp.JspServlet.internalService(JspServlet.java, Compiled Code)
at oracle.jsp.JspServlet.service(JspServlet.java)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at oracle.portal.provider.v1.http.JspRenderer.renderBody(JspRenderer.java:133)
at oracle.portal.provider.v1.RenderManager.render(RenderManager.java:164)
at oracle.portal.provider.v1.http.ServletProviderResponse.showPortlet(ServletProviderResponse.java:510)
at oracle.portal.provider.v1.http.HttpProvider.dispatchProviderAction(HttpProvider.java:647)
at oracle.portal.provider.v1.http.HttpProvider.service(HttpProvider.java:383)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java, Compiled Code)
at org.apache.jserv.JServConnection.run(JServConnection.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
I have no problems parsing the same XSL containing static Arabic text using Transviewer beans' XSLTransformPanelSample class. This means that my XSL has no errors in it.
null

You need to use the correct and the same character encoding (charset) thorough the complete process.
Whenever you get question marks, then it means that the charset used does not recognize the bytes (which on its turn are apparently encoded by a different charset).
This is an important read, read it from top to bottom, preferably twice: [http://www.joelonsoftware.com/articles/Unicode.html].

Convert XSL-FO template back to RTF template

Report's layout that I have to create has strict size requirements (e.g. page margins, cell sizes and so on).
I created a simple RTF template using MS Word. RTF template meets this size requirements but when I print my report using Acrobat Reader report looks different.
I know that this happens because at runtime BI Publisher converts report to XSL-FO automatically to XSL-FO and only after that it renders pdf.
In order to meet thissize requirements I converted my RTF template to XSL-FO stylesheet using Template Builder and changed appropriate cells and margins etc. manually.
And everything works well but now I know that there will be a lot of changes in this report's layout (e.g. several complex tables will be added).
It's quit difficult for me to create tables in XSL-FO. And so my question is
HOW CAN I CONVERT MY XSL-FO STYLESHEET BACK INTO RTF FORMAT WITH ALL THE LOGIC IT HAS?
BI Publisher Release 10.1.3.4
Thanks.
Edited by: Ruslan on 20.07.2011 5:22

No way , you can't go back.

Help-XML report which uses XSL-FO and XSL-FO contains OAF VO

Hello All,
I want to know functionality of one XML report developed by Oracle.
From one oracle form after clicking one button, it is populating PDF file output of report to open.
Here is what Oracle has done to achieve this:
On the click of button on oracle form, it is calling one OAF form. (fnd_function.execute(function_name=> 'ONT_PRINT').
This OAF form contains nothing on its layout. One CO (File is attached) and AM is attached to this OAF page.
In CO, may be it is somehow it is calling RTF file.
I got the RTF file from XML publisher, RTF imports one XSL-FO (ONTBSAEXSL is a Template of XSL-FO type in Oracle apps in XMP Publisher administrator responsibility) file using <?import:xdo://ONT.ONTBSAEXSL.en.00/?>
In the XSL file, OAF View Objects has been used like,
<xsl:variable name="LinesVO" select="/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow"/>
What is the meaning of " /*/HeaderVO/HeaderVORow/LinesVO "? Does it mean LinesVO is getting called by HeadersVO. But in OAF this never happens.
I want to add some columns in the RTF from LinesVO. But "Unit price" is not available in LinesVO.
Do I need to extend this VO in JDeveloper and upload the .JPX and extended VO files?
I have done extending the VO, but no use..
So,
In short my question is,
If I extend the VO LinesVO by XXLinesVO, then will this <xsl:variable name="LinesVO" select="/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow"/>
statement in XSL-FO use my XXLinesVO or LinesVO?
Regards,
Parag

I want to customize one RTF template by adding some columns. This RTF imports one XSL-FO stylesheet.
RTF has tags like <?for-each:/*/HeaderVO/HeaderVORow/LinesVO/LinesVORow?>
and XSL file has tags like <xsl:variable name="InternalOrgName" select="/*/HeaderVO/HeaderVORow/InternalOrgVO/InternalOrgVORow/Name"/>
If I want to add one colun in LinesVO, what are all things I need to do?
I customized it by adding the new columns through JDeveloper and extending the VO's and substituting them, importing JPX and bounced apache.
But the XSL-FO file is very strange (attached herewith). Those changes are not reflecting in report even after extension.

Problem with Apex layout report XSL-FO build by bi-publisher word plug-in

Hi all...
this is what I should do:
- generate a layout with bi-publisher word plug-in ---> it's ok
- export this layout in xsl-fo stylesheet --> it's ok.
- create an apex layout report with xsl-fo stylesheet --> it's ok.
- create an apex query report with the above layout
At this point when I test the report I have a corrupted pdf file....
can you help me!!!
Many thanks
araf

Hi,
do you use BI Publisher or another XSL-FO-Engine? Is BI Publisher running? Is it configured in the instance settings?
Regards
Rainer

HowTo Set the xml-stylesheet processing instruction node?

Hi,
Can anyone tell me via PLSQL XMLDOM object what method or attribute to set or howto specify the xml-stylesheet value at the time of generation of the xml document?
eg
<?xml version = '1.0'?>
<?xml-stylesheet type="text/xsl" href="reporthtml.xsl"?>
<Report>
<Title>ABC Report</Title>
</Report>
Currently my XML just comes out as
<?xml version = '1.0'?>
<Report>
<Title>ABC Report</Title>
</Report>
and I want to add the stylesheet reference....
<?xml-stylesheet type="text/xsl" href="reporthtml.xsl"?>
Any help is appreciated...

A COTS product builds the XML and inserts the respective xsl (xml:stylesheet) file name to be used for transforming the xml. I am trying to interrupt this xml and make some updations on an element and finally send the updated xml to the stream.
For the above process, I parse the input XML using DOMParser and update the elements (some internal elements). While I view the final XML that would be passed to the stream, I found the <?xml-stylesheet... PI is missing.
I somehow managed using a temp fix by doing the below. I manually pulled the PI using document.getFirstChild().getNodeValue() and reconstructed the PI and inserted it to the outgoing XML. This needs to be done every time. This might run into problems when more than one PI is used in the XML.
If the parsed XML could get the PI along with it the above problem could be resolved.
Is there any property that could be set on the parser (prior to parsing) to resolve the issue?.

Usage of an xsl in xi ?

Hi
I need to create a message type and the informstion that i have is the documentation of the fields (elements) for that message , it is really very complex and big one. I also have an xsl , how this could help me building my message type?
Thanks

Hi,
XSL (Extensible Stylesheet Language), formerly called Extensible Style Language, is a language for creating a style sheet that describes how data sent over the Web using the Extensible Markup Language (XML) is to be presented to the user.
to simplify
XSL is nothing but the file that is linked to XSLT mapping.
XSL - http://w3schools.com/xsl/xsl_languages.asp
I think you can use that xsl file in your XSLT mapping.
You can only use XSDs,DTDs or WSDLs for your message types.
Thanks,
Vijaya.

Universal xsl(:fo) stylesheet

Similar Messages

Maybe you are looking for