You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ferdinand Soethe <fe...@apache.org> on 2008/02/04 21:38:10 UTC
pdf-plugin with fop .94 - can sbdy please help?
I have prepared the pdf-plugin and done all the steps that I
thought were needed:
- moved the libs from lib/core to the plugin-lib-dir
- moved the style-sheets from common skin to
plugin-resources-dir
- adjusted output.xmap to the best of my understanding
- removed the fo-pipeline from main sitemap
- changed build.xml
- done a local-deploy
- run fop94-forrest
but something is badly wrong. I don't even get the .fo anymore.
Any hints where I made a mistake?
Thanks,
Ferdinand
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Batik versions until 1.7 don't use xmlgraphics-commons.jar at all, so
there won't be any conflicts there for now. The next Batik release,
however, will use XML Graphics Commons. The JAR contains classes used by
both FOP and Batik but Batik hasn't switched over to use it, yet.
On 06.02.2008 00:54:36 David Crossley wrote:
> Are you also getting conflicts between batik-all.jar and
> your newer xmlgraphics.jar ? I don't know what is in
> the latter, by the way.
>
> There are tests for our SVG in the forrest seed sample site
> at linking.html#images and the generated banner images.
>
> -David
Jeremias Maerki
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by David Crossley <cr...@apache.org>.
Are you also getting conflicts between batik-all.jar and
your newer xmlgraphics.jar ? I don't know what is in
the latter, by the way.
There are tests for our SVG in the forrest seed sample site
at linking.html#images and the generated banner images.
-David
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> David Crossley wrote:
> >Ferdinand Soethe wrote:
> >>
> >>Actually I regret having moved them back.
> >>If we do, the plugin won't work with Forrest 0.8 w/o manual
> >>copying of libraries.
> >>
> >>Therefore I'd suggest to move them back into the plugin-in
> >>dir at least until Forrest 0.9 is released.
> >>
> >>wdyt?
> >
> >Not clear what you mean. I am talking about two copies of
> >"commons logging" ...
> >http://svn.apache.org/viewvc/forrest/branches/UpdateFOPto094/lib/core/
>
> Yes I know. And both issues are related.
>
> fop requires the newer version of that lib and Forrest used
> the older version so I was not sure what happended if I
> removed it.
As with all supporting libraries, if a newer one is available
and someone feels that there are benefits, then replace
the jar and run 'build test' and the site-author docs.
This does a reasonably thorough test. Plus for example
if it the logging library, then ensure logging still works.
Obviously it is best to do this one library at a time.
> I simply figured that two differently named
> versions of a library could coexist.
>
> How does library calling work inside. Does the caller know
> which version it needs an call the right library if there is
> more than one?
As far as i know, the answer is no. At least in current Forrest.
-David
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Thorsten Scherler <th...@apache.org>.
On Tue, 2008-02-05 at 16:59 +0100, Ferdinand Soethe wrote:
...
> >>> There are now copies of at least "commons-logging" jars.
> >>>
> >
>
> Yes I know. And both issues are related.
>
> fop requires the newer version of that lib and Forrest used
> the older version so I was not sure what happended if I
> removed it. I simply figured that two differently named
> versions of a library could coexist.
May peacefully coexist, may not. We need to try if forrest works with
the new one as well and remove the old one.
It is never a good idea to have different versions of a lib in the
classpath. You cannot assure which version will be used since it would
depend on the position in the classpath. That can lead to very ugly
bugs.
>
> How does library calling work inside. Does the caller know
> which version it needs an call the right library if there is
> more than one?
>
No. Libs are basically an aggregation of java classes in a zip. A java
class will call methods and/or classes of such an aggregation. There is
no way to determine which version of a method to use in java.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Ferdinand Soethe <fe...@apache.org>.
David Crossley wrote:
> Ferdinand Soethe wrote:
>> Actually I regret having moved them back.
>> If we do, the plugin won't work with Forrest 0.8 w/o manual
>> copying of libraries.
>>
>> Therefore I'd suggest to move them back into the plugin-in
>> dir at least until Forrest 0.9 is released.
>>
>> wdyt?
>
> Not clear what you mean. I am talking about two copies of
> "commons logging" ...
> http://svn.apache.org/viewvc/forrest/branches/UpdateFOPto094/lib/core/
>
> -David
>
>> David Crossley wrote:
>>> Ferdinand Soethe wrote:
>>>> Thorsten Scherler wrote:
>>>>> Ferdinand Soethe wrote:
>>>>>> - moved the libs from lib/core to the plugin-lib-dir
>>>>> IMO you moved too much (see the other mail).
>>>> That's fixed.
>>> There are now copies of at least "commons-logging" jars.
>>>
>
Yes I know. And both issues are related.
fop requires the newer version of that lib and Forrest used
the older version so I was not sure what happended if I
removed it. I simply figured that two differently named
versions of a library could coexist.
How does library calling work inside. Does the caller know
which version it needs an call the right library if there is
more than one?
Best regards,
Ferdinand Soethe
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> Actually I regret having moved them back.
> If we do, the plugin won't work with Forrest 0.8 w/o manual
> copying of libraries.
>
> Therefore I'd suggest to move them back into the plugin-in
> dir at least until Forrest 0.9 is released.
>
> wdyt?
Not clear what you mean. I am talking about two copies of
"commons logging" ...
http://svn.apache.org/viewvc/forrest/branches/UpdateFOPto094/lib/core/
-David
> David Crossley wrote:
> >Ferdinand Soethe wrote:
> >>Thorsten Scherler wrote:
> >>>Ferdinand Soethe wrote:
> >>>>- moved the libs from lib/core to the plugin-lib-dir
> >>>IMO you moved too much (see the other mail).
> >>That's fixed.
> >
> >There are now copies of at least "commons-logging" jars.
> >
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Ferdinand Soethe <fe...@apache.org>.
Actually I regret having moved them back.
If we do, the plugin won't work with Forrest 0.8 w/o manual
copying of libraries.
Therefore I'd suggest to move them back into the plugin-in
dir at least until Forrest 0.9 is released.
wdyt?
Ferdinand
David Crossley wrote:
> Ferdinand Soethe wrote:
>> Thorsten Scherler wrote:
>>> Ferdinand Soethe wrote:
>>>> - moved the libs from lib/core to the plugin-lib-dir
>>> IMO you moved too much (see the other mail).
>> That's fixed.
>
> There are now copies of at least "commons-logging" jars.
>
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by David Crossley <cr...@apache.org>.
Ferdinand Soethe wrote:
> Thorsten Scherler wrote:
> > Ferdinand Soethe wrote:
> >>- moved the libs from lib/core to the plugin-lib-dir
> >
> >IMO you moved too much (see the other mail).
>
> That's fixed.
There are now copies of at least "commons-logging" jars.
> >>- moved the style-sheets from common skin to
> >> plugin-resources-dir
> >>- adjusted output.xmap to the best of my understanding
> >
> >Try cocoon:// instead (see side note on the other mail) and I guess you
> >get back the fo.
>
> Thanks Thorsten. That did the trick.
>
> >>- removed the fo-pipeline from main sitemap
> >>- changed build.xml
> >
> >What did you change? Did not see a commit.
>
> I actually had not committed build.xml yet.
> Done now.
See the notes at http://forrest.apache.org/docs/dev/howto/howto-buildPlugin.html#descriptor
"Managing the plugins descriptors" and keeping them
synchronised with the plugin's build.xml.
Although i suppose that that will happen after the merge and before
deploying the new plugin.
-David
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Ferdinand Soethe <fe...@apache.org>.
Thorsten Scherler wrote:
>> - moved the libs from lib/core to the plugin-lib-dir
>
> IMO you moved too much (see the other mail).
That's fixed.
>> - moved the style-sheets from common skin to
>> plugin-resources-dir
>> - adjusted output.xmap to the best of my understanding
>
> Try cocoon:// instead (see side note on the other mail) and I guess you
> get back the fo.
Thanks Thorsten. That did the trick.
>> - removed the fo-pipeline from main sitemap
>> - changed build.xml
>
> What did you change? Did not see a commit.
I actually had not committed build.xml yet.
Done now.
Best regards,
Ferdinand Soethe
Re: pdf-plugin with fop .94 - can sbdy please help?
Posted by Thorsten Scherler <th...@apache.org>.
On Mon, 2008-02-04 at 21:38 +0100, Ferdinand Soethe wrote:
> I have prepared the pdf-plugin and done all the steps that I
> thought were needed:
>
> - moved the libs from lib/core to the plugin-lib-dir
IMO you moved too much (see the other mail).
> - moved the style-sheets from common skin to
> plugin-resources-dir
> - adjusted output.xmap to the best of my understanding
Try cocoon:// instead (see side note on the other mail) and I guess you
get back the fo.
> - removed the fo-pipeline from main sitemap
> - changed build.xml
What did you change? Did not see a commit.
> Any hints where I made a mistake?
HTH
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions