Marc,

I've tried to replicate your solution with no success.  In my case I'm 
using TDK 2.1 instead of 2.2, and so did the following:

- removed xerces-1.3.0.jar from WEB-INF/lib in my webapp
- downloaded Xerces-J-bin.2.2.0.tar.gz from xml.apache.org
- extracted xercesImpl.jar xercesSamples.jar and xmlParserAPIs.jar from the 
tarball
- placed those three jars in my WEB-INF/lib directory
- started tomcat and tried to access my webapp

at which point I got a ClassNotFoundException for classes in the 
org.apache.xerces.framework package; upon investigating the three jars from 
the tarball, that package no longer exists!

I'm pretty sure I'm doing something wrong or forgetting something here... 
anyone have any pointers?  Perhaps this fix won't work with tdk2.1, only 
with 2.2?  Or does something need to be recompiled with the new 
classes?  Help -- we launch in 4 days! :)

Thanks,
Derek

At 10:53 AM 9/24/2002, you wrote:
>I was lucky and fixed this finally by doing the following:
>
>1) removing all XML-Parser related jars from my system (not only from TDK,
>but also from classpath), so that I get a classDefNotFound error in the end
>2) downloading the latest Xerces-packages
>3) putting them into web-inf/lib
>
>No double initialization of Turbine anymore.
>No Intake init error anymore.
>
>I really think this should be fixed in a final 2.2 release.
>
>Another issue: I was moving my app outside of webapps to fix the
>context-problem with server.xml.
>It works well, but when you want to re-compile the project,
>web-inf/build/build.xml is expecting the app to reside right under webapps,
>and nowhere else.
>So I guess I need to move my app back under webapps/ and adjust server.xml
>again.
>
>Marc
>
>
> > -----Ursprungliche Nachricht-----
> > Von: Marc Lustig [mailto:[EMAIL PROTECTED]]
> > Gesendet: Dienstag, 24. September 2002 18:05
> > An: Turbine Users List
> > Betreff: which xerces-version to use for Intake? (was: error
> > instantiating Intake with T2.2)
> >
> >
> >
> > > Sheesh, I was really hoping the xml location would fix it.
> > >
> > > Are you by any chance starting Intake both from the coupled services and
> > > fulcrum?
> > >
> > > If you search the user list
> > > (http://marc.theaimsgroup.com/?l=turbine-user&r=1&w=2) for "double
> > > initialization", there are some posts about a misconfigured
> > > server.xml file.
> >
> > Yes, Chris, I went throu these.
> > I fixed something by modifying server.xml and putting my baseDoc
> > outside of
> > webapps.
> > I have only one context in server.xml now:
> > <Context path="/audiotex" docBase="F:\\atsite\\audiotex"
> > reloadable="true"/>
> >
> > It didn't help thou.
> > But looking in the tomcat log let me found an error that is occuring when
> > tomcat/turbine is started up (before the first template is requested):
> >
> > 2002-09-24 15:50:18 StandardContext[/audiotex]: Servlet /audiotex threw
> > load() exception
> > javax.servlet.ServletException: Servlet.init() for servlet audiotex threw
> > exception
> >       at
> > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapp
> > er.java:94
> > 6)
> > ..
> > ----- Root Cause -----
> > java.lang.VerifyError: (class:
> > org/apache/turbine/services/intake/transform/XmlToAppData,
> > method: parseFile
> > signature:
> > (Ljava/lang/String;Z)Lorg/apache/turbine/services/intake/xmlmodel/
> > AppData;)
> > Incompatible object argument for function call
> >       at
> > org.apache.turbine.services.intake.TurbineIntakeService.writeAppDa
> > ta(Turbine
> > IntakeService.java:234)
> >       at
> > org.apache.turbine.services.intake.TurbineIntakeService.init(Turbi
> > neIntakeSe
> > rvice.java:184)
> >       at
> > org.apache.turbine.services.TurbineBaseService.init(TurbineBaseSer
> > vice.java:
> > 108)
> >       at
> > org.apache.turbine.services.BaseInitableBroker.initClass(BaseInita
> > bleBroker.
> > java:149)
> >       at
> > org.apache.turbine.services.BaseServiceBroker.doInitService(BaseSe
> > rviceBroke
> > r.java:224)
> >       at
> > org.apache.turbine.services.BaseServiceBroker.initServices(BaseSer
> > viceBroker
> > .java:193)
> >       at org.apache.turbine.Turbine.init(Turbine.java:257)
> > ..
> >
> > The error seems to occur somewhere in this method:
> > ( parseFile(string) is calling parseFile(String, boolean false) )
> >
> >     /**
> >      * Parse and xml input file and returns a newly
> >      * created and populated AppData structure
> >      */
> >     public AppData parseFile(String xmlFile, boolean skipValidation)
> >         throws Exception
> >     {
> >         SAXParser parser = new SAXParser();
> >
> >         // set the Resolver for the database DTD
> >         DTDResolver dtdResolver = new DTDResolver();
> >         parser.setEntityResolver(dtdResolver);
> >
> >         // We don't use an external content handler - we use this object
> >         parser.setContentHandler(this);
> >         parser.setErrorHandler(this);
> >
> >         // Validate the input file
> >         parser.setFeature(
> >             "http://apache.org/xml/features/validation/dynamic";, true);
> >         parser.setFeature("http://xml.org/sax/features/validation";, true);
> >
> >         FileReader fr = new FileReader (xmlFile);
> >         BufferedReader br = new BufferedReader (fr);
> >         try
> >         {
> >             InputSource is = new InputSource (br);
> >             parser.parse(is);
> >         }
> >         finally
> >         {
> >             br.close();
> >         }
> >
> >         return app;
> >     }
> >
> > So the only exlanation that I have is that there is problem with the
> > Xerces-edition that is provided to Intake.
> > I have xercesImpl-2.0.2.jar in web-inf/lib that came along with the TDK
> > package.
> > Is this wrong??
> > What else xerces-edition to use here?
> >
> > Marc
> >
> >
> > --
> > To unsubscribe, e-mail:
><mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail:
><mailto:[EMAIL PROTECTED]>
>
>
>--
>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to