You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Sonja Löhr <so...@arcor.de> on 2005/09/12 11:40:50 UTC
upgrading from 20.0.5 to the trunk
Hi!
After inspecting the new compliance page (:-)) great improvements!!), I
finally downloaded the trunk and built it.
Now my servlet code is missing several packages/classes :
org.apache.fop.messaging
org.apache.fop.configuration
and classes in org.apache.fop.apps (Driver and Options)
Did I miss some sources or where can I find documentation about a new
way of programmatic configuration, logging and Servlet integration?
Sorry, I'm a bit lost in the developer's section of the fop site.
Thank you for some hints,
I would love to use the new features!
sonja
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
Ok, I can now answer some of my questions myself ;-)
I use the Fop class instead of the Driver class, right?
I'll try to change the code according to the source of FopServlet,
putting the extra steps somwhere between.
But some questions remain:
a) What about the configuration? I have had the following for
fop-20.0.5:
org.apache.fop.configuration.Configuration.put("baseDir",
ctx.getRealPath("/"));
org.apache.fop.configuration.Configuration.put("fontBaseDir",
ctx.getRealPath("/WEB-INF/fonts"));
org.apache.fop.configuration.Configuration.put("strokeSVGText",
"false");
File userConfigFile = new File(ctx.getRealPath(CONFIG_FILE));
new Options(userConfigFile);
b) My app already uses commons.logging with log4j. May I just do nothing
more and FOP will log onto the same appender as my servlet does?
Greetings!
sonja
Am Montag, den 12.09.2005, 11:40 +0200 schrieb Sonja Löhr:
> Hi!
>
> After inspecting the new compliance page (:-)) great improvements!!), I
> finally downloaded the trunk and built it.
> Now my servlet code is missing several packages/classes :
> org.apache.fop.messaging
> org.apache.fop.configuration
> and classes in org.apache.fop.apps (Driver and Options)
>
> Did I miss some sources or where can I find documentation about a new
> way of programmatic configuration, logging and Servlet integration?
> Sorry, I'm a bit lost in the developer's section of the fop site.
>
> Thank you for some hints,
> I would love to use the new features!
>
> sonja
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
That positioning was totally arbitrary, so I moved generate-id onto the
cell and everything is fine!
Thank you once more :-)
sonja
Am Dienstag, den 13.09.2005, 18:53 +0200 schrieb Jeremias Maerki:
> I should have realized from your snippets what was wrong. D'oh! The
> problem is that on certain FOs the "id" property is not properly
> processed, yet, and therefore not available to page-number-citation.
> This was properly shown in our test cases but not on our compliance page
> and I didn't remember, so I've updated the compliance page with the
> details (not live, yet):
> http://svn.apache.org/viewcvs?rev=280586&view=rev
>
> ATM, you can't use an ID defined on table-row. Please try to move the id
> to the first table-cell in the row and it should work. I hope we'll have
> time to fix that eventually.
>
> On 13.09.2005 18:22:29 Sonja Löhr wrote:
> > Am Dienstag, den 13.09.2005, 17:41 +0200 schrieb Jeremias Maerki:
> > > You can send the FO file to me directly, and I'll try to isolate the
> > > problem so I can create a simple, automatable test case for our
> > > collection.
> >
> > .... case it is not my fault!!
> > The file is on its way ...
> >
> >
> > >
> > > On 13.09.2005 17:22:33 Sonja Löhr wrote:
> > > >
> > > >
> > > >
> > > > > Can you provide an example? I can't reproduce the problem. Thanks.
> > > >
> > > > Of course.
> > > > Shall/May I attach the whole big fo file here so you could just plug it
> > > > in? Here are some snippets.
> > > >
> > > > The index table of contents has its own page-sequence-master as it is in
> > > > two columns.
> > > > In the pdf output, there is just one question mark instead of a number.
> > > > I already simplyfied index to exclude problems with overflow or so.
> > > >
> > > > <fo:page-sequence language="de" hyphenate="false"
> > > > initial-page-number="3" master-reference="inhaltsverzeichnis">
> > > >
> > > > <fo:static-content flow-name="toc-odd-after">
> > > > <fo:block padding-top="0.6cm" text-align="end">
> > > > <fo:page-number/>
> > > > </fo:block>
> > > > </fo:static-content>
> > > >
> > > > <fo:static-content flow-name="toc-even-after">
> > > > <fo:block padding-top="0.6cm" text-align="start">
> > > > <fo:page-number/>
> > > > </fo:block>
> > > > </fo:static-content>
> > > >
> > > > <fo:flow flow-name="xsl-region-body">
> > > >
> > > > <fo:block space-after="1.5cm" font-size="20pt">Inhalt</fo:block>
> > > > <fo:block>
> > > > <fo:page-number-citation ref-id="N1005A"/> :
> > > > Bartschneider
> > > > </fo:block>
> > > > <fo:block>
> > > > <fo:page-number-citation ref-id="N1006A"/> :
> > > > Dampfbügeleisen
> > > > </fo:block>
> > > > <fo:block>
> > > > <fo:page-number-citation ref-id="N1007A"/> :
> > > > ProStyle Bügeleisen
> > > > </fo:block>
> > > > [and so on]
> > > >
> > > >
> > > > </fo:flow>
> > > > </fo:page-sequence>
> > > >
> > > >
> > > >
> > > > <fo:page-sequence hyphenate="true" master-reference="content">
> > > > [A long, long table with table-header, some of the table rows (those
> > > > containing the group name) carry the ids for the page-number-citation:]
> > > >
> > > > <fo:table-row height="2.2cm" id="N1005A">
> > > > <fo:table-cell border="0.2mm solid black"
> > > > display-align="center" number-columns-spanned="8">
> > > > <fo:block start-indent="3.6cm"
> > > > font-weight="bold" font-size="24pt" display-align="center"
> > > > space-before="0.8cm"> Bartschneider
> > > > </fo:block>
> > > > </fo:table-cell>
> > > > </fo:table-row>
> > > >
> > > >
> > > > [...]
> > > > </fo:page-sequence>
> > > <snip/>
> > >
> > >
> > > Jeremias Maerki
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > >
> > --
> > Sonja Löhr <so...@arcor.de>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I should have realized from your snippets what was wrong. D'oh! The
problem is that on certain FOs the "id" property is not properly
processed, yet, and therefore not available to page-number-citation.
This was properly shown in our test cases but not on our compliance page
and I didn't remember, so I've updated the compliance page with the
details (not live, yet):
http://svn.apache.org/viewcvs?rev=280586&view=rev
ATM, you can't use an ID defined on table-row. Please try to move the id
to the first table-cell in the row and it should work. I hope we'll have
time to fix that eventually.
On 13.09.2005 18:22:29 Sonja Löhr wrote:
> Am Dienstag, den 13.09.2005, 17:41 +0200 schrieb Jeremias Maerki:
> > You can send the FO file to me directly, and I'll try to isolate the
> > problem so I can create a simple, automatable test case for our
> > collection.
>
> .... case it is not my fault!!
> The file is on its way ...
>
>
> >
> > On 13.09.2005 17:22:33 Sonja Löhr wrote:
> > >
> > >
> > >
> > > > Can you provide an example? I can't reproduce the problem. Thanks.
> > >
> > > Of course.
> > > Shall/May I attach the whole big fo file here so you could just plug it
> > > in? Here are some snippets.
> > >
> > > The index table of contents has its own page-sequence-master as it is in
> > > two columns.
> > > In the pdf output, there is just one question mark instead of a number.
> > > I already simplyfied index to exclude problems with overflow or so.
> > >
> > > <fo:page-sequence language="de" hyphenate="false"
> > > initial-page-number="3" master-reference="inhaltsverzeichnis">
> > >
> > > <fo:static-content flow-name="toc-odd-after">
> > > <fo:block padding-top="0.6cm" text-align="end">
> > > <fo:page-number/>
> > > </fo:block>
> > > </fo:static-content>
> > >
> > > <fo:static-content flow-name="toc-even-after">
> > > <fo:block padding-top="0.6cm" text-align="start">
> > > <fo:page-number/>
> > > </fo:block>
> > > </fo:static-content>
> > >
> > > <fo:flow flow-name="xsl-region-body">
> > >
> > > <fo:block space-after="1.5cm" font-size="20pt">Inhalt</fo:block>
> > > <fo:block>
> > > <fo:page-number-citation ref-id="N1005A"/> :
> > > Bartschneider
> > > </fo:block>
> > > <fo:block>
> > > <fo:page-number-citation ref-id="N1006A"/> :
> > > Dampfbügeleisen
> > > </fo:block>
> > > <fo:block>
> > > <fo:page-number-citation ref-id="N1007A"/> :
> > > ProStyle Bügeleisen
> > > </fo:block>
> > > [and so on]
> > >
> > >
> > > </fo:flow>
> > > </fo:page-sequence>
> > >
> > >
> > >
> > > <fo:page-sequence hyphenate="true" master-reference="content">
> > > [A long, long table with table-header, some of the table rows (those
> > > containing the group name) carry the ids for the page-number-citation:]
> > >
> > > <fo:table-row height="2.2cm" id="N1005A">
> > > <fo:table-cell border="0.2mm solid black"
> > > display-align="center" number-columns-spanned="8">
> > > <fo:block start-indent="3.6cm"
> > > font-weight="bold" font-size="24pt" display-align="center"
> > > space-before="0.8cm"> Bartschneider
> > > </fo:block>
> > > </fo:table-cell>
> > > </fo:table-row>
> > >
> > >
> > > [...]
> > > </fo:page-sequence>
> > <snip/>
> >
> >
> > Jeremias Maerki
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> >
> --
> Sonja Löhr <so...@arcor.de>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
Am Dienstag, den 13.09.2005, 17:41 +0200 schrieb Jeremias Maerki:
> You can send the FO file to me directly, and I'll try to isolate the
> problem so I can create a simple, automatable test case for our
> collection.
.... case it is not my fault!!
The file is on its way ...
>
> On 13.09.2005 17:22:33 Sonja Löhr wrote:
> >
> >
> >
> > > Can you provide an example? I can't reproduce the problem. Thanks.
> >
> > Of course.
> > Shall/May I attach the whole big fo file here so you could just plug it
> > in? Here are some snippets.
> >
> > The index table of contents has its own page-sequence-master as it is in
> > two columns.
> > In the pdf output, there is just one question mark instead of a number.
> > I already simplyfied index to exclude problems with overflow or so.
> >
> > <fo:page-sequence language="de" hyphenate="false"
> > initial-page-number="3" master-reference="inhaltsverzeichnis">
> >
> > <fo:static-content flow-name="toc-odd-after">
> > <fo:block padding-top="0.6cm" text-align="end">
> > <fo:page-number/>
> > </fo:block>
> > </fo:static-content>
> >
> > <fo:static-content flow-name="toc-even-after">
> > <fo:block padding-top="0.6cm" text-align="start">
> > <fo:page-number/>
> > </fo:block>
> > </fo:static-content>
> >
> > <fo:flow flow-name="xsl-region-body">
> >
> > <fo:block space-after="1.5cm" font-size="20pt">Inhalt</fo:block>
> > <fo:block>
> > <fo:page-number-citation ref-id="N1005A"/> :
> > Bartschneider
> > </fo:block>
> > <fo:block>
> > <fo:page-number-citation ref-id="N1006A"/> :
> > Dampfbügeleisen
> > </fo:block>
> > <fo:block>
> > <fo:page-number-citation ref-id="N1007A"/> :
> > ProStyle Bügeleisen
> > </fo:block>
> > [and so on]
> >
> >
> > </fo:flow>
> > </fo:page-sequence>
> >
> >
> >
> > <fo:page-sequence hyphenate="true" master-reference="content">
> > [A long, long table with table-header, some of the table rows (those
> > containing the group name) carry the ids for the page-number-citation:]
> >
> > <fo:table-row height="2.2cm" id="N1005A">
> > <fo:table-cell border="0.2mm solid black"
> > display-align="center" number-columns-spanned="8">
> > <fo:block start-indent="3.6cm"
> > font-weight="bold" font-size="24pt" display-align="center"
> > space-before="0.8cm"> Bartschneider
> > </fo:block>
> > </fo:table-cell>
> > </fo:table-row>
> >
> >
> > [...]
> > </fo:page-sequence>
> <snip/>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
You can send the FO file to me directly, and I'll try to isolate the
problem so I can create a simple, automatable test case for our
collection.
On 13.09.2005 17:22:33 Sonja Löhr wrote:
>
>
>
> > Can you provide an example? I can't reproduce the problem. Thanks.
>
> Of course.
> Shall/May I attach the whole big fo file here so you could just plug it
> in? Here are some snippets.
>
> The index table of contents has its own page-sequence-master as it is in
> two columns.
> In the pdf output, there is just one question mark instead of a number.
> I already simplyfied index to exclude problems with overflow or so.
>
> <fo:page-sequence language="de" hyphenate="false"
> initial-page-number="3" master-reference="inhaltsverzeichnis">
>
> <fo:static-content flow-name="toc-odd-after">
> <fo:block padding-top="0.6cm" text-align="end">
> <fo:page-number/>
> </fo:block>
> </fo:static-content>
>
> <fo:static-content flow-name="toc-even-after">
> <fo:block padding-top="0.6cm" text-align="start">
> <fo:page-number/>
> </fo:block>
> </fo:static-content>
>
> <fo:flow flow-name="xsl-region-body">
>
> <fo:block space-after="1.5cm" font-size="20pt">Inhalt</fo:block>
> <fo:block>
> <fo:page-number-citation ref-id="N1005A"/> :
> Bartschneider
> </fo:block>
> <fo:block>
> <fo:page-number-citation ref-id="N1006A"/> :
> Dampfbügeleisen
> </fo:block>
> <fo:block>
> <fo:page-number-citation ref-id="N1007A"/> :
> ProStyle Bügeleisen
> </fo:block>
> [and so on]
>
>
> </fo:flow>
> </fo:page-sequence>
>
>
>
> <fo:page-sequence hyphenate="true" master-reference="content">
> [A long, long table with table-header, some of the table rows (those
> containing the group name) carry the ids for the page-number-citation:]
>
> <fo:table-row height="2.2cm" id="N1005A">
> <fo:table-cell border="0.2mm solid black"
> display-align="center" number-columns-spanned="8">
> <fo:block start-indent="3.6cm"
> font-weight="bold" font-size="24pt" display-align="center"
> space-before="0.8cm"> Bartschneider
> </fo:block>
> </fo:table-cell>
> </fo:table-row>
>
>
> [...]
> </fo:page-sequence>
<snip/>
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
> Can you provide an example? I can't reproduce the problem. Thanks.
Of course.
Shall/May I attach the whole big fo file here so you could just plug it
in? Here are some snippets.
The index table of contents has its own page-sequence-master as it is in
two columns.
In the pdf output, there is just one question mark instead of a number.
I already simplyfied index to exclude problems with overflow or so.
<fo:page-sequence language="de" hyphenate="false"
initial-page-number="3" master-reference="inhaltsverzeichnis">
<fo:static-content flow-name="toc-odd-after">
<fo:block padding-top="0.6cm" text-align="end">
<fo:page-number/>
</fo:block>
</fo:static-content>
<fo:static-content flow-name="toc-even-after">
<fo:block padding-top="0.6cm" text-align="start">
<fo:page-number/>
</fo:block>
</fo:static-content>
<fo:flow flow-name="xsl-region-body">
<fo:block space-after="1.5cm" font-size="20pt">Inhalt</fo:block>
<fo:block>
<fo:page-number-citation ref-id="N1005A"/> :
Bartschneider
</fo:block>
<fo:block>
<fo:page-number-citation ref-id="N1006A"/> :
Dampfbügeleisen
</fo:block>
<fo:block>
<fo:page-number-citation ref-id="N1007A"/> :
ProStyle Bügeleisen
</fo:block>
[and so on]
</fo:flow>
</fo:page-sequence>
<fo:page-sequence hyphenate="true" master-reference="content">
[A long, long table with table-header, some of the table rows (those
containing the group name) carry the ids for the page-number-citation:]
<fo:table-row height="2.2cm" id="N1005A">
<fo:table-cell border="0.2mm solid black"
display-align="center" number-columns-spanned="8">
<fo:block start-indent="3.6cm"
font-weight="bold" font-size="24pt" display-align="center"
space-before="0.8cm"> Bartschneider
</fo:block>
</fo:table-cell>
</fo:table-row>
[...]
</fo:page-sequence>
>
> > Thanks again!
> > sonja
> >
> >
> >
> >
> >
> >
> >
> > Am Montag, den 12.09.2005, 14:37 +0200 schrieb Jeremias Maerki:
> > > On 12.09.2005 13:31:14 Sonja Löhr wrote:
> > > >
> > > > I try learning ...
> > > >
> > > > Could you please just tell me whether I am on the right track for
> > > > configuration with the fop-trunk?
> > > >
> > > >
> > > > DefaultConfigurationBuilder confbuilder = new
> > > > DefaultConfigurationBuilder();
> > > > Configuration fileconf =
> > > > confbuilder.buildFromFile(ctx.getRealPath(CONFIG_FILE));
> > >
> > > So far so good. :-)
> > >
> > > > DefaultConfiguration conf = new DefaultConfiguration(fileconf);
> > >
> > > I wouldn't do that. It doesn't help because....
> > >
> > > > conf.setAttribute("strokeSVGText", false);
> > >
> > > Doesn't exist anymore. There's an open task for me to revisit that.
> > >
> > > > conf.setAttribute("fontBaseDir", ctx.getRealPath("/WEB-INF/fonts"));
> > >
> > > fontBaseDir was introduced after FOP was branched from the main dev tree
> > > and since nobody implemented this for FOP Trunk, yet, this is not
> > > available. ATM you need to use absolute paths in the font configuration.
> > > Patches welcome. Ideally, the fonts will be loaded through the
> > > URIResolver.
> > >
> > > > conf.setAttribute("baseDir", ctx.getRealPath("/"));
> > >
> > > Cannot be specified through the config file right now.
> > >
> > > The equivalent would be:
> > >
> > > userAgent.setBaseURL(ctx.getRealPath("/"));
> > >
> > >
> > > > .....
> > > > Fop fop = new Fop(Fop.RENDER_PDF);
> > > > fop.getUserAgent().setUserConfig(conf);
> > >
> > > that's ok but only the font setup and the PDF library are currently
> > > configured through the config file.
> > >
> > > In the following post you will find an attachment with a sample config
> > > file. You will notice that the whole thing has changed slightly.
> > > http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200509.mbox/%3c20050906222251.1F2B.DEV.JEREMIAS@greenmail.ch%3e
> > >
> > > > .....
> > > >
> > > > or
> > >
> > > No, "and". :-)
> > >
> > > > fop.getUserAgent().setBaseURL()
> > > > instead of specifying this inside the DefaultConfiguration?
> > >
> > > Not instead. You need to do both.
> > >
> > > > (Font basedir is not essential since it is under baseDir)
> > >
> > > but relative paths for fonts are currently not possible, I'm afraid.
> > >
> > > >
> > > > Leaving now, I'll simply try tomorrow if no veto occurs ;-)
> > >
> > > Veto? It's simply your time. You will see that there are still a few
> > > things to do to bring FOP Trunk up to the same level for everything. But
> > > it's good we get reminded this way. But I'll write the docs soon and I'm
> > > sure I will need to fix a few things while I'm doing that.
> > >
> > > > Thanks in advance!
> > > > sonja
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Am Montag, den 12.09.2005, 12:12 +0200 schrieb Sonja Löhr:
> > > > > Thank you for the turbo-answer, Jeremias!
> > > > >
> > > > > We wrote at the same time ...
> > > > >
> > > > > I would be brave ;-) and change the code since it is really small and
> > > > > differs not much from what happens in FopServlet, I just have some In-
> > > > > and OutputStreams between but should come along with the javadoc for
> > > > > that.
> > > > >
> > > > > The only complex thing could be the configuration (with both config-file
> > > > > and programmatically) - is that a great thing to change?
> > > > > If it is, I would just wait for the release and don't bother you with
> > > > > questions.
> > > > >
> > > > > sonja
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> > > > > > Sorry, Sonja, but a lot of changes have happened during the redesign
> > > > > > which break API compatibility. The packages and classes you listed don't
> > > > > > exist anymore. And the new API has not been documented, yet. This will
> > > > > > be done in the next two weeks and before the first preview release. In
> > > > > > the meantime, you can look at the embedding examples in
> > > > > > examples/embedding on how to embed FOP Trunk in a Java application.
> > > > > >
> > > > > > If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> > > > > > started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> > > > > > But either way, you will have to change your application once.
> > > > > >
> > > > > > Also needless to say that FOP Trunk is unstable (alpha) as will be the
> > > > > > first preview release.
> > > > > >
> > > > > > On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > > > > > > Hi!
> > > > > > >
> > > > > > > After inspecting the new compliance page (:-)) great improvements!!), I
> > > > > > > finally downloaded the trunk and built it.
> > > > > > > Now my servlet code is missing several packages/classes :
> > > > > > > org.apache.fop.messaging
> > > > > > > org.apache.fop.configuration
> > > > > > > and classes in org.apache.fop.apps (Driver and Options)
> > > > > > >
> > > > > > > Did I miss some sources or where can I find documentation about a new
> > > > > > > way of programmatic configuration, logging and Servlet integration?
> > > > > > > Sorry, I'm a bit lost in the developer's section of the fop site.
> > > > > > >
> > > > > > > Thank you for some hints,
> > > > > > > I would love to use the new features!
> > > > > > >
> > > > > > > sonja
> > > > > >
> > > > > >
> > > > > > Jeremias Maerki
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > > > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > > > > >
> > > > --
> > > > Sonja Löhr <so...@arcor.de>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > >
> > >
> > >
> > > Jeremias Maerki
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > >
> > --
> > Sonja Löhr <so...@arcor.de>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 13.09.2005 16:42:41 Sonja Löhr wrote:
>
>
> Many, many thanks for the great help, Jeremias!
You're welcome. :-)
> I finally got something out !!
> Font configuration worked well thanks to your example. I had to fight
> down some new exceptions because of overflows that didn't occur before.
>
> Just one "trunk-only" problem remains:
> The page-number-citations now show up as question-marks. In the FO, it
> looks well and I find the corresponding id.
> May the problem stem from the fact that index and document-content are
> in different page-sequences?
Can you provide an example? I can't reproduce the problem. Thanks.
> Thanks again!
> sonja
>
>
>
>
>
>
>
> Am Montag, den 12.09.2005, 14:37 +0200 schrieb Jeremias Maerki:
> > On 12.09.2005 13:31:14 Sonja Löhr wrote:
> > >
> > > I try learning ...
> > >
> > > Could you please just tell me whether I am on the right track for
> > > configuration with the fop-trunk?
> > >
> > >
> > > DefaultConfigurationBuilder confbuilder = new
> > > DefaultConfigurationBuilder();
> > > Configuration fileconf =
> > > confbuilder.buildFromFile(ctx.getRealPath(CONFIG_FILE));
> >
> > So far so good. :-)
> >
> > > DefaultConfiguration conf = new DefaultConfiguration(fileconf);
> >
> > I wouldn't do that. It doesn't help because....
> >
> > > conf.setAttribute("strokeSVGText", false);
> >
> > Doesn't exist anymore. There's an open task for me to revisit that.
> >
> > > conf.setAttribute("fontBaseDir", ctx.getRealPath("/WEB-INF/fonts"));
> >
> > fontBaseDir was introduced after FOP was branched from the main dev tree
> > and since nobody implemented this for FOP Trunk, yet, this is not
> > available. ATM you need to use absolute paths in the font configuration.
> > Patches welcome. Ideally, the fonts will be loaded through the
> > URIResolver.
> >
> > > conf.setAttribute("baseDir", ctx.getRealPath("/"));
> >
> > Cannot be specified through the config file right now.
> >
> > The equivalent would be:
> >
> > userAgent.setBaseURL(ctx.getRealPath("/"));
> >
> >
> > > .....
> > > Fop fop = new Fop(Fop.RENDER_PDF);
> > > fop.getUserAgent().setUserConfig(conf);
> >
> > that's ok but only the font setup and the PDF library are currently
> > configured through the config file.
> >
> > In the following post you will find an attachment with a sample config
> > file. You will notice that the whole thing has changed slightly.
> > http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200509.mbox/%3c20050906222251.1F2B.DEV.JEREMIAS@greenmail.ch%3e
> >
> > > .....
> > >
> > > or
> >
> > No, "and". :-)
> >
> > > fop.getUserAgent().setBaseURL()
> > > instead of specifying this inside the DefaultConfiguration?
> >
> > Not instead. You need to do both.
> >
> > > (Font basedir is not essential since it is under baseDir)
> >
> > but relative paths for fonts are currently not possible, I'm afraid.
> >
> > >
> > > Leaving now, I'll simply try tomorrow if no veto occurs ;-)
> >
> > Veto? It's simply your time. You will see that there are still a few
> > things to do to bring FOP Trunk up to the same level for everything. But
> > it's good we get reminded this way. But I'll write the docs soon and I'm
> > sure I will need to fix a few things while I'm doing that.
> >
> > > Thanks in advance!
> > > sonja
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Am Montag, den 12.09.2005, 12:12 +0200 schrieb Sonja Löhr:
> > > > Thank you for the turbo-answer, Jeremias!
> > > >
> > > > We wrote at the same time ...
> > > >
> > > > I would be brave ;-) and change the code since it is really small and
> > > > differs not much from what happens in FopServlet, I just have some In-
> > > > and OutputStreams between but should come along with the javadoc for
> > > > that.
> > > >
> > > > The only complex thing could be the configuration (with both config-file
> > > > and programmatically) - is that a great thing to change?
> > > > If it is, I would just wait for the release and don't bother you with
> > > > questions.
> > > >
> > > > sonja
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> > > > > Sorry, Sonja, but a lot of changes have happened during the redesign
> > > > > which break API compatibility. The packages and classes you listed don't
> > > > > exist anymore. And the new API has not been documented, yet. This will
> > > > > be done in the next two weeks and before the first preview release. In
> > > > > the meantime, you can look at the embedding examples in
> > > > > examples/embedding on how to embed FOP Trunk in a Java application.
> > > > >
> > > > > If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> > > > > started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> > > > > But either way, you will have to change your application once.
> > > > >
> > > > > Also needless to say that FOP Trunk is unstable (alpha) as will be the
> > > > > first preview release.
> > > > >
> > > > > On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > > > > > Hi!
> > > > > >
> > > > > > After inspecting the new compliance page (:-)) great improvements!!), I
> > > > > > finally downloaded the trunk and built it.
> > > > > > Now my servlet code is missing several packages/classes :
> > > > > > org.apache.fop.messaging
> > > > > > org.apache.fop.configuration
> > > > > > and classes in org.apache.fop.apps (Driver and Options)
> > > > > >
> > > > > > Did I miss some sources or where can I find documentation about a new
> > > > > > way of programmatic configuration, logging and Servlet integration?
> > > > > > Sorry, I'm a bit lost in the developer's section of the fop site.
> > > > > >
> > > > > > Thank you for some hints,
> > > > > > I would love to use the new features!
> > > > > >
> > > > > > sonja
> > > > >
> > > > >
> > > > > Jeremias Maerki
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > > > >
> > > --
> > > Sonja Löhr <so...@arcor.de>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> >
> >
> >
> > Jeremias Maerki
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> >
> --
> Sonja Löhr <so...@arcor.de>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
Many, many thanks for the great help, Jeremias!
I finally got something out !!
Font configuration worked well thanks to your example. I had to fight
down some new exceptions because of overflows that didn't occur before.
Just one "trunk-only" problem remains:
The page-number-citations now show up as question-marks. In the FO, it
looks well and I find the corresponding id.
May the problem stem from the fact that index and document-content are
in different page-sequences?
Thanks again!
sonja
Am Montag, den 12.09.2005, 14:37 +0200 schrieb Jeremias Maerki:
> On 12.09.2005 13:31:14 Sonja Löhr wrote:
> >
> > I try learning ...
> >
> > Could you please just tell me whether I am on the right track for
> > configuration with the fop-trunk?
> >
> >
> > DefaultConfigurationBuilder confbuilder = new
> > DefaultConfigurationBuilder();
> > Configuration fileconf =
> > confbuilder.buildFromFile(ctx.getRealPath(CONFIG_FILE));
>
> So far so good. :-)
>
> > DefaultConfiguration conf = new DefaultConfiguration(fileconf);
>
> I wouldn't do that. It doesn't help because....
>
> > conf.setAttribute("strokeSVGText", false);
>
> Doesn't exist anymore. There's an open task for me to revisit that.
>
> > conf.setAttribute("fontBaseDir", ctx.getRealPath("/WEB-INF/fonts"));
>
> fontBaseDir was introduced after FOP was branched from the main dev tree
> and since nobody implemented this for FOP Trunk, yet, this is not
> available. ATM you need to use absolute paths in the font configuration.
> Patches welcome. Ideally, the fonts will be loaded through the
> URIResolver.
>
> > conf.setAttribute("baseDir", ctx.getRealPath("/"));
>
> Cannot be specified through the config file right now.
>
> The equivalent would be:
>
> userAgent.setBaseURL(ctx.getRealPath("/"));
>
>
> > .....
> > Fop fop = new Fop(Fop.RENDER_PDF);
> > fop.getUserAgent().setUserConfig(conf);
>
> that's ok but only the font setup and the PDF library are currently
> configured through the config file.
>
> In the following post you will find an attachment with a sample config
> file. You will notice that the whole thing has changed slightly.
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200509.mbox/%3c20050906222251.1F2B.DEV.JEREMIAS@greenmail.ch%3e
>
> > .....
> >
> > or
>
> No, "and". :-)
>
> > fop.getUserAgent().setBaseURL()
> > instead of specifying this inside the DefaultConfiguration?
>
> Not instead. You need to do both.
>
> > (Font basedir is not essential since it is under baseDir)
>
> but relative paths for fonts are currently not possible, I'm afraid.
>
> >
> > Leaving now, I'll simply try tomorrow if no veto occurs ;-)
>
> Veto? It's simply your time. You will see that there are still a few
> things to do to bring FOP Trunk up to the same level for everything. But
> it's good we get reminded this way. But I'll write the docs soon and I'm
> sure I will need to fix a few things while I'm doing that.
>
> > Thanks in advance!
> > sonja
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Am Montag, den 12.09.2005, 12:12 +0200 schrieb Sonja Löhr:
> > > Thank you for the turbo-answer, Jeremias!
> > >
> > > We wrote at the same time ...
> > >
> > > I would be brave ;-) and change the code since it is really small and
> > > differs not much from what happens in FopServlet, I just have some In-
> > > and OutputStreams between but should come along with the javadoc for
> > > that.
> > >
> > > The only complex thing could be the configuration (with both config-file
> > > and programmatically) - is that a great thing to change?
> > > If it is, I would just wait for the release and don't bother you with
> > > questions.
> > >
> > > sonja
> > >
> > >
> > >
> > >
> > >
> > > Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> > > > Sorry, Sonja, but a lot of changes have happened during the redesign
> > > > which break API compatibility. The packages and classes you listed don't
> > > > exist anymore. And the new API has not been documented, yet. This will
> > > > be done in the next two weeks and before the first preview release. In
> > > > the meantime, you can look at the embedding examples in
> > > > examples/embedding on how to embed FOP Trunk in a Java application.
> > > >
> > > > If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> > > > started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> > > > But either way, you will have to change your application once.
> > > >
> > > > Also needless to say that FOP Trunk is unstable (alpha) as will be the
> > > > first preview release.
> > > >
> > > > On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > > > > Hi!
> > > > >
> > > > > After inspecting the new compliance page (:-)) great improvements!!), I
> > > > > finally downloaded the trunk and built it.
> > > > > Now my servlet code is missing several packages/classes :
> > > > > org.apache.fop.messaging
> > > > > org.apache.fop.configuration
> > > > > and classes in org.apache.fop.apps (Driver and Options)
> > > > >
> > > > > Did I miss some sources or where can I find documentation about a new
> > > > > way of programmatic configuration, logging and Servlet integration?
> > > > > Sorry, I'm a bit lost in the developer's section of the fop site.
> > > > >
> > > > > Thank you for some hints,
> > > > > I would love to use the new features!
> > > > >
> > > > > sonja
> > > >
> > > >
> > > > Jeremias Maerki
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > > >
> > --
> > Sonja Löhr <so...@arcor.de>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 12.09.2005 13:31:14 Sonja Löhr wrote:
>
> I try learning ...
>
> Could you please just tell me whether I am on the right track for
> configuration with the fop-trunk?
>
>
> DefaultConfigurationBuilder confbuilder = new
> DefaultConfigurationBuilder();
> Configuration fileconf =
> confbuilder.buildFromFile(ctx.getRealPath(CONFIG_FILE));
So far so good. :-)
> DefaultConfiguration conf = new DefaultConfiguration(fileconf);
I wouldn't do that. It doesn't help because....
> conf.setAttribute("strokeSVGText", false);
Doesn't exist anymore. There's an open task for me to revisit that.
> conf.setAttribute("fontBaseDir", ctx.getRealPath("/WEB-INF/fonts"));
fontBaseDir was introduced after FOP was branched from the main dev tree
and since nobody implemented this for FOP Trunk, yet, this is not
available. ATM you need to use absolute paths in the font configuration.
Patches welcome. Ideally, the fonts will be loaded through the
URIResolver.
> conf.setAttribute("baseDir", ctx.getRealPath("/"));
Cannot be specified through the config file right now.
The equivalent would be:
userAgent.setBaseURL(ctx.getRealPath("/"));
> .....
> Fop fop = new Fop(Fop.RENDER_PDF);
> fop.getUserAgent().setUserConfig(conf);
that's ok but only the font setup and the PDF library are currently
configured through the config file.
In the following post you will find an attachment with a sample config
file. You will notice that the whole thing has changed slightly.
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200509.mbox/%3c20050906222251.1F2B.DEV.JEREMIAS@greenmail.ch%3e
> .....
>
> or
No, "and". :-)
> fop.getUserAgent().setBaseURL()
> instead of specifying this inside the DefaultConfiguration?
Not instead. You need to do both.
> (Font basedir is not essential since it is under baseDir)
but relative paths for fonts are currently not possible, I'm afraid.
>
> Leaving now, I'll simply try tomorrow if no veto occurs ;-)
Veto? It's simply your time. You will see that there are still a few
things to do to bring FOP Trunk up to the same level for everything. But
it's good we get reminded this way. But I'll write the docs soon and I'm
sure I will need to fix a few things while I'm doing that.
> Thanks in advance!
> sonja
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Am Montag, den 12.09.2005, 12:12 +0200 schrieb Sonja Löhr:
> > Thank you for the turbo-answer, Jeremias!
> >
> > We wrote at the same time ...
> >
> > I would be brave ;-) and change the code since it is really small and
> > differs not much from what happens in FopServlet, I just have some In-
> > and OutputStreams between but should come along with the javadoc for
> > that.
> >
> > The only complex thing could be the configuration (with both config-file
> > and programmatically) - is that a great thing to change?
> > If it is, I would just wait for the release and don't bother you with
> > questions.
> >
> > sonja
> >
> >
> >
> >
> >
> > Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> > > Sorry, Sonja, but a lot of changes have happened during the redesign
> > > which break API compatibility. The packages and classes you listed don't
> > > exist anymore. And the new API has not been documented, yet. This will
> > > be done in the next two weeks and before the first preview release. In
> > > the meantime, you can look at the embedding examples in
> > > examples/embedding on how to embed FOP Trunk in a Java application.
> > >
> > > If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> > > started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> > > But either way, you will have to change your application once.
> > >
> > > Also needless to say that FOP Trunk is unstable (alpha) as will be the
> > > first preview release.
> > >
> > > On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > > > Hi!
> > > >
> > > > After inspecting the new compliance page (:-)) great improvements!!), I
> > > > finally downloaded the trunk and built it.
> > > > Now my servlet code is missing several packages/classes :
> > > > org.apache.fop.messaging
> > > > org.apache.fop.configuration
> > > > and classes in org.apache.fop.apps (Driver and Options)
> > > >
> > > > Did I miss some sources or where can I find documentation about a new
> > > > way of programmatic configuration, logging and Servlet integration?
> > > > Sorry, I'm a bit lost in the developer's section of the fop site.
> > > >
> > > > Thank you for some hints,
> > > > I would love to use the new features!
> > > >
> > > > sonja
> > >
> > >
> > > Jeremias Maerki
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> > >
> --
> Sonja Löhr <so...@arcor.de>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
I try learning ...
Could you please just tell me whether I am on the right track for
configuration with the fop-trunk?
DefaultConfigurationBuilder confbuilder = new
DefaultConfigurationBuilder();
Configuration fileconf =
confbuilder.buildFromFile(ctx.getRealPath(CONFIG_FILE));
DefaultConfiguration conf = new DefaultConfiguration(fileconf);
conf.setAttribute("strokeSVGText", false);
conf.setAttribute("fontBaseDir", ctx.getRealPath("/WEB-INF/fonts"));
conf.setAttribute("baseDir", ctx.getRealPath("/"));
.....
Fop fop = new Fop(Fop.RENDER_PDF);
fop.getUserAgent().setUserConfig(conf);
.....
or
fop.getUserAgent().setBaseURL()
instead of specifying this inside the DefaultConfiguration?
(Font basedir is not essential since it is under baseDir)
Leaving now, I'll simply try tomorrow if no veto occurs ;-)
Thanks in advance!
sonja
Am Montag, den 12.09.2005, 12:12 +0200 schrieb Sonja Löhr:
> Thank you for the turbo-answer, Jeremias!
>
> We wrote at the same time ...
>
> I would be brave ;-) and change the code since it is really small and
> differs not much from what happens in FopServlet, I just have some In-
> and OutputStreams between but should come along with the javadoc for
> that.
>
> The only complex thing could be the configuration (with both config-file
> and programmatically) - is that a great thing to change?
> If it is, I would just wait for the release and don't bother you with
> questions.
>
> sonja
>
>
>
>
>
> Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> > Sorry, Sonja, but a lot of changes have happened during the redesign
> > which break API compatibility. The packages and classes you listed don't
> > exist anymore. And the new API has not been documented, yet. This will
> > be done in the next two weeks and before the first preview release. In
> > the meantime, you can look at the embedding examples in
> > examples/embedding on how to embed FOP Trunk in a Java application.
> >
> > If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> > started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> > But either way, you will have to change your application once.
> >
> > Also needless to say that FOP Trunk is unstable (alpha) as will be the
> > first preview release.
> >
> > On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > > Hi!
> > >
> > > After inspecting the new compliance page (:-)) great improvements!!), I
> > > finally downloaded the trunk and built it.
> > > Now my servlet code is missing several packages/classes :
> > > org.apache.fop.messaging
> > > org.apache.fop.configuration
> > > and classes in org.apache.fop.apps (Driver and Options)
> > >
> > > Did I miss some sources or where can I find documentation about a new
> > > way of programmatic configuration, logging and Servlet integration?
> > > Sorry, I'm a bit lost in the developer's section of the fop site.
> > >
> > > Thank you for some hints,
> > > I would love to use the new features!
> > >
> > > sonja
> >
> >
> > Jeremias Maerki
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> > For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
> >
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Sonja Löhr <so...@arcor.de>.
Thank you for the turbo-answer, Jeremias!
We wrote at the same time ...
I would be brave ;-) and change the code since it is really small and
differs not much from what happens in FopServlet, I just have some In-
and OutputStreams between but should come along with the javadoc for
that.
The only complex thing could be the configuration (with both config-file
and programmatically) - is that a great thing to change?
If it is, I would just wait for the release and don't bother you with
questions.
sonja
Am Montag, den 12.09.2005, 11:57 +0200 schrieb Jeremias Maerki:
> Sorry, Sonja, but a lot of changes have happened during the redesign
> which break API compatibility. The packages and classes you listed don't
> exist anymore. And the new API has not been documented, yet. This will
> be done in the next two weeks and before the first preview release. In
> the meantime, you can look at the embedding examples in
> examples/embedding on how to embed FOP Trunk in a Java application.
>
> If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
> started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
> But either way, you will have to change your application once.
>
> Also needless to say that FOP Trunk is unstable (alpha) as will be the
> first preview release.
>
> On 12.09.2005 11:40:50 Sonja Löhr wrote:
> > Hi!
> >
> > After inspecting the new compliance page (:-)) great improvements!!), I
> > finally downloaded the trunk and built it.
> > Now my servlet code is missing several packages/classes :
> > org.apache.fop.messaging
> > org.apache.fop.configuration
> > and classes in org.apache.fop.apps (Driver and Options)
> >
> > Did I miss some sources or where can I find documentation about a new
> > way of programmatic configuration, logging and Servlet integration?
> > Sorry, I'm a bit lost in the developer's section of the fop site.
> >
> > Thank you for some hints,
> > I would love to use the new features!
> >
> > sonja
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
--
Sonja Löhr <so...@arcor.de>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: upgrading from 20.0.5 to the trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Sorry, Sonja, but a lot of changes have happened during the redesign
which break API compatibility. The packages and classes you listed don't
exist anymore. And the new API has not been documented, yet. This will
be done in the next two weeks and before the first preview release. In
the meantime, you can look at the embedding examples in
examples/embedding on how to embed FOP Trunk in a Java application.
If you prefer an API that works on both FOP 0.20.5 and FOP Trunk, I have
started a solution at http://www.jeremias-maerki.ch/dev/jaxg/index.html.
But either way, you will have to change your application once.
Also needless to say that FOP Trunk is unstable (alpha) as will be the
first preview release.
On 12.09.2005 11:40:50 Sonja Löhr wrote:
> Hi!
>
> After inspecting the new compliance page (:-)) great improvements!!), I
> finally downloaded the trunk and built it.
> Now my servlet code is missing several packages/classes :
> org.apache.fop.messaging
> org.apache.fop.configuration
> and classes in org.apache.fop.apps (Driver and Options)
>
> Did I miss some sources or where can I find documentation about a new
> way of programmatic configuration, logging and Servlet integration?
> Sorry, I'm a bit lost in the developer's section of the fop site.
>
> Thank you for some hints,
> I would love to use the new features!
>
> sonja
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org