RE: cactus:catifyear

[Ma...@VerizonWireless.com]

OK, finally have time to attempt this.

My plan is:
1) get cactus:test-war-in-ear working.  This will build the cactified war as
normal, wrap the war in an ear including any dependencies that have
ear.bundle
2) Look into modifying cactus:test to detect whether to call :test-war,
:test-ear, or :test-war-in-ear



-----Original Message-----
From: Vincent Massol [mailto:vmassol@pivolis.com]
Sent: Saturday, August 21, 2004 2:59 AM
To: 'Cactus Users List'
Subject: RE: cactus:catifyear


Hi Marc,

Yes, I think that would be very useful. Maybe the plugin can automatically
detect if it needs to deploy the WAR as an EAR or not?

I'd suggest that the plugin checks to see if there are any ejb defined as
dependencies in the project.xml and that they are tagged with some property
such as ear.bundle (this is the property used by the EAR plugin to decide
what artifact to bundle in the ear). If there are any the plugin could wrap
the cactified war in an ear, adding to the ear the artifacts marked with
ear.bundle. Another alternative is to name the property cactus.ear.bundle.

We can also have an explicitely named goal. We already have cactus:test-war
and cactus:test-ear. We could have cactus:test-war-in-ear.

Thanks
-Vincent

> -----Original Message-----
> From: Marc.Northover@VerizonWireless.com
> [mailto:Marc.Northover@VerizonWireless.com]
> Sent: mercredi 18 août 2004 19:35
> To: cactus-user@jakarta.apache.org
> Subject: cactus:catifyear
> 
> I have been using cactus and ant extensively and now attempting to convert
> to maven.  I have been successful at the following:
> 
> - run ejb tests
> - run war tests (no ejb dependencies)
> 
> Now I am trying to run war tests that have dependencies on ejbs (jsps call
> Business Delegate which calls stateless session bean).  In our current dev
> process we bundle the ejb and war into one ear file and don't use ejb-ref
> declarations in the web.xml.  In other words, we don't use the
> java:comp/env
> approach when we look up our ejbs.  This is causing problems for me as I
> want to test the servlet code that uses the ejbs, but at the same time
> don't
> want to change the code to support run the tests.  I ran into the same
> issues when using cactus and ant, and ended up writing a customer target
> to
> do what I needed.
> 
> I guess what I am looking for is cactus:cactifywarinear (war-in-ear):
> - call cactus:cactifywar
> - create an ear that contains the the cactified war as well as depencies
> with cactus.bundle = true
> - do the normal startup, deploy the cactus-ear, run tests, shut down.
> 
> Since the *.jelly file code is very straightforward I am gonna attempt to
> create a new goal to test and see how it goes.  Is this a feature that
> others would like?  I hope I explained things clearly.
> 
> Marc
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org



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