Subject:Install Apache FOP Plugin with Windows VIsta problem Author:Jan Verhoek Date:10 Jul 2007 12:06 PM
I've had problems installing Apache FOP plugin with Stylus Studio by just running the 'catalog' example. SS immediately starts downloading the FOP extension and the Vista UAC will ask confirmation. Nevertheless, installing FOP will not take place and the rendering leaves the error message NoClassDeFoundError For. There will also not be any <program\bin\plugins\fop> directory.
I tried starting SS as Administrator but to no success.
I managed though to install Apache FOP under Stylus Studio on Windows XP and copied the whole <plugins\FOP> directory to my Vista system and now it runs fine!
So, I'm fine now. But wonder what I should have done or is this a Vista problem? Anybody experienced the same?
Subject:Install Apache FOP Plugin with Windows VIsta problem Author:Minollo I. Date:10 Jul 2007 12:43 PM
Are you sure Stylus Studio is able to access the Internet to download the on-demand FOP package? For example, if you try to open this from Stylus Studio (File > Open), does it work fine? http://www.stylusstudio.com/SSDN/rss?.xml
Subject:Install Apache FOP Plugin with Windows VIsta problem Author:Jan Verhoek Date:10 Jul 2007 02:01 PM
Thanks again.
Unzipping the FOP file had the same effect as copying the version of my XP-system into the Vista system. So yes, this works.
To eliminate any downloading problem (Firewall etc) I deleted my IDE.CHM file which forces SS to download it again on pressing F1. So it did and installed it perfectly showing the Documentation file.
So, it seems to have nothing to do with the SS plugin installation system, but something with the FOP component in peculiar.
I can continu running my FO now. But if you require any help from me analizing this problem for other 'potential' Vista users, you may contact me.
Subject:Install Apache FOP Plugin with Windows VIsta problem Author:(Deleted User) Date:18 Jul 2008 05:18 AM
Hi Hans,
fop 0.94 is not compatible with 0.20, so you cannot simply replace the jars with the new ones. You have to set up a custom post processing step, e.g specifying c:\fop-0.94\fop.bat %1 %2