jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Sole Franzin" <mariasole.fran...@allos.it>
Subject testing ejb, classpath problems
Date Wed, 21 May 2003 07:08:55 GMT
>From: Christopher Lenz <cmlenz@gmx.de>
>Subject: testing ejb, classpath problems
>Date: Tue, 20 May 2003 12:24:38 +0200
>Content-Type: text/plain; charset=windows-1252; format=flowed
 
>Hello Maria,
 
>first let me say that I know nothing about the Borland AppServer or 
>JBuilder :-)
 
I>n any case, the classpath with which you start the container should 
>*not* matter for the tests as long as the container can be successfully

>started.
 
>What matters is the classpath of the web-application, which is 
>determined by what classes you put in WEB-INF/classes and what JARs you

>put in WEB-INF/lib. As you're using the ServletTestRunner (I missed
>that 
>part before), the client classpath is the same as the web-application 
>classpath.
 
>Can you verify that this is the case?
 
>-chris
 
 
Hi Chris, Hi all, 
Well, i do verify it more than once.... unfortunatly it seems that
that's not the problem:
These are the dirs inside my WEB-INF:
 
     WEB-INF/classes/junit/framework/....
                    -/org/apache---  
                        -/aspectj
                    -/testcactus/ConverterBean.class ...
                               ...stub...
                               ..... 
                              -/ConverterTest.class 
                    -log4j.xml
            -/lib/aspectjrt.jat
                -/cactus-1.4b1.jar
                -/commons-logging.jar
                -/junit.jar
                -/log4j-1.2.5.jar
            -web.xml
 
that's all
 
thanks ;-)
 
Mariasole 
             
 

Mime
View raw message