Andrew, I'm actually testing it now with an EAR. I should have it working soon. I will let you know.
Thanks -Vincent > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: 13 September 2003 12:08 > To: 'Cactus Users List' > Subject: RE: cactus ant integration with OC4J / Orion > > Thanks Andrew. In the end, I have defined 2 sets of Orion config files: > one for WAR deployments and one for EAR deployments. Another solution > would have been to systematically EARify war deployments but that was more > difficult to implement and more time-consuming during execution. > > A pity Orion doesn't support automatic deployments for War (I haven't > tried it though but all docs I have read seem to imply it). > > A pity also that Orion requires a default web app. Not sure I understand > the rationale... > > I have tried it for WAR deployments and it works. I haven't tried it for > EAR deployments yet and thus it still probably has some errors... If you > want to give it a go please do so. In the mean time I'm trying to setup an > EJB sample in Cactus that will deploy an EAR. It will also serve as a > functional test for EAR deployments. But I haven't finished it and it will > still take some time. In the meantime, I'd like to release Cactus 1.5... > > Thanks > -Vincent > > > -----Original Message----- > > From: Andrew Chapman [mailto:[EMAIL PROTECTED] > > Sent: 12 September 2003 15:57 > > To: [EMAIL PROTECTED] > > Subject: RE: cactus ant integration with OC4J / Orion > > > > > > Hi Vincent, > > > > I can't see any way around defining a default-web-app in > > default-web-site.xml. You'll then need to define a web-module in > > application.xml with a path to a valid web application - the minimum > > requirements for which appears to be a WEB-INF/web.xml containing an > empty > > <web-app/> tag. The default app is needed to create a valid default web > > site which orion can auto-bind the automatically deployed web app to. > > > > I agree with you that using the auto-deploy method is pobably the > simplest > > for ear files - however I don't think it supports auto deploying of war > > files so you might just leave well alone there and have different deploy > > methods for ears and wars. The config changes and inclusion of the > web.xml > > in AbstractOrionContainer.java to support ear auto-deploy shouldn't > affect > > current war deployment. > > > > I also found that if I didn't set deployment-directory in server.xml > then > > I > > got an "IO error writing cache" error for each ejb module that was > > deployed. > > > > Thus for my ear containing a cactified war plus two ejb modules I had > the > > following config: > > > > server.xml > > ========= > > <application-server application-auto-deploy-directory="../" > > deployment-directory="../application-deployments"> > > <rmi-config path="./rmi.xml" /> > > <transaction-config timeout="30000" /> > > <global-application name="default" path="./application.xml" /> > > <global-web-app-config path="./global-web-application.xml" /> > > <web-site default="true" path="./default-web-site.xml" /> > > </application-server> > > > > default-web-site.xml > > ================= > > <web-site port="8888" display-name="Default Orion WebSite"> > > <default-web-app application="default" name="defaultWebApp" /> > > </web-site> > > > > application.xml > > ============= > > <orion-application> > > <web-module id="defaultWebApp" path="../default-web-app" /> > > . > > . > > </orion-application> > > > > With the web.xml described above in default-web-app/WEB-INF > > > > Hope this helps. > > > > Andy > > > > > > > > > > > > [EMAIL PROTECTED] > > om To: cactus- > > [EMAIL PROTECTED] > > cc: Andrew > > Chapman/[EMAIL PROTECTED] > > 11/09/03 16:51 Subject: RE: cactus ant > > integration with OC4J / Orion > > Please respond to > > cactus-user > > > > > > > > > > > > > > Hi Andrew, > > > > I'm no orion expert. I'm trying to set it up so that it uses automatic > > deployment (as described in > > http://www.orionserver.com/docs/application-deployment.html#autoDeploy). > > That seems the simplest to me as it means we don't need to define > > whether we are deploying a war file or an ear file in the config files. > > > > However, I need your help as I cannot find the right config. > > > > Basically my issue is that I still want to tell Orion on what port the > > web container should listen to. Thus, I think I need a <web-site > > path="./default-web-site.xml" /> entry in server.xml because the port is > > defined in the <web-site host="[ALL]" port="@cactus.port@"[...] element. > > > > By apparently, the <web-site> element *requires* a <default-web-app> > > entry. But then I don't want to add one as I don't know what it will be > > as I don't know what file will be deployed. > > > > Any idea? I guess I should ask on on the orion mailing list/forum but I > > thought I'd run this by you first. > > > > Thanks > > -Vincent > > > > > -----Original Message----- > > > From: Andrew Chapman [mailto:[EMAIL PROTECTED] > > > Sent: 10 September 2003 12:45 > > > To: [EMAIL PROTECTED] > > > Subject: cactus ant integration with OC4J / Orion > > > > > > Hi, > > > > > > 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? > > > > > > Andy > > > > > > > > > > > > > > > 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 > > > ********************************************************************** > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > PLEASE NOTE: THE ABOVE MESSAGE WAS RECEIVED FROM THE INTERNET. > > > > On entering the GSI, this email was scanned for viruses by the > Government > > Secure Intranet (GSI) virus scanning service supplied exclusively by > Cable > > & Wireless in partnership with MessageLabs. > > > > GSI users see > > http://www.gsi.gov.uk/main/notices/information/gsi-003-2002.pdf for > > further > > details. In case of problems, please call your organisational IT > helpdesk. > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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]
