Hi
We are accessing the file as per the below url http://172.27.8.57:8081/hub/app/classic/security/Logon_ezelogin.json. In chrome browser. The file Logon_ezelogin.json file is available in the path inside webapps\hub#app#classic#security.war See the below deployed structure Thanks Mohan [cid:image001.png@01D7678C.6CEA3650] -----Original Message----- From: Mark Thomas <ma...@apache.org> Sent: 22 June 2021 16:27 To: users@tomcat.apache.org Subject: Re: Request for suggestion CAUTION: You received this email from external Domain. Check reliability of sender’s email ID. Do not click links, open attachments unless you recognize the sender and know the content is safe. – Ramco IMG On 22/06/2021 11:43, Mohan T wrote: > Hi, > > Thanks for the suggestion. > > We agree that .ear cannot be deployed on tomcat . > > Our requirement is as under > > 1. We have deployed a binary as below in webapps > hub#app#classic#security.war OK. > 2. The same is explored and deployed as hub#app#classic#security OK. With the default settings the WAR will be unpacked to a directory for performance reasons. > 3. Now we are trying to access the file inside > <tomcathome>/webapps/hub/app/classic/security/<Filename>. How, exactly, are you trying to access that file? > 4. The war file name is hub#app#classic#security.war Same as point 1. > 5. and context path is hub/app/classic/security. Strictly, the context path is: /hub/app/classic/security The leading "/" is important when you are working with paths in an application although I don't think it will be a factor here. Mark > > Kindly suggest how to proceed > > Thanks > > Mohan > -----Original Message----- > From: Mark Thomas <ma...@apache.org<mailto:ma...@apache.org>> > Sent: 22 June 2021 14:43 > To: users@tomcat.apache.org<mailto:users@tomcat.apache.org> > Subject: Re: Request for suggestion > > CAUTION: You received this email from external Domain. Check > reliability of sender’s email ID. Do not click links, open attachments > unless you recognize the sender and know the content is safe. – Ramco > IMG > > > > On 22/06/2021 07:40, Mohan T wrote: >> Hi, >> >> We are using tomcat 8.5.35 on RHEL. >> >> I have a .ear file that has a application.xml file in meta-inf folder. See >> below the contents of the application.xml file . >> >> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application PUBLIC >> "-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN" >> "https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjav >> a >> .sun.com%2Fj2ee%2Fdtds%2Fapplication_1_2.dtd&data=04%7C01%7CMohan. >> T%40ramco.com%7C6b7c563128f94d814b3e08d9355dfcb1%7C75f8ca7fffca4bf8a4 >> d >> 28a83d0d6e896%7C0%7C0%7C637599500050593410%7CUnknown%7CTWFpbGZsb3d8ey >> J >> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C100 >> 0 >> &sdata=9cRF11EhNgwg%2FxPmbM0ybMUttNlsBz3iBhpmld7rNGM%3D&reser >> v >> ed=0"> >> <application> >> <display-name>Application WEB</display-name> <description>RVWJ >> Application</description> >> <module><web><web-uri>adminWEB.war</web-uri><context-root>/hub/app/cl >> a ssic/admin</context-root></web></module> >> <module><web><web-uri>auditWEB.war</web-uri><context-root>/hub/app/cl >> a ssic/audit</context-root></web></module> >> <module><web><web-uri>deploymentWEB.war</web-uri><context-root>/hub/a >> p p/classic/deployment</context-root></web></module> >> <module><web><web-uri>implementationWEB.war</web-uri><context-root>/h >> u b/app/classic/implementation</context-root></web></module> >> <module><web><web-uri>securityWEB.war</web-uri><context-root>/hub/app >> / classic/security</context-root></web></module> >> <module><web><web-uri>hubWEB.war</web-uri><context-root>/hub</context >> - >> root></web></module> >> <module><web><web-uri>daemonWEB.war</web-uri><context-root>/hub/app/c >> l assic/daemon</context-root></web></module> >> </application> >> >> In each .war file I have the contents of the component along with a web-inf >> folder and the web.xml file. See sample contents of the file of audit >> component. >> >> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE web-app PUBLIC >> "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" >> "https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjav >> a >> .sun.com%2Fdtd%2Fweb-app_2_3.dtd&data=04%7C01%7CMohan.T%40ramco.c >> o >> m%7C6b7c563128f94d814b3e08d9355dfcb1%7C75f8ca7fffca4bf8a4d28a83d0d6e8 >> 9 >> 6%7C0%7C0%7C637599500050593410%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj >> A >> wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata= >> I QDnroJTM2jmjKZECiOPyngjFYyEeWZs6FebcTGXgrs%3D&reserved=0"> >> <web-app >> id="WebApp_ID"><display-name>Audit</display-name><description>web.xml >> for Audit component</description></web-app> >> >> I am able to deploy individual .war files but the launch page is not >> getting set . >> >> My launch page is >> >> http:\\localhost:8080\hub >> >> Kindly guide on how to deploy (Considering the launching page >> mentioned above) > > You can't. Tomcat does not support EARs. > > Tomcat also ignores any <context-root>...</context-root> in a WAR file. > As per the Servlet spec, any such setting may be over-ridden by container > specific configuration and since Tomcat derives the context path from the > file name it always overrides any <context-root>...</context-root>. > > The process Tomcat uses to determine the context path is documented at: > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomca > t.apache.org%2Ftomcat-8.5-doc%2Fconfig%2Fcontext.html%23Naming&dat > a=04%7C01%7CMohan.T%40ramco.com%7C930cf7339b3f4020a09708d9356c7e0a%7C7 > 5f8ca7fffca4bf8a4d28a83d0d6e896%7C0%7C0%7C637599562395780217%7CUnknown > %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ > XVCI6Mn0%3D%7C2000&sdata=RgWUuZVpZ3iVEyiUs%2BWm7ciQccdL9IRdg73%2FF > nLBCu8%3D&reserved=0 > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: > users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org> > > DISCLAIMER: This communication contains information which is confidential and > the copyright of Ramco Systems Ltd, its subsidiaries or a third party > (“Ramco”). This email may also contain legally privileged information. > Confidentiality and legal privilege attached to this communication are not > waived or lost by reason of mistaken delivery to you.This email is intended > to be read or used by the addressee only. If you are not the intended > recipient, any use, distribution, disclosure or copying of this email is > strictly prohibited without the express written approval of Ramco. Please > delete and destroy all copies and email Ramco at > le...@ramco.com<mailto:le...@ramco.com> immediately. Any views expressed in > this communication are those of the individual sender, except where the > sender specifically states them to be the views of Ramco. Except as required > by law, Ramco does not represent, warrant and/or guarantee that the integrity > of this communication has been maintained nor that the communication is free > of errors, virus, interception or interference. If you do not wish to receive > such communications, please forward this communication to > market...@ramco.com<mailto:market...@ramco.com> and express your wish not to > receive such communications henceforth. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > users-unsubscr...@tomcat.apache.org<mailto:users-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: > users-h...@tomcat.apache.org<mailto:users-h...@tomcat.apache.org> > Т ХF V 7V'67& &R R â W6W'2 V 7V'67& &T F 6B 6 R &pФf "FF F 6 G2 R â W6W'2ֆV ________________________________ F 6B 6 R &pР DISCLAIMER: This communication contains information which is confidential and the copyright of Ramco Systems Ltd, its subsidiaries or a third party (“Ramco”). This email may also contain legally privileged information. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you.This email is intended to be read or used by the addressee only. If you are not the intended recipient, any use, distribution, disclosure or copying of this email is strictly prohibited without the express written approval of Ramco. Please delete and destroy all copies and email Ramco at le...@ramco.com immediately. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Ramco. Except as required by law, Ramco does not represent, warrant and/or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference. If you do not wish to receive such communications, please forward this communication to market...@ramco.com and express your wish not to receive such communications henceforth.
