You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Aaron Humphrey <Hu...@Kakari.com> on 2003/07/15 23:47:03 UTC
Error instantiating class with 1.5b1
I've been having problems with Cactus and StrutsTestCase, so I thought I'd download the new version, beta though it is.
Now, unfortunately, it can't even instantiate my classes. What I get when I try to run my CactusStrutsTestCase tests is:
ERROR [AbstractWebTestCaller] Error instantiating class [my.test.class.name([myTestName], [null])]
java.lang.reflect.InvocationTargetException
in my Jboss/Tomcat log, and
javax.servlet.ServletException: Error instantiating class [my.test.class.name([myTestName], [null])]
at org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459)
(I'd provide more info if either my command window or my jUnit window provided cut & paste...)
These tests worked under Cactus 1.4.1. I updated all the appropriate .jar files with the ones from the 1.5b1 distribution.
I was hoping that the new version might fix the problem I was having with 1.4.1, where running my CactusStrutsTestCase would somehow screw up my JSP's <html:form action="..."> mapping.
Aaron V. Humphrey
Kakari Systems, Ltd.
Re: Error instantiating class with 1.5b1
Posted by Christopher Lenz <cm...@gmx.de>.
Just to avoid confusion here, Cactus 1.5-beta1 is not 100% binary
compatible with Cactus 1.4.1, but it should be possible to use
StrutsTestCase 2.0 without problems (and without recompilation of
StrutsTestCase itself). At least it worked in all my tests :-P
-chris
Bastian Bowe wrote:
> Don't know much about cactus jet, but according to the 1.5-beta1
> announcment from Vincent on this mailing list you have to recompile
> all classes. Search for "AbstractWeb" in his mail for details.
>
> Regards
>
> On Tue, Jul 15, 2003 at 03:47:03PM -0600, Aaron Humphrey wrote:
>
>>I've been having problems with Cactus and StrutsTestCase, so I thought I'd download the new version, beta though it is.
>>
>>Now, unfortunately, it can't even instantiate my classes. What I get when I try to run my CactusStrutsTestCase tests is:
>>
>>ERROR [AbstractWebTestCaller] Error instantiating class [my.test.class.name([myTestName], [null])]
>>java.lang.reflect.InvocationTargetException
>>
>>in my Jboss/Tomcat log, and
>>
>>javax.servlet.ServletException: Error instantiating class [my.test.class.name([myTestName], [null])]
>> at org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459)
>>
>>(I'd provide more info if either my command window or my jUnit window provided cut & paste...)
>>
>>These tests worked under Cactus 1.4.1. I updated all the appropriate .jar files with the ones from the 1.5b1 distribution.
>>
>>I was hoping that the new version might fix the problem I was having with 1.4.1, where running my CactusStrutsTestCase would somehow screw up my JSP's <html:form action="..."> mapping.
>>
>>
>>Aaron V. Humphrey
>>Kakari Systems, Ltd.
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: Error instantiating class with 1.5b1
Posted by Bastian Bowe <Ba...@gmx.de>.
Don't know much about cactus jet, but according to the 1.5-beta1
announcment from Vincent on this mailing list you have to recompile
all classes. Search for "AbstractWeb" in his mail for details.
Regards
On Tue, Jul 15, 2003 at 03:47:03PM -0600, Aaron Humphrey wrote:
> I've been having problems with Cactus and StrutsTestCase, so I thought I'd download the new version, beta though it is.
>
> Now, unfortunately, it can't even instantiate my classes. What I get when I try to run my CactusStrutsTestCase tests is:
>
> ERROR [AbstractWebTestCaller] Error instantiating class [my.test.class.name([myTestName], [null])]
> java.lang.reflect.InvocationTargetException
>
> in my Jboss/Tomcat log, and
>
> javax.servlet.ServletException: Error instantiating class [my.test.class.name([myTestName], [null])]
> at org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459)
>
> (I'd provide more info if either my command window or my jUnit window provided cut & paste...)
>
> These tests worked under Cactus 1.4.1. I updated all the appropriate .jar files with the ones from the 1.5b1 distribution.
>
> I was hoping that the new version might fix the problem I was having with 1.4.1, where running my CactusStrutsTestCase would somehow screw up my JSP's <html:form action="..."> mapping.
>
>
> Aaron V. Humphrey
> Kakari Systems, Ltd.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
>
--
Bastian Bowe
Re: Error instantiating class with 1.5b1
Posted by Christopher Lenz <cm...@gmx.de>.
Hi Aaron,
Aaron Humphrey wrote:
> I've been having problems with Cactus and StrutsTestCase, so I thought I'd download the new version, beta though it is.
>
> Now, unfortunately, it can't even instantiate my classes. What I get when I try to run my CactusStrutsTestCase tests is:
>
> ERROR [AbstractWebTestCaller] Error instantiating class [my.test.class.name([myTestName], [null])]
> java.lang.reflect.InvocationTargetException
>
> in my Jboss/Tomcat log, and
>
> javax.servlet.ServletException: Error instantiating class [my.test.class.name([myTestName], [null])]
> at org.apache.cactus.server.AbstractWebTestCaller.getTestClassInstance(AbstractWebTestCaller.java:459)
>
> (I'd provide more info if either my command window or my jUnit window provided cut & paste...)
I suspect there must be a root cause printed further down in the stack
trace... without more details it is really hard to help.
You should be able to copy from the command line BTW, except you're in a
rather exotic environment ;-)
> These tests worked under Cactus 1.4.1. I updated all the appropriate .jar files with the ones from the 1.5b1 distribution.
>
> I was hoping that the new version might fix the problem I was having with 1.4.1, where running my CactusStrutsTestCase would somehow screw up my JSP's <html:form action="..."> mapping.
That sounds more like a problem with StrutsTestCase.
--
Christopher Lenz
/=/ cmlenz at gmx.de