jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Chapman" <Andrew.Chap...@ons.gsi.gov.uk>
Subject cactus ant integration with OC4J / Orion
Date Wed, 10 Sep 2003 10:44:49 GMT

Has anybody succesfully used the <cactus> task with an ear file on oc4j or
Orion 1x? As far as I can tell the configurations for oc4j and orion 1x
should be the same. Everything seems to work OK but the resulting
configuration doesn't look right to me...

The server.xml file points to the (global) application.xml file which in
turn decalres a <web-module> with the path set to
"../ejb-component-cactus,war". But as the cactus task only generates the
ear which contains the war this setup can surely never work.

As the task doesn't use the admin utility to deploy the ear, then surely it
should add an <application> element to server.xml to point to the generated
ear - e.g.

      <application name="ejb-component-cactus"
path="../ejb-component-cactus.ear" auto-start="true" />

and a <web-app> element in default-web-site.xml such as:

      <web-app application="ejb-component-cactus"
name="ejb-component-cactus" root="/ejb-component-cactus"/>

I thought perhaps it was a bug but then I had a look at
http://issues.apache.org/bugzilla/show_bug.cgi?id=22794 and saw Vincent's
comment at the bottom saying he'd tested it with an ear and it worked fine.
Am I missing something?


For the latest data on the economy and society 
consult National Statistics at http://www.statistics.gov.uk

Please Note:  Incoming and outgoing email messages
are routinely monitored for compliance with our policy
on the use of electronic communications
Legal Disclaimer  :  Any views expressed by
the sender of this message are not necessarily
those of the Office for National Statistics

View raw message