On Jan 17, 2005, at 3:31 AM, Vincent Massol wrote:



-----Original Message-----
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: lundi 17 janvier 2005 06:13
To: Maven Users List
Subject: Re: Help with Maven, JBOSS and Cactus


On Jan 17, 2005, at 12:28 AM, Vincent Massol wrote:

Hi David,

Cactus is definitely not a web testing framework. It's a unit testing
framework (i.e. testing at the level of methods) for all J2EE
components
(including EJBs). You're not the first one to think Cactus is a web
testing
framework. I wonder why... :-)

Probably because the first N pages don't mention ejbs.... it took me a while to find the ejb section.

Come on! :-) That's the first sentence on the web site... :-)
True, but the next N pages are all about web stuff. It took me a long time to find the ejb link.

http://jakarta.apache.org/cactus/

That said, any idea on how to improve it or make it more visible?

I'm really bad at web design...


Is it possible to use cactus on an ejb container if no web container is
present?

Not currently. We have planned a loooong time back to have an EJB redirector
(that would thus not require any web container to be present) but that was
never finished (some have contributed some code but it didn't get integrated
into cactus).


[snip]

 BTW, I have created a few
months ago the Cargo framework (http://cargo.codehaus.org) which is a
Java
API to start/stop/configure/deploy J2EE containers. It also provides
Ant
tasks and will soon have a Maven plugin.

Does it work through jsr 88? If so it should have no problems with geronimo.

AFAIK jsr88 does not handle: start, stop and configuration of containers. We
are planning to use it for the management of archives though (start/stop
applications, hot deployments, etc).


correct
I have read jsr88 relatively quickly and I am no expert so please let me
know if I'm wrong in my assumptions about jsr88.



Have you figured out any way to test app client containers?

Not sure what you mean here. A container that is a client of another container? What would be the issues?


I should perhaps say app clients running in their container. They are j2ee modules that can be deployed standalone or in an ear, how you start one is up to the vendor, but they get jndi refs like web or ejb applications, and they run in a separate vm from the server. The client app supplies a main class just like a plain application, but it gets started inside the container. I haven't figured out an easy way of testing one of these.... right now all I've thought of is making the test framework be a main class that delegates to the real main class. You then need some way to communicate from maven running your "tests" to inside the app client container where the test framework is actually running your tests. Since there is no defined input to app clients, I guess you have to open up a socket or something.


many thanks,
david jencks



I'll have to look into cactus some more. Thanks for pointing me towards it!

Cool

[snip]

Thanks
-Vincent



---------------------------------------------------------------------
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]



Reply via email to