Tool to transform XSL-FO to IDML

Hi,
is there a tool, a script or a plugin to transform a XSL-FO to IDML?
Thanks for any helps!

Here is a clue for you to follow:
https://code.google.com/p/ickmull/

Similar Messages

Tool for creating xsl for .xsql

I am looking for tool that will give me the
default code for xsl base on a .xsql file as imput.
What I am looking for is a xsl designer.
null

If you are doing HTML you can just start with a well-formed HTML file and:
(1) Add the xsl namespace to the top element,
(2) Add in <xsl:for-each> tags where you
need to loop
(3) Add in <xsl:value-of> tags where
you want to plug-in values.
<html xmlns:xsl="http://www.w3.org/1999/XSL/Transform xsl:version="1.0">
<body>
<xsl:for-each select="ROWSET/ROW">
<tr>
<td><xsl:value-of select="ENAME"/></td>
<td><xsl:value-of select="SAL"/></td>
</tr>
</xsl:for-each>
</body>
</html>
That's it. We don't yet offer an XSL visual editor.
null

CAN'T CREATE or Modify ESB PROJECT ROUTER TRANSFORM/XSL FILE

I have a problem that started today. I did not have a problem last Friday. I am working on an ESB Project/program using JDeveloper 10.3.1.2. I
have a router service that has 2 routing rules. Today when I went to edit the transforms/XSL files it will not show the design view and gives me the error message: "Required attribute version missing from element xsl:stylesheet". In the source view I can see that in any one of my xsl files it has "version="1.0". I tried to delete and recreate the transform files and I still get the same problem (only this time it will not even save the mappings). If I try to validate the XML file Jdeveloper hangs and has to be killed. I tried rebooting my machine and that did not help. I went to another project that I hadn't worked on in 2 weeks and tried to look at some routing service transforms and got the same error message when I tried to display them.
I don't know what is going on. Anyone ever have this problem?
Nick

Strange but the problem seems to have just gone away on its own!

Where to put the Transform.xsl File

Good evening!
I am trying to execute a bpel:doXslTransform(xslURI,$a) and i dont know where to put the transform.xsl file for this operation.
Can anybody tell me?
Greetz,
RaRu

It needs to be in the same folder as the .bpel process - the bpel folder of your project.
Hope this helps,
Shanmuhanathan Thiagaraja

Using xsl document function in transform xsl

I'm trying to use an external xml document in an xsl transform that's used in a Transform activity in an 11g BPEL process:
<xsl:variable name="plants" select="document('plantTransposeLookup.xml')/plants"/>
I need to load up the document to use it in a lookup to get replacement values for a key.
This works fine in JDev, but not when I deploy it to the server.
The error I get when I run it is:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22021: (Error) Error parsing external document: 'no protocol: plantTransposeLookup.xml'.. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
I've also gotten:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22021: (Error) Error parsing external document: 'Unsupported feature: 'document(''), when stylesheet built using InputStream, Reader'.
I've also tried using the ora:doc function:
<xsl:variable name="plants" select="ora:doc('plantTransposeLookup.xml', 'plants')"/>
......but this doesn't work in JDev and is also erroring off on the server with:
The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: XML-22016: (Error) Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Does anyone know how to actually import an xml doc into a mapper??? I must be doing something stupid.
Thanks for any help.

In OSB, document() function needs absolute path of the XML file. So if you want to access the XML document for lookup, you need to put the XML file on the server itself and use the path of the XML file.
Although this is not a correct approach for managing lookups in OSB. The resource of XML Document type are not to be used for such use cases. What you can do is create a XQuery which can server as DVM.
Here is an example on how to use DVMs in OSB:
https://blogs.oracle.com/christomkins/entry/domain_value_maps_in_oracle_se
If you dont want to use XQuery and want to rely only on XSLT, then within the same XSLT document create a separate template which can store all the lookup data.

Java Transform XSL not appending namespaces

Hello !
I have a string
<dataroot><xiMsgHeader><SeqID>2</SeqID><SequenceNo>LST000000000000001</SequenceNo>...</xiMsgHeader></dataroot>
and style sheet
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="xml" version="1.0" indent="yes" />
<xsl:template match="dataroot">
     <STANDARDMESSAGE xmlns="http://abc.com/sap/xi/R3FI/lst/ap">
     <xsl:apply-templates select="xiMsgHeader"/>
</STANDARDMESSAGE>
</xsl:template>
<xsl:template match="xiMsgHeader">
     <STANDARDMESSAGEHEADER xmlns="http://abc.com/sap/xi/R3FI/lst/ap">
          <SEQUENCENUMBER><xsl:value-of select="SequenceNo"/></SEQUENCENUMBER>
          <CORRELATIONID><xsl:value-of select="SequenceName"/></CORRELATIONID>
          <SYSTEM><xsl:value-of select="SystemName"/></SYSTEM>
          <RETRANSMIT><xsl:value-of select="ReTrans"/></RETRANSMIT>
     </STANDARDMESSAGEHEADER>
     <STANDARDMESSAGEBODY xmlns="http://abc.com/sap/xi/R3FI/lst/ap">
          <DT_ACCOUNT_PAYABLE xmlns="http://abc.com/sap/xi/R3FI/lst/ap">
               <xsl:apply-templates select="xiMsgDocHeader[1]"/>
          </DT_ACCOUNT_PAYABLE>
     </STANDARDMESSAGEBODY>
</xsl:template>
and then I run java tranform provided with jdk1.4.2.10
now you can see that stylesheet says that for
<dataroot> create a tag <STANDARDMESSAGE xmlns="abc.com/sap/xi/R3F!/lst/ap">
and for
<xiMsgHeader> create a tag <STANDARDMESSAGEHEADER xmlns="http://abc.com/sap/xi/R3FI/lst/ap">
but the result that I get is
<?xml version="1.0" encoding="UTF-8"?>
<STANDARDMESSAGE xmlns="http://awb.com.au/sap/xi/R3FI/lst/ap">
<STANDARDMESSAGEHEADER>
<SEQUENCENUMBER>LST000000000000001</SEQUENCENUMBER>
</STANDARDMESSAGEHEADER>
</STANDARDHEADER>
so my question is that why tranform is writing xmlns vales of child tag of main tag.
Can anybody suggest me what is going wrong.

Looks okay to me. I suppose you don't know that the namespace declared on an element also applies to all that element's children.

Selection tool not transforming rectangles but works fine with other shapes

I can't transform rectangle shapes with the selection tool. I've already tried showing the bounding box (command+shift+B), but it still doesn't work. I have no transforming issues with any of the other shapes, just the rectangles. Please help!

2bcris,
The Live Rectangle bug which is limited to the MAC versions starting with 10.7 and 10.8, but not 10.9 (Mavericks).
So a switch to Mavericks with a reinstallation might be the way to solve it here and now.
To get round it in each case, it is possible to Expand the Live Rectangles to get normal old fashioned rectangles, or to Pathfinder>Unite, or to use the Scale Tool.
A more permanent way round that is to create normal old fashioned rectangles, after running the free script created by Pawel, see this thread with download link:
https://forums.adobe.com/thread/1587587

Move tool "Show transform controls" with a type layer

I just recently figured this "show transform controls" option with the Move Tool and while trying it out, I noticed it works differently with type layers than others.
On regular bitmap layers it moves, resizes and rotates as supposed, but with type layer it jumps to "free transform" -function when trying to do anything with the transform controls. Causing the tool to drop and the anchor points change place (from text outline to text box?).
Is this normal behaviour or is there something I don't get?

Yes, being able to assign shortcuts to UI elements would be a major productivity jump in several cases! I tought that it
was the advantage of the object-oriented programming, but I my coding abilities stop at "20 go to 10"...

Documentation tool for xsql-xsl-xml ??

Hi,
can anybody tell me if there is a good tool for documenting XSQL / XML / XSL Projects ?
Like JavaDoc or any XREF programms?
Thank you
Thomas
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Thomas Viohl ([email protected]):
Hi,
can anybody tell me if there is a good tool for documenting XSQL / XML / XSL Projects ?
Like JavaDoc or any XREF programms?
Thank you
Thomas<HR></BLOCKQUOTE>
I recommend you take a look to XML Spy http://www.xmlspy.com
null

Stuck on Hand Tool during Transform!

Help! I'm trying a simple transform of the content of a layer's image and no matter what I do it's stuck on the hand tool and will not move or effect the art in any way.
What's going on? I tried a new file and same thing. Never had this happen before.
Screen shot attached.
Many thanks,
Seth

It looks as though you are on the Rotate View tool that is nested with the Hand Tool. Switch to the Hand tool and see if that solves the problem.

Selection Tool - free transform

So I was working on some wireframes, no problem – came back and when I'm selecting any objects I don't get the little rotate option in the corners, can't click and drag to increase/decrease sizes... anyone know what's going on? Installed all updates, restarted comp, nothing :S
I'm running CS5.

Thaaaank you! Don't know when the hell I hit cmnd/shift/B!

Error in IDML java tool

Hi
java tool which convert xsl file to corresponding IDML file giving me an error in tokenize function.
As far as my knowledge is concern I think it will be producing through saxon jar file which is comprised in Jing folder in SDK.
Could any one help me to know that which version of saxon is used in InDesign CS4 windows SDK or if that is due to other resion what it is ??
Mac

You should ask this in the SDK forum: http://forums.adobe.com/community/indesign/indesign_sdk

How to use an .xsl file to transform input XML to re-formatted output XML?

Hello,
I have a .xml file from a report that I want to use a stylesheet to transform into a different .xml format.
I am reading that I can create a .xsl file to read my input and then transform it to a new output .xml file.
How do I load this into the Apps?
I tried creating a template definition and loading the .xsl in as type 'XSL-TEXT' and also, I added
<?xml-stylesheet type="text/xsl" href="Transform.xsl"?> to my xml data source. The output looked the same as the input.
Has anyone done this before? Any suggestions would be great!
Thanks
-CC

This is how I use e4x with HTTPService:
import mx.collections.XMLListCollection;
import mx.rpc.events.ResultEvent;
[Bindable] private var claimsXLC:XMLListCollection;
private function claimsHandler(evt:ResultEvent):void{
claimsXLC = new XMLListCollection(evt.result..claim as XMLList);
XML data is being returned, but I use XMLList to create the XMLListCollection.
If this post answers your question or helps, please mark it as such.

XSL Transformation between arrays

Dear all
I create to XSD for my variables:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://www.asre-andishe.com/Inspec/General"
targetNamespace="http://www.asre-andishe.com/Inspec/General"
elementFormDefault="qualified">
<xsd:complexType name="AgentArrayType">
<xsd:sequence>
<xsd:element name="Agent" type="ns:AgentType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AgentType">
<xsd:sequence>
<xsd:element name="user" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Agent" type="ns:AgentType"></xsd:element>
<xsd:element name="AgentsArray" type="ns:AgentArrayType"></xsd:element>
</xsd:schema>
and the other one:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://www.asre-andishe.com/Inspec/DetermineInspec/retrive/relam"
targetNamespace="http://www.asre-andishe.com/Inspec/DetermineInspec/retrive/relam"
elementFormDefault="qualified">
<xsd:complexType name="RelamAgentType">
<xsd:sequence>
<xsd:element name="user" type="xsd:string" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="RelamAgents" type="ns:RelamAgentType"></xsd:element>
</xsd:schema>
I create two empty variable and then initialized the second variable
<RelamAgents>
<user>john</user>
<user>david</user>
<user>jack</user>
</RelamAgents>
after that i use a transformation XSL and the second variable has been filled without no problem.
<AgentsArray>
<ns0:Agent>
<ns0:user>john</ns0:user>
</ns0:Agent>
<ns0:Agent>
<ns0:user>david</ns0:user>
</ns0:Agent>
<ns0:Agent>
<ns0:user>jack</ns0:user>
</ns0:Agent>
</AgentsArray>
but when i fill the first variable by receiving the output parameter from a service call, the XSL transformation did not work at all and the second variable remains empty.
I have checked the first variable and i am sure that it is not null and it has the same vale:
<RelamAgents>
<user>john</user>
<user>david</user>
<user>jack</user>
</RelamAgents>
Would anybody please help me with this problem?
Thank you very much

Hi,
receiving the output parameter from a service call, the XSL transformation did not workNamespaces... Check the namespaces the service call is using and see if they match with the XSL is expecting...
Cheers,
Vlad

XSL transformation not working

Hi!
I am having problems when trying to generate XSL transformation from XML to XML (where XML output is actually XHTML). It always fails executing <xsl:callTemplate name="something", when <xsl:callTemplate /> is executed from another <xsl:template> which is also called with <xsl:callTemplate. Version of database is 10.2.0.4.0, received error is: ORA-00604: invalid character value 'burek' for attribute 'name'.
Transformation is working in Java and Altova XMLSpy.
PL/SQL code:
procedure process_xsl(p_xml in clob, p_xsl in clob, p_result out clob) is
w_xsl_proc dbms_XSLProcessor.Processor;
w_xsl_ss dbms_XSLProcessor.Stylesheet;
w_dom_xsl dbms_xmldom.DOMDocument;
w_dom_xml dbms_xmldom.DOMDocument;
w_parser dbms_xmlparser.Parser;
begin
--xml in xsl iz cloba v DOMDocument
w_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(w_parser, p_xml);
w_dom_xml := dbms_xmlparser.getDocument(w_parser);
dbms_xmlparser.freeParser(w_parser);
w_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(w_parser, p_xsl);
w_dom_xsl := dbms_xmlparser.getDocument(w_parser);
dbms_xmlparser.freeParser(w_parser);
--xsl procesiranje
w_xsl_proc := dbms_XSLProcessor.newProcessor;
w_xsl_ss := dbms_XSLProcessor.newStylesheet(w_dom_xsl, null); <-- Here error is received
END;
Stylesheet:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"></xsl:output>
     <xsl:decimal-format name="dec" decimal-separator="," grouping-separator="."/>
     
     <xsl:variable name="einvoiceIssuerCode" select="'II'"></xsl:variable>
     <xsl:variable name="einvoiceRecipientCode" select="'IV'"></xsl:variable>
     <xsl:variable name="einvoiceIssueLocationCode" select="91"></xsl:variable>
     <xsl:variable name="einvoiceIssueDateCode" select="137"></xsl:variable>
     
     <xsl:variable name="einvoiceNumber" select="/IzdaniRacunEnostavni/Racun/GlavaRacuna/StevilkaRacuna/text()"></xsl:variable>
     
     *<xsl:template name="burek"> *
          <xsl:text>TEST</xsl:text>
     </xsl:template>
     
     <xsl:template name="einvoice">
          <html xmlns="http://www.w3.org/1999/xhtml">
          <head>
               <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
               <title>Vizualizacija e-računa št. </title>
               <xsl:call-template name="burek"></xsl:call-template>
          </head>
          <body>
          </body>
          </html>
     </xsl:template>
     
     <xsl:template match="/">
*          <xsl:call-template name="einvoice"></xsl:call-template> *
     </xsl:template>
</xsl:stylesheet>
XML document
<?xml version="1.0" encoding="UTF-8"?>
<IzdaniRacunEnostavni>
<Racun Id="data">
<GlavaRacuna>
<VrstaRacuna>380</VrstaRacuna>
<StevilkaRacuna>1205019908211</StevilkaRacuna>
<FunkcijaRacuna>9</FunkcijaRacuna>
</GlavaRacuna>
<DatumiRacuna>
<VrstaDatuma>137</VrstaDatuma>
<DatumRacuna>2012-05-07T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-28T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-05-27T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-03-28T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-26T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<DatumiRacuna>
<VrstaDatuma>263</VrstaDatuma>
<DatumRacuna>2012-04-27T00:00:00.0Z</DatumRacuna>
</DatumiRacuna>
<Lokacije>
<VrstaLokacije>91</VrstaLokacije>
<NazivLokacije>Ljubljana</NazivLokacije>
</Lokacije>
</Racun>
</IzdaniRacunEnostavni>
Edited by: 938026 on 01-Jun-2012 00:35

Hi,
I think your problem lies in the <title>. You are using non UTF-8 characters in the title (š), but you marked your XML as UTF-8. So change the title to have unicode charaters and it will work.
Herald ten Dam
http://htendam.wordpress.com

Tool to transform XSL-FO to IDML

Similar Messages

Maybe you are looking for