Re: Continuing Frustration and Misery with Deployer
What happens if you deploy using the Tomcat manager application? Same error or doesn't occur then? This may help zero in on the problem. Glen Allistair Crossley wrote: Hi List, Honestly, I wish Tomcat web application deployment would be easier/smarter. To pre-empt certain list members from telling me it's my fault, I can assure you my WAR itself is totally 100% no doubts valid. Perhaps it is my method of deploying that is causing the issue, I don't know. I am attempting to use the Tomcat Client Deployer (the Ant script that comes with deployer). I use it to compile the WAR and now want to deploy it to a waiting Tomcat. I ensured my Tomcat webapps folder was wiped and the conf/Catalina/localhost had no context configuration files. My WAR contains a META-INF/context.xml for deploying the context configuration. After I compile my WAR with Deployer, I call C:\apache-tomcat-5.5.12-deployerant -Dserver=intratest deploy Buildfile: build.xml deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I wait 5 minutes and then put a request into Tomcat. 404. Why? Because it failed to start the context which in a nutshell is all I ever get when deploying from WARs. My WAR has been exploded fully which is at least something. The logs reveal: 2005-10-07 16:18:29,882 - WARN (org.apache.catalina.startup.HostConfig:597) - A docBase D:\jakarta-tomcat\webapps\ROOT inside the host appBase has been specified, and will be ignored 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3796) - Error starting static Resources java.lang.IllegalArgumentException: Document base D:\jakarta-tomcat\webapps\ROOT does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3777) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3948) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:603) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:680) at org.apache.catalina.startup.Catalina.start(Catalina.java:536) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3949) - Error in resourceStart() 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4100) - Error getConfigured 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4153) - Context [] startup failed due to previous errors 2005-10-07 16:18:30,195 - INFO (org.apache.catalina.core.StandardContext:4250) - Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/] has not been started It is not clear if this exception is thrown at the time when the WAR has not been exploded and of course ROOT will not exist. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true Does nobody else have issues with using the Deployer? Is it just me having all this bad luck? Honestly I am at my wits end with this deployment. I am fed up with manually having to deploy files to our Tomcat servers, exploding them myself and then restarting Tomcat. When will Deployer actually work? Kindest, frustrated, Allistair. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474
Continuing Frustration and Misery with Deployer
Hi List, Honestly, I wish Tomcat web application deployment would be easier/smarter. To pre-empt certain list members from telling me it's my fault, I can assure you my WAR itself is totally 100% no doubts valid. Perhaps it is my method of deploying that is causing the issue, I don't know. I am attempting to use the Tomcat Client Deployer (the Ant script that comes with deployer). I use it to compile the WAR and now want to deploy it to a waiting Tomcat. I ensured my Tomcat webapps folder was wiped and the conf/Catalina/localhost had no context configuration files. My WAR contains a META-INF/context.xml for deploying the context configuration. After I compile my WAR with Deployer, I call C:\apache-tomcat-5.5.12-deployerant -Dserver=intratest deploy Buildfile: build.xml deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I wait 5 minutes and then put a request into Tomcat. 404. Why? Because it failed to start the context which in a nutshell is all I ever get when deploying from WARs. My WAR has been exploded fully which is at least something. The logs reveal: 2005-10-07 16:18:29,882 - WARN (org.apache.catalina.startup.HostConfig:597) - A docBase D:\jakarta-tomcat\webapps\ROOT inside the host appBase has been specified, and will be ignored 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3796) - Error starting static Resources java.lang.IllegalArgumentException: Document base D:\jakarta-tomcat\webapps\ROOT does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3777) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3948) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:603) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:680) at org.apache.catalina.startup.Catalina.start(Catalina.java:536) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3949) - Error in resourceStart() 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4100) - Error getConfigured 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4153) - Context [] startup failed due to previous errors 2005-10-07 16:18:30,195 - INFO (org.apache.catalina.core.StandardContext:4250) - Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/] has not been started It is not clear if this exception is thrown at the time when the WAR has not been exploded and of course ROOT will not exist. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true Does nobody else have issues with using the Deployer? Is it just me having all this bad luck? Honestly I am at my wits end with this deployment. I am fed up with manually having to deploy files to our Tomcat servers, exploding them myself and then restarting Tomcat. When will Deployer actually work? Kindest, frustrated, Allistair. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged.
RE: Continuing Frustration and Misery with Deployer [255790:132313]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Allistair Crossley [EMAIL PROTECTED] Received: 10/7/2005 4:34 PM To: tomcat-user@jakarta.apache.org Subject: Continuing Frustration and Misery with Deployer Hi List, Honestly, I wish Tomcat web application deployment would be easier/smarter. To pre-empt certain list members from telling me it's my fault, I can assure you my WAR itself is totally 100% no doubts valid. Perhaps it is my method of deploying that is causing the issue, I don't know. I am attempting to use the Tomcat Client Deployer (the Ant script that comes with deployer). I use it to compile the WAR and now want to deploy it to a waiting Tomcat. I ensured my Tomcat webapps folder was wiped and the conf/Catalina/localhost had no context configuration files. My WAR contains a META-INF/context.xml for deploying the context configuration. After I compile my WAR with Deployer, I call C:\apache-tomcat-5.5.12-deployerant -Dserver=intratest deploy Buildfile: build.xml deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I wait 5 minutes and then put a request into Tomcat. 404. Why? Because it failed to start the context which in a nutshell is all I ever get when deploying from WARs. My WAR has been exploded fully which is at least something. The logs reveal: 2005-10-07 16:18:29,882 - WARN (org.apache.catalina.startup.HostConfig:597) - A docBase D:\jakarta-tomcat\webapps\ROOT inside the host appBase has been specified, and will be ignored 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3796) - Error starting static Resources java.lang.IllegalArgumentException: Document base D:\jakarta-tomcat\webapps\ROOT does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3777) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3948) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:603) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020) at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) at org.apache.catalina.core.StandardService.start(StandardService.java:450) at org.apache.catalina.core.StandardServer.start(StandardServer.java:680) at org.apache.catalina.startup.Catalina.start(Catalina.java:536) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) 2005-10-07 16:18:30,163 - ERROR (org.apache.catalina.core.StandardContext:3949) - Error in resourceStart() 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4100) - Error getConfigured 2005-10-07 16:18:30,195 - ERROR (org.apache.catalina.core.StandardContext:4153) - Context [] startup failed due to previous errors 2005-10-07 16:18:30,195 - INFO (org.apache.catalina.core.StandardContext:4250) - Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/] has not been started It is not clear if this exception is thrown at the time when the WAR has not been exploded and of course ROOT will not exist. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true Does nobody else have issues with using the Deployer? Is it just me having all this bad luck? Honestly I am at my wits end with this deployment. I am fed up with manually having
RE: Continuing Frustration and Misery with Deployer
From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: Continuing Frustration and Misery with Deployer deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I suspect all that means is that it was successfully copied to webapps, but I'm not certain. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true The docBase attribute doesn't look right - it's specifying an absolute path to the directory, and I doubt that's where the war is exploded to. Have you tried removing this? Also, I seem to recall that if you're trying to deploy the default application for the host, it must be named ROOT.war (at least on 5.5.x). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer [255802:132327]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Caldarale, Charles R [EMAIL PROTECTED] Received: 10/7/2005 5:01 PM To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: RE: Continuing Frustration and Misery with Deployer From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: Continuing Frustration and Misery with Deployer deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I suspect all that means is that it was successfully copied to webapps, but I'm not certain. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true The docBase attribute doesn't look right - it's specifying an absolute path to the directory, and I doubt that's where the war is exploded to. Have you tried removing this? Also, I seem to recall that if you're trying to deploy the default application for the host, it must be named ROOT.war (at least on 5.5.x). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer
Hi, Thanks for your thoughts. I agree, deployed OK certainly does not mean a valid deployment ;) The docs say of docBase The Document Base ... for this web application, or the pathname to the web application archive file (if this web application is being executed directly from the WAR file). You may specify an absolute pathname for this directory or WAR file, or a pathname that is relative to the appBase directory of the owning Host. The thing is, I do not wish to execute directly from the WAR as that would be inefficient. I thought I could deploy a WAR, that it would explode and then initialise itself. It seems to me like (if it actually manages to explode in time which is not always the case) that initialisation of the context does not wait on complete extraction of the WAR. Therefore to avoid executing from the WAR itself I use a relative path to the web application. Perhaps I should be specifying docBase=ROOT rather than /ROOT. Thanks again, I need all the help I can get with this deployment malarky! Cheers, Allistair -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: 07 October 2005 17:03 To: Tomcat Users List Subject: RE: Continuing Frustration and Misery with Deployer From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: Continuing Frustration and Misery with Deployer deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I suspect all that means is that it was successfully copied to webapps, but I'm not certain. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true The docBase attribute doesn't look right - it's specifying an absolute path to the directory, and I doubt that's where the war is exploded to. Have you tried removing this? Also, I seem to recall that if you're trying to deploy the default application for the host, it must be named ROOT.war (at least on 5.5.x). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer [255805:132330]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Allistair Crossley [EMAIL PROTECTED] Received: 10/7/2005 5:11 PM To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: RE: Continuing Frustration and Misery with Deployer Hi, Thanks for your thoughts. I agree, deployed OK certainly does not mean a valid deployment ;) The docs say of docBase The Document Base ... for this web application, or the pathname to the web application archive file (if this web application is being executed directly from the WAR file). You may specify an absolute pathname for this directory or WAR file, or a pathname that is relative to the appBase directory of the owning Host. The thing is, I do not wish to execute directly from the WAR as that would be inefficient. I thought I could deploy a WAR, that it would explode and then initialise itself. It seems to me like (if it actually manages to explode in time which is not always the case) that initialisation of the context does not wait on complete extraction of the WAR. Therefore to avoid executing from the WAR itself I use a relative path to the web application. Perhaps I should be specifying docBase=ROOT rather than /ROOT. Thanks again, I need all the help I can get with this deployment malarky! Cheers, Allistair -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: 07 October 2005 17:03 To: Tomcat Users List Subject: RE: Continuing Frustration and Misery with Deployer From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: Continuing Frustration and Misery with Deployer deploy: [deploy] OK - Deployed application at context path /ROOT So it's deployed OK. I suspect all that means is that it was successfully copied to webapps, but I'm not certain. My META-INF/context.xml has Context docBase=/ROOT reloadable=true antiJARLocking=true antiResourceLocking=true swallowOutput=true The docBase attribute doesn't look right - it's specifying an absolute path to the directory, and I doubt that's where the war is exploded to. Have you tried removing this? Also, I seem to recall that if you're trying to deploy the default application for the host, it must be named ROOT.war (at least on 5.5.x). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer
From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: RE: Continuing Frustration and Misery with Deployer The thing is, I do not wish to execute directly from the WAR as that would be inefficient. If you only have classes (as opposed to resource files) I don't think it will make a difference. If you do have other resources in there, then yes, expanding the war would probably be better. However, I think that's controlled solely by the unpackWARs attribute of the Host tag, and has nothing to do with docBase. Therefore to avoid executing from the WAR itself I use a relative path to the web application. Perhaps I should be specifying docBase=ROOT rather than /ROOT. That would probably be better; I wonder if you even need a docBase attribute at all? If the war file is under webapps, it may be redundant (and possibly a contributor to the errors in the log). Is your app deployed from ROOT.war? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer [255810:132337]
Many thanks for your email. This is an automated response acknowledging receipt. Please be advised that Badge mailing commences beginning of October 2005. Should your message require a response we will respond shortly. Regards Meridian Club -Original Message- From: Caldarale, Charles R [EMAIL PROTECTED] Received: 10/7/2005 5:21 PM To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: RE: Continuing Frustration and Misery with Deployer From: Allistair Crossley [mailto:[EMAIL PROTECTED] Subject: RE: Continuing Frustration and Misery with Deployer The thing is, I do not wish to execute directly from the WAR as that would be inefficient. If you only have classes (as opposed to resource files) I don't think it will make a difference. If you do have other resources in there, then yes, expanding the war would probably be better. However, I think that's controlled solely by the unpackWARs attribute of the Host tag, and has nothing to do with docBase. Therefore to avoid executing from the WAR itself I use a relative path to the web application. Perhaps I should be specifying docBase=ROOT rather than /ROOT. That would probably be better; I wonder if you even need a docBase attribute at all? If the war file is under webapps, it may be redundant (and possibly a contributor to the errors in the log). Is your app deployed from ROOT.war? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Meridian Club Unit 5, Caxton Centre Porters Wood St Albans Herts UNITED KINGDOM AL3 6XT Tel: +44 1727 738855 Fax: +44 1700 578955 email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuing Frustration and Misery with Deployer
Hi, The thing is, I do not wish to execute directly from the WAR as that would be inefficient. If you only have classes (as opposed to resource files) I don't think it will make a difference. If you do have other resources in there, then yes, expanding the war would probably be better. However, I think that's controlled solely by the unpackWARs attribute of the Host tag, and has nothing to do with docBase. The web application is a whopping 22MB WAR consisting of resources, jsps, classes, you name it (although the web server is linked to the unpacked resources location to serve those). Therefore to avoid executing from the WAR itself I use a relative path to the web application. Perhaps I should be specifying docBase=ROOT rather than /ROOT. That would probably be better; I wonder if you even need a docBase attribute at all? If the war file is under webapps, it may be redundant (and possibly a contributor to the errors in the log). Is your app deployed from ROOT.war? The docBase attribute is listed in the docs as being needed, I could try without it. My WAR is called ROOT.war yes. Thanks again, I will need to try these permutations and get back to the list. Allistair FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLACK Disclaimer: The information contained within this e-mail is confidential and may be privileged. This email is intended solely for the named recipient only; if you are not authorised you must not disclose, copy, distribute, or retain this message or any part of it. If you have received this message in error please contact the sender at once so that we may take the appropriate action and avoid troubling you further. Any views expressed in this message are those of the individual sender. QAS Limited has the right lawfully to record, monitor and inspect messages between its employees and any third party. Your messages shall be subject to such lawful supervision as QAS Limited deems to be necessary in order to protect its information, its interests and its reputation. Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS Limited cannot guarantee that attachments are virus free or compatible with your systems and does not accept any liability in respect of viruses or computer problems experienced. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
