I've some few alternatives:
1. Use a Java Web Proxy to convert requests and responses between
ooffice and Tomcat;
2. Use a Java crawler (spider/mirror tool) to make the first request,
generate local files and then call oo.
I was just wondering if was easier to modify/specialize tomcat behavior
than my previous alternatives.
On Mon, 2009-06-29 at 19:24 -0300, Daniel Henrique Alves Lima wrote:
> Yes !
>
> Now imagine my frustration with ooffice escaping a ';' :-(
>
> Browser, wget and other applications seems to work ok with URL encoded
> jsessionid.
>
>
> On Tue, 2009-06-30 at 00:00 +0200, André Warnier wrote:
> > Daniel Henrique Alves Lima wrote:
> > ...
> > Hi.
> > If I understand what you are trying to do :
> > 1) a client enters your application, authenticates, navigates, and
> > displays a result html page.
> > 2) on this page, is a button that says "get this page as PDF"
> > 3) the client clicks on that button, and is supposed to receive the same
> > page, but this time as a PDF.
> > 4) At the server side, you want to use OOo to create the PDF version
> > from the html page
> > 5) and OOo is capable, given a URL, to retrieve this page, and then
> > given appropriate commands, to return a PDF version of the page.
> > 6) But OOo has trouble with the "jsessionid" part of the URL, although
> > it needs it in order to retrieve the page on behalf of the client.
> > Right ?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
users-unsubscribe@...
> > For additional commands, e-mail:
users-help@...
> >
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
