Regardless of the Ant task etc if I drop a cactified WAR into the apps dir of Weblogic it attempts to hot deploy and fails. The WAR itself only contains the following :
META-INF/ META-INF/MANIFEST.MF jspRedirector.jsp WEB-INF/ WEB-INF/web.xml WEB-INF/lib/ WEB-INF/lib/aspectjrt-1.1.1.jar WEB-INF/lib/cactus-1.5.jar WEB-INF/lib/commons-logging-1.0.3.jar WEB-INF/lib/commons-httpclient-2.0-rc2.jar WEB-INF/lib/junit.jar I might be missing the point but I assumed that at least this should deploy ??? -----Original Message----- From: Mark Lybarger [mailto:[EMAIL PROTECTED] Sent: 25 March 2004 15:17 To: Cactus Users List Subject: RE: Weblogic 8.1 deploy issue I'm not familiar with what needs done to properly initialize the cactified war. Maybe someone else can elaborate. Perhaps it's just a classpath type of thing. Are you using weblogic provided ant tasks to deploy your application? Can you run your server in development mode (non-production) to let the cactified war auto deploy when it's placed into the applications folder? Only thing i can think of is that things are getting put into the classpath when running the ant task that cactus doesn't like. IIRC, wls includes their own older version of ant (1.5.3) which may or may not impact things. Personally, I stay clear of weblogic's ant tasks since they lock you into that ant version. > -----Original Message----- > From: Darren Witham [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 25, 2004 8:27 AM > To: Cactus Users List > Subject: RE: Weblogic 8.1 deploy issue > > > Hi Mark, > > Thanks for reply. I attempted to deploy just a plain test > war that I created as you suggest : > > <cactifywar version="2.3" destfile="testcact.war"/>. > > This still fails so it is something silly ??????? Outside > of the logs the deployer churns out the following : > > Deploying: coreservices-cactus-test.ear > [java] Initiated Task: [9] [Deployer:149026]Deploy > application coreservices-cactus-test on cgServer. > [java] Application coreservices-cactus-test preparing on > server cgServer. > [java] Module testcact: unprepared to prepared on server > cgServer. > [java] Application coreservices-cactus-test prepared on > server cgServer. > [java] Application coreservices-cactus-test activating > on server cgServer. > [java] Module testcact: prepared to active on server cgServer. > [java] Application coreservices-cactus-test failed on > server cgServer. > [java] Module testcact: active to prepared on server cgServer. > [java] Module testcact: prepared to unprepared on server > cgServer. > [java] Task 9 failed: [Deployer:149026]Deploy > application coreservices-cactus-test on cgServer. > [java] Deployment failed on Server cgServer > [java] weblogic.management.DeploymentException: > [java] > Exception:weblogic.management.ApplicationException: start() failed. > [java] Module: testcact Error: > java.lang.ExceptionInInitializerError > > Thx > > -----Original Message----- > From: Mark Lybarger [mailto:[EMAIL PROTECTED] > Sent: 25 March 2004 13:01 > To: Cactus Users List > Subject: RE: Weblogic 8.1 deploy issue > > > Darren, > > Are you able to deploy a plain jane cactified war? Using > something like this: > <cactifywar version="2.3" destfile="test.war"/> > I'm only using cactus to test ejbs with wls 8.1 right now. > We don't have any client items that we can easily test using > cactus (turbine/velocity framework). Someone correct me if > i'm wrong, but all cactus needs on the cactified war side is > to have the .class files of the tests and all classes needed > to invoke the tests classes. maybe some supporting jars as > well (web-inf/lib). For ejbs this means having remote > interfaces available. Then cactus will proxy off to the > actual running component. So for me, I deploy a > cactifiedwar, and our ear which contains only ejbs and > supporting jar files. The cactified war contains (as a > convenience) all our class files, but not deployment > descriptors or anything like that. the beans the war uses are > the beans deployed as part of our ear. > > I've found Weblogic's error messages to be cryptic and hard > to track down. A rough guess would be that something in your > app (within the cactified war) wasn't able to initialize so > it bailed out. that's probably way off, probably would need > more info from the log file to help better determine the cause. > > Maybe you can try to deploy your war, as well as a cactified > war that contains just your class files and web-inf/lib > folder to the same server (maybe you just have one in > development), and see how that goes? > > > -----Original Message----- > > From: Darren Witham [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 25, 2004 7:44 AM > > To: [EMAIL PROTECTED] > > Subject: Weblogic 8.1 deploy issue > > > > > > Hi, > > > > I am having some issues deploying a cactified WAR onto Weblogic. > > > > I am simply creating a WAR file using ANT and then applying > > the <cactifywar> task. When I examine what this task has done > > I see that the web.xml file has been modified and a few > > libraries added to WEB-INF/lib as expected. However when I > > attempt to deploy this WAR either via ANT (using > > Weblogic.deploy) or simply attempting to hot deploy it, > > Weblogic complains with the following : > > > > [java] > > Exception:weblogic.management.ApplicationException: start() failed. > > [java] Module: coreservices Error: > > java.lang.ExceptionInInitializerError > > > > A further look in the logs shows : > > > > weblogic.management.DeploymentException: > > Exception:weblogic.management.ApplicationException: start() > > failed Module: coreservices Error: > > java.lang.ExceptionInInitializerError at > > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.do > > Commit(SlaveDeployer.java:2549 at > > weblogic.management.deploy.slave.SlaveDeployer$Task.commit(Sla > > veDeployer.java:2349 at > > weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoC > > ommit(SlaveDeployer.java:2431 at > > weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(Sl > > aveDeployer.java:2343 at > > weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.pr > > epare(SlaveDeployer.java:2511 at > > weblogic.management.deploy.slave.SlaveDeployer.processPrepareT > > ask(SlaveDeployer.java:833 at > > weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Sl > > aveDeployer.java:542 at > > weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(S > > laveDeployer.java:500 at > > weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCall > > backHandler.java:25 at > > weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197 > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170 > > The WAR file itself deploys fine prior to cactifying it. > > There is no obvious message telling me that the WAR file > > maybe be missing something it requires. > > Any pointers appreciated........ > > Thx > > > > > > > > > > > > > > > > > > ----------------------------------------------------- > > > > You can find us at www.bacs.co.uk > > > > ***************************************************** > > This communication is confidential and intended for > > the exclusive use of the addressee only. You should > > not disclose its contents to any other person. > > If you are not the intended recipient please notify > > the sender named above immediately. > > > > BACS Limited, registered in England, No 1023742, > > 3 De Havilland Road, Edgware, Middlesex, HA8 5QA > > ***************************************************** > > > > > > > --------------------------------------------------------------------- > 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] > > > --------------------------------------------------------------------- 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]
