eXist › exist-open

Memory leaks on XEP rendering process

Classic

List

Threaded

22 messages Options

Yuwono Gunawan

Memory leaks on XEP rendering process

Hi All,

I had this xquery which will render a PDF using XEP and file module. I am running eXist as a service.

The xquery work fine when only rendering a PDF. However when rendering third or may be second one, the process is freeze.

The fo file size is quite big which is 16MB or more. I am suspicious on XEP "cleanup" method because this statement bellow. However if it is correct that method cause the problem, how can I clean up the resource?

To reclaim disk space and memory taken by the caches, you should call a cleanup method from time to time between formatting sessions:
void cleanup()
Note:
This method is not thread-safe: it should be called when no formatting methods are running from this object. Otherwise, ongoing formatting sessions may fail.

Does anybody know why it fails on the third one or sometimes it failed on the second PDF rendering process? How can I fix this issue?

xquery version "1.0";

declare namespace fo="http://www.w3.org/1999/XSL/Format";
declare namespace rx="http://www.renderx.com/XSL/Extensions";
declare namespace request="http://exist-db.org/xquery/request";
declare namespace file="http://exist-db.org/xquery/file";
declare namespace system="http://exist-db.org/xquery/system";
declare namespace util="http://exist-db.org/xquery/util";
declare namespace response="http://exist-db.org/xquery/response";
declare namespace langSYS="java:java.lang.System";
declare namespace utilProps="java:java.util.Properties";
declare namespace ioOS="java:java.io.OutputStream";
declare namespace ioBOS="java:java.io.BufferedOutputStream";
declare namespace ioFOS="java:java.io.FileOutputStream";
declare namespace ioFile="java:java.io.File";
declare namespace ioPS="java:java.io.PrintStream";
declare namespace netURL="java:java.net.URL";

declare namespace xmlStream="java:javax.xml.transform.stream.StreamSource";
declare namespace xepFormat="java:com.renderx.xep.FormatterImpl";
declare namespace xepTarget="java:com.renderx.xep.FOTarget";
declare option exist:serialize "method=xhtml media-type=text/html";


declare function local:get_xmldoc() as element()
{

   let $xslFO:= doc($xslDocument),
   $foNode := transform:transform($ditaMapNode, $xslFO, ()),
   $isFoSaved := system:as-user($eXistUsername, $eXistPassword,file:serialize($foNode, $FOFileName,())),

   $source := xmlStream:new($FOFileName),
   $pdfOutputStream := ioBOS:new(ioFOS:new($pdfFile)),


   $foTarget := xepTarget:new($pdfOutputStream, "PDF"),
   $options := utilProps:new(),
   $optionsSet := utilProps:setProperty($options,"CONFIG", $xepConfig),
   $xep := xepFormat:new($options),
   $render := xepFormat:render($xep,$source,$foTarget),
   $flush2 := ioBOS:flush($pdfOutputStream),
   $flush2 := ioBOS:close($pdfOutputStream),

   $pdfContent := system:as-user($eXistUsername, $eXistPassword, file:read-binary(concat("file:///", $pdfFile))),
   $pdfResult := xmldb:store($tmpCol, $pdfFileName, $pdfContent),
   $isFoSaved := xmldb:store($tmpCol, $ditaMapFileName, $ditaNode2)
      $cleanup := xepFormat:cleanup($xep),


   return

if ($format = "fo")

then <html><body onload="location.href='{$urlBase}{concat($tmpCol,$pdfFileName)}'"/></html>

(:then <t>{$selectedDocType}</t>:)

else $ditaMapNode
};

local:get_xmldoc()

Thank you,

Yuwono

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

Yuwono Gunawan

Memory leaks on XEP rendering process

Hi All,

I had this xquery which will render a PDF using XEP and file module. I am running eXist as a service.

The xquery work fine when only rendering a PDF. However when rendering third or may be second one, the process is freeze.

To reclaim disk space and memory taken by the caches, you should call a cleanup method from time to time between formatting sessions:
void cleanup()
Note:
This method is not thread-safe: it should be called when no formatting methods are running from this object. Otherwise, ongoing formatting sessions may fail.

Does anybody know why it fails on the third one or sometimes it failed on the second PDF rendering process? How can I fix this issue?

xquery version "1.0";

declare namespace fo="http://www.w3.org/1999/XSL/Format";
declare namespace rx="http://www.renderx.com/XSL/Extensions";
declare namespace request="http://exist-db.org/xquery/request";
declare namespace file="http://exist-db.org/xquery/file";
declare namespace system="http://exist-db.org/xquery/system";
declare namespace util="http://exist-db.org/xquery/util";
declare namespace response="http://exist-db.org/xquery/response";
declare namespace langSYS="java:java.lang.System";
declare namespace utilProps="java:java.util.Properties";
declare namespace ioOS="java:java.io.OutputStream";
declare namespace ioBOS="java:java.io.BufferedOutputStream";
declare namespace ioFOS="java:java.io.FileOutputStream";
declare namespace ioFile="java:java.io.File";
declare namespace ioPS="java:java.io.PrintStream";
declare namespace netURL="java:java.net.URL";

declare namespace xmlStream="java:javax.xml.transform.stream.StreamSource";
declare namespace xepFormat="java:com.renderx.xep.FormatterImpl";
declare namespace xepTarget="java:com.renderx.xep.FOTarget";
declare option exist:serialize "method=xhtml media-type=text/html";


declare function local:get_xmldoc() as element()
{

   let $xslFO:= doc($xslDocument),
   $foNode := transform:transform($ditaMapNode, $xslFO, ()),
   $isFoSaved := system:as-user($eXistUsername, $eXistPassword,file:serialize($foNode, $FOFileName,())),

   $source := xmlStream:new($FOFileName),
   $pdfOutputStream := ioBOS:new(ioFOS:new($pdfFile)),


   $foTarget := xepTarget:new($pdfOutputStream, "PDF"),
   $options := utilProps:new(),
   $optionsSet := utilProps:setProperty($options,"CONFIG", $xepConfig),
   $xep := xepFormat:new($options),
   $render := xepFormat:render($xep,$source,$foTarget),
   $flush2 := ioBOS:flush($pdfOutputStream),
   $flush2 := ioBOS:close($pdfOutputStream),

   $pdfContent := system:as-user($eXistUsername, $eXistPassword, file:read-binary(concat("file:///", $pdfFile))),
   $pdfResult := xmldb:store($tmpCol, $pdfFileName, $pdfContent),
   $isFoSaved := xmldb:store($tmpCol, $ditaMapFileName, $ditaNode2)
      $cleanup := xepFormat:cleanup($xep),


   return

if ($format = "fo")

then <html><body onload="location.href='{$urlBase}{concat($tmpCol,$pdfFileName)}'"/></html>

(:then <t>{$selectedDocType}</t>:)

else $ditaMapNode
};

local:get_xmldoc()

Thank you,

Yuwono

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

Dan McCreary

Re: Memory leaks on XEP rendering process

In reply to this post by Yuwono Gunawan

Hello Yuwono,

I am not sure that most of the people on this list are familiar with XEP. Perhaps you could give us some background. I assume it is some third party library for doing XSL-FO to PDF conversion?

http://www.renderx.com/tools/xep.html

Can you tell us the relationship of XEP to eXist in your context?

Thanks - Dan

On Wed, Jan 12, 2011 at 5:04 PM, Yuwono Gunawan <[hidden email]> wrote:

Hi All,

I had this xquery which will render a PDF using XEP and file module. I am running eXist as a service.

The xquery work fine when only rendering a PDF. However when rendering third or may be second one, the process is freeze.

The fo file size is quite big which is 16MB or more. I am suspicious on XEP "cleanup" method because this statement bellow. However if it is correct that method cause the problem, how can I clean up the resource?

To reclaim disk space and memory taken by the caches, you should call a cleanup method from time to time between formatting sessions:
void cleanup()
Note:
This method is not thread-safe: it should be called when no formatting methods are running from this object. Otherwise, ongoing formatting sessions may fail.

Does anybody know why it fails on the third one or sometimes it failed on the second PDF rendering process? How can I fix this issue?

xquery version "1.0";

declare namespace fo="http://www.w3.org/1999/XSL/Format";
declare namespace rx="http://www.renderx.com/XSL/Extensions";
declare namespace request="http://exist-db.org/xquery/request";
declare namespace file="http://exist-db.org/xquery/file";
declare namespace system="http://exist-db.org/xquery/system";
declare namespace util="http://exist-db.org/xquery/util";
declare namespace response="http://exist-db.org/xquery/response";
declare namespace langSYS="java:java.lang.System";
declare namespace utilProps="java:java.util.Properties";
declare namespace ioOS="java:java.io.OutputStream";
declare namespace ioBOS="java:java.io.BufferedOutputStream";
declare namespace ioFOS="java:java.io.FileOutputStream";
declare namespace ioFile="java:java.io.File";
declare namespace ioPS="java:java.io.PrintStream";
declare namespace netURL="java:java.net.URL";

declare namespace xmlStream="java:javax.xml.transform.stream.StreamSource";
declare namespace xepFormat="java:com.renderx.xep.FormatterImpl";
declare namespace xepTarget="java:com.renderx.xep.FOTarget";
declare option exist:serialize "method=xhtml media-type=text/html";


declare function local:get_xmldoc() as element()
{

   let $xslFO:= doc($xslDocument),
   $foNode := transform:transform($ditaMapNode, $xslFO, ()),
   $isFoSaved := system:as-user($eXistUsername, $eXistPassword,file:serialize($foNode, $FOFileName,())),

   $source := xmlStream:new($FOFileName),
   $pdfOutputStream := ioBOS:new(ioFOS:new($pdfFile)),


   $foTarget := xepTarget:new($pdfOutputStream, "PDF"),
   $options := utilProps:new(),
   $optionsSet := utilProps:setProperty($options,"CONFIG", $xepConfig),
   $xep := xepFormat:new($options),
   $render := xepFormat:render($xep,$source,$foTarget),
   $flush2 := ioBOS:flush($pdfOutputStream),
   $flush2 := ioBOS:close($pdfOutputStream),

   $pdfContent := system:as-user($eXistUsername, $eXistPassword, file:read-binary(concat("file:///", $pdfFile))),
   $pdfResult := xmldb:store($tmpCol, $pdfFileName, $pdfContent),
   $isFoSaved := xmldb:store($tmpCol, $ditaMapFileName, $ditaNode2)
      $cleanup := xepFormat:cleanup($xep),


   return

if ($format = "fo")

then <html><body onload="location.href='{$urlBase}{concat($tmpCol,$pdfFileName)}'"/></html>

(:then <t>{$selectedDocType}</t>:)

else $ditaMapNode
};

local:get_xmldoc()

Thank you,

Yuwono

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

--
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

rhaley

Re: Memory leaks on XEP rendering process

Hello Yuwono,

We use XEP/RenderX for our PDFs quite successfully but not the same way. Our users see HTML news articles and if they want a PDF of them they click on a PDF button which goes to this link

http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

We have eXist behind our Apache web server (hence proxy in the url)

The exist version of this URL would be:
http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

Obviously the file is shown in the browser (don't know if this is your end goal)

We store out XSL that does the XML to FO translation in exist under a stylesheets collection as we found this has some improved performance.

We use cocoons sitemap.xmap file to determine which transformation pipeline to execute:

this is an example from the render X website of what you need to put in sitemap.xmap

<map:pipeline>
   <map:match pattern="*-*-*.pdf">
   <map:generate src="path/to/some/pdf.xq" type="xquery">
      <map:parameter name="docname" value="{3}"/> <!-- the {3} coincides with the third * --> 
   </map:generate>
   <map:transform type="xinclude"/>
   <!-- this can be a normal http url to a stylsheets as well -->
   <map:transform type="xslt" src="xmldb:exist:///db/stylesheets/article.xsl"/>
   <map:serialize type="fo2pdf"/>
   </map:match>
</map:pipeline>

Thanks
Russ

Yuwono Gunawan

Re: Memory leaks on XEP rendering process

Hi,

Dan:

XEP is an transformation XSL-FO engine which in my case I use it for rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or Postscript.

Russell:

I stored XSL files in eXist as a XSL collection which is same as what you did. However I do not use sitemap.map file because I only have one pipeline. I call XEP transformation process through java binding method.

So something I do not understand how did you connect cocoons sitemap.map with eXist? Can you elaborate more?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:

Hello Yuwono,

We use XEP/RenderX for our PDFs quite successfully but not the same way. Our
users see HTML news articles and if they want a PDF of them they click on a
PDF button which goes to this link

http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

We have eXist behind our Apache web server (hence proxy in the url)

The exist version of this URL would be:
http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

Obviously the file is shown in the browser (don't know if this is your end
goal)

We store out XSL that does the XML to FO translation in exist under a
stylesheets collection as we found this has some improved performance.

We use cocoons sitemap.xmap file to determine which transformation pipeline
to execute:

this is an example from the render X website of what you need to put in
sitemap.xmap

<map:pipeline>
<map:match pattern="*-*-*.pdf">
<map:generate src="path/to/some/pdf.xq" type="xquery">
<map:parameter name="docname" value="{3}"/> 
</map:generate>
<map:transform type="xinclude"/>

<map:transform type="xslt"
src="xmldb:exist:///db/stylesheets/article.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
</map:pipeline>

Thanks
Russ
--
View this message in context: http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

rhaley

Re: Memory leaks on XEP rendering process

Yep I will add more comments in the morning.

Do you only have one pipeline because of some limitation or technical issue?

On Jan 13, 2011, at 6:35 PM, "Yuwono Gunawan [via eXist]"<[hidden email]> wrote:

Hi,

Dan:

XEP is an transformation XSL-FO engine which in my case I use it for rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or Postscript.

Russell:
I stored XSL files in eXist as a XSL collection which is same as what you did. However I do not use sitemap.map file because I only have one pipeline. I call XEP transformation process through java binding method.

So something I do not understand how did you connect cocoons sitemap.map with eXist? Can you elaborate more?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:

Hello Yuwono,

We use XEP/RenderX for our PDFs quite successfully but not the same way. Our
users see HTML news articles and if they want a PDF of them they click on a
PDF button which goes to this link

http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

We have eXist behind our Apache web server (hence proxy in the url)

The exist version of this URL would be:
http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

Obviously the file is shown in the browser (don't know if this is your end
goal)

We store out XSL that does the XML to FO translation in exist under a
stylesheets collection as we found this has some improved performance.

We use cocoons sitemap.xmap file to determine which transformation pipeline
to execute:

this is an example from the render X website of what you need to put in
sitemap.xmap

<map:pipeline>
<map:match pattern="*-*-*.pdf">
<map:generate src="path/to/some/pdf.xq" type="xquery">
<map:parameter name="docname" value="{3}"/> 
</map:generate>
<map:transform type="xinclude"/>

<map:transform type="xslt"
src="xmldb:exist:///db/stylesheets/article.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
</map:pipeline>

Thanks
Russ
--
View this message in context: http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

View message @ http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3216389.html
To unsubscribe from Memory leaks on XEP rendering process, click here.

Yuwono Gunawan

Re: Memory leaks on XEP rendering process

Thanks Russell.

It is using one pipeline because I want to use renderX's XEP engine only to transform XSL-FO. What XSL-FO engine transformation do you use?

On Thu, Jan 13, 2011 at 2:18 PM, rhaley <[hidden email]> wrote:

Yep I will add more comments in the morning.

Do you only have one pipeline because of some limitation or technical issue?

On Jan 13, 2011, at 6:35 PM, "Yuwono Gunawan [via eXist]"<[hidden email]> wrote:

Hi,

Dan:

XEP is an transformation XSL-FO engine which in my case I use it for rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or Postscript.

Russell:
I stored XSL files in eXist as a XSL collection which is same as what you did. However I do not use sitemap.map file because I only have one pipeline. I call XEP transformation process through java binding method.

So something I do not understand how did you connect cocoons sitemap.map with eXist? Can you elaborate more?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:

Hello Yuwono,

We use XEP/RenderX for our PDFs quite successfully but not the same way. Our
users see HTML news articles and if they want a PDF of them they click on a
PDF button which goes to this link

http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

We have eXist behind our Apache web server (hence proxy in the url)

The exist version of this URL would be:
http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

Obviously the file is shown in the browser (don't know if this is your end
goal)

We store out XSL that does the XML to FO translation in exist under a
stylesheets collection as we found this has some improved performance.

We use cocoons sitemap.xmap file to determine which transformation pipeline
to execute:

this is an example from the render X website of what you need to put in
sitemap.xmap

<map:pipeline>
<map:match pattern="*-*-*.pdf">
<map:generate src="path/to/some/pdf.xq" type="xquery">
<map:parameter name="docname" value="{3}"/> 
</map:generate>
<map:transform type="xinclude"/>

<map:transform type="xslt"
src="xmldb:exist:///db/stylesheets/article.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
</map:pipeline>

Thanks
Russ
--
View this message in context: http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list

[hidden email]

https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

View message @ http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3216389.html
To unsubscribe from Memory leaks on XEP rendering process, click here.

View this message in context: Re: Memory leaks on XEP rendering process

Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

Adam Retter

Re: Memory leaks on XEP rendering process

In reply to this post by Yuwono Gunawan

Yuwono,

I am not sure if you know this but eXist-db does have an XQuery
extension module for natively supporting XSL-FO through Apache FOP.

Whilst this is geared specifically toward Apache FOP at present, the
amount of Apache specific code is pretty small. This could easily be
isolated and the module made configurable so that it supports both
Apache FOP and RenderHouse XEP. This may be a cleaner and easier
approach for you, as opposed to the Java binding method.

Let me know if you are interested. If you have Java skills we could
discuss the design and implementation, otherwise it may be possible
for me to extend this after next week...

On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]> wrote:

> Hi,
> Dan:
> XEP is an transformation XSL-FO engine which in my case I use it for
> rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
> Postscript.
> Russell:
> I stored XSL files in eXist as a XSL collection which is same as what you
> did. However I do not use sitemap.map file because I only have one pipeline.
> I call XEP transformation process through java binding method.
> So something I do not understand how did you connect cocoons sitemap.map
> with eXist? Can you elaborate more?
> Thank you,
> Yuwono
>
> On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:
>>
>> Hello Yuwono,
>>
>> We use XEP/RenderX for our PDFs quite successfully but not the same way.
>> Our
>> users see HTML news articles and if they want a PDF of them they click on
>> a
>> PDF button which goes to this link
>>
>> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>
>> We have eXist behind our Apache web server (hence proxy in the url)
>>
>> The exist version of this URL would be:
>> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>
>> Obviously the file is shown in the browser (don't know if this is your end
>> goal)
>>
>> We store out XSL that does the XML to FO translation in exist under a
>> stylesheets collection as we found this has some improved performance.
>>
>> We use cocoons sitemap.xmap file to determine which transformation
>> pipeline
>> to execute:
>>
>> this is an example from the render X website of what you need to put in
>> sitemap.xmap
>>
>>
>> <map:pipeline>
>> <map:match pattern="*-*-*.pdf">
>> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> <map:parameter name="docname" value="{3}"/> 
>> </map:generate>
>> <map:transform type="xinclude"/>
>> 
>> <map:transform type="xslt"
>> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> <map:serialize type="fo2pdf"/>
>> </map:match>
>> </map:pipeline>
>>
>>
>> Thanks
>> Russ
>> --
>> View this message in context:
>> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> Sent from the exist-open mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
> --
> Thank you,
>
> Yuwono Gunawan
> Application Developer
> Dakota Systems, Inc.
> www.daksys.com
>
> Phone: 312-263-4400
> Fax: 312-263-3400
> Email: [hidden email]
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>

--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

rhaley

Re: Memory leaks on XEP rendering process

In reply to this post by Yuwono Gunawan

We use RenderX XEP exclusively.

We have more than on pipeline because we have different params that we pass to the tranformation based on the URL. Note:They all are still using RenderX XEP.

Part of the integration included a change to some xml configuration file... I think the jetty one. (that's a recollection from a late night mushy brain.)

Then you need to put the xep.jar and another jar from xep into the existhome/lib/user directory.....

And place the XEP directory into the webapp dir.

These are all late night guesses.

On Thu, Jan 13, 2011 at 9:34 PM, Yuwono Gunawan <[hidden email]> wrote:

Thanks Russell.
It is using one pipeline because I want to use renderX's XEP engine only to transform XSL-FO. What XSL-FO engine transformation do you use?

On Thu, Jan 13, 2011 at 2:18 PM, rhaley <[hidden email]> wrote:

Yep I will add more comments in the morning.

Do you only have one pipeline because of some limitation or technical issue?

On Jan 13, 2011, at 6:35 PM, "Yuwono Gunawan [via eXist]"<[hidden email]> wrote:

Hi,

Dan:

XEP is an transformation XSL-FO engine which in my case I use it for rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or Postscript.

Russell:
I stored XSL files in eXist as a XSL collection which is same as what you did. However I do not use sitemap.map file because I only have one pipeline. I call XEP transformation process through java binding method.

So something I do not understand how did you connect cocoons sitemap.map with eXist? Can you elaborate more?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:

Hello Yuwono,

We use XEP/RenderX for our PDFs quite successfully but not the same way. Our
users see HTML news articles and if they want a PDF of them they click on a
PDF button which goes to this link

http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

We have eXist behind our Apache web server (hence proxy in the url)

The exist version of this URL would be:
http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf

Obviously the file is shown in the browser (don't know if this is your end
goal)

We store out XSL that does the XML to FO translation in exist under a
stylesheets collection as we found this has some improved performance.

We use cocoons sitemap.xmap file to determine which transformation pipeline
to execute:

this is an example from the render X website of what you need to put in
sitemap.xmap

<map:pipeline>
<map:match pattern="*-*-*.pdf">
<map:generate src="path/to/some/pdf.xq" type="xquery">
<map:parameter name="docname" value="{3}"/> 
</map:generate>
<map:transform type="xinclude"/>

<map:transform type="xslt"
src="xmldb:exist:///db/stylesheets/article.xsl"/>
<map:serialize type="fo2pdf"/>
</map:match>
</map:pipeline>

Thanks
Russ
--
View this message in context: http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list

[hidden email]

https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

View message @ http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3216389.html
To unsubscribe from Memory leaks on XEP rendering process, click here.

View this message in context: Re: Memory leaks on XEP rendering process

Sent from the exist-open mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Exist-open mailing list

[hidden email]

https://lists.sourceforge.net/lists/listinfo/exist-open

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

rhaley

Re: Memory leaks on XEP rendering process

In reply to this post by Adam Retter

why would extending be necessary?

On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:

Yuwono,

I am not sure if you know this but eXist-db does have an XQuery
extension module for natively supporting XSL-FO through Apache FOP.

Whilst this is geared specifically toward Apache FOP at present, the
amount of Apache specific code is pretty small. This could easily be
isolated and the module made configurable so that it supports both
Apache FOP and RenderHouse XEP. This may be a cleaner and easier
approach for you, as opposed to the Java binding method.

Let me know if you are interested. If you have Java skills we could
discuss the design and implementation, otherwise it may be possible
for me to extend this after next week...

On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]> wrote:
> Hi,
> Dan:
> XEP is an transformation XSL-FO engine which in my case I use it for
> rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
> Postscript.
> Russell:
> I stored XSL files in eXist as a XSL collection which is same as what you
> did. However I do not use sitemap.map file because I only have one pipeline.
> I call XEP transformation process through java binding method.
> So something I do not understand how did you connect cocoons sitemap.map
> with eXist? Can you elaborate more?
> Thank you,
> Yuwono
>
> On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]> wrote:
>>
>> Hello Yuwono,
>>
>> We use XEP/RenderX for our PDFs quite successfully but not the same way.
>> Our
>> users see HTML news articles and if they want a PDF of them they click on
>> a
>> PDF button which goes to this link
>>
>> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>
>> We have eXist behind our Apache web server (hence proxy in the url)
>>
>> The exist version of this URL would be:
>> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>
>> Obviously the file is shown in the browser (don't know if this is your end
>> goal)
>>
>> We store out XSL that does the XML to FO translation in exist under a
>> stylesheets collection as we found this has some improved performance.
>>
>> We use cocoons sitemap.xmap file to determine which transformation
>> pipeline
>> to execute:
>>
>> this is an example from the render X website of what you need to put in
>> sitemap.xmap
>>
>>
>> <map:pipeline>
>> <map:match pattern="*-*-*.pdf">
>> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> <map:parameter name="docname" value="{3}"/> 
>> </map:generate>
>> <map:transform type="xinclude"/>
>> 
>> <map:transform type="xslt"
>> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> <map:serialize type="fo2pdf"/>
>> </map:match>
>> </map:pipeline>
>>
>>
>> Thanks
>> Russ
>> --
>> View this message in context:
>> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> Sent from the exist-open mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Exist-open mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
> --
> Thank you,
>
> Yuwono Gunawan
> Application Developer
> Dakota Systems, Inc.
> www.daksys.com
>
> Phone: 312-263-4400
> Fax: 312-263-3400
> Email: [hidden email]
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

Adam Retter

Re: Memory leaks on XEP rendering process

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

rhaley

Re: Memory leaks on XEP rendering process

ah ok.

We just use cocoon to do the transform after an xq file passes the xml back.

On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

Yuwono Gunawan

Re: Memory leaks on XEP rendering process

Hi,

Adam:

I saw a module specifically for Apache FOP. If you think you have a XEP module or we can extend/modify one of transformation module(may be Apache FOP module), I would be happy to discuss it with you.

Russell:

I saw webapp contains many folder. So did you put XEP folder in webapp folder as a direct child folder or folder insight webapp folder such as WEB-INF? Is there any documentation how to use concoon in eXist?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]> wrote:

ah ok.

We just use cocoon to do the transform after an xq file passes the xml back.

On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

rhaley

Re: Memory leaks on XEP rendering process

We didn't do everything on this page....

http://www.renderx.com/cocoon.html

We did the usage section. The sitemap.xmap has a serializer section where you configure to look like the example in the link above.

I can get you the exact location for the XEP dir in the morning when I get to work but if you want to try now try each of these webapp or webapp/cocoon.

On Thu, Jan 13, 2011 at 11:09 PM, Yuwono Gunawan <[hidden email]> wrote:

Hi,

Adam:
I saw a module specifically for Apache FOP. If you think you have a XEP module or we can extend/modify one of transformation module(may be Apache FOP module), I would be happy to discuss it with you.

Russell:
I saw webapp contains many folder. So did you put XEP folder in webapp folder as a direct child folder or folder insight webapp folder such as WEB-INF? Is there any documentation how to use concoon in eXist?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]> wrote:

ah ok.

We just use cocoon to do the transform after an xq file passes the xml back.

On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

rhaley

Re: Memory leaks on XEP rendering process

We placed XEP4_10 directory directly in the eXist_HOME/webapp dir.

In eXist_HOME/webapp

edit sitemap.xmap and add

<map:serializer mime-type="application/pdf" name="fo2pdf" src="com.renderx.xepx.cocoon.Serializer">

    <parameter name="com.renderx.xep.CONFIG" type="string" value="XEP_HOME/xep.xml"/>
</map:serializer>

to the map:serializers.section.

Change XEP_HOME to <path-to-XEP4_10-dir>

Add XEPSerializer.jar, XEPTask.jar, xep.jar, xt.jar, nwalsh-xalan27.jar to the eXist_HOME/lib/user.

Restart Exist.

On Thu, Jan 13, 2011 at 11:21 PM, Russell Haley <[hidden email]> wrote:

We didn't do everything on this page....

http://www.renderx.com/cocoon.html

We did the usage section. The sitemap.xmap has a serializer section where you configure to look like the example in the link above.

I can get you the exact location for the XEP dir in the morning when I get to work but if you want to try now try each of these webapp or webapp/cocoon.

On Thu, Jan 13, 2011 at 11:09 PM, Yuwono Gunawan <[hidden email]> wrote:

Hi,

Adam:
I saw a module specifically for Apache FOP. If you think you have a XEP module or we can extend/modify one of transformation module(may be Apache FOP module), I would be happy to discuss it with you.

Russell:
I saw webapp contains many folder. So did you put XEP folder in webapp folder as a direct child folder or folder insight webapp folder such as WEB-INF? Is there any documentation how to use concoon in eXist?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]> wrote:

ah ok.

We just use cocoon to do the transform after an xq file passes the xml back.

On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

Adam Retter

Re: Memory leaks on XEP rendering process

In reply to this post by Yuwono Gunawan

> I saw a module specifically for Apache FOP. If you think you have a XEP
> module or we can extend/modify one of transformation module(may be Apache
> FOP module), I would be happy to discuss it with you.

Okay great, do you have Skype, perhaps we could discuss this next week?

> Russell:
> I saw webapp contains many folder. So did you put XEP folder in webapp
> folder as a direct child folder or folder insight webapp folder such as
> WEB-INF? Is there any documentation how to use concoon in eXist?
> Thank you,
> Yuwono
> On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]>
> wrote:
>>
>> ah ok.
>>
>> We just use cocoon to do the transform after an xq file passes the xml
>> back.
>>
>> On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:
>>>
>>> On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
>>> > why would extending be necessary?
>>>
>>> If you wanted to avoid the security implications of enabling java
>>> binding, and expose methods natively to XQuery for use with XEP.
>>>
>>> > On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>> >>
>>> >> Yuwono,
>>> >>
>>> >> I am not sure if you know this but eXist-db does have an XQuery
>>> >> extension module for natively supporting XSL-FO through Apache FOP.
>>> >>
>>> >> Whilst this is geared specifically toward Apache FOP at present, the
>>> >> amount of Apache specific code is pretty small. This could easily be
>>> >> isolated and the module made configurable so that it supports both
>>> >> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>>> >> approach for you, as opposed to the Java binding method.
>>> >>
>>> >> Let me know if you are interested. If you have Java skills we could
>>> >> discuss the design and implementation, otherwise it may be possible
>>> >> for me to extend this after next week...
>>> >>
>>> >>
>>> >>
>>> >> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>>> >> wrote:
>>> >> > Hi,
>>> >> > Dan:
>>> >> > XEP is an transformation XSL-FO engine which in my case I use it for
>>> >> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF
>>> >> > or
>>> >> > Postscript.
>>> >> > Russell:
>>> >> > I stored XSL files in eXist as a XSL collection which is same as
>>> >> > what
>>> >> > you
>>> >> > did. However I do not use sitemap.map file because I only have one
>>> >> > pipeline.
>>> >> > I call XEP transformation process through java binding method.
>>> >> > So something I do not understand how did you connect cocoons
>>> >> > sitemap.map
>>> >> > with eXist? Can you elaborate more?
>>> >> > Thank you,
>>> >> > Yuwono
>>> >> >
>>> >> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>>> >> > wrote:
>>> >> >>
>>> >> >> Hello Yuwono,
>>> >> >>
>>> >> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>>> >> >> way.
>>> >> >> Our
>>> >> >> users see HTML news articles and if they want a PDF of them they
>>> >> >> click
>>> >> >> on
>>> >> >> a
>>> >> >> PDF button which goes to this link
>>> >> >>
>>> >> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>> >> >>
>>> >> >> We have eXist behind our Apache web server (hence proxy in the url)
>>> >> >>
>>> >> >> The exist version of this URL would be:
>>> >> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>> >> >>
>>> >> >> Obviously the file is shown in the browser (don't know if this is
>>> >> >> your
>>> >> >> end
>>> >> >> goal)
>>> >> >>
>>> >> >> We store out XSL that does the XML to FO translation in exist under
>>> >> >> a
>>> >> >> stylesheets collection as we found this has some improved
>>> >> >> performance.
>>> >> >>
>>> >> >> We use cocoons sitemap.xmap file to determine which transformation
>>> >> >> pipeline
>>> >> >> to execute:
>>> >> >>
>>> >> >> this is an example from the render X website of what you need to
>>> >> >> put in
>>> >> >> sitemap.xmap
>>> >> >>
>>> >> >>
>>> >> >> <map:pipeline>
>>> >> >> <map:match pattern="*-*-*.pdf">
>>> >> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>>> >> >> <map:parameter name="docname" value="{3}"/> 
>>> >> >> </map:generate>
>>> >> >> <map:transform type="xinclude"/>
>>> >> >> 
>>> >> >> <map:transform type="xslt"
>>> >> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>>> >> >> <map:serialize type="fo2pdf"/>
>>> >> >> </map:match>
>>> >> >> </map:pipeline>
>>> >> >>
>>> >> >>
>>> >> >> Thanks
>>> >> >> Russ
>>> >> >> --
>>> >> >> View this message in context:
>>> >> >>
>>> >> >>
>>> >> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>>> >> >> Sent from the exist-open mailing list archive at Nabble.com.
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> ------------------------------------------------------------------------------
>>> >> >> Protect Your Site and Customers from Malware Attacks
>>> >> >> Learn about various malware tactics and how to avoid them.
>>> >> >> Understand
>>> >> >> malware threats, the impact they can have on your business, and how
>>> >> >> you
>>> >> >> can protect your company and customers by using code signing.
>>> >> >> http://p.sf.net/sfu/oracle-sfdevnl
>>> >> >> _______________________________________________
>>> >> >> Exist-open mailing list
>>> >> >> [hidden email]
>>> >> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Thank you,
>>> >> >
>>> >> > Yuwono Gunawan
>>> >> > Application Developer
>>> >> > Dakota Systems, Inc.
>>> >> > www.daksys.com
>>> >> >
>>> >> > Phone: 312-263-4400
>>> >> > Fax: 312-263-3400
>>> >> > Email: [hidden email]
>>> >> >
>>> >> >
>>> >> >
>>> >> > ------------------------------------------------------------------------------
>>> >> > Protect Your Site and Customers from Malware Attacks
>>> >> > Learn about various malware tactics and how to avoid them.
>>> >> > Understand
>>> >> > malware threats, the impact they can have on your business, and how
>>> >> > you
>>> >> > can protect your company and customers by using code signing.
>>> >> > http://p.sf.net/sfu/oracle-sfdevnl
>>> >> > _______________________________________________
>>> >> > Exist-open mailing list
>>> >> > [hidden email]
>>> >> > https://lists.sourceforge.net/lists/listinfo/exist-open
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Adam Retter
>>> >>
>>> >> eXist Developer
>>> >> { United Kingdom }
>>> >> [hidden email]
>>> >> irc://irc.freenode.net/existdb
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Adam Retter
>>>
>>> eXist Developer
>>> { United Kingdom }
>>> [hidden email]
>>> irc://irc.freenode.net/existdb
>>
>
>
>
> --
> Thank you,
>
> Yuwono Gunawan
> Application Developer
> Dakota Systems, Inc.
> www.daksys.com
>
> Phone: 312-263-4400
> Fax: 312-263-3400
> Email: [hidden email]
>

Yuwono Gunawan

Re: Memory leaks on XEP rendering process

In reply to this post by rhaley

Thanks Russell. I will take a look at the link.

On Fri, Jan 14, 2011 at 4:29 AM, Russell Haley <[hidden email]> wrote:

We placed XEP4_10 directory directly in the eXist_HOME/webapp dir.

In eXist_HOME/webapp

edit sitemap.xmap and add
<map:serializer mime-type="application/pdf" name="fo2pdf" src="com.renderx.xepx.cocoon.Serializer">

    <parameter name="com.renderx.xep.CONFIG" type="string" value="XEP_HOME/xep.xml"/>
</map:serializer>
to the map:serializers.section.

Change XEP_HOME to <path-to-XEP4_10-dir>

Add XEPSerializer.jar, XEPTask.jar, xep.jar, xt.jar, nwalsh-xalan27.jar to the eXist_HOME/lib/user.

Restart Exist.

On Thu, Jan 13, 2011 at 11:21 PM, Russell Haley <[hidden email]> wrote:
We didn't do everything on this page....

http://www.renderx.com/cocoon.html

We did the usage section. The sitemap.xmap has a serializer section where you configure to look like the example in the link above.

I can get you the exact location for the XEP dir in the morning when I get to work but if you want to try now try each of these webapp or webapp/cocoon.

On Thu, Jan 13, 2011 at 11:09 PM, Yuwono Gunawan <[hidden email]> wrote:

Hi,

Adam:
I saw a module specifically for Apache FOP. If you think you have a XEP module or we can extend/modify one of transformation module(may be Apache FOP module), I would be happy to discuss it with you.

Russell:
I saw webapp contains many folder. So did you put XEP folder in webapp folder as a direct child folder or folder insight webapp folder such as WEB-INF? Is there any documentation how to use concoon in eXist?

Thank you,

Yuwono

On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]> wrote:

ah ok.

We just use cocoon to do the transform after an xq file passes the xml back.

On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:

On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
> why would extending be necessary?

If you wanted to avoid the security implications of enabling java
binding, and expose methods natively to XQuery for use with XEP.

> On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>
>> Yuwono,
>>
>> I am not sure if you know this but eXist-db does have an XQuery
>> extension module for natively supporting XSL-FO through Apache FOP.
>>
>> Whilst this is geared specifically toward Apache FOP at present, the
>> amount of Apache specific code is pretty small. This could easily be
>> isolated and the module made configurable so that it supports both
>> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>> approach for you, as opposed to the Java binding method.
>>
>> Let me know if you are interested. If you have Java skills we could
>> discuss the design and implementation, otherwise it may be possible
>> for me to extend this after next week...
>>
>>
>>
>> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>> wrote:
>> > Hi,
>> > Dan:
>> > XEP is an transformation XSL-FO engine which in my case I use it for
>> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF or
>> > Postscript.
>> > Russell:
>> > I stored XSL files in eXist as a XSL collection which is same as what
>> > you
>> > did. However I do not use sitemap.map file because I only have one
>> > pipeline.
>> > I call XEP transformation process through java binding method.
>> > So something I do not understand how did you connect cocoons sitemap.map
>> > with eXist? Can you elaborate more?
>> > Thank you,
>> > Yuwono
>> >
>> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>> > wrote:
>> >>
>> >> Hello Yuwono,
>> >>
>> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>> >> way.
>> >> Our
>> >> users see HTML news articles and if they want a PDF of them they click
>> >> on
>> >> a
>> >> PDF button which goes to this link
>> >>
>> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> We have eXist behind our Apache web server (hence proxy in the url)
>> >>
>> >> The exist version of this URL would be:
>> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>> >>
>> >> Obviously the file is shown in the browser (don't know if this is your
>> >> end
>> >> goal)
>> >>
>> >> We store out XSL that does the XML to FO translation in exist under a
>> >> stylesheets collection as we found this has some improved performance.
>> >>
>> >> We use cocoons sitemap.xmap file to determine which transformation
>> >> pipeline
>> >> to execute:
>> >>
>> >> this is an example from the render X website of what you need to put in
>> >> sitemap.xmap
>> >>
>> >>
>> >> <map:pipeline>
>> >> <map:match pattern="*-*-*.pdf">
>> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>> >> <map:parameter name="docname" value="{3}"/> 
>> >> </map:generate>
>> >> <map:transform type="xinclude"/>
>> >> 
>> >> <map:transform type="xslt"
>> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>> >> <map:serialize type="fo2pdf"/>
>> >> </map:match>
>> >> </map:pipeline>
>> >>
>> >>
>> >> Thanks
>> >> Russ
>> >> --
>> >> View this message in context:
>> >>
>> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>> >> Sent from the exist-open mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Protect Your Site and Customers from Malware Attacks
>> >> Learn about various malware tactics and how to avoid them. Understand
>> >> malware threats, the impact they can have on your business, and how you
>> >> can protect your company and customers by using code signing.
>> >> http://p.sf.net/sfu/oracle-sfdevnl
>> >> _______________________________________________
>> >> Exist-open mailing list
>> >> [hidden email]
>> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>> >
>> > --
>> > Thank you,
>> >
>> > Yuwono Gunawan
>> > Application Developer
>> > Dakota Systems, Inc.
>> > www.daksys.com
>> >
>> > Phone: 312-263-4400
>> > Fax: 312-263-3400
>> > Email: [hidden email]
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Protect Your Site and Customers from Malware Attacks
>> > Learn about various malware tactics and how to avoid them. Understand
>> > malware threats, the impact they can have on your business, and how you
>> > can protect your company and customers by using code signing.
>> > http://p.sf.net/sfu/oracle-sfdevnl
>> > _______________________________________________
>> > Exist-open mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/exist-open
>> >
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> [hidden email]
>> irc://irc.freenode.net/existdb
>
>

--

Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

--
Thank you,

Yuwono Gunawan
Application Developer
Dakota Systems, Inc.
www.daksys.com

Phone: 312-263-4400
Fax: 312-263-3400
Email: [hidden email]

Adam Retter

Re: Memory leaks on XEP rendering process

In reply to this post by Adam Retter

Okay I have now implemented support for RenderHouse XEP in the XSL-FO
XQuery module of eXist-db as of revision 13687 in trunk.

You have to use the 4 argument version of the xslfo:render() function,
that takes an argument to a XEP config file.
Otherwise you just have to make sure that the xep.jar is on eXist-db's
classpath (probably just place it in $EXIST_HOME/lib/user) and you
have to configure the module in conf.xml to use the XEP adapter.

Cheers Adam.

On 14 January 2011 12:47, Adam Retter <[hidden email]> wrote:

>> I saw a module specifically for Apache FOP. If you think you have a XEP
>> module or we can extend/modify one of transformation module(may be Apache
>> FOP module), I would be happy to discuss it with you.
>
> Okay great, do you have Skype, perhaps we could discuss this next week?
>
>> Russell:
>> I saw webapp contains many folder. So did you put XEP folder in webapp
>> folder as a direct child folder or folder insight webapp folder such as
>> WEB-INF? Is there any documentation how to use concoon in eXist?
>> Thank you,
>> Yuwono
>> On Thu, Jan 13, 2011 at 3:50 PM, Russell Haley <[hidden email]>
>> wrote:
>>>
>>> ah ok.
>>>
>>> We just use cocoon to do the transform after an xq file passes the xml
>>> back.
>>>
>>> On Thu, Jan 13, 2011 at 9:48 PM, Adam Retter <[hidden email]> wrote:
>>>>
>>>> On 13 January 2011 22:45, Russell Haley <[hidden email]> wrote:
>>>> > why would extending be necessary?
>>>>
>>>> If you wanted to avoid the security implications of enabling java
>>>> binding, and expose methods natively to XQuery for use with XEP.
>>>>
>>>> > On Thu, Jan 13, 2011 at 9:43 PM, Adam Retter <[hidden email]> wrote:
>>>> >>
>>>> >> Yuwono,
>>>> >>
>>>> >> I am not sure if you know this but eXist-db does have an XQuery
>>>> >> extension module for natively supporting XSL-FO through Apache FOP.
>>>> >>
>>>> >> Whilst this is geared specifically toward Apache FOP at present, the
>>>> >> amount of Apache specific code is pretty small. This could easily be
>>>> >> isolated and the module made configurable so that it supports both
>>>> >> Apache FOP and RenderHouse XEP. This may be a cleaner and easier
>>>> >> approach for you, as opposed to the Java binding method.
>>>> >>
>>>> >> Let me know if you are interested. If you have Java skills we could
>>>> >> discuss the design and implementation, otherwise it may be possible
>>>> >> for me to extend this after next week...
>>>> >>
>>>> >>
>>>> >>
>>>> >> On 13 January 2011 19:33, Yuwono Gunawan <[hidden email]>
>>>> >> wrote:
>>>> >> > Hi,
>>>> >> > Dan:
>>>> >> > XEP is an transformation XSL-FO engine which in my case I use it for
>>>> >> > rendering PDF. XEP can transform XSL-FO or intermediate XEP into PDF
>>>> >> > or
>>>> >> > Postscript.
>>>> >> > Russell:
>>>> >> > I stored XSL files in eXist as a XSL collection which is same as
>>>> >> > what
>>>> >> > you
>>>> >> > did. However I do not use sitemap.map file because I only have one
>>>> >> > pipeline.
>>>> >> > I call XEP transformation process through java binding method.
>>>> >> > So something I do not understand how did you connect cocoons
>>>> >> > sitemap.map
>>>> >> > with eXist? Can you elaborate more?
>>>> >> > Thank you,
>>>> >> > Yuwono
>>>> >> >
>>>> >> > On Thu, Jan 13, 2011 at 12:45 AM, rhaley <[hidden email]>
>>>> >> > wrote:
>>>> >> >>
>>>> >> >> Hello Yuwono,
>>>> >> >>
>>>> >> >> We use XEP/RenderX for our PDFs quite successfully but not the same
>>>> >> >> way.
>>>> >> >> Our
>>>> >> >> users see HTML news articles and if they want a PDF of them they
>>>> >> >> click
>>>> >> >> on
>>>> >> >> a
>>>> >> >> PDF button which goes to this link
>>>> >> >>
>>>> >> >> http://www/proxy/xml/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>>> >> >>
>>>> >> >> We have eXist behind our Apache web server (hence proxy in the url)
>>>> >> >>
>>>> >> >> The exist version of this URL would be:
>>>> >> >> http://existserver:8080/exist/cocoon/YYYYMMDD-HHMM-TestDocument.pdf
>>>> >> >>
>>>> >> >> Obviously the file is shown in the browser (don't know if this is
>>>> >> >> your
>>>> >> >> end
>>>> >> >> goal)
>>>> >> >>
>>>> >> >> We store out XSL that does the XML to FO translation in exist under
>>>> >> >> a
>>>> >> >> stylesheets collection as we found this has some improved
>>>> >> >> performance.
>>>> >> >>
>>>> >> >> We use cocoons sitemap.xmap file to determine which transformation
>>>> >> >> pipeline
>>>> >> >> to execute:
>>>> >> >>
>>>> >> >> this is an example from the render X website of what you need to
>>>> >> >> put in
>>>> >> >> sitemap.xmap
>>>> >> >>
>>>> >> >>
>>>> >> >> <map:pipeline>
>>>> >> >> <map:match pattern="*-*-*.pdf">
>>>> >> >> <map:generate src="path/to/some/pdf.xq" type="xquery">
>>>> >> >> <map:parameter name="docname" value="{3}"/> 
>>>> >> >> </map:generate>
>>>> >> >> <map:transform type="xinclude"/>
>>>> >> >> 
>>>> >> >> <map:transform type="xslt"
>>>> >> >> src="xmldb:exist:///db/stylesheets/article.xsl"/>
>>>> >> >> <map:serialize type="fo2pdf"/>
>>>> >> >> </map:match>
>>>> >> >> </map:pipeline>
>>>> >> >>
>>>> >> >>
>>>> >> >> Thanks
>>>> >> >> Russ
>>>> >> >> --
>>>> >> >> View this message in context:
>>>> >> >>
>>>> >> >>
>>>> >> >> http://exist.2174344.n4.nabble.com/Memory-leaks-on-XEP-rendering-process-tp3214991p3215314.html
>>>> >> >> Sent from the exist-open mailing list archive at Nabble.com.
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> ------------------------------------------------------------------------------
>>>> >> >> Protect Your Site and Customers from Malware Attacks
>>>> >> >> Learn about various malware tactics and how to avoid them.
>>>> >> >> Understand
>>>> >> >> malware threats, the impact they can have on your business, and how
>>>> >> >> you
>>>> >> >> can protect your company and customers by using code signing.
>>>> >> >> http://p.sf.net/sfu/oracle-sfdevnl
>>>> >> >> _______________________________________________
>>>> >> >> Exist-open mailing list
>>>> >> >> [hidden email]
>>>> >> >> https://lists.sourceforge.net/lists/listinfo/exist-open
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > Thank you,
>>>> >> >
>>>> >> > Yuwono Gunawan
>>>> >> > Application Developer
>>>> >> > Dakota Systems, Inc.
>>>> >> > www.daksys.com
>>>> >> >
>>>> >> > Phone: 312-263-4400
>>>> >> > Fax: 312-263-3400
>>>> >> > Email: [hidden email]
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > ------------------------------------------------------------------------------
>>>> >> > Protect Your Site and Customers from Malware Attacks
>>>> >> > Learn about various malware tactics and how to avoid them.
>>>> >> > Understand
>>>> >> > malware threats, the impact they can have on your business, and how
>>>> >> > you
>>>> >> > can protect your company and customers by using code signing.
>>>> >> > http://p.sf.net/sfu/oracle-sfdevnl
>>>> >> > _______________________________________________
>>>> >> > Exist-open mailing list
>>>> >> > [hidden email]
>>>> >> > https://lists.sourceforge.net/lists/listinfo/exist-open
>>>> >> >
>>>> >> >
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Adam Retter
>>>> >>
>>>> >> eXist Developer
>>>> >> { United Kingdom }
>>>> >> [hidden email]
>>>> >> irc://irc.freenode.net/existdb
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Adam Retter
>>>>
>>>> eXist Developer
>>>> { United Kingdom }
>>>> [hidden email]
>>>> irc://irc.freenode.net/existdb
>>>
>>
>>
>>
>> --
>> Thank you,
>>
>> Yuwono Gunawan
>> Application Developer
>> Dakota Systems, Inc.
>> www.daksys.com
>>
>> Phone: 312-263-4400
>> Fax: 312-263-3400
>> Email: [hidden email]
>>
>
>
>
> --
> Adam Retter
>
> eXist Developer
> { United Kingdom }
> [hidden email]
> irc://irc.freenode.net/existdb
>

--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open

mountainbiker

Re: Memory leaks on XEP rendering process

Adam, what am I doing wrong? In conf.xml, I have uncommented

<module uri="http://exist-db.org/xquery/xslfo" class="org.exist.xquery.modules.xslfo.XSLFOModule"> <parameter
name="processorAdapter"
value="org.exist.xquery.modules.xslfo.ApacheFopProcessorAdapter"/>
</module>

I restarted eXist (2.0-preview), but I don't see the documentation for the module.

Joe Wicentowski

Re: Memory leaks on XEP rendering process

Hi Mountainbiker,

> I restarted eXist (2.0-preview), but I don't see the documentation for the
> module.

Assuming based on your conf.xml changes that you're using FOP (and not
RenderHouse XEP as in this thread, as XEP would take a different
processorAdapter parameter value), did you edit your
extensions/local.build.properties to change include.module.xslfo from
"false" to "true" and rebuild eXist?

Joe

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open