Hello Marina

That's weird. It should never be necessary to unjar these jar to make
them work. Looking a bit closer at your case I have a few comments:
- You seem to edit Tomcat's classpath to include all jars you need. It's
  better if you placed all jars needed by your SOAP service in the
  WEB-INF/lib directory. That way they are packed together with your
  webapp/soap-service and loaded automatically without adjusting
  Tomcat's classpath. The jars I'd put there, are: avalon-framework,
  logkit, fop, batik, soap, mail and activation. xerces is needed by
  Tomcat and I've had troubles putting xalan.jar in WEB-INF/lib because
  of the way JAXP works, so leave them there.
- In you last mail you mentioned a batik-1.1.1.jar. If I'm right FOP
  needs a specially built batik.jar (included in the distribution), so
  you might run into problems if you use an official release. Keiron,
  please correct me if I'm wrong.
- I've done similar stuff to what you're doing, and I could do without
  any special work-arounds. On Windows and Linux.
- Think about making a WAR file from your web service. That way, it's
  much simpler to deploy. Without manual classpath surgery.
- I propose you install a fresh Tomcat to another location and start
  over with the hints I gave you. It may well work what you've done, but
  it's a hell to maintain.
- I guess you're using Tomcat 3.x. Try 4.0.x. I like it a lot better.
- Maybe have a look at the current CVS version of FOP. In the contrib
  directory, there's the sources of the FopServlet. The build creates a
  WAR file. It's quite similar to what you're doing. Apache SOAP is a
  servlet, too, right?

Good luck!

On 12.04.2002 15:13:24 Marina Pérel wrote:
> Hello Jeremias,
> 
> Thanks for your help, but I finally found the problem : you must unjar the
> avalon-framework-4.1.2's jar and the
> batik-1.1.1's jar. I take a lot of time to find that because there isn't
> this information in fop's doc or in mailing list. It's curious, no?
> You don't have to unjar the avalon-framework-4.1.1'sjar.
> Greetings
> Marina
> 
> ----- Original Message -----
> From: "Jeremias Maerki" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 11, 2002 12:07 PM
> Subject: Re: Help! Problem with Fop in Tomcat
> 
> 
> > > I developped a Fop service via a service web (with Apache SOAP) in
> Windows Nt : it works good.
> > > But, now i'm trying to set the Fop Service in Linux machine (RedHat7.2).
> > > I have this error :
> > >     Genarated fault :
> > >        Fault Code = SOAP-ENV:Server
> > >         Fault String = Exception from service object :
> > >                 org/apache/avalon/framework/loggable/Loggable
> >
> > That should be org/apache/avalon/framework/logger/Loggable. Did you
> > write that by hand or using copy/paste?
> >
> > Loggable is in avalon-framework(-4.1.2).jar.
> >
> > >  A Hello's service works, so my web service is fine and it's a Fop
> problem.
> > > My Tomcat's classpath is :
> > >
> /tools/beluga/SOAP/xerces-1_2_3/xerces.jar:/tools/beluga/SOAP/jakarta-tomcat
> -4.0.3/lib/xalan.jar:/tools/beluga/SOAP/jakarta-tomcat-4.0.3/lib/avalon-fram
> ework-4.1.2.jar:/tools/beluga/SOAP/jakarta-tomcat-4.0.3/lib/logkit-1.0.1.jar
> :/tools/beluga/SOAP/jakarta-tomcat-4.0.3/lib/batik.jar:/tools/beluga/SOAP/ja
> karta-tomcat-4.0.3/lib/fop.jar:/tools/beluga/SOAP/soap-2_2/lib/soap.jar:/too
> ls/beluga/SOAP/javamail-1.2/mail.jar:/tools/beluga/SOAP/jaf-1.0.1/activation
> .jar:.:/tools/beluga/SOAP/jakarta-tomcat-4.0.3/webapps/soap/WEB-INF/classes/
> :/usr/java/j2sdk1.4.0/lib/tools.jar:/tools/beluga/SOAP/jakarta-tomcat-4.0.3/
> bin/bootstrap.jar
> > > (my .jar files are in the Tomcat lib directory)
> > >
> > > My code for the logger :
> > >     Logger log = null;
> > >   if(log == null) {
> > >     Hierarchy hierarchy = Hierarchy.getDefaultHierarchy();
> > >     log = hierarchy.getLoggerFor("fop");
> > >     log.setPriority(Priority.WARN);
> > >   }
> > >    driver.setLogger(log);
> > >
> > > Does anybody know what's wrong? All ideas are welcome!
> >
> > Avalon Framework and LogKit seem to be present in Tomcat's classpath. So
> > nothing wrong here. Did you check that the files with the names
> > specified in the classpath really exist?
> >
> > Anyway, FOP was recently changed to use
> > org.apache.avalon.framework.logger.Logger (Avalon Logger Interface)
> > instead of org.apache.log.Logger (LogKit). Loggable is used with LogKit.
> > It has been deprecated in favor of
> > org.apache.avalon.framework.logger.LogEnabled (which uses the Avalon
> > Logger Interface). Maybe that helps finding a solution.
> >
> > Cheers,
> > Jeremias Märki
> >
> > mailto:[EMAIL PROTECTED]
> >
> > OUTLINE AG
> > Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
> > Tel. +41 41 317 2020 - Fax +41 41 317 2029
> > Internet http://www.outline.ch



Cheers,
Jeremias Märki

mailto:[EMAIL PROTECTED]

OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - 6002 Luzern
Fon +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch

Reply via email to