Yes, I am using Ant. I believe the problem spawns from an issue possibly
with SAX with Tomcat? No properties are being changed, but I can see that
the exception is being thrown from the cactus invocator servlet--- from
tomcat when it tries to resolve the dtd. What is weird to me, is that the
parser is trying to resolve to my project's root.
com.mckesson.smo
--bin
--src <-- source code
----etc
----java
----test
--cactus <-- template/code for copying into test environment with source
----env
----war
--test <-- created by target in ant for testing
+-cactus
+-env
+-conf <-- server.xml, etc
+-webapps
+-test <--- where cactus tests are being run (app)
+-WEB-INF
+-classes
+-object-factory_1_0.dtd <-- the dtd in question
+-core-factory.xml <-- the xml with a SYSTEM dtd spec
Again, nothing is being changed in my ant build files at all, just changing
the 'extends' to ServletTestCase, that is all.
Thanks,
Jacob
-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 12:40 PM
To: 'Cactus Users List'
Subject: RE: Classpath Resolving
Hi Jacob,
How are you starting your Cactus tests? Using Ant? If so, I'm sure
you've changed some lines in your build script. They may cause the
problem?
Thanks
-Vincent
> -----Original Message-----
> From: Hookom, Jacob [mailto:[EMAIL PROTECTED]
> Sent: 06 August 2003 15:33
> To: Cactus Users List
> Subject: RE: Classpath Resolving
>
> Vincent,
>
> I'm wondering the same thing as to why it would be different. From my
> tests, the only thing I change is taking my java test case and making
it
> extend ServletTestCase instead-- which causes SAX to resolve the DTD
to
> the
> project root instead of where the XML is being loaded from?
>
> Cactus is going to save us LOTS of time with development here, we are
very
> appreciative of your efforts. If worst comes to worst, we will just
> duplicate the DTD in the project's root folder.
>
> Thanks,
> Jacob
>
> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 06, 2003 2:38 AM
> To: 'Cactus Users List'
> Subject: RE: Classpath Resolving
>
> Hi Jacob,
>
> There is no difference between TestCase and ServletTestCase WRT paths
> (how could there be?). ServletTestCase simply extends TestCase. I
think
> the problem comes more from the way you execute the Cactus test cases.
> You probably use some Ant task for that and you may be setting the
> execution directory to some location different from what you were
using
> previously.
>
> -Vincent
>
> > -----Original Message-----
> > From: Hookom, Jacob [mailto:[EMAIL PROTECTED]
> > Sent: 06 August 2003 03:34
> > To: [EMAIL PROTECTED]
> > Subject: Classpath Resolving
> >
> > I'm running Ant targets for Unit Testing.
> >
> > One of the steps in the TestCase is to validate an XML file via
DTD--
> > which
> > is resolving wrong with the ServletTestCase.
> >
> > When I declare my test case extending junit.framework.TestCase, no
> > problems
> > arise and the System DTD is located in the same directory as the
XML.
> >
> > But, when I extend ServletTestCase, the DTD location is being
resolved
> > back
> > to the root of project, which is wrong and I get a SAX error with
> > digester's
> > validation.
> >
> > I would much apprechiate any hints as to why the DTD is resolving
> > differently between TestCase and ServletTestCase?
> >
> > Thanks!
> > Jacob
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
