hello Aaron > 1)It was mentioned that the J2EE application client is needed to run the ant > scripts. Which means that the user has to install both ANT and the J2EE > application client onto the build machine. Is this correct??
A J2EE application client component is automatically packaged into the testable ear by the AppserverUnit ant task. It may then be invoked from within ant by using the command line tool that comes with Sun 8 application server (see the test.runXX targets in build.xml). I am not sure how this is done with other servers, but since J2EE application clients are part of the spec, it should be possible there as well. > 2)It was mentioned that in ASU there is a session bean called > TestRunnerSession. Does this mean that this session bean needs to be > deployed onto the appserver before testing? If this is the case, does it > have it's own ear or need to be packaged into the application which you are > testing? the session bean is also automatically packaged into the ear by the Appserverunit ant task. One side effect of this is that only one testable ear can be deployed at a time, as otherwise the JNDI names will conflict. This is an outstanding issue (see tracker) regards, christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
