jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: urgent help needed -to run cactus on jboss-4.2.0
Date Thu, 26 Jun 2008 20:39:31 GMT
Thanks a lot

-----Original Message-----
From: Daniel Lipofsky [mailto:Daniel.Lipofsky@bricsnet.com] 
Sent: Thursday, June 26, 2008 1:37 PM
To: Cactus Users List
Subject: RE: urgent help needed -to run cactus on jboss-4.2.0

First off, I was never able to get cactus to run
out of the box on JBoss 4.2.x.  I had to patch it.
You can see my patch at http://danlipofsky.com/technical/cactus/
My cactus tests ran on other app servers (Orion 2.0.7 and
WebSphere 6.0).  They seem to work pretty well on JBoss 4.2.2
with this patch, but it is definitely a hack.

If anyone has a better way please let me know.

Here are my ant targets.
It's probably more complex than you need.
Hopefully the vars are self-explanatory.
Don't start or stop the server but does test that it is running.

<target name="test.cactus.all" depends="init">
    <antcall target="test.cactus.generic">
        <param name="cactus_test_target" value="test.cactus.junit"/>
        <param name="cactus_test_pattern" value="**/*Test.java"/>

<!-- run the Cactus tests (takes ${cactus_test_target} param) -->
<target name="test.cactus.generic" depends="init" description="run the
Cactus tests on the core module">

    <echo>test.cactus.generic: target=${cactus_test_target}</echo>
    <echo>cactusContextURL: ${cactusContextURL}</echo>
    <fail unless="cactus_test_target" message="Missing
cactus_test_target parameter"/>

    <!-- Check if server is running -->
    <delete file="${java.io.tmpdir}/servercheck.txt" />
dest="${java.io.tmpdir}/servercheck.txt" ignoreerrors="yes" />
    <fail message="Cannot connect to

    Start application before running this task.

                <available file="${java.io.tmpdir}/servercheck.txt" />

    <!-- Define the Cactus tasks -->
    <taskdef resource="cactus.tasks">
        <classpath refid="test.jar.path" />

stoptarget="test.server.stop.bogus" testtarget="${cactus_test_target}"

<target name="test.cactus.junit" depends="init">

    <echo>test.cactus.junit: pattern=${cactus_test_pattern}</echo>
    <fail unless="cactus_test_target" message="Missing
cactus_test_target parameter"/>

    <mkdir dir="${test.report.dir}" />
    <junit printsummary="yes" fork="yes">
        <classpath refid="cactus.full.path" />
        <sysproperty key="cactus.contextURL" value="${cactusContextURL}"
        <sysproperty key="test.app.server" value="${install.app.server}"
        <sysproperty key="baseDirectory" value="${install.dir}" />

        <formatter type="xml" />

        <batchtest fork="yes" todir="${test.report.dir}">
            <fileset dir="${test.src.web.dir}">
                <include name="${cactus_test_pattern}" />
                <exclude name="**/*BaseTest.java" />
            <fileset dir="${test.generated.java.dir}">
                <include name="${cactus_test_pattern}" />

> -----Original Message-----
> Sent: Wednesday, June 18, 2008 1:43 PM
> To: cactus-user@jakarta.apache.org
> Subject: urgent help needed -to run cactus on jboss-4.2.0
> Hi,
>           I want to run cactus test as part of my automation build
> cruisecontrol  ) using ant  on already running jboss-4.2.0. server
> After completing the cactus test i don't want to stop the jboss-4.2.0.
> Please send me the sample ant script code snippet. Cactus test should
> not initiate neither start nor stop the server ,it should just run the
> test alone on running Jboss-4.2.0
> Thanks
> Kumaran

To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-user-help@jakarta.apache.org

View raw message